Repository navigation
Fix tune leaks - #1448
Merged
Merged
Fix tune leaks#1448
Conversation
kurtmckee
requested review from
MaxTueckeGlobus,
aaschaer,
ada-globus,
derek-globus,
m1yag1 and
sirosen
as code owners
November 7, 2026 00:33
This file contains hidden or 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.
Fixed
RequestsTransport.tune()andRetryConfig.tune()now restore the settingseven if an exception is raised.
Previously, an exception inside a tuned context
(like
with client.transport.tune(verify_ssl=False):)would leave the modified settings configured for subsequent requests.