Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

can't use SES.confineExpr with --no-ses

See original GitHub issue

It’s probably obvious, but when we run the vat with --no-ses, we no longer have the SES.confineExpr safe two-argument evaluator for guest code. This means we can’t run the contractHost example with --no-ses, at least not the variant that actually uses the contract host (which needs to evaluate the contract source code it receives).

This is related to the question of how to best expose this evaluator. At present, SES provides a SES global endowment, from which .confineExpr (and I think plain .confine) are available. Since this is an endowment, any further evaluation (like the one performed by the contract host) must pass SES through to the evaluated code, since it isn’t automatically there, and it isn’t otherwise obtainable.

It might be nicer to provide SES as an importable module (possibly with some special-casing when run inside a SES realm), like we do with @agoric/harden. It’s not clear how to achieve that, but eventually we need a better approach than a global.