-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Upgrade] Alpha TestNet v0.0.10 upgrade #894
Conversation
Merged in 78a7445, seems like there are no changes that would affect the release so gtg. |
Merged in ff76430 and began testing the upgrade locally. The upgrade failed initially. Here's a gist with a panic: https://gist.github.com/okdas/535bc3c0282483fef27454c70d889aa6 I believe the reason is we've changed the data type of the protobuf field here. Meaning the new version is unable to map the existing After I manually created a new We probably need to treat protobuf files as they used are production - meaning no type/field changes, any change that needs to be done should go through adding a new field, ensuring backwards-compatibility. |
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
Noted. We'll start doing this in Beta. We'll have one last cleanup opportunity prior to mainnet. cc @red-0ne |
I'm going to create a release using f0d0e7a as this is the commit that has been tested using this branch. Looking at new changes in main branch, there are more state changes required in the upgrade. As discussed in the meeting yesterday, we will add them in another upgrade shortly after. Let's practice upgrades! |
The release has been created: https://github.com/pokt-network/poktroll/releases/tag/v0.0.10 I did not use @Olshansk let's get this in main to preserve the upgrade code! :) |
"plan": { | ||
"name": "v0.0.10", | ||
"height": "20", | ||
"info": "NOT NEEDED FOR LOCAL TESTING" |
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.
#PUC why we have this file then
Thanks for the review @Olshansk. At this point, with many changes here, I want to delete the v0.0.10 version we currently have a release for, remove the merges from the main branch (so the code only contains the commits we wrote an upgrade for), and test the upgrade again. Will re-create release and apply an upgrade on the network after that. |
05aeeb2
to
10d45b7
Compare
I've verified all new params and grants locally - we're good to upgrade! |
The image is going to be pushed after the next commit. You can use If you also want to run E2E tests, please add |
@Olshansk the upgrade has been applied on Alpha TestNet. We don't really have to merge this, but I still would to have an example for future upgrades. |
// Should we use the same address/wallet for DAO or find a way to detect the network the upgrade is being applied to, | ||
// to pick different addresses depending on the name of the network? (e.g chain-id) | ||
|
||
const ( |
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.
Ty for the comments
Co-authored-by: Daniel Olshansky <[email protected]>
* todo_beta/upnext: [C&P] Populate NumEstimatedComputeUnits and ClaimedUpokt of Claim and Proof events (#927) [Tokenomics] feat: add `dao_reward_address` param to tokenomics module (#922) chore: review feedback improvements chore: review feedback improvements [Service] Return the default RelayMinerDifficuly for services that have none. (#926) [Upgrade] Alpha TestNet v0.0.10 upgrade (#894) Update reviewdog.yml
Summary
Prep for
v0.0.10
release and upgrade.Type of change
Select one or more from the following:
consensus-breaking
label if so. See [Infra] Automatically add theconsensus-breaking
label #791 for detailsTesting
Went through upgrade testing locally.
Sanity Checklist