Provide more information when a filewatcher failure is hit. #13715
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
alice-i-cecile
approved these changes
Jun 6, 2024
alice-i-cecile
added
D-Trivial
|
The panic may be related to what people are running into here: #10575 |
IceSentry
approved these changes
Jun 6, 2024
|
Also #7008 |
alice-i-cecile
added
S-Ready-For-Final-Review
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.
A naked unwrap led to an opaque error that can be hit when using the embedded filewatcher.
I've changed this an unwrap_or_else panic! with the error message providing more details about the failed operation.
A better solution would be to print an error! and not panic...
This was tested with the asset_processing example.