-
Notifications
You must be signed in to change notification settings - Fork 33
SC: Add SHiP support for sync call traces #1340
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
Conversation
libraries/state_history/abi.cpp
Outdated
| ] | ||
| }, | ||
| { | ||
| "name": "sync_call_trace", "fields": [ |
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.
I guess this is where my comment https://github.com/AntelopeIO/abieos/pull/42/files#r2036377296 should have originally gone. ship does a good job versioning everything, so I think we ought to have this as sync_call_trace_v0 to follow existing pattern.
I think it probably ought to be a variant as well, to match existing established pattern. Not sure how problematic that may be off hand.
| { "name": "sender_ordinal", "type": "varuint32" }, | ||
| { "name": "receiver", "type": "name" }, | ||
| { "name": "read_only", "type": "bool" }, | ||
| { "name": "data", "type": "bytes" }, |
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.
Is data something we should expand into a versioned type? It is not clear to me what is expected for this data. How would a user expand it?
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.
That would be similar to data in action. The user can parse it once ABI is ready.
Add sync call traces to SHiP.
Depending on Abieos AntelopeIO/abieos#42
Resolves #1334