-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading file Capabilities insufficient
the first time
#263
Comments
Thanks heaps for filing! There's a lot of useful detail here. If you're able to, could I also get any error logs from the browser console and a screenshot of the network tab in the inspector showing the first request loading? That would really help with understanding and reproducing! |
Here is a packaged example. Unpack it and run $ tar tfz debug.tgz
debug/
debug/run.sh
debug/cat.wasi.wasm
debug/index.html
debug/bundle.js
debug/server.py |
Thanks heaps! I'll do my best to look at this within the next week. |
Hi! This appears to be working for me now on |
@taybenlor yes, now it works! Thanks! (But I had to do
|
Oh awkward. I've stuffed that dependency up. I'll file that as an issue. I want to remove that dependency. |
Runno is really neat! Great work!
I'm trying out the example with cat.wasi.wasm that reads two files defined in
runno-file
tags. It is started with autorun, andit gets a Capabilities insufficient error, number 76. This is the error I am reporting.
But in my
runno-wasi
tag i also havecontrols
so I have a Run button. When I press it and re-run, the program is able to read the file (which is the expected behaviour).I have tried it with other wasm programs too, for example a haskell program that compiles with the new ghc with wasm32-wasi support. The first read fails, but if i restart with the Run button, it works fine.
Here is my setup:
index.html
main.js
(that I compile tobundle.js
with the nodejs programrollup
)server.py
that serves with the extra response headersThe text was updated successfully, but these errors were encountered: