-
Notifications
You must be signed in to change notification settings - Fork 212
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
Wallet factory upgrade 2 branch #8593
Wallet factory upgrade 2 branch #8593
Conversation
@@ -1,27 +1,20 @@ | |||
# Defaults | |||
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals@sha256:ac10c09b5927d759d37b1525b5a0bc4aeb3034df8d0f0fbb15b51203555ffb1b | |||
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals:pr33 |
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.
Agoric/agoric-3-proposals#33 merged. I guess this isn't main
because that flow is failing?
Please leave a comment here about why it isn't main
as it should be. We should unbreak that.
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals:pr33 | |
// Once https://github.com/Agoric/agoric-3-proposals/pull/37 merges, s/pr33/main | |
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals:pr33 |
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.
Even if it was pushed to the main
tag, I do not feel confident using main
until Agoric/agoric-3-proposals#25 is resolved.
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 your concern is about this CI starting to fail once main
includes the upgrade being tested here.
So even after 25, you wouldn't want :main
, right? You'd want :upgrade12
or something like that.
Given that I propose a different comment.
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals:pr33 | |
# Don't use `:main` because once this upgrade is incorporated into it, this test would break | |
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals:pr33 |
|
||
# DEST (TEST) | ||
#this is agoric-upgrade-12 / multi-collateral, etc. | ||
#this is wallet-factory-upgrade |
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 don't need to distinguish now that there's one DEST
#this is wallet-factory-upgrade |
ARG DEST_IMAGE | ||
FROM ${DEST_IMAGE} as agoric-upgrade-12 | ||
FROM ${DEST_IMAGE} as wallet-factory-upgrade |
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.
similarly, this stage doesn't need a name now
FROM ${DEST_IMAGE} as wallet-factory-upgrade | |
FROM ${DEST_IMAGE} |
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 the name is still used as a target for the Makefile
, which I haven't changed that drastically.
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 see. We can clean this up when migrating on top of #8635
# BASE | ||
FROM ${BASE_IMAGE} as base-wallet-factory-upgrade |
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.
this isn't doing any work now. better to inline…
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.
Inlining didn't work. Apparently COPY --from
doesn't like variables...
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.
ah. then how about,
# BASE | |
FROM ${BASE_IMAGE} as base-wallet-factory-upgrade | |
# BASE stage for the `COPY --from` below | |
FROM ${BASE_IMAGE} as base |
agoric-upgrade-12: propose-agoric-upgrade-12 | ||
$(BUILD) --target agoric-upgrade-12 -t $(REPOSITORY):agoric-upgrade-12$(TAG_SUFFIX) | ||
wallet-factory-upgrade: | ||
$(BUILD) --target wallet-factory-upgrade -t $(REPOSITORY):wallet-factory-upgrade |
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.
being last, it's the default target
$(BUILD) --target wallet-factory-upgrade -t $(REPOSITORY):wallet-factory-upgrade | |
$(BUILD) -t $(REPOSITORY):wallet-factory-upgrade |
test.before(async t => { | ||
await mintIST(GOV1ADDR, 12340000000, 10000, 2000); | ||
}); | ||
|
||
test.skip('Open Vaults', async t => { | ||
const currentVaults = await agops.vaults('list', '--from', GOV1ADDR); | ||
t.is(currentVaults.length, 5); | ||
|
||
// TODO get as return value from openVault | ||
const vaultId = 'vault6'; | ||
await openVault(GOV1ADDR, 7, 11); | ||
await adjustVault(GOV1ADDR, vaultId, { giveMinted: 1.5 }); | ||
await adjustVault(GOV1ADDR, vaultId, { giveCollateral: 2.0 }); | ||
await closeVault(GOV1ADDR, vaultId, 5.75); | ||
}); |
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.
there are no actions to perform.
this test and its prep should move to post.test.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.
I think I haven't learned how Dockerfiles work - especially this one - well enough to review this.
If it's important that I review this more thoroughly, let's please discuss it.
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals@sha256:ac10c09b5927d759d37b1525b5a0bc4aeb3034df8d0f0fbb15b51203555ffb1b | ||
ARG BASE_IMAGE=ghcr.io/agoric/agoric-3-proposals:pr33 |
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.
:main
isn't on target for this?
pr33
, while more readable than a hash, seems somewhat fragile. "pr33" in a comment and a hash in the code would make more sense to me.
not critical
e00e2c9
to
ba752a6
Compare
@@ -1,25 +1,23 @@ | |||
# Defaults | |||
# Use a stable base image to prevent this test from breaking when | |||
# new upgrade proposals are added to a3p. | |||
# TODO: pr-33 is upgrade-12, use the upgrade-13 PR once it exists |
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.
Still working on the upgrade-13 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.
No concerns here. I expect this will reach a3p before being proposed on agoric-3, and that will use the design in #8635
ARG DEST_IMAGE | ||
FROM ${DEST_IMAGE} as agoric-upgrade-12 | ||
FROM ${DEST_IMAGE} as wallet-factory-upgrade |
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 see. We can clean this up when migrating on top of #8635
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 clicked the wrong radio button somehow.
No concerns here
That means I approve :)
9476fb0
to
552879a
Compare
552879a
to
f1732a4
Compare
refs: #8578
Description
This prepares the
dev-upgrade-wallet-factory-2
branch for the wallet factory core eval. The branch is based onrelease-mainnet1B
afteragoric-upgrade-13
.Security Considerations
None
Scaling Considerations
None
Documentation Considerations
None
Testing Considerations
Docker upgrade tests are empty in this branch for lack of core eval testing framework
Upgrade Considerations
The
dev
branch should be merged back to therelease-mainnet1B
branch before generating the release artifacts.