-
Notifications
You must be signed in to change notification settings - Fork 696
Create TransactionEventPayload struct and add vm_error to it #6025
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
base: develop
Are you sure you want to change the base?
Create TransactionEventPayload struct and add vm_error to it #6025
Conversation
Signed-off-by: Jacinta Ferrant <[email protected]>
72f575f
to
1e55e15
Compare
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
… into chore/add-vm-error-to-transaction-event-payload
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6025 +/- ##
===========================================
- Coverage 84.10% 84.00% -0.10%
===========================================
Files 528 528
Lines 385765 386373 +608
Branches 323 323
===========================================
+ Hits 324442 324577 +135
- Misses 61315 61788 +473
Partials 8 8
... and 50 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
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.
Looks good, just two small requests.
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
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.
👍
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.
This looks good to me, but we should have some tests that make tighter assertions about the outputted JSON -- we want this to be compatible with the previous version, so we should add some explicit equality checks on the outputted JSON with fixtures generated from the prior version.
…rds compatibility satisfied for TransactionEventPayload Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
… into chore/add-vm-error-to-transaction-event-payload
Added a proper deserializer for the custom block stack ops. Not sure that is exactly what you want. The equality check on the outputted JSON will not match. In my update, we now output the vm_error whereas before we did not. So the results will not match. They match on everything else and now that I have added the deserializer, it shows that it can serialize and deserialize into the same result whether using the legacy output or the current output. Note though that the serialization of some of those blockstack ops are lossy (For example PoxAddresses are serialized in a way that is lossy) |
Signed-off-by: Jacinta Ferrant <[email protected]>
… into chore/add-vm-error-to-transaction-event-payload
… into chore/add-vm-error-to-transaction-event-payload
Closes #6021