-
Notifications
You must be signed in to change notification settings - Fork 4
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
api: Add runtime and Consensus transaction failure details #347
api: Add runtime and Consensus transaction failure details #347
Conversation
966dd33
to
35f4518
Compare
👍🏻 |
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.
Thank you! Looks good in general, I just have some suggestions for a more ergonomic API.
BTW, thank you for showing the output. This:
"is_total_count_clipped": false,
"total_count": 0,
made me realize we report total_count incorrectly for single txs, a bug from a previous PR. I piggy-backed a small fix commit onto your PR since it's vaguely related :), LMK and I can fork it into a separate PR if you'd prefer. Otherwise, please pull the commit to your local machine. Thanks!
8cb02ac
to
57c02d4
Compare
New
|
79b3e16
to
df27850
Compare
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.
Thanks! The API LGTM now, we're pretty close.
0a3c449
to
18ac305
Compare
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.
Thank you!
18ac305
to
a41f7dc
Compare
a41f7dc
to
6eaebd1
Compare
What
Add runtime failure details including
code
,module
, andmessage
to API response for runtime transactions.Add failure details including
code
,module
, andmessage
to API response for Consensus transactions.Changes
Runtime
For
v1/emerald/transactions/af4c53ebbc11570a4b4fc086ea52cea48e50d6a52a0b2e81446bc54ae727baae
, we see:For a transaction with error such as
v1/emerald/transactions/9f80d9ae209a1f487bf7bc4b548aab11ab5fb1e3d6dab80d30ab7a9d68259356
, we see:Consensus
For
v1/consensus/transactions/1224426e4126f79c6486fa5b74f096c07471bfd51e6b25242c131eb5fa7ecc8f
, we see:For
v1/consensus/transactions/e7b22c0153c78f66b810f78ab68fbcb5d7a2d70bb5ec617c704817cf57d32903
, we see:TODO
error
substructure