Do not fill in a stack trace for ResourceChangedException - #2885
Open
vogella wants to merge 1 commit into
Open
Conversation
The exception is only a control-flow signal, and its single catch site reads just the target resource.
Contributor
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
1 participant
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.
IsSynchronizedVisitorthrowsResourceChangedExceptionpurely as a control-flow signal for the first out-of-sync node, and its only catch site inFileSystemResourceManagerreads just the target resource. The class comment already states the stack trace is meaningless, so overridingfillInStackTraceavoids capturing one.RefreshLocalTestandUnifiedTreeTestpass unchanged.