-
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
can't build bundles compatible with mainnet due to endo patterns breaking change #8826
Comments
@erights might have some insights |
I wonder if I'm jumping to conclusions about patterns... the stack trace doesn't show any patterns code. |
@erights I think the steps to reproduce above are complete now. Please try it and let me know. |
Hi @gibson042 , I co-assigned this to myself. Before starting on a fix for this, we should talk. |
This is part of the larger effort to handle versioning, and should be included in that effort's design, where we should decide what the fix looks like. |
Got a pointer to 1 or 2 of the relevant issues? Maybe worth a label? |
I think @warner is drafting notes from out meeting last week. Part of the effort to have a plan upgrading endo, XS, liveslots, etc. |
and
and
|
my version of @mhofman plans to try to reproduce a couple things, though the timing might be complicated by upgrade-14 |
Some progress at endojs/endo#2038 |
Reopening to track integration in agoric-sdk |
Describe the bug
I ran into
SwingSet: xsnap: v11: RangeError#1: Expected undefined is same as Interface
, asked for help, and learned in discussion with @Chris-Hibbert, @kriskowal , @mhofman that it's due to a breaking change in @endo/patterns, and that as a result, I wouldn't be able to test the upgrade fix for #8311 on master; I'd have to do development in the release branch, which (presumably) doesn't include the breaking change to patterns.To Reproduce
683733d
as of this writing)cd agoric-sdk; yarn
cd a3p-integration; corepack enable; yarn
yarn test
yarn test
needs docker as usual for working with agoric-3-proposals)=> CACHED [test-names-by-addr test-names-by-addr 4/4]
Running test image for proposal upgrade-14
runs okRunning test image for proposal names-by-addr
starts; goes ok thruv1: upgradeProvisioningVat...
, but thenv1: Error: vat-upgrade failure
stack for v1: Error: vat-upgrade failure
Expected behavior
The upgrade should work just as well as on the release branch (#8786).
Platform Environment
IOU
git describe --tags --always
)Additional context
was working on #8311
Screenshots / Stack trace
earlier stack from 2024-01-22
The text was updated successfully, but these errors were encountered: