Bump flask from 1.1.1 to 2.2.5 in /extra/libcbor/doc/source - #5
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump flask from 1.1.1 to 2.2.5 in /extra/libcbor/doc/source#5dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [flask](https://github.com/pallets/flask) from 1.1.1 to 2.2.5. - [Release notes](https://github.com/pallets/flask/releases) - [Changelog](https://github.com/pallets/flask/blob/main/CHANGES.rst) - [Commits](pallets/flask@1.1.1...2.2.5) --- updated-dependencies: - dependency-name: flask dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Author
|
Superseded by #14. |
dependabot
Bot
deleted the
dependabot/pip/extra/libcbor/doc/source/flask-2.2.5
branch
May 6, 2024 15:15
ben-thul
pushed a commit
that referenced
this pull request
Aug 19, 2026
https://perconadev.atlassian.net/browse/PS-11242 percona.clone_consistent_snapshot crashed in a debug build with: [InnoDB] Assertion failure: trx0sys.cc:821: prev_trx == nullptr || prev_trx->id > trx->id #5 trx_sys_validate_trx_list trx0sys.cc:821 #6 trx_erase_lists trx0trx.cc:1838 #8 trx_commit_in_memory trx0trx.cc:2009 ... #21 Clone_persist_gtid::write_to_table clone0repl.cc:475 #24 clone_gtid_thread clone0repl.cc:723 trx_sys->rw_trx_list is required to be ordered by descending trx->id, and trx_sys_validate_trx_list() (UNIV_DEBUG only) enforces it on every erase. The consistent snapshot clone-view feature preallocates a transaction id for a donor read-only transaction (ReadView::clone() in read0read.cc). When that donor is later promoted to read-write via trx_set_rw_mode() -> trx_assign_id_for_rw(), it reuses the preallocated id, which - as the existing comment notes - "might not be received in ascending order" and can therefore be smaller than ids handed out to other transactions in the meantime. trx_assign_id_for_rw() already accounts for this when maintaining the sorted rw_trx_ids vector (the std::upper_bound insert), but trx_add_to_rw_trx_list() always did UT_LIST_ADD_FIRST, which assumes the new id is the greatest. Prepending an out-of-order preallocated id breaks the descending-id ordering of rw_trx_list. The corruption goes unnoticed at insertion time because trx_set_rw_mode() (unlike trx_start_low()) has no post-insert validation, and is only caught later when an unrelated transaction - here the clone GTID persister thread - commits and runs the validation during trx_erase_lists(). Fix trx_add_to_rw_trx_list() to insert a transaction carrying a preallocated_id at the position that preserves descending-id order, mirroring the rw_trx_ids handling. The common case (a freshly allocated id, which is always the greatest) keeps the O(1) prepend, so there is no hot-path regression.
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
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.
Bumps flask from 1.1.1 to 2.2.5.
Release notes
Sourced from flask's releases.
... (truncated)
Changelog
Sourced from flask's changelog.
... (truncated)
Commits
47af817release version 2.2.5afd63b1Merge pull request #5109 from pallets/backport-vary-cookie8646edcsetVary: Cookieheader consistently for sessiona6367daMerge pull request #5108 from pallets/werkzeug-compat3fbfbadwerkzeug 2.3.3 compatibility726d3f4start version 2.2.5ddc7accMerge pull request #5081 from pallets/release-2.2.474e0329release version 2.2.42d46068update dev env64bc458update dev dependenciesDependabot 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 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.