Docs fixups following implement socket factory (#10534)#10568
Merged
bdraco merged 1 commit intoaio-libs:masterfrom Mar 30, 2025
Merged
Docs fixups following implement socket factory (#10534)#10568bdraco merged 1 commit intoaio-libs:masterfrom
bdraco merged 1 commit intoaio-libs:masterfrom
Conversation
CodSpeed Performance ReportMerging #10568 will not alter performanceComparing Summary
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #10568 +/- ##
=======================================
Coverage 98.71% 98.71%
=======================================
Files 125 125
Lines 37368 37368
Branches 2064 2064
=======================================
Hits 36886 36886
Misses 335 335
Partials 147 147
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
TimMenninger
force-pushed
the
tcp-socket-factory-style-fixups
branch
from
c41d7a4 to
b2cd192
Compare
psf-chronographer
bot
added
the
bot:chronographer:provided
TimMenninger
force-pushed
the
tcp-socket-factory-style-fixups
branch
from
b2cd192 to
000d120
Compare
TimMenninger
force-pushed
the
tcp-socket-factory-style-fixups
branch
from
000d120 to
7ba697b
Compare
TimMenninger
changed the title
bdraco
reviewed
Mar 21, 2025
TimMenninger
force-pushed
the
tcp-socket-factory-style-fixups
branch
from
7ba697b to
f378fbb
Compare
bdraco
approved these changes
Mar 26, 2025
Member
|
Thanks @TimMenninger |
Contributor
Backport to 3.12: 💚 backport PR created✅ Backport PR branch: Backported as #10637 🤖 @patchback |
Merged
5 tasks
bdraco
pushed a commit
that referenced
this pull request
Mar 30, 2025
…ocket factory (#10534) (#10637) **This is a backport of PR #10568 as merged into master (8ac4830).** Co-authored-by: Tim Menninger <[email protected]>
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
2 participants
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 do these changes do?
Docs
Are there changes in behavior for the user?
No
Is it a substantial burden for the maintainers to support this?
No
Related issue number
N/A
Checklist
CONTRIBUTORS.txtCHANGES/foldername it
<issue_or_pr_num>.<type>.rst(e.g.588.bugfix.rst)if you don't have an issue number, change it to the pull request
number after creating the PR
.bugfix: A bug fix for something the maintainers deemed animproper undesired behavior that got corrected to match
pre-agreed expectations.
.feature: A new behavior, public APIs. That sort of stuff..deprecation: A declaration of future API removals and breakingchanges in behavior.
.breaking: When something public is removed in a breaking way.Could be deprecated in an earlier release.
.doc: Notable updates to the documentation structure or buildprocess.
.packaging: Notes for downstreams about unobvious side effectsand tooling. Changes in the test invocation considerations and
runtime assumptions.
.contrib: Stuff that affects the contributor experience. e.g.Running tests, building the docs, setting up the development
environment.
.misc: Changes that are hard to assign to any of the abovecategories.
Make sure to use full sentences with correct case and punctuation,
for example:
Use the past tense or the present tense a non-imperative mood,
referring to what's changed compared to the last released version
of this project.