ragflow
ragflow copied to clipboard
Bump werkzeug from 3.0.3 to 3.0.6
Bumps werkzeug from 3.0.3 to 3.0.6.
Release notes
Sourced from werkzeug's releases.
3.0.6
This is the Werkzeug 3.0.6 security fix release, which fixes security issues but does not otherwise change behavior and should not result in breaking changes.
PyPI: https://pypi.org/project/Werkzeug/3.0.6/ Changes: https://werkzeug.palletsprojects.com/en/stable/changes/#version-3-0-6
- Fix how
max_form_memory_sizeis applied when parsing large non-file fields. GHSA-q34m-jh98-gwm2safe_joincatches certain paths on Windows that were not caught byntpath.isabson Python < 3.11. GHSA-f9vj-2wh5-fj8j3.0.5
This is the Werkzeug 3.0.5 fix release, which fixes bugs but does not otherwise change behavior and should not result in breaking changes.
PyPI: https://pypi.org/project/Werkzeug/3.0.5/ Changes: https://werkzeug.palletsprojects.com/en/stable/changes/#version-3-0-5 Milestone: https://github.com/pallets/werkzeug/milestone/37?closed=1
- The Watchdog reloader ignores file closed no write events. #2945
- Logging works with client addresses containing an IPv6 scope. #2952
- Ignore invalid authorization parameters. #2955
- Improve type annotation fore
SharedDataMiddleware. #2958- Compatibility with Python 3.13 when generating debugger pin and the current UID does not have an associated name. #2957
3.0.4
This is the Werkzeug 3.0.4 fix release, which fixes bugs but does not otherwise change behavior and should not result in breaking changes.
PyPI: https://pypi.org/project/Werkzeug/3.0.4/ Changes: https://werkzeug.palletsprojects.com/en/3.0.x/changes/#version-3-0-4 Milestone: https://github.com/pallets/werkzeug/milestone/36?closed=1
- Restore behavior where parsing
multipart/x-www-form-urlencodeddata with invalid UTF-8 bytes in the body results in no form data parsed rather than a 413 error. #2930- Improve
parse_options_headerperformance when parsing unterminated quoted string values. #2904- Debugger pin auth is synchronized across threads/processes when tracking failed entries. #2916
- Dev server handles unexpected
SSLEOFErrordue to issue in Python < 3.13. #2926- Debugger pin auth works when the URL already contains a query string. #2918
Changelog
Sourced from werkzeug's changelog.
Version 3.0.6
Released 2024-10-25
- Fix how
max_form_memory_sizeis applied when parsing large non-file fields. :ghsa:q34m-jh98-gwm2safe_joincatches certain paths on Windows that were not caught byntpath.isabson Python < 3.11. :ghsa:f9vj-2wh5-fj8jVersion 3.0.5
Released 2024-10-24
- The Watchdog reloader ignores file closed no write events. :issue:
2945- Logging works with client addresses containing an IPv6 scope :issue:
2952- Ignore invalid authorization parameters. :issue:
2955- Improve type annotation fore
SharedDataMiddleware. :issue:2958- Compatibility with Python 3.13 when generating debugger pin and the current UID does not have an associated name. :issue:
2957Version 3.0.4
Released 2024-08-21
- Restore behavior where parsing
multipart/x-www-form-urlencodeddata with invalid UTF-8 bytes in the body results in no form data parsed rather than a 413 error. :issue:2930- Improve
parse_options_headerperformance when parsing unterminated quoted string values. :issue:2904- Debugger pin auth is synchronized across threads/processes when tracking failed entries. :issue:
2916- Dev server handles unexpected
SSLEOFErrordue to issue in Python < 3.13. :issue:2926- Debugger pin auth works when the URL already contains a query string. :issue:
2918
Commits
5eaefc3release version 3.0.62767bcbMerge commit from fork87cc78acatch special absolute path on Windows Python < 3.1150cfeebMerge commit from fork8760275apply max_form_memory_size another level up in the parser8d6a12estart version 3.0.6a7b121arelease version 3.0.5 (#2961)9caf72arelease version 3.0.5e28a245catch OSError from getpass.getuser (#2960)e6b4ccecatch OSError from getpass.getuser- Additional commits viewable in compare view
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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
I have the same problem.
openSUSE Tumbleweed (KDE) 64-bit KDE Plasma Version 5.24.1 KDE Frameworks Version 5.90.0 Qt Version 5.15.2 Graphics X11
qBittorrent 4.4.1 (64-bit) Qt: 6.2.3 Libtorrent: 2.0.5.0 Boost: 1.78.0
Does Breeze even have a Qt6 theme?
@scorpion-sm can you check again if this is still the case? As on Debian 12 + KDE Plasma (Wayland) and the latest few releases of this program, I could not notice this problem. It used the Dark Breeze theme by default, without me doing anything to it.
This ticket has been closed.
Closure Reason: being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.
-
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.
-
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
-
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.
-
A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
-
Thank you for your contribution(s).
NOTE: This ticket will be locked in ~30 Days to avoid any necroing.