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

fix: emit ante events even for the failed txs #10631

Merged

Conversation

yun-yeo
Copy link
Contributor

@yun-yeo yun-yeo commented Nov 29, 2021

Description

Closes: #10618

This is example implementation to emit ante events(especially of tx fee deduction) for the failed txs.

The master branch has huge difference in ante handler side (changed to middleware), so I just made changes only for v0.44.x branch.


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
  • 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)

@yun-yeo yun-yeo force-pushed the feature/emit-failed-tx-ante-events branch from c7125ad to 4e04904 Compare November 29, 2021 08:23
Copy link
Contributor

@amaury1093 amaury1093 left a comment

Choose a reason for hiding this comment

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

Thanks @YunSuk-Yeo, this PR makes sense to me.

The behavior is correct on master, right?

types/errors/abci.go Outdated Show resolved Hide resolved
baseapp/abci.go Show resolved Hide resolved
types/errors/abci.go Outdated Show resolved Hide resolved
types/errors/abci.go Outdated Show resolved Hide resolved
@yun-yeo
Copy link
Contributor Author

yun-yeo commented Nov 29, 2021

Thanks @YunSuk-Yeo, this PR makes sense to me.

The behavior is correct on master, right?

I'm not sure, master still have this problem. but v0.44.x should have this update for rosetta support

Copy link
Member

@tac0turtle tac0turtle left a comment

Choose a reason for hiding this comment

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

lgtm

@amaury1093 amaury1093 added this to the 0.44.5 milestone Nov 30, 2021
@amaury1093 amaury1093 changed the title emit ante events even for the failed txs fix: emit ante events even for the failed txs Dec 1, 2021
@amaury1093 amaury1093 merged commit b3646ac into cosmos:release/v0.44.x Dec 1, 2021
@yihuang
Copy link
Collaborator

yihuang commented Feb 16, 2022

This change is consensus-breaking because of the tx result change right?

@amaury1093
Copy link
Contributor

I don't think emitting new events is considered as consensus-breaking

@tac0turtle
Copy link
Member

correct events are not included in hashes in the header

zakir-code pushed a commit to PundiAI/cosmos-sdk that referenced this pull request Apr 14, 2022
* emit ante events even for the failed txs

* apply comment

* add changelog
JeancarloBarrios pushed a commit to agoric-labs/cosmos-sdk that referenced this pull request Sep 28, 2024
* emit ante events even for the failed txs

* apply comment

* add changelog
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.

5 participants