-
Notifications
You must be signed in to change notification settings - Fork 34
feat(core, types): add CheckpointData to bcs iota.yaml description file #6912
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: core-node/upstream-changes/mainnet-1.34.2-1.35.4
Are you sure you want to change the base?
feat(core, types): add CheckpointData to bcs iota.yaml description file #6912
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 4 Skipped Deployments
|
@@ -56,6 +67,13 @@ fn get_registry() -> Result<Registry> { | |||
// tracer.trace_value(&mut samples, ...)?; | |||
// with all the base types contained in messages, especially the ones with | |||
// custom serializers; or involving generics (see [serde_reflection documentation](https://novifinancial.github.io/serde-reflection/serde_reflection/index.html)). | |||
|
|||
let m = ModuleId::new(AccountAddress::ZERO, Identifier::new("foo").unwrap()); |
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.
These lines were originally introduced by 6d8ceed which we didn't port yet. Do you plan to port that commit @iotaledger/vm-language ?
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 was just writing a note about that line:
Note for the reviewers: To be able to apply the upstream changes, I had to add line 71 and the next line myself. Those lines are still in latest upstream.
Description of change
Upstream range: [v1.34.2, v1.35.4)
Port MystenLabs/sui@68497e3
Add CheckpointData to bcs iota.yaml description file
Links to any relevant issues
Part of #3990
Type of change
Choose a type of change, and delete any options that are not relevant.
How the change has been tested