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

chore: log panic recovery in runTx #17556

Merged
merged 1 commit into from
Aug 28, 2023

Conversation

calbera
Copy link
Contributor

@calbera calbera commented Aug 27, 2023

Description

Allows for easier debugging when panics occur during tx execution. Willing to change the log message if needed.

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
  • added ! to 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
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • run make lint and make test
  • 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 ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

@calbera calbera requested a review from a team as a code owner August 27, 2023 22:32
@calbera calbera changed the title log panic recovery chore: log panic recovery in runTx Aug 27, 2023
Comment on lines 807 to 813
if r := recover(); r != nil {
recoveryMW := newOutOfGasRecoveryMiddleware(gasWanted, ctx, app.runTxRecoveryMiddleware)
err, result = processRecovery(r, recoveryMW), nil
ctx.Logger().Error("panic recovered in runTx", "err", err)
}

gInfo = sdk.GasInfo{GasWanted: gasWanted, GasUsed: ctx.GasMeter().GasConsumed()}
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:792)
(*github.com/cosmos/cosmos-sdk/baseapp.BaseApp).deliverTx (baseapp/baseapp.go:722)
(*github.com/cosmos/cosmos-sdk/baseapp.BaseApp).FinalizeBlock (baseapp/baseapp.go:658)

@tac0turtle tac0turtle added the backport/v0.50.x PR scheduled for inclusion in the v0.50's next stable release label Aug 28, 2023
@tac0turtle tac0turtle added this pull request to the merge queue Aug 28, 2023
Merged via the queue into cosmos:main with commit cc6511e Aug 28, 2023
48 of 51 checks passed
@tac0turtle tac0turtle deleted the cal-log-panic-recovery branch August 28, 2023 07:24
mergify bot pushed a commit that referenced this pull request Aug 28, 2023
@itsdevbear
Copy link
Contributor

@tac0turtle are we down to back port into 0.50?

@tac0turtle
Copy link
Member

it was already

mmsqe pushed a commit to mmsqe/cosmos-sdk that referenced this pull request Sep 11, 2023
tac0turtle pushed a commit that referenced this pull request Sep 11, 2023
Co-authored-by: Cal Bera <calbera@berachain.com>
@faddat faddat mentioned this pull request Mar 20, 2024
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.50.x PR scheduled for inclusion in the v0.50's next stable release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants