-
Notifications
You must be signed in to change notification settings - Fork 208
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
chore: Integrate on top of upgrade-15 #9436
Conversation
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.
How much of the upgrade-15 a3p-integration should remain in a:upgrade-next?
Everything that's not already tested in the A3P repo.
I'm thinking specifically about exit-reclaim.test.js and associated preparation.
That is covered in https://github.com/Agoric/agoric-3-proposals/tree/main/proposals/74%3Aupgrade-15
So please remove all tests in upgrade-next that aren't testing upgrade-next changes.
golang/cosmos/app/app.go
Outdated
// Upgrade ZCF only | ||
vm.CoreProposalStepForModules("@agoric/builders/scripts/vats/upgrade-zcf.js"), |
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.
for Upgrade 16, we want to replace upgrade ZCF only with upgrade Zoe. I presume that's separate from this.
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.
Since the failing test indicates that a ZCF upgrade is needed, this PR should at least maintain the ZCF upgrade core proposal. Since the plan for the next upgrade seem to upgrade both Zoe and ZCF, we could also do that instead in this PR.
I don't think it'll be necessary to add anything. |
I'm seeing failures in c:stake-bld/stakeBld.test.js broadcasting executeOffer with offer id 'request-stake': https://github.com/Agoric/agoric-sdk/actions/runs/9321875452/job/25661786100?pr=9436#step:9:2071
Is that meaningful to anyone here? |
What are the chances that the proposal for orchestration ran before the proposal that set a new ZCF version? If that happened, stakeBid could have been built against a support library that presumed that ZCF was updated, but then deployed against the ZCF that hadn't yet changed. |
Deploying agoric-sdk with Cloudflare Pages
|
634c565
to
147ee96
Compare
For posterity, the ZCF changes in upgrade-15 were intentionally minimal (and in particular excluded the addition of |
Fixes #9260
Description
As of Agoric/agoric-3-proposals#157 ,
a3p:latest
now includes results of upgrade-15. This removes the duplication from the UNRELEASED upgrade handler and a3p-integration.Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
n/a
Testing Considerations
How much of the upgrade-15 a3p-integration should remain in a:upgrade-next? I'm thinking specifically about exit-reclaim.test.js and associated preparation.
Upgrade Considerations
@Chris-Hibbert Does initial.test.js needs some extension for the vaultFactory and/or scaledPriceAuthority upgrades?