GitHub migration exceeds API rate limit #6186

New Issue

GiteaMirror · 2025-11-02T06:47:39-06:00

GiteaMirror commented

2025-11-02 06:47:39 -06:00

Originally created by @davidak on GitHub (Oct 21, 2020).

Gitea version (or commit ref): 1.13.0+rc1
Git version: 2.20.1
Operating system: debian stable 10.6
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- i get migration failed too, but can't look into your logs ;)

Description

That should not happen. It should rather wait and inform the user, so the migration does not fail.

Related to https://github.com/go-gitea/gitea/issues/13241 and https://github.com/go-gitea/gitea/issues/13242

Originally created by @davidak on GitHub (Oct 21, 2020). - Gitea version (or commit ref): 1.13.0+rc1 - Git version: 2.20.1 - Operating system: debian stable 10.6 - Database (use `[x]`): - [ ] PostgreSQL - [X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] i get migration failed too, but can't look into your logs ;) ## Description That should not happen. It should rather wait and inform the user, so the migration does not fail. Related to https://github.com/go-gitea/gitea/issues/13241 and https://github.com/go-gitea/gitea/issues/13242

GiteaMirror added the topic/repo-migration label 2025-11-02 06:47:39 -06:00

GiteaMirror commented

2025-11-02 06:47:40 -06:00

@stale[bot] commented on GitHub (Dec 26, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 26, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:47:40 -06:00

@lunny commented on GitHub (Dec 26, 2020):

The problem will occur when you finished a migration and start another. On that situation, we haven't know if it's exceeds API rate limit.

@lunny commented on GitHub (Dec 26, 2020): The problem will occur when you finished a migration and start another. On that situation, we haven't know if it's exceeds API rate limit.

GiteaMirror commented

2025-11-02 06:47:40 -06:00

@zeripath commented on GitHub (Dec 27, 2020):

Maybe we should cache the github limit per user? We can even set the TTL to simply be the timeout.

@zeripath commented on GitHub (Dec 27, 2020): Maybe we should cache the github limit per user? We can even set the TTL to simply be the timeout.

GiteaMirror commented

2025-11-02 06:47:40 -06:00

@lunny commented on GitHub (Dec 27, 2020):

We can try. And also when start two or more migrations per Github User, I think it also maybe failed.

@lunny commented on GitHub (Dec 27, 2020): We can try. And also when start two or more migrations per Github User, I think it also maybe failed.

GiteaMirror commented

2025-11-02 06:47:41 -06:00

@lafriks commented on GitHub (Dec 28, 2020):

Doesn't github returns current rate limit in headers?

@lafriks commented on GitHub (Dec 28, 2020): Doesn't github returns current rate limit in headers?

GiteaMirror commented

2025-11-02 06:47:41 -06:00

@lunny commented on GitHub (Dec 28, 2020):

Doesn't github returns current rate limit in headers?

If only one thread to do that, the returned current rate limit is meaningful. But when two or more threads requests github at the same time, it will not be useful.

@lunny commented on GitHub (Dec 28, 2020): > Doesn't github returns current rate limit in headers? If only one thread to do that, the returned current rate limit is meaningful. But when two or more threads requests github at the same time, it will not be useful.

GiteaMirror commented

2025-11-02 06:47:41 -06:00

@6543 commented on GitHub (Feb 27, 2021):

look's like switching to GraphQL API will give us more requests per limit:
https://github.com/MichaelMure/git-bug/issues/315#issuecomment-786966651

@6543 commented on GitHub (Feb 27, 2021): look's like switching to GraphQL API will give us more requests per limit: https://github.com/MichaelMure/git-bug/issues/315#issuecomment-786966651

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6186