Related, we will likely want to make `M.await` be vow aware too (issue TBD), and figure out how `M.callWhen` and `M.asyncFlow` interact. (`M.callWhen(M.asyncFlow(M.await(Foo)))` ?)
## What is the Problem Being Solved?
Today `Far` accepts either a function or an object (with methods). However the same support for exportable functions is not extended to virtual / durable kin...
## Describe the bug
My memory is a little fuzzy on this, but I remember when looking at zones and how we were storing kind handles that there was the possibility that the user could define one k...
## What is the Problem Being Solved?
To support async flow exo methods (#9832) without liveslots support (#9881), we need to provide exo state access on top of the existing exo infrastructure. T...
## What is the Problem Being Solved?
- Ability to replay swingset activity as a whole without requiring tendermint and cosmos. For example this can be useful in evaluating performance issues.
-...
Part of this check is technically redundant
```suggestion
if eventHandler.exportMode != keeper.SwingStoreArtifactModeDebug &&
eventHandler.snapshotHeight != provider.BlockHeight {
```
In the case of debug mode (and only in this case), the export artifact should capture the blockHeight of the swing-store, so we don't completely lose track of it (we unfortunately don't have a bett...
I very much would like to not change this as it matches [cosmic-swingset definitions](https://github.com/Agoric/agoric-sdk/blob/4b1403aa06a6c08aae2d4cce0fd582480b7e3c7f/packages/cosmic-swingset/src...
It really is a bit unfortunate we have to read, decode, re-encode it all in memory before finally writing it out, but streamlining this is definitely out of scope.
This should actually always be set, even in skip mode, to avoid triggering the ["bootstrap" logic from import genesis](https://github.com/Agoric/agoric-sdk/blob/4b1403aa06a6c08aae2d4cce0fd582480b7e...
Thanks for digging through this. The main issue is that we don't currently write out the "export data" as "untrusted copy" in debug mode, but instead we-write the cosmos DB copy.
Thanks for digging through this. The main issue is that we don't currently write out the "export data" as "untrusted copy" in debug mode, but instead we-write the cosmos DB copy.
https://github.com/Agoric/agoric-sdk/issues/10424 would add out of consensus instrumentation. Once this becomes part of consensus, we can consider letting some measurements made by xsnap affect sna...
## What is the Problem Being Solved?
We need to figure out where we're spending time in xsnap, and be able to quickly compare timings of the same delivery between validators, or compare equivale...
> At least in the web platform, all objects are expected to be associated with a realm, so creating an object before the realm exists is somewhat inconvenient.
I'm surprised. I thought engines wer...
> I am fine with the restriction to ignore all but non-wellknown symbols as keys.
I think there's still a misunderstanding somewhere. To prevent observable mutable global state, the only kinds o...
This seems like a superset of `../types-index.d.ts`. Should we look into making that explicit somehow by having the internal file reexport the external file? (they would likely have to be moved aro...
This seems like a duplicate of `types-index.d.ts`. How do you propose to keep them in sync under maintenance?
I'm actually wondering if this file shouldn't just go away given that we export type...