Reduce conflict errors on number generation #2258
Merged
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.
Description of the issue/feature this PR addresses
This PR reduces conflict errors that might occur if multiple threads are requesting new numbers at the same time.
Current behavior before PR
storage was fetched before the lock was acquired
Desired behavior after PR is merged
storage is always fetched from the annotation storage
--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.