-
Notifications
You must be signed in to change notification settings - Fork 0
refactor: encapsulate prep and bump logic #107
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: prestwich/some-cleaning-submit
Are you sure you want to change the base?
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
56cb4d0
to
628ae83
Compare
491b9cd
to
0d88be1
Compare
628ae83
to
b5082b8
Compare
0d88be1
to
72d2c26
Compare
48a1e82
to
4f0445e
Compare
4f0445e
to
ecc8355
Compare
src/utils.rs
Outdated
|
||
let blob_basefee = prev_header | ||
.next_block_blob_fee(BlobParams::prague()) | ||
.expect("signet deployed after 4844 active"); |
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.
So, this expect
was panicking at runtime. I updated it to an unwrap_or
and it defaults to the Prague value, but I'm not sure why it was panicking.
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.
Tested and working in dev-net with the commits that patch the expect
issue. Approving to unblock.
Encapsulate logic for the following processes:
So that they are out of the main retrying loop
Closes ENG-1084