8000 fix(mempool): converting to uint64 before additions to avoid overflows (backport #2498) by mergify[bot] · Pull Request #2526 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix(mempool): converting to uint64 before additions to avoid overflows (backport #2498) #2526

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

Merged
merged 4 commits into from
Mar 11, 2024

Conversation

mergify[bot]
Copy link
Contributor
@mergify mergify bot commented Mar 6, 2024

This is an automatic backport of pull request #2498 done by Mergify.


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> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

#2498)

Closes #2445
<!--

Please add a reference to the issue that this PR addresses and indicate
which
files are most critical to review. If it fully addresses a particular
issue,
please include "Closes #XXX" (where "XXX" is the issue number).

If this PR is non-trivial/large/complex, please ensure that you have
either
created an issue that the team's had a chance to respond to, or had some
discussion with the team prior to submitting substantial pull requests.
The team
can be reached via GitHub Discussions or the Cosmos Network Discord
server in
the #cometbft channel. GitHub Discussions is preferred over Discord as
it
allows us to keep track of conversations topically.
https://github.com/cometbft/cometbft/discussions

If the work in this PR is not aligned with the team's current
priorities, please
be advised that it may take some time before it is merged - especially
if it has
not yet been discussed with the team.

See the project board for the team's current priorities:
https://github.com/orgs/cometbft/projects/1

-->

---

#### PR checklist

- [ ] Tests written/updated
- [ ] Changelog entry added in `.changelog` (we use
[unclog](https://github.com/informalsystems/unclog) to manage our
changelog)
- [ ] Updated relevant documentation (`docs/` or `spec/`) and code
comments
- [ ] Title follows the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec

(cherry picked from commit 551fc9b)
@mergify mergify bot requested review from a team as code owners March 6, 2024 08:07
andynog
andynog previously requested changes Mar 6, 2024
Copy link
Contributor
@andynog andynog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please validate comment for overflow issues

@adizere
Copy link
Member
adizere commented Mar 8, 2024

@odeke-em any thoughts?

@odeke-em
Copy link
Contributor
odeke-em commented Mar 8, 2024

In the issue that I filed, I listed why just uint64 is sufficient: but sure, making a safeAdd would be even better.

Copy link
Contributor
@sergio-mena sergio-mena left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Folks, if we agree on a different (better) solution, then let's tackle it in a different PR.
Don't forget this is a backport PR, so, unless something will definitely break if we merge it, the way to go is to go ahead and merge this backport (since the original PR, #2498, was approved and merged), so that, later on, it is easier to interpret what we are doing now.

@andynog
Copy link
Contributor
andynog commented Mar 11, 2024

let's merge this one and then fix on another PR

@melekes melekes dismissed andynog’s stale review March 11, 2024 13:38

let's merge this one and then fix on another PR

@melekes melekes merged commit ffc4a41 into v1.x Mar 11, 2024
@melekes melekes deleted the mergify/bp/v1.x/pr-2498 branch March 11, 2024 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

7 participants
0