You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
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.
The text was updated successfully, but these errors were encountered: