Clear executionID when recovering from orphaned entities #1128
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
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 test "DurableEntity_CleanEntityStorage" in the DF Extension has been really flakey as of late. It seems this is because, when we send a "orphaned lock fix" external event to a locked entity, we send that request with an executionID, and the executionID of entities is always changing. Therefore, if the entity has changed its executionID (example: after processing some operation request) the event will not unlock the entity and the test will fail.
This PR makes sure to clear the executionID of the raised event so that "orphaned lock fix" events are always honored, instead of discarded.