You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since recently the script cannot update an existing draft anymore, instead it triggers a "404". We should figure out what is going on and fix the script.
As a work-around one can drop any drafts on Zenodo before minting a new RC or release.
The text was updated successfully, but these errors were encountered:
Traceback (most recent call last):
File "/home/runner/work/LiberTEM/LiberTEM/scripts/zenodo_upload", line 399, in main
r = update_deposition(deposition_id=deposition_id, data=make_data())
File "/home/runner/work/LiberTEM/LiberTEM/scripts/zenodo_upload", line 150, in update_deposition
raise ZenodoException(prettystring(r))
ZenodoException: Status code: 404
{'message': 'Not found.', 'status': 404}
Possible next debugging steps: the deposition_id used in the update_deposition call comes from get_latest_draft of get_geposition(deposition_id=parent). More concretely, it comes from the latest_draft link.
In the case of the successful update (newly created deposition), latest_draft is something like https://zenodo.org/api/deposit/depositions/11204954 - it would be good to find out how this looks like in the case of updating an existing draft.
Also a note:
defget_latest_draft(r):
data=r.json()
url=data['links']['latest_draft']
parts=url.split('/')
# The last bit of the URL is the IDreturnparts[-1]
This can be error-prone, maybe instead we should directly fetch the url and access the id of the returned object? Then we don't rely on the exact URL layout (imagine they add a URL parameter, for example, for whatever reason...)
Since recently the script cannot update an existing draft anymore, instead it triggers a "404". We should figure out what is going on and fix the script.
As a work-around one can drop any drafts on Zenodo before minting a new RC or release.
The text was updated successfully, but these errors were encountered: