GeezerVison is showing github.com — [Snyk] Security upgrade aiohttp from 3.8.6 to 3.14.4 by caniszczyk · Pull Request #28 · OpenFunction/functions-framework-python
Conversation

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):
examples/openfunction_dapr_trigger/caller/requirements.txt
⚠️ Warning
dapr 1.10.0 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
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|

The upgrade from aiohttp 3.8.6 to a later 3.x version introduces several breaking changes and deprecations. The target version 3.14.4 appears to be incorrect, as the latest stable series is 3.9.x. Analysis is based on changes up to the 3.9 series.
Key Changes:
- Python Version Support: Support for Python 3.7 was dropped in version 3.9.0. This upgrade requires your environment to be running Python 3.8 or newer.
- API Behavioral Changes:
- In v3.9.0,
web.FileField and MultipartReader.next() now return None when exhausted, instead of raising StopAsyncIteration. This can break loops that are not adapted to this change.
- The
ClientResponseError.history attribute is now a tuple of ClientResponse objects, removing the previously included URL.
- A security fix in a later version made the internal
decode() method asynchronous to prevent decompression bomb attacks. A new synchronous decode_iter() method was added for non-blocking decompression.
Deprecations:
- The
loop parameter has been deprecated throughout the library in preparation for version 4.0.
- Registering synchronous web handlers is deprecated and will be removed in version 4.0.
Recommendation:
Verify that your environment uses Python 3.8+. Review any code that iterates over MultipartReader or uses ClientResponseError.history to ensure compatibility with the new behavior. It is critical to identify the correct target version and review the complete changelog for all changes between 3.8.6 and your final version.
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.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You have signed the CLA already but the status is still pending? Let us recheck it.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.