-
Notifications
You must be signed in to change notification settings - Fork 19
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
added migrations for key fix #2226
Conversation
Codecov ReportAttention: Patch coverage is
🚨 Try these New Features:
|
let weights = T::DbWeight::get().reads_writes(reads, writes).add_proof_size(bytes); | ||
log::info!(target: LOG_TARGET, "migrate_msa_ids weights={:?}",weights); | ||
weights | ||
} |
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.
logic looks good
nit: reduce nesting but since its a one time migration
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.
Yeah I was on the fence about that but since I wanted to log all the failure cases the other alternative was to use a lot of continue
in the loop for failure cases which is also not that great.
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 think it's cleared up once you get down to the alternate cases, but a couple of comments would be nice. I wonder if you have found any empty itemized pages stored.
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 couldn't find any empty itemized pages but still had to handle it just in case.
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.
lgtm
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.
Read through the code, looks good to go given the migration tests.
let weights = T::DbWeight::get().reads_writes(reads, writes).add_proof_size(bytes); | ||
log::info!(target: LOG_TARGET, "migrate_msa_ids weights={:?}",weights); | ||
weights | ||
} |
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 think it's cleared up once you get down to the alternate cases, but a couple of comments would be nice. I wonder if you have found any empty itemized pages stored.
@@ -181,9 +181,10 @@ jobs: | |||
steps: | |||
- name: Check Out Repo | |||
uses: actions/checkout@v4 | |||
# using older version of cargo deny since the new one requires rustc version >= 1.81 |
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.
Do we want to upgrade our base image container to a newer version?
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.
We should do it but outside the scope of this PR.
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.
- Read through changes
- Executed
make try-runtime-upgrade-paseo-testnet
- Did not see observed host function errors, but did get errors scraping keys, probably network related
🚢 it!
Goal
The goal of this PR is
Closes #2227
Details
but the actual multi-block migration is using
on_initialize
hook and a new storage item calledMigrationPageIndex
that would store the progress.Verification
Checklist