Skip to content
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

Avoiding Github rate limiting #70

Closed
danepowell opened this issue May 24, 2016 · 2 comments
Closed

Avoiding Github rate limiting #70

danepowell opened this issue May 24, 2016 · 2 comments

Comments

@danepowell
Copy link
Contributor

Despite all of Github's promises that anonymous API calls are no longer rate limited, we still see Travis tests fail from time to time because of throttling. Not sure who's at fault, but I do know that simply adding a personal oauth token following this guide prevents the issue.

Ideally Bolt would prompt for an oauth token on initial setup, and then automatically create .travis.composer.config.json and modify .travis.yml to accept it.

@geerlingguy
Copy link
Contributor

Note that if you use 2FA, it's slightly more annoying, as you have to make a normal request that fails, which triggers a text message, then a 2nd request that has:

curl -u 'username' -d '{"note":"Travis Composer 2"}' --header "X-GitHub-OTP: TOKENHERE" https://api.github.com/authorizations

(Inserting your token where it says TOKENHERE).

@danepowell
Copy link
Contributor Author

A github rep just replied to me and said that the remaining throttling was accidentally left in place on an upstream balancer or something. It should be fixed now, which means this is no longer necessary. We can re-open if people are still getting throttled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants