-
Notifications
You must be signed in to change notification settings - Fork 34
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
Comments
On the Zenodo Support email thread:
|
I'm also consistently getting this error. It is a 504 timeout after 30 seconds. I only have one organization, but it's a large one: https://github.com/JaneliaSciComp This effectively means that we can no longer use Zenodo for new repositories, which is really a shame. To anyone from Zenodo reading this: this type of error is usually easy to mitigate by increasing the read timeout of your reverse proxy. For example, with Nginx the relevant configuration option is |
+1 for this; I'm a member of a number of large orgs and this would really help! |
I am also experiencing this error and I'm in ~16 different orgs. |
I am also experiencing this error... |
Having the 504 issue today. Tried clicking sync several times within an hour without success. Does anyone know the server "napping" to awake time (assuming this is a temporary problem)? |
Aha - for me logging out and in again (in Zenodo) resulted in a successful sync. |
I get the same problem when trying to publish a W3C CG effort: w3c-cg/awesome-semantic-shapes#37 .
|
Thanks everyone for the continuing reports!! Also a big thumbs up to listing your number of orgs and repositories to provide data points for the maintainers. |
Ack!! I clicked on the wrong comment button. 🤦🏽 Can maintainer please re-open? Apologies for the noise. |
This is a re-opening of #957. Please see the discussion there.
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]
The text was updated successfully, but these errors were encountered: