Workaround to avoid false-positive version warning #6656
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.
See the code comment. I'd consider the issue closed then until we get another report about this (but I'd hope that this won't happen again).
I ran into the original issue while testing #6652 (luckily I had a breakpoint in that saga from another debugging session). I could verify that the version mismatch was off by one and directly after continuing from the breakpoint in the warning-saga, the
updateVersionAction
was dispatched which led to my theory about the race condition.URL of deployed dev instance (used for testing):
Steps to test:
sleep
s at the right spots would probably work, but then one would only verify that the described race condition is fixed (maybe others exist which we didn't see yet?)Issues:
(Please delete unneeded items, merge only when none are left open)