Better libuv error message for ENOENT ~ #22647
Merged
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
|
I think |
ararslan
added
domain:error handling
vtjnash
reviewed
Oct 27, 2023
vtjnash
added
status:merge me
vtjnash
reviewed
Jan 31, 2024
inkydragon
removed
the
status:merge me
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.
This came up a few times, so I thought it'd be nice to provide a helpful error message here.
I'd like to add some tests for this, but
@test_throwscan't seem to test the error message. Should I usetry/catchand manually test thesprint(showerror, e), or is there a better way of doing so?