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

Sync with Github error (Request failed with status code: 504) #1107

Open
joshmoore opened this issue Dec 18, 2024 · 1 comment
Open

Sync with Github error (Request failed with status code: 504) #1107

joshmoore opened this issue Dec 18, 2024 · 1 comment

Comments

@joshmoore
Copy link

This is a re-opening of #957. Please see the discussion there.

image

Issue is (additionally) related to the number of organizations and repositories a user is a member of.

The only workaround currently is to disconnect repositories and reconnect them, which for users with many repositories is very sub-optimal.

Related to Zenodo Support email [Ticket#332699]

@joshmoore
Copy link
Author

On the Zenodo Support email thread:

We are aware of an issue with the Github integration for users that have a large amount of repositories, such as in your case. Unfortunately, we haven't fixed this yet and we still need to investigate the issue further to solve it. What happens is that we iterate over the list of repositories that we fetch from the user's Github account, which causes the request from the client to eventually timeout and return an HTTP 504 Gateway Timeout.
Sometimes the sync process manages to complete, even if the request timed out, but it is unclear to us how to force this. For instance, I tried to sync your repositories and couldn't make it work.

In the future, we might have a workaround for this, but we can't commit to a date/timeframe since our team is fully committed to working on other features.

We are sorry for the inconvenience this is causing you.

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

1 participant