Skip to content
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

dummy PR to test github CI hang #1460

Closed
wants to merge 171 commits into from

Conversation

warner
Copy link
Member

@warner warner commented Aug 13, 2020

No description provided.

michaelfig and others added 30 commits July 29, 2020 14:16
This rejects promises with the abort exception.
Includes security claims about the split, as well as description of
how Zoe and Zcf communicate while making new instances of contracts.
refactor VatManager, prepare for VatWorker
docs: prose overview for the interaction diagram for Zoe and Zcf
More captp connection aborting when disconnected
This makes it possible to have dapp package dependencies diverge
from agoric-sdk's.
This is necessary to prevent version conflicts due to outdated
dapps.
refactor: break the cycle between notifier and adaptor
feat(agoric): make `agoric --sdk install` use `yarn link`
This emphasizes passing bundles into the kernel, rather than a pre-evaluated
`setup` function. The controller is responsible for `bundleSource`, leaving
the kernel responsible for `importBundle`. This will make it easier to let a
VatManager do that importBundle in a different process (e.g. an XS
VatWorker).

`kernel.addGenesisVatSetup` was added to let unit tests do their thing with
raw `setup` functions.
The comms vat is used to route messages from one swingset to a remote
swingset: its job is to figure out which remote machine each message should
go to, and to translate our object/promise references to ones that the remote
machine will recognize.

It uses the vattp vat to actually send the messages. Some other
application-provided vat must talk to vattp and give it a way to send and
receive messages (generally through some device).

The timer wrapper vat is used to talk to the timer device, and provide a
pleasant API.

Previously, the application was responsible for adding all three to the
swingset config table. Swingset exported functions like `getVatTPSourcePath`
to let the application discover what pathname should be passed back in to
swingset's configuration. This was a drag.

Now, these three vats are added automatically to all swingsets. Applications
no longer need to ask for them; the bootstrap function can simply reference
`vats.comms`, `vats.vattp`, and `vats.timer`.

Applications are still responsible for wiring comms and vattp together, as
well as wiring `vats.timer` to `devices.timer`. This will be changed in the
future.

cosmic-swingset, the primary customer (and the only one which uses these vats
for real) was modified to match.
Change kernel API for adding vats/devices to emphasize bundles over `setup`.

Swingset now adds comms/timer/vattp vats automatically, and the `cosmic-swingset` code which added them externally has been removed.
* fix: rename producePromise to makePromiseKit

* fix: add timeout to spawner test because of appveyor madness

* fix: oops. add @deprecated tag
Chris-Hibbert and others added 27 commits August 11, 2020 17:16
 tests: update swingset tests. This makes the autoswap test work
feat: use debugName to differentiate sim-chain instances
Get VatTP-over-IBC into shape
The prior golden test log relied on a race between deposit and
the new purse values.  Correct that ambiguity.
Create and use unique petname paths
… tests for now (need to be rewritten entirely, I think using the real ZCF, not a mock) (#1435)
@warner
Copy link
Member Author

warner commented Aug 13, 2020

nevermind

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants