Provide more descriptive errors when DOI request fails #477
+3
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Raise the `requests` response to provide more informative errors when the status code is between 400 and 600.
Member
Author
|
@leouieda, apparently the tests failures are due to figshare blocking some requests, particularly the ones ran from the macos hosts. I'm ok if you want to skip these tests in order to make the release, or to just run them in a few hosts only. We can work this out later. |
Member
|
@santisoler thanks for implementing this! It might be something to do with them trying to block AI agents. I think it's fine to skip those since it's not a huge issue. |
|
This would be useful to get this PR merged to diagnose issues caused by recently introduced rate limits in zenodo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Raise the
requestsresponse to provide more informative errors when the status code is between 400 and 600.Relevant issues/PRs:
Part of #456