-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: skip same-sender non-sequential sequence and then add others txs new solution (backport #19177) #19249
Merged
facundomedica
merged 3 commits into
release/v0.50.x
from
mergify/bp/release/v0.50.x/pr-19177
Jan 26, 2024
Merged
fix: skip same-sender non-sequential sequence and then add others txs new solution (backport #19177) #19249
facundomedica
merged 3 commits into
release/v0.50.x
from
mergify/bp/release/v0.50.x/pr-19177
Jan 26, 2024
Conversation
This file contains 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
… new solution (#19177) Co-authored-by: SuperLee <9109321+superlee_8@user.noreply.gitee.com> Co-authored-by: Facundo Medica <14063057+facundomedica@users.noreply.github.com> Co-authored-by: Aleksandr Bezobchuk <alexanderbez@users.noreply.github.com> (cherry picked from commit fe32bcc) # Conflicts: # CHANGELOG.md # baseapp/abci_utils_test.go
alexanderbez
approved these changes
Jan 25, 2024
@@ -42,6 +42,8 @@ Ref: https://keepachangelog.com/en/1.0.0/ | |||
|
|||
* (abci): [#19200](https://github.com/cosmos/cosmos-sdk/pull/19200) Ensure that sdk side ve math matches cometbft | |||
* [#19106](https://github.com/cosmos/cosmos-sdk/pull/19106) Allow empty public keys when setting signatures. Public keys aren't needed for every transaction. | |||
* (baseapp) [#19198](https://github.com/cosmos/cosmos-sdk/pull/19198) Remove usage of pointers in logs in all OE goroutines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this cl was in v0.50.3 by mistake
Comment on lines
+281
to
+287
for sender, seq := range txSignersSeqs { | ||
if txsLen != selectedTxsNums { | ||
selectedTxsSignersSeqs[sender] = seq | ||
} else if _, ok := selectedTxsSignersSeqs[sender]; !ok { | ||
selectedTxsSignersSeqs[sender] = seq - 1 | ||
} | ||
} |
Check warning
Code scanning / CodeQL
Iteration over map Warning
Iteration over map may be a possible source of non-determinism
facundomedica
approved these changes
Jan 26, 2024
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.
This is an automatic backport of pull request #19177 done by Mergify.
Cherry-pick of fe32bcc has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com