-
Notifications
You must be signed in to change notification settings - Fork 1
Sui system cherry pick #77
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: next
Are you sure you want to change the base?
Conversation
|
@andreistefanescu .to_int() is still working with preferred local deps because we are basically in our sui repo |
andreistefanescu
left a comment
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.
let's merge only the rust changes in next, and sync with @msaaltink regarding merging the move changes back in his branch.
|
#82 rust part merge separetly |
8d4dc8a to
0fb0e07
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.
I don't think sender_spec and epoch_spec are needed any more with the latest prover
|
|
||
| // === specs utils === | ||
|
|
||
| #[spec_only] |
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.
Should be test_only
| #[spec_only] | ||
| use sui_system::staking_pool::activation_epoch; | ||
|
|
||
| #[spec_only] |
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.
should be test_only here, and at line 101
msaaltink
left a comment
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.
Mostly this looks fine. As noted a few spec_only should probably be test_only, and I think the "other_specs" are not needed with the latest prover versions.
Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.