-
Notifications
You must be signed in to change notification settings - Fork 239
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
github: improve error message instead of "Unknown error occured" (1) #799
Comments
Thanks for reporting the issue. We are looking into it. |
I'm experiencing the same thing with https://zenodo.org/account/settings/github/repository/poldracklab/fmriprep# Here's the corresponding release: https://github.com/poldracklab/fmriprep/releases/tag/0.6.0 |
I was experiencing the same error when using v1.0.0 as release tag. However, when I removed the v and just let the tag as 1.0.0, (this release), the error disappeared and the publishing went on without further issues. |
In our case the version did not include "v", but the error still happened. Maybe something was fixed on the backend between your two releases? |
I'm experiencing the same issue with https://github.com/ms609/Ternary/releases/tag/1.0.0. |
I'm experiencing the same issue with https://github.com/neuropsychology/psycho.R/releases/tag/0.1.0 What could I do? |
Me too with https://github.com/fact-project/fact-tools, please help |
Same problem with https://zenodo.org/account/settings/github/repository/duetosymmetry/qnm#1e717028-b4a4-4338-b632-b7d445ea753c-event , v0.2.5-beta. Error message:
Github payload:
|
I have the same issue with geopandas/geopandas (previous succeeded release: https://zenodo.org/record/2585849) It seems that github triggered multiple push events for the single release (where the first did not contain the assets, not sure if that is related to the problem), and the the first was received by zenodo, but the second and third were denied saying that zenodo already received that release. Is there a possibility to "delete" a github release on zenodo, so that it can be re-delivered by the github webhook? |
@jorisvandenbossche and @duetosymmetry, we just found out as well about these multiple event triggers, and we are preparing a patch to address the issue so that future release events get properly handled. For past failed cases (like yours) we will try to "recover" the releases and publish them as expected, though it might take some time (since we have to search for the proper release event on our side). |
releases of SageMath started to error our with "Unknown error occured" in 2018 or so: How can this be fixed?
|
Issue:
Created a release of ALPSCore, and it is marked as "failed" on https://zenodo.org/account/settings/github/repository/ALPSCore/ALPSCore.
Diagnostics:
Additional observations:
<h5>...</h5>
), e.g.,v0.5.4
; however, this release has the tag, the repository name, and the release title there:v0.5.5 ALPSCore/ALPSCore: Version 0.5.5
github-payload-fail.json.txt
The text was updated successfully, but these errors were encountered: