Closed sgnn7 closed 2 years ago
When exiting the context or when manual close_buffer is invoked, we should restore the buffering state that existed before the context/manual buffer changes were applied.
Fixes: https://github.com/DataDog/datadogpy/issues/714
Buffering state is restored when buffer is manually closed or the managed context is left.
N/A
Unit tests cover the functionality but manual test can be done by following directions in the upstream issue
changelog/
backward-incompatible
do-not-merge/
kind/
severity/
/azp run
What does this PR do?
When exiting the context or when manual close_buffer is invoked, we should restore the buffering state that existed before the context/manual buffer changes were applied.
Fixes: https://github.com/DataDog/datadogpy/issues/714
Description of the Change
Buffering state is restored when buffer is manually closed or the managed context is left.
Alternate Designs
N/A
Possible Drawbacks
N/A
Verification Process
Unit tests cover the functionality but manual test can be done by following directions in the upstream issue
Additional Notes
Release Notes
Review checklist (to be filled by reviewers)
changelog/
label attached. If applicable it should have thebackward-incompatible
label attached.do-not-merge/
label attached.kind/
andseverity/
labels attached at least.