Repository navigation
Fix thread-safety of several recipes - #1284
Merged
Merged
Conversation
… static instances across threads
… suppressions and stop test workers on interrupt
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.
What's changed?
AssertionsArgumentOrdernow creates itsUsesMethodprecondition visitors inside eachgetVisitor()call. Before, it kept them in astaticfield that every thread shared.Also the same change in
AddMissingNestedandLifecycleNonPrivate, but only as a precaution. In practiceUsesTypeis thread-safe, but not guaranteed to be.What's your motivation?
OpenRewriteRecipeBestPracticesfails on random test files in nightly Moderne runs, with 1–12 files a night across several repos.UsesMethodkeeps a cursor, and when files run in parallel one thread resets that cursor while another is still using it: