-
Notifications
You must be signed in to change notification settings - Fork 389
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: Don't emit events from failed transactions #2806
fix: Don't emit events from failed transactions #2806
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2806 +/- ##
==========================================
+ Coverage 60.44% 60.78% +0.34%
==========================================
Files 563 563
Lines 75157 75729 +572
==========================================
+ Hits 45426 46032 +606
+ Misses 26341 26298 -43
- Partials 3390 3399 +9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
except for my comment where I'm not sure. LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to go if concerns are addressed.
I noticed that we emit events from the VM even when a transaction fails. This is very difficult to write tests for because we don't display events when a transaction fails, but I was able to verify the following behavior BEFORE this fix:
r/sys/validators
will be processed and the state updated as normal, even if the transaction that emitted them failsCorrect me if I'm wrong, but I don't think we want to persist or take any other actions on events sourced from failing transactions.
I'm open to suggestions on how to write tests for this, but the fix should be self-explanatory.
Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description