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.
Apply obstore as storage backend #3033
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
base: master
Are you sure you want to change the base?
Apply obstore as storage backend #3033
Changes from all commits
58ba73c
79ea46d
caaa657
7ba66e2
0ef7c05
17bde4a
353f000
7f0782a
04bdf20
0189419
deb9f3d
0ca6dbc
42cc75f
a1c99ec
9c7e8db
6fba41b
99f9ede
f317ff7
749a7fe
31d8880
9645dc7
5ac0766
8a0f262
4009f80
89cdc64
222df10
e40fedf
4dcb8a3
eb27d76
aad1b5e
d79c61d
2a67bac
3244d82
83f4db5
6346fc3
dfbf854
54c57ed
4beb285
568aa90
c90a2ff
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider handling
GenericError
separately fromOSError
since they may require different error handling approaches. The current implementation treats them the same way which could mask important error details.Code suggestion
Code Review Run #ab65d8
Is this a valid issue, or was it incorrectly flagged by the Agent?