You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there is something strange with Dart bindings for web:
When I try to setup WasiConfig, the first execution in flutter run -d chrome return an error: TypeError: Cannot read properties of undefined (reading 'WASI').
or if I enable captureStdErr TypeError: Cannot read properties of undefined (reading 'Fd').
simply doing "r" seems that the "refresh" initialise what failed the first time.
Everything seems to work after but is very strange, because of this issue I gave up with WasiConfig and I decided to "write" by myself wasix import basic like fd_write, fd_seek, clock_time_get, proc_exit so that the config can be null... Any solution? If would be possible to expand the test with loading a valid WasiConfig would be also helpful, because I think my config is set up correctly otherwise the code wouldn't work ever.
Here seems the problem from the debugger, I'm investigating:
The Readme was saying that is not necessary in flutter web, I was assuming this process was done under the hood, but apparently is not because Fd is requested as import in my binary when using WASI call that have an fd, like fd_seek ecc...
I think that just updating the Readme will be sufficient
I think there is something strange with Dart bindings for web:
When I try to setup WasiConfig, the first execution in flutter run -d chrome return an error:
TypeError: Cannot read properties of undefined (reading 'WASI')
.or if I enable captureStdErr
TypeError: Cannot read properties of undefined (reading 'Fd')
.simply doing "r" seems that the "refresh" initialise what failed the first time.
Everything seems to work after but is very strange, because of this issue I gave up with WasiConfig and I decided to "write" by myself wasix import basic like fd_write, fd_seek, clock_time_get, proc_exit so that the config can be null... Any solution? If would be possible to expand the test with loading a valid WasiConfig would be also helpful, because I think my config is set up correctly otherwise the code wouldn't work ever.
Here seems the problem from the debugger, I'm investigating:
The text was updated successfully, but these errors were encountered: