Actually I think we can persist an empty context instead (so you can keep `null` as missing).
```suggestion
persistContext(finalBody.remainingBeans > 0 ? {} : triggerContext);
...
I think we need to reset the context on finish for the reporting of the finish event, or it gets some leftover delivery details. Also let's include the vatID here.
```suggestion
case ...
Now that we're gonna persist `null` values as context, I think we should differentiate uninitialized (`undefined`) from `null` contexts (and of course let the initial value of the context be `undef...
I forgot that this would transiently show up in the output for this event. `undefined` will make it be skipped while still reserving the position.
```suggestion
'run.num': undefined,
...
Well I knew I wouldn't get it right just by staring at the code generating slog events. After looking at the output, looks like we have some tweaks to make.
Well I knew I wouldn't get it right just by staring at the code generating slog events. After looking at the output, looks like we have some tweaks to make.
This looks good, but holding my approval until I review the output of aa processed slog in case I missed anything. Is the grafana link up top still valid? I'll also look at the processed slog file ...
This looks good, but holding my approval until I review the output of aa processed slog in case I missed anything. Is the grafana link up top still valid? I'll also look at the processed slog file ...
Let's make sure we don't imply that the host must commit after a single call to run. The host is free to perform multiple runs between commits if it so wishes. The only condition is that commit not...
I think we should generalize the devices not just to transmission but to effects.
```suggestion
SwingSet provides robust and deterministic computation, even in the face of unexpected reboot, an...
Let's make sure this only happens in consensus restarts
```suggestion
if (upgradeEvents) {
isBootstrap ||
upgradeDetails ||
Fail`Unexpected upgrade ...