fix: avoid checking for the reaper out of its mutex #1692
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.
What does this PR do?
This PR removes redudant checks for getting the test session ID, simply delegating it to the sessionID global value, not reading it from the reaper (which already uses the very same value).
Why is it important?
Having a nil-check for the
reaperInstance
to get the test sessionID introduced a race condition, as it's only set to not nil under a code block that is protected by a Mutex. Therefore, the check caused problems instead of benefits. I added that check intentionally, thinking that always reading from the reaper could be a good idea. But it was not.Related issues
How to test this PR
This should demonstrate the bug (before this fix) and the fix:
Also running all reaper tests: