capture: fix disabled()/global_and_fixture_disabled() enabling capturing when it was disabled #7651
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
CaptureManager.global_and_fixture_disabled()
context manager (andCaptureFixture.disabled()
which calls it) didsuspend(); ...; resume()
but if the capturing was already suspended, theresume()
would resume it when it shouldn't.This caused caused some messages to be swallowed when
--log-cli
is used because it usesglobal_and_fixture_disabled
when capturing is not necessarily resumed.