-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[event_v2] migrate the rest files in aptos-framework #11688
Conversation
⏱️ 7h 11m total CI duration on this PR
🚨 2 jobs on the last run were significantly faster/slower than expected
|
cec4cd9
to
5a1f775
Compare
5a1f775
to
3329fa6
Compare
da0e98b
to
e03a9c4
Compare
549a928
to
22f159f
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11688 +/- ##
===========================================
- Coverage 69.2% 62.6% -6.7%
===========================================
Files 2296 821 -1475
Lines 438064 184173 -253891
===========================================
- Hits 303482 115391 -188091
+ Misses 134582 68782 -65800 ☔ View full report in Codecov by Sentry. |
22f159f
to
40f0989
Compare
6087009
to
e695fc1
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.
would be good to test this with an updated indexer processor and verify it is correct before we end up shipping this.
also might be worth adding the disabling of v1 in there as well for that reason.
let new_block_event_v2 = NewBlock { | ||
hash, | ||
epoch, | ||
round, | ||
height: block_metadata_ref.height, | ||
previous_block_votes_bitvec, | ||
proposer, | ||
failed_proposer_indices, | ||
time_microseconds: timestamp, | ||
}; | ||
emit_new_block_event(vm, &mut block_metadata_ref.new_block_events, new_block_event, new_block_event_v2); |
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.
if we're doing this, we might incur a performance impact on each block before we even migrate.
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.
one more event per block? should not be an issue regarding perf.
spec create_staking_contract( | ||
staker: &signer, | ||
operator: address, | ||
voter: address, | ||
amount: u64, | ||
commission_percentage: u64, | ||
contract_creation_seed: vector<u8>, | ||
staker: &signer, | ||
operator: address, | ||
voter: address, | ||
amount: u64, | ||
commission_percentage: u64, | ||
contract_creation_seed: vector<u8>, |
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.
something weird
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.
intellij move plugin does this automatically and I have no way to disable it...
I will rebase once #11224 lands |
@grao1991 do you need to change the new block event tracking after this PR? |
Yes. It's protected by the sharding flag which hasn't been enabled. You go first and I can try to make the change later. FYI, you need to double check if other things (e.g. consensus) that depending on the new block event works correctly after your change. |
3c0145c
to
24f567d
Compare
I trust you. Didn't carefully review. |
When are we removing the old events though? |
24f567d
to
f8d9432
Compare
Let's do it after 1-2 release. |
add feature flags use feature_flag to switch
f8d9432
to
356731a
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
Description
migrate other files
Test Plan