lmeyerov

Indeed, I think this is preventing us from packaging a react component library with esbuild and then being liberal in who can import, e.g., a webpack consumer is giving warnings...

Ah maybe false alarm in our case: https://github.com/facebook/react/issues/13991#issuecomment-435587809

@tkem @northyorkshire This is of interest to us as well for asyncio servers 1. Resolving handlers place a key-level write lock without blocking the eventloop, allowing progress for requests on...

Ah, excellent. Thanks! Out of those, the include and import statements seem concerning under most threat models (including ours.) +1 for sandboxed mode flag for this and future features :)...

It may help, as simple policies, to consider two of the most basic security properties: data confidentiality & integrity. I'd expect "--sandbox" to provide both. Integrity doesn't seem to be...

Same... we do a DB query (`gremlinpython`), which handles async etc. fine and gets back the result, but upon `conn.close()`, get a similar error: ``` streamlit | Traceback (most recent...

@tvst Are you still having issues reproducing, e.g., starting nest_asyncio?

This is hitting us pretty hard as the end-user is putting in config vals, not ourselves.

Wrapping in `[...]` seems to protect against this, at least preventing crashing.

RE:VPC issue, after some sleuthing: - default settings sagemaker notebooks work w/ Graphistry Hub fine: outside internet - ... but fails with graph-app-kit + aws marketplace private aws graphistry instances:...