Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PR #9368/02d8dba9 backport][3.10] Avoid using the proxy headers in the ConnectionKey if no proxy is in use #9378

Conversation

patchback[bot]
Copy link
Contributor

@patchback patchback bot commented Oct 1, 2024

This is a backport of PR #9368 as merged into master (02d8dba).

What do these changes do?

Default proxy headers may be passed to the connector to be included in the event a proxy is being used. If no proxy is being used, we should not include the proxy auth and proxy headers in the ConnectionKey since it means we could end up creating a connection when one was already available for reuse

Are there changes in behavior for the user?

no

Is it a substantial burden for the maintainers to support this?

no

@bdraco bdraco enabled auto-merge (squash) October 1, 2024 16:57
CHANGES/9368.bugfix.rst Outdated Show resolved Hide resolved
Copy link

codecov bot commented Oct 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.78%. Comparing base (0a74b54) to head (7e828dd).
Report is 2 commits behind head on 3.10.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             3.10    #9378   +/-   ##
=======================================
  Coverage   97.78%   97.78%           
=======================================
  Files         108      108           
  Lines       34888    34905   +17     
  Branches     4174     4176    +2     
=======================================
+ Hits        34116    34133   +17     
  Misses        574      574           
  Partials      198      198           
Flag Coverage Δ
CI-GHA 97.67% <100.00%> (+<0.01%) ⬆️
OS-Linux 97.35% <100.00%> (+<0.01%) ⬆️
OS-Windows 94.98% <100.00%> (+0.01%) ⬆️
OS-macOS 97.05% <100.00%> (+<0.01%) ⬆️
Py-3.10.11 96.91% <100.00%> (+<0.01%) ⬆️
Py-3.10.15 96.85% <100.00%> (+<0.01%) ⬆️
Py-3.11.10 96.93% <100.00%> (+<0.01%) ⬆️
Py-3.11.9 97.01% <100.00%> (-0.01%) ⬇️
Py-3.12.6 97.39% <100.00%> (+<0.01%) ⬆️
Py-3.13.0-rc.2 97.37% <100.00%> (+<0.01%) ⬆️
Py-3.8.10 94.36% <100.00%> (+0.01%) ⬆️
Py-3.8.18 96.65% <100.00%> (+<0.01%) ⬆️
Py-3.9.13 96.83% <100.00%> (+<0.01%) ⬆️
Py-3.9.20 96.77% <100.00%> (+<0.01%) ⬆️
Py-pypy7.3.16 96.37% <100.00%> (+<0.01%) ⬆️
VM-macos 97.05% <100.00%> (+<0.01%) ⬆️
VM-ubuntu 97.35% <100.00%> (+<0.01%) ⬆️
VM-windows 94.98% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

CHANGES/9368.bugfix.rst Outdated Show resolved Hide resolved
@bdraco bdraco merged commit 6198a56 into 3.10 Oct 1, 2024
38 of 39 checks passed
@bdraco bdraco deleted the patchback/backports/3.10/02d8dba9a320e4d15d8d7539ca5fb6d93083bd26/pr-9368 branch October 1, 2024 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant