bug fix in actor locking -- overly forgiving reentrancy bypass #309
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
The outermost call must clear activeFlow before scheduling the next invocation on an actor instance to prevent a race condition where a non-reentrant invocation using the same flow can conflict with the next queued invocation that is being released.
dgrove-oss
commented
Apr 19, 2022
dgrove-oss
commented
Apr 19, 2022
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.
The outermost call must clear activeFlow before scheduling the next
invocation on an actor instance to prevent a race condition where
a non-reentrant invocation using the same flow can conflict (execute concurrently) with
the next queued invocation that is being released.