-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 Connector: Syncs are consuming the whole API quota #5669
Comments
Okay @marcosmarxm, I'll give it a try and get back to you! |
i think i ran into the same thing. where the UI required the organization (even though i was looking to sync one repo) and by adding the organization, it then sync the entire org (all repos etc.) |
@danieldiamond I actually intend to sync the whole organization, this is a feature I've been asking for, but after version 0.1.4 it is failing. |
@yevhenii-ldv any ideas? |
Hello @jgtvares
I suspect that these repositories may be causing the error, which may very well be empty or somehow incorrect. |
@yevhenii-ldv You're right! Those repos are really empty and syncing them alone is raising the same error. |
@jgtvares In version 0.1.6, we added processing of HTTP errors, and therefore it may happen that in version 0.1.4 error with empty repositories is still skipped, but in 0.1.6 it is no longer. But I'm working on fixing this situation, the fix is almost ready. |
@yevhenii-ldv Thanks a lot!!! |
@jgtvares We just merged this fix into master and released a new version of the connector. Upgrade your connector to version 0.1.9 and get started. To upgrade your connector version, go to the admin panel in the left hand side of the UI, find this connector in the list, and input the latest connector version. Please let us know if you have any further questions. |
Enviroment
Current Behavior
I'm trying to sync all the repos in our organization (about 500 repos) using only
commits
andpull_requests
streams. But the problem is that syncs are failing in all three attempts and I realized that Airbyte is using all the API quota (which for us is 5000).Expected Behavior
Syncs shouldn't use the whole quota. Maybe you could add a field for us to input a
quota use percentage by sync
.A curious thing is that this wasn't happening in version 0.1.4. I rolledback to that version and syncs are okay!
Logs
If applicable, please upload the logs from the failing operation.
For sync jobs, you can download the full logs from the UI by going to the sync attempt page and
clicking the download logs button at the top right of the logs display window.
First attempt LOG
Steps to Reproduce
commits
andpull_requests
streamsAre you willing to submit a PR?
No.
The text was updated successfully, but these errors were encountered: