-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
github sync nonetype error when listing collaborators #1404
Comments
@achantavy I see! I knew less when I did this a few weeks ago. It would be easy to add in the nonetype checking. Is it okay if I do it tomorrow (Fri Dec 13)? I should be able to do it fairly easily with the same backoff generator approach, I just am not really online today. |
@achantavy upd I did push a tix to a draft PR just now, in case this is urgent: #1405 But as noted there I did not yet have a chance to add testing or sanity check beyond running |
…ollaborators (#1409) ### Summary > Describe your changes. Allows the GitHub sync to continue if the user is unable to list repository collaborators. ### Checklist Provide proof that this works (this makes reviews move faster). Please perform one or more of the following: - [x] Update/add unit or integration tests. - [x] Include a screenshot showing what the graph looked like before and after your changes. - [ ] Include console log trace showing what happened before and after your changes. If you are changing a node or relationship: - [ ] Update the [schema](https://github.com/lyft/cartography/tree/master/docs/root/modules) and [readme](https://github.com/lyft/cartography/blob/master/docs/schema/README.md). If you are implementing a new intel module: - [ ] Use the NodeSchema [data model](https://cartography-cncf.github.io/cartography/dev/writing-intel-modules.html#defining-a-node).
Title:
GitHub sync crashes when listing collaborators with a Nonetype error;
Description:
Similar as #1334.
To Reproduce:
Run github sync. I guess this becomes more pronounced on a large enough graph or in conditions when your github quota is low or some other condition is flaky.
Logs:
Crash
Screenshots:
Please complete the following information::
0.96.0
cc: @danbrauer - any chance you have time to help here? maybe adding a retry + sleep of some sort, either with your decorator technique or the older technique. np if you're busy!
The text was updated successfully, but these errors were encountered: