-
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) #957
Comments
Well, after several refreshing attempts the sync just worked. So I suppose the server was just having a nap. |
Running in to this now repeatedly for my account. I assume it's tied to a user's number of organizations. (I've run into this with other applications.) I'd suggest having a sync button per organization as well. |
Also running into this. My user is tied to multiple organizations, but I only need Zenodo to sync one of them. Short of having a per-organization "sync" button, another option would be to be able to revoke Zenodo authorization on a per-organization basis. I don't see any way to do that from the GitHub OAuth settings. |
Thanks for the confirmation, @wsnoble. No maintainers have commented here, so I've filed an issue with https://zenodo.org/support (per https://github.com/zenodo/zenodo/issues/new/choose) cross-linking this page. I'll send any updates I receive. |
I'm getting this a lot today (probably a dozen sync attempts over several hours). @joshmoore, is there a way that I can also follow the Zenodo support issue/ticket you filed? If not, I'll check back here. Note that I am also in four different GitHub orgs, but only the repos associated with my own GitHub username are Zenodo-enabled. I do see repos from one org (where I am the owner) in the Zenodo list, but my repo list was last synced two months ago. |
@zimolzak: I've not received any notification unfortunately. |
@zimolzak et al.
|
Update: I checked today, and now Zenodo reports that a successful sync of my GitHub repos happened 3 days ago. However, if I try to request sync again, I get the same error. (I only tried once today, though.) I got the repo I wanted, so that's good, I guess? But the problem seems to be persisting. 🤷 |
What worked for me was to go to "Linked accounts" in the left sidebar just above the "GitHub" menu we are currently in , then click "Disconnect" on the "GitHub" option, then click "Connect" again. Upon returning to the prior menu it says "updated now" (unless that coincidentally went through from a prior click of sync). Warning Just realized that you will have to click the "On" switch again for any repo you previously synced with Zenodo! I only had five to re-enable, so it wasn't a huge deal. So, not an ideal workaround... |
+1 happening to me when I added an new organisation |
This sounds very daunting. I will reply on the email and see if this issue can be re-opened. |
@joshmoore I agree that re-connecting is not an ideal solution. Any news regarding your email? |
same here, only this worked for me. |
@thawn: new news though I had pinged them about this thread and said:
|
I'm going to try creating a new issue and see if that will be seen: #1107 Please join me there. |
Having the 504 issue today. Tried clicking sync several times within an hour without success. Does anyone know the server "nap" time? |
Hi,
I'm trying to sync a github repo from an organization (of which I'm the onwer) with my Zenodo. This is something I have done before with other organization, but the problem is with a new one. I have enabled third-party access to the Zenodo application, however my new organization's repositories do not show up in the list.
I think the problem is that my list of repos was updated 10 months ago, and the organization and repo I want to add are new.
However, when I click "Sync now" after few seconds I'm getting the error Request failed with status code: 504
My internet connection is stable and of 17 Mbps. Is there a gateway timeout problem from your side? Or what can I do? I'm having this problem since yesterday and it is starting to become urgent.
This issue is related to zenodo/zenodo#1814 but since I think the problem is with the sync, I opened a new issue instead of reporting it in that thread.
Thanks!
The text was updated successfully, but these errors were encountered: