> Is this test environment appropriate for reproducing the issue, or would you prefer an alternative setup?
Yep, but it needs `force-integration` before it'll run the docker tests. I added the l...
The advice I got was that this upgrade should be tested in KREAd's repo rather than `agoric-sdk/a3p-integration`.
The way to proceed would be to
* create a PR against `https://github.com/Kryha...
```suggestion
/// ////////// Make sure an election held by a given committee /////////////
/// ////////// (see @agoric/governance) turned out as expected /////////////
```
[see the wiki](https://github.com/Agoric/agoric-sdk/wiki/Coding-Style#code-comments). As an explicit statement about something to change shortly, this makes more sense as a TODO than as tech debt....
> https://github.com/Agoric/agoric-sdk/issues/10425 tracks this now. From your comment I understand the path for this PR to land;
> * Close 10425
> * wait the plan for upgrading `vat-bootstrap`...
I don't think there is any difference between the above and this shorter version.
```suggestion
const makeQueryWalletCurrent = follow => (/** @type {string} */ addr) =>
follow('-lF', `:publish...
> To mitigate this, I utilized the [resolution field](https://github.com/Jorge-Lopes/KREAd/blob/jorge/10392-contract-upgrade/agoric/package.json#L58-L84) to address both dependency and size issues....
Is this log message intended to be once for the entire loop, or once per step? It's either in the wrong place, or not clear enough. How about
```suggestion
for await (const i of asyncGenerator...
> Do we already have tests of that?
We do not. But now that we've replace auctions and upgraded vaults, I'd expect such tests to pass. I'll work on adding them.
Oh! good point. I'll have to figure out how to pass the bundle through without installing a contract.
We use `publishRef(install())` in the Zoe proposals. I don't know why that's okay.