Skip to content
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

feat: exceeding block gas meter don't fail #19318

Closed
wants to merge 2 commits into from

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Feb 1, 2024

Closes: #19317

Description

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features
    • Enhanced resilience against block gas limit exceedance; transactions no longer fail under such conditions, improving reliability.
  • Documentation
    • Updated to reflect new handling of block gas meter exceedance behavior.

@yihuang yihuang requested a review from a team as a code owner February 1, 2024 01:01
Copy link
Contributor

coderabbitai bot commented Feb 1, 2024

Warning

Rate Limit Exceeded

@yihuang has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 27 minutes and 27 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits Files that changed from the base of the PR and between 5ee1ccb and e7c5767.

Walkthrough

The update introduces a mechanism to gracefully handle situations where the execution of a transaction exceeds the block gas limit within the baseapp. By adding a deferred function to recover from panics specifically caused by gas limit breaches, and adjusting the control flow in the runTx method, the system now logs and ignores these panics, ensuring that transactions are processed more reliably without causing failures due to gas limit issues.

Changes

File Change Summary
baseapp/baseapp.go Introduced deferred function for panic recovery in runTx. Adjusted error handling for block gas limit exceedance.
CHANGELOG.md Documented the new behavior of handling block gas meter exceedance without causing transaction failure.

Assessment against linked issues

Objective Addressed Explanation
Address out-of-gas error overriding transaction execution result (#19317)
Ensure transaction result reflects actual situation for better handling by indexers and explorers (#19317)
Modify consumeBlockGas to recover out-of-gas panic internally (#19317) The changes introduce a new approach by handling the recovery in runTx rather than modifying consumeBlockGas directly.
Create TryConsumeGas method for non-panic out-of-gas handling (#19317) Instead of creating a new method, the solution implemented adjusts the control flow and error handling within existing methods.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

CHANGELOG.md Outdated Show resolved Hide resolved
Comment on lines 842 to +848
// fails. Hence, it's execution is deferred.
consumeBlockGas := func() {
if !blockGasConsumed {
defer func() {
// log and ignore, see: https://github.com/cosmos/cosmos-sdk/issues/19317
if err := recover(); err != nil {
ctx.Logger().Error("block gas limit exceeded", "err", err)
Copy link
Contributor

Choose a reason for hiding this comment

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

Change potentially affects state.

Call sequence:

(*github.com/cosmos/cosmos-sdk/baseapp.BaseApp).runTx (baseapp/baseapp.go:814)
(*github.com/cosmos/cosmos-sdk/baseapp.BaseApp).deliverTx (baseapp/baseapp.go:744)
(*github.com/cosmos/cosmos-sdk/baseapp.BaseApp).internalFinalizeBlock (baseapp/baseapp.go:713)
(*github.com/cosmos/cosmos-sdk/baseapp.BaseApp).FinalizeBlock (baseapp/baseapp.go:874)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 2

Configuration used: .coderabbit.yml

Commits Files that changed from the base of the PR and between f86f753 and 5ee1ccb.
Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • baseapp/baseapp.go (1 hunks)
Additional comments: 1
baseapp/baseapp.go (1)
  • 845-850: The implementation of the deferred function to recover from a panic caused by exceeding the block gas limit is correct. However, it's essential to ensure that this change does not inadvertently mask other types of panics that could occur in the runTx method. Consider adding additional logging or metrics to monitor the frequency of these recoveries to assess the impact on the system's overall stability and performance.

CHANGELOG.md Outdated
@@ -73,6 +73,7 @@ Every module contains its own CHANGELOG.md. Please refer to the module you are i
* (crypto/keys) [#18026](https://github.com/cosmos/cosmos-sdk/pull/18026) Made public key generation constant time on `secp256k1`
* (crypto | x/auth) [#14372](https://github.com/cosmos/cosmos-sdk/pull/18194) Key checks on signatures antehandle.
* (types) [#18963](https://github.com/cosmos/cosmos-sdk/pull/18963) Swap out amino json encoding of `ABCIMessageLogs` for std lib json encoding
* (baseapp) [#]() Exceeding block gas meter don't make transaction fail.
Copy link
Contributor

Choose a reason for hiding this comment

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

The changelog entry for the modification in baseapp behavior regarding the block gas meter is missing a PR link. Including the PR link provides valuable context and allows readers to easily access more detailed information about the changes. Consider adding the PR link for consistency with other entries and to improve the documentation's utility.


There's a grammatical error in the changelog entry. The correct form should maintain proper subject-verb agreement. Consider revising the sentence for clarity and correctness.

- Exceeding block gas meter don't make transaction fail.
+ Exceeding the block gas meter does not cause transactions to fail.

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
* (baseapp) [#]() Exceeding block gas meter don't make transaction fail.
* (baseapp) [#]() Exceeding the block gas meter does not cause transactions to fail.

Copy link
Contributor

@alexanderbez alexanderbez left a comment

Choose a reason for hiding this comment

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

if err := recover(); err != nil {
ctx.Logger().Error("block gas limit exceeded", "err", err)
}
}()
blockGasConsumed = true
ctx.BlockGasMeter().ConsumeGas(
Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, can you please explain again how this could panic, thus making recovery needed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It's related to unused gas refunding, if we include tx by user provided gas limit, they can fill block space with unused gas, the actually used gas is always lower than the block gas limit, we did some hack to include more txs, so we got exceeding block gas limit situation occasionally.
If we plan to remove block gas meter at all, maybe we can simply live with the situation.

@yihuang yihuang closed this Feb 3, 2024
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.

[Feature]: consume block gas meter don't panic
2 participants