-
Notifications
You must be signed in to change notification settings - Fork 221
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(acceptance): upgrade pp's governor #10817
Conversation
for await (const vatName of Object.keys(vats)) { | ||
actual[vatName] = await getVatDetails(vatName); | ||
} | ||
t.like(actual, vats); |
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.
Is it safe to assume that, at the moment that this test is executed, the incarnation of provisionPool and provisionPool-governor is always 0?
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, it might be worth setting the incarnation values in vats
from test.before
, and asserting that they have increased by one.
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.
resolved in 5d68e48
Deploying agoric-sdk with Cloudflare Pages
|
9c4067a
to
5d68e48
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.
The changes introduced on this PR looks good to me.
Particularly, the use of runCommitteeElectionParamChange
to reduce duplicated code.
refs: #10411 fix: forgot to include `null upgrade` fix into the previous commit
5d68e48
to
8c6668f
Compare
closes: #10411
Description
According to #10411 we need to showcase we can upgrade contractGovernor for a governed contract. This PR chooses
provisionPool
as it's example governed contract because;Security Considerations
No security considerations.
Scaling Considerations
As long as CI passes, scaling shouldn't be a problem.
Documentation Considerations
None.
Testing Considerations
CI with integration tests should pass.
Upgrade Considerations
This PR concerns upgrading provisionPool's governor itself.