Closed nuest closed 5 months ago
I had to add considerable timeouts to the post requests, maybe the new sandbox has some throttling issues? I also got a few 504 Gateway Timeout errors on the "publish" action, but the record is published just fine in the sandbox, see https://sandbox.zenodo.org/records/10001337
@nuest maybe you're aware, but Zenodo just did a full backend upgrade last week. It might be the case that the zenodo-client doesn't work at all anymore, I haven't had time to look and see to what extent the API changed
I was aware, but I rather attributed this to performance issues with the sandbox.
Let me check if I can see what changed for the publish
action!
Well https://developers.zenodo.org/ seems down, so I think we'll have to revisit this later.
It seems like the client hast do create a draft first, and that the action URL for publishing then also changes:
I somehow see the needed changes, but your are the more experienced Python developer and it's your library, so I'll wait for you how to handle this. It seems there is no edit
action anymore, but you go POST .../draft
. So, the internal function _action(...)
probably needs quite a few changes.
@cthoyt https://developers.zenodo.org/ is back up, so that's at least a chance to take a look at the changes. It's hard for me to commit a specific amount of time, but it would be really useful to get the lib working again, so let me know if you need help, e.g., with testing.
@cthoyt Hi! :wave: Did you give the API updates a look? Shall I rebase my changes, or can I do some testing?
@nuest thanks, I updated with the new API in 0468a69ba773b8ac8d93d504711df2eff26cb2d0 and updated your branch. I also moved some of the new docs out of the README and into the more detailed docs, to de-clutter the front page. It appears there's still some issues with you missing a zenodo API token in your github secrets. I will try and improve the error message to make this more obvious, but the short version is you need to have this
when you navigate to https://github.com/nuest/zenodo-client/settings/secrets/actions
Superseded by #36
This is the first part of #23