3 ms·
I have Covid and it's late in the UK, but tried poking at wasmtime-py for the first time and got this far: https://gist.github.com/callahad/81b33e4e4456e4b27a59
by callahad 4y ago
I have Covid and it's late in the UK, but tried poking at wasmtime-py for the first time and got this far: https://gist.github.com/callahad/81b33e4e4456e4b27a5934c1a36cf7ff https://gist.github.com/callahad/81b33e4e4456e4b27a5934c1a36...
If anyone else is awake and wants to pick up the baton...
- CPU limits are just using an arbitrary amount of wasmtime "fuel". Would be worth looking into epoch interrupts instead.
- Memory limits aren't implemented. Seems like wasmtime-py doesn't expose bindings to anything with a wasmtime::ResourceLimiter trait.
- All i/o is going through tempfiles instead of dealing with proper interfaces.