Avatar for the aio-libs user
aio-libs
aiohttp
BlogDocsChangelog

Performance History

Latest Results

Fix BodyPartReader.read_chunk crash on Content-Length: 0 `BodyPartReader.read_chunk` picked its read strategy by testing `self._length` for truthiness, which routed a part with `Content-Length: 0` through `_read_chunk_from_stream` instead of `_read_chunk_from_length`. The stream path then asserted that the requested chunk size is at least `_boundary_len`, and any caller asking for a small chunk hit `AssertionError` -- even though `Content-Length: 0` already says there is nothing to read. A `Content-Length: 0` body part is legal outside `multipart/form-data` (used by `multipart/mixed`, `multipart/related`, and similar), where the empty-part special case that nulls out `_length` does not apply. Every other use of `self._length` in `multipart.py` already checks `is not None`; `read_chunk` is the odd one out. Switching the test to `is not None` keeps the empty length on the length path, which returns `b""` immediately and marks the part at EOF -- matching the behaviour of any other zero-length Content-Length caller.
qianbkk:fix-issue-13758-content-length-zero
4 hours ago
Removed old issue template (#13791) <!-- Thank you for your contribution! --> ## What do these changes do? Remove old issue_template.md file, as the project currently uses issue_template directory <!-- Please give a short brief about these changes. --> ## Are there changes in behavior for the user? No, this issue template was not accesible when creating an issue <!-- Outline any notable behaviour for the end users. --> ## Is it a substantial burden for the maintainers to support this? No, this should just remove an unused file <!-- Stop right there! Pause. Just for a minute... Can you think of anything obvious that would complicate the ongoing development of this project? Try to consider if you'd be able to maintain it throughout the next 5 years. Does it seem viable? Tell us your thoughts! We'd very much love to hear what the consequences of merging this patch might be... This will help us assess if your change is something we'd want to entertain early in the review process. Thank you in advance! --> ## Related issue number <!-- Will this resolve any open issues? --> <!-- Remember to prefix with 'Fixes' if it closes an issue (e.g. 'Fixes #123'). --> ## Checklist - [ ] I think the code is well written N/A - [ ] Unit tests for the changes exist N/A - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is &lt;Name&gt; &lt;Surname&gt;. * Please keep alphabetical order, the file is sorted by names. - [ ] Add a new news fragment into the `CHANGES/` folder * name 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 an improper 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 breaking changes 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 build process. * `.packaging`: Notes for downstreams about unobvious side effects and 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 above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` I think this doesn't require a changes file, ut happy to add it 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.
master
8 hours ago
Bump platformdirs from 4.11.10 to 4.11.11 (#13789) Bumps [platformdirs](https://github.com/tox-dev/platformdirs) from 4.11.10 to 4.11.11. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/platformdirs/releases">platformdirs's releases</a>.</em></p> <blockquote> <h2>4.11.11</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>fix: reject app arguments that leave the base directory by <a href="https://github.com/Pitchfork-and-Torch"><code>@​Pitchfork-and-Torch</code></a> in <a href="https://redirect.github.com/tox-dev/platformdirs/pull/552">tox-dev/platformdirs#552</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/Pitchfork-and-Torch"><code>@​Pitchfork-and-Torch</code></a> made their first contribution in <a href="https://redirect.github.com/tox-dev/platformdirs/pull/552">tox-dev/platformdirs#552</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tox-dev/platformdirs/compare/4.11.10...4.11.11">https://github.com/tox-dev/platformdirs/compare/4.11.10...4.11.11</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/platformdirs/blob/main/docs/changelog.rst">platformdirs's changelog</a>.</em></p> <blockquote> <p>########### Changelog ###########</p> <p>.. towncrier-draft-entries:: Unreleased</p> <p>.. towncrier release notes start</p> <hr /> <p>4.11.12 (2026-09-22)</p> <hr /> <ul> <li>Ignore relative paths in the XDG user directory environment variables, so <code>XDG_DOCUMENTS_DIR=Documents</code> no longer makes :func:<code>~platformdirs.user_documents_dir</code> and the other media directories return a path relative to the working directory. They now fall back to the platform default like the XDG Base Directory variables, and like the same keys read from <code>user-dirs.dirs</code> - by :user:<code>darrenhuai</code>. :pr:<code>554</code></li> <li>Copy nested directories in the versioned data migration recipe. :pr:<code>553</code></li> <li>Exclude sphinx-llm 1.1.0 from documentation dependencies because its Markdown builder emits unknown-node warnings. :pr:<code>556</code></li> </ul> <hr /> <p>4.11.11 (2026-09-19)</p> <hr /> <ul> <li>Reject <code>appname</code>, <code>appauthor</code> and <code>version</code> values that leave the platform base directory (a <code>..</code> segment, a leading separator, a drive or a UNC share) with <code>ValueError</code>, so <code>ensure_exists</code> cannot create directories outside it - by :user:<code>Pitchfork-and-Torch</code>. :pr:<code>552</code></li> </ul> <hr /> <p>4.11.10 (2026-09-18)</p> <hr /> <ul> <li>With <code>ensure_exists</code>, the <code>site_*_dir</code> and <code>site_*_path</code> properties and the <code>iter_*_dirs</code> iterators only create the site directories they return or yield, instead of every entry in the site list - by :user:<code>darrenhuai</code>. :pr:<code>550</code></li> </ul> <hr /> <p>4.11.9 (2026-09-16)</p> <hr /> <ul> <li>Accept <code>multipath</code> in :func:<code>~platformdirs.site_cache_dir</code> and :func:<code>~platformdirs.site_cache_path</code>. Without it, the function API could not return the Homebrew cache prefix that :attr:<code>~platformdirs.macos.MacOS.site_cache_dir</code> adds under <code>multipath</code> - by :user:<code>darrenhuai</code>. :pr:<code>544</code></li> <li>Parse Unix <code>user-dirs.dirs</code> line by line like <code>xdg-user-dir</code>. The INI parser raised on a repeated key or a line without <code>=</code>, and returned trailing comments and backslash escapes inside :func:<code>~platformdirs.user_documents_dir</code> and the other media directories. The last valid assignment now wins, and platformdirs unescapes the quoted value and ignores text after the closing quote - by :user:<code>darrenhuai</code>. :pr:<code>545</code></li> <li>Read <code>PUBLIC</code> before the home directory in :func:<code>~platformdirs.user_publicshare_dir</code> on Windows, so it no longer raises <code>RuntimeError</code> when <code>PUBLIC</code> is set and the home directory cannot be determined - by :user:<code>emme1t</code>. :pr:<code>546</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tox-dev/platformdirs/commit/321e35ad6fe7a72a2975d5eeed7f7b5dfed08a11"><code>321e35a</code></a> Release 4.11.11</li> <li><a href="https://github.com/tox-dev/platformdirs/commit/902c268c99193b0513be03ef7a7f897dd8e83912"><code>902c268</code></a> fix: reject app arguments that leave the base directory (<a href="https://redirect.github.com/tox-dev/platformdirs/issues/552">#552</a>)</li> <li>See full diff in <a href="https://github.com/tox-dev/platformdirs/compare/4.11.10...4.11.11">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=platformdirs&package-manager=pip&previous-version=4.11.10&new-version=4.11.11)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
master
19 hours ago
Removed old issue template
Polandia94:remove-old-issue_template
1 day ago
Add Eliahu Frusin to CONTRIBUTORS.txt
eliahu-frusin:fix-5304-naive-datetime-last-modified
1 day ago

Latest Branches

CodSpeed Performance Gauge
0%
Fix BodyPartReader.read_chunk crash on Content-Length: 0#13795
4 hours ago
c2e7a2b
qianbkk:fix-issue-13758-content-length-zero
CodSpeed Performance Gauge
0%
1 day ago
56383f7
nipunhsud:fix-zero-content-length-read-chunk
CodSpeed Performance Gauge
+9%
15 hours ago
cae4216
dependabot/pip/3.15/virtualenv-21.9.0
© 2026 CodSpeed Technology
Home Terms Privacy Docs