[Snyk] Security upgrade aiohttp from 3.10.11 to 3.13.4

[mandibles232]

Snyk has created this PR to fix 10 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• tools/python/requirements.txt

⚠️ Warning

openai 0.27.8 requires aiohttp, which is not installed.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Information Exposure

[mandibles232]

This upgrade for aiohttp introduces behavioral changes that require verification.

Key Changes:

• WebSocket Timeout: In version 3.11.0, the default receive timeout for ClientSession.ws_connect was changed from infinite (None) to 10.0 seconds. Applications relying on long-lived, idle WebSocket connections may experience unexpected timeouts. The timeout and receive_timeout parameters for this method are also deprecated.
• Decompression Limit: To address security concerns (decompression bombs), version 3.13.3 introduced a default maximum output size of 32MiB for each decompression call. If your application processes larger compressed responses, this may cause issues.

Recommendation:

• Verify that any WebSocket connections using ws_connect can handle the new 10-second default timeout or explicitly set a different timeout value.
• Confirm that your application does not need to decompress single responses larger than 32MiB. If it does, you may need to review the new decompression handling logic.

Source: aiohttp Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.