-
Notifications
You must be signed in to change notification settings - Fork 242
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
Zenodo not reflecting latest GitHub Release #2243
Comments
I made another new release today: https://github.com/peterjc/thapbi-pict/releases/tag/v0.10.3 I could see that it was "processing" here, and quickly "published": https://zenodo.org/account/settings/github/repository/peterjc/thapbi-pict/ So things seem to be working now, but no sign of the missing v0.10.2 release from earlier this month. |
Observing the same problem, just created https://github.com/poliastro/poliastro/releases/tag/v0.16.0 and it's not reflected on https://zenodo.org/account/settings/github/repository/poliastro/poliastro. Is there a way to "refresh" the list of releases? |
By the way, the webhook was sent and Zenodo responded with HTTP 202 ACCEPTED. I redelivered the webhook, Zenodo replied 202 again, and still no luck. |
How did you manually trigger the webhook? (I suspect this is a load issue, and retrying later will work) |
You need to go to https://github.com/peterjc/thapbi-pict/settings/hooks, locate the zenodo webhook, go to "recent deliveries", check the response (optional), and click "redeliver" |
Redelivered again, no luck. |
Dear @peterjc could I kindly ask that you reach out to us via our support channel at info@zenodo.org so we can look into this issue further? |
Done - although the automatic reply does say:
|
My missing release was fixed by Zenodo support, who explained that according to their logs Zenodo never received the notification from GitHub when I made that release. i.e. This appears to have been a GitHub outage. Zenodo support's suggested workaround was to tweak the "missing" GitHub release (e.g. a trivial edit to the release text), which ought to re-notify Zenodo. I will close this for now, but @astrojuanlu let me know if you'd rather we left it open to address your missing poliastro https://doi.org/10.5281/zenodo.593610 release? |
Hi @peterjc, I gave up on the previous release. Will make a new one soon. |
Haha. I'd actually given up on my v0.10.2 release appearing on Zenodo, happily all the point releases since have been fine. It would be trivial to try the workaround they suggested though? |
Making minor edits to re-trigger the webhook didn't work 🤷🏽♂️ and looks like the Zenodo support team is quite resource-constrained, so I prefer to wait until the next release. |
The new release got published correctly 👍🏽 |
Browser & OS (see also https://www.whatismybrowser.com/): Chrome & macOS
Describe the bug
New release on made GitHub, but 5 days later and it has not appeared on linked Zenodo repository.
Steps to Reproduce
Expected behavior
Zenodo should import any new release from GitHub within a day or two, or if there is an error inform the repository owner. e.g. Via the GitHub settings page: https://zenodo.org/account/settings/github/repository/peterjc/thapbi-pict
Screenshots (if applicable)
Additional context
This had been working as I expected prior to the few months interval with no new releases. The
.zenodo.json
configuration file has not been touched during this time:https://github.com/peterjc/thapbi-pict/commits/master/.zenodo.json
My GitHub account is still linked according to https://zenodo.org/account/settings/linkedaccounts/
The text was updated successfully, but these errors were encountered: