Handle validation errors when fetching zarr checksums #1007
Conversation
This file contains 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
Currently, if the `.checksum` file is malformed, any API request that
requires the checksum (like `GET /zarr/` or `GET /zarr/{zarr_id}/`)
throws an error 500 because of the validation error. That should be
handled gracefully and `None` returned instead.
dchiquito
added
patch
jjnesbitt
approved these changes
Apr 6, 2022
|
🚀 PR was released in |
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.
Currently, if the
.checksumfile is malformed, any API request thatrequires the checksum (like
GET /zarr/orGET /zarr/{zarr_id}/)throws an error 500 because of the validation error. That should be
handled gracefully and
Nonereturned instead.Should fix #1004