8000 perf(internal/state): avoid double-saving FinalizeBlockResponse (backport #2017) by mergify[bot] · Pull Request #2401 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

perf(internal/state): avoid double-saving FinalizeBlockResponse (backport #2017) #2401

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

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor
@mergify mergify bot commented Feb 21, 2024

This is an automatic backport of pull request #2017 done by Mergify.
Cherry-pick of f2c7466 has failed:

On branch mergify/bp/v1.x/pr-2017
Your branch is up to date with 'origin/v1.x'.

You are currently cherry-picking commit f2c746638.
  (fix conflicts and 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/2017-state-avoid-double-saving-finalize-block-response.md
	modified:   internal/state/store_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   internal/state/store.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


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

for performance reasons.
Closes #1976

---

#### PR checklist

- [ ] Tests written/updated
- [x] Changelog entry added in `.changelog` (we use
[unclog](https://github.com/informalsystems/unclog) to manage our
changelog)
- [x] Updated relevant documentation (`docs/` or `spec/`) and code
comments

(cherry picked from commit f2c7466)

# Conflicts:
#	internal/state/store.go
@mergify mergify bot requested review from a team as code owners February 21, 2024 18:00
@mergify mergify bot added the conflicts label Feb 21, 2024
@melekes
Copy link
Contributor
melekes commented Feb 22, 2024

@mergify rebase

Copy link
Contributor Author
mergify bot commented Feb 22, 2024

rebase

☑️ Nothing to do

  • -conflict [📌 rebase requirement]
  • -closed [📌 rebase requirement]

@melekes
Copy link
Contributor
melekes commented Feb 22, 2024

@Mergifyio refresh

Copy link
Contributor Author
mergify bot commented Feb 22, 2024

refresh

✅ Pull request refreshed

@melekes
Copy link
Contributor
melekes commented Feb 22, 2024

@Mergifyio rebase

Copy link
Contributor Author
mergify bot commented Feb 22, 2024

rebase

☑️ Nothing to do

  • -conflict [📌 rebase requirement]
  • -closed [📌 rebase requirement]

@melekes
Copy link
Contributor
melekes commented Feb 22, 2024

@Mergifyio update

Copy link
Contributor Author
mergify bot commented Feb 22, 2024

update

☑️ Nothing to do

  • -conflict [📌 update requirement]
  • #commits-behind>0 [📌 update requirement]
  • -closed [📌 update requirement]

@melekes melekes closed this Feb 22, 2024
@melekes melekes deleted the mergify/bp/v1.x/pr-2017 branch February 22, 2024 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0