Repository navigation
Tell which path an I/O error failed on - #177
Merged
Merged
Conversation
- Give the path of the database file in the I/O errors of PageReader opening it, keeping FileError::Io and the error kind - Give the path in the I/O errors of jetdb export --attachments when it cannot write a folder or a file - Test the errors for a missing database file and an attachments directory that cannot be created Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
CoverageFor 4c123b9. |
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
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.
Summary
jetdb: I/O error: /nonexistent.mdb: No such file or directory (os error 2). PageReader adds it; theFileError::Iovariant and the error kind stay, so the public API is unchanged.jetdb export --attachmentsname that path:jetdb: I/O error: /dev/null/x/2: Not a directory (os error 20).🤖 Generated with Claude Code