I mean, it's "run a subset that is supported by wasi" not "untrusted code"
Traceback (most recent call last):
File "/src/code.py", line 3, in <module>
print(os.listdir('/'))
^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 44] No such file or directory: '/'
OT1H, I do appreciate the sandbox-y nature of run fake code, but OTOH I would think a much less explodey way of shimming out untrusted code would be an in-memory filesystem so things blow up less
I guess put another way: who is the target audience for this?
I would think a much less explodey way of shimming out untrusted code would be an in-memory filesystem so things blow up less
Filesystem access is the first item on our roadmap (https://docs.riza.io/reference/roadmap). If you want to see it in action, try opening /src/code.py. While adding an in-memory filesystem would be easy, we want to make it usable for reading and writing potentially large files.
I guess put another way: who is the target audience for this?
Our customers are using our API to run LLM-generated code, build plugin systems, and power customer-defined data transformations.
Comments
I mean, it's "run a subset that is supported by wasi" not "untrusted code"
OT1H, I do appreciate the sandbox-y nature of run fake code, but OTOH I would think a much less explodey way of shimming out untrusted code would be an in-memory filesystem so things blow up lessI guess put another way: who is the target audience for this?
Filesystem access is the first item on our roadmap (https://docs.riza.io/reference/roadmap). If you want to see it in action, try opening /src/code.py. While adding an in-memory filesystem would be easy, we want to make it usable for reading and writing potentially large files.
Our customers are using our API to run LLM-generated code, build plugin systems, and power customer-defined data transformations.