Skip to content

perf(state): Cache the block hash (backport #2924)#2931

Merged
melekes merged 1 commit intov0.38.xfrom
mergify/bp/v0.38.x/pr-2924
Apr 29, 2024
Merged

perf(state): Cache the block hash (backport #2924)#2931
melekes merged 1 commit intov0.38.xfrom
mergify/bp/v0.38.x/pr-2924

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Apr 29, 2024

Closes #2923

Caches the block hash to ensure we only compute it once in consensus execution.


PR checklist

  • Tests written/updated - not sure what test I should write, any suggestions?
  • Changelog entry added in .changelog (we use unclog to manage our changelog)
  • Updated relevant documentation (docs/ or spec/) and code comments
  • Title follows the Conventional Commits spec

This is an automatic backport of pull request #2924 done by [Mergify](https://mergify.com).

<!--

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

-->

Closes #2923

Caches the block hash to ensure we only compute it once in consensus
execution.

---

#### PR checklist

- [x] Tests written/updated - not sure what test I should write, any
suggestions?
- [x] 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
- [x] Title follows the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec

(cherry picked from commit 1b16d91)

# Conflicts:
@mergify mergify bot requested a review from a team as a code owner April 29, 2024 10:15
@mergify mergify bot added the conflicts label Apr 29, 2024
@mergify
Copy link
Contributor Author

mergify bot commented Apr 29, 2024

Cherry-pick of 1b16d91 has failed:

On branch mergify/bp/v0.38.x/pr-2924
Your branch is up to date with 'origin/v0.38.x'.

You are currently cherry-picking commit 1b16d9192.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .changelog/unreleased/improvements/2924-consensus-cache-block-hash.md
	modified:   types/block.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@melekes melekes merged commit 203bf33 into v0.38.x Apr 29, 2024
@melekes melekes deleted the mergify/bp/v0.38.x/pr-2924 branch April 29, 2024 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants