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

"API rate limit exceeded" not considered an error #2133

Closed
IoriBranford opened this Issue Apr 5, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@IoriBranford

IoriBranford commented Apr 5, 2017

I deploy builds of my project with Travis CI. On this and any other issue where not all files are downloaded, git-lfs should exit with a non-zero error code so the build will stop. But on this issue, the build continues on.

From https://travis-ci.org/IoriBranford/demonizer/builds/219084582
Line 1610

$ git lfs pull
Git LFS: (9 of 109 files) 1.32 MB / 11.35 MB                                   
batch response: API rate limit exceeded for <IP>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)
@technoweenie

This comment has been minimized.

Show comment
Hide comment
@technoweenie

technoweenie Apr 7, 2017

Member

We'll have to investigate any rate limit changes on the server. It might be worse since you're making a public repository request from a shared server (travis). One workaround is to set the lfs.<url>.basic git config value inside the local repository:

$ git config lfs.https://github.com/OWNER/REPO.git/info/lfs.access basic
Member

technoweenie commented Apr 7, 2017

We'll have to investigate any rate limit changes on the server. It might be worse since you're making a public repository request from a shared server (travis). One workaround is to set the lfs.<url>.basic git config value inside the local repository:

$ git config lfs.https://github.com/OWNER/REPO.git/info/lfs.access basic
@technoweenie

This comment has been minimized.

Show comment
Hide comment
@technoweenie

technoweenie Apr 7, 2017

Member

Bah, I left out one important detail. If you set lfs.<url>.access = basic, you'll need a login too. You can create a github personal access token with no scopes. This will get you a higher rate limit, without providing access to any private resources.

Member

technoweenie commented Apr 7, 2017

Bah, I left out one important detail. If you set lfs.<url>.access = basic, you'll need a login too. You can create a github personal access token with no scopes. This will get you a higher rate limit, without providing access to any private resources.

@IoriBranford

This comment has been minimized.

Show comment
Hide comment
@IoriBranford

IoriBranford Apr 9, 2017

Yes, I now have Travis add my user name and token to the remote URL, so I no longer exceed the rate limit.

IoriBranford commented Apr 9, 2017

Yes, I now have Travis add my user name and token to the remote URL, so I no longer exceed the rate limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment