Repository navigation
fix: prevent concurrent validations from sharing converters - #254
Merged
Merged
Conversation
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.
Concurrent validations can overwrite the shared validator's
@converter, causing restrictions to be parsed in another attribute's time zone.This reproduction forces another thread's UTC validation to run between the local value conversion and restriction check:
The local value is 22:00 in Melbourne and should violate the 12:00 restriction. Before the fix, the UTC converter incorrectly accepts it.
Keep the converter local to
validate_eachand pass it tovalidate_restrictionsso each validation uses its own converter.