Replies: 1 comment
-
Hey @mikelsr! Lots of code in WASIX assumes the file system is always created through the use of |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Let me start by apologizing in advance if this is not the place to ask this, and asking you to point me to the correct place.
I am creating a custom
[FileSystem](https://github.com/wasmerio/wasmer/blob/037aa4b861a4211a06eb98edc20076a9c0b400e3/lib/virtual-fs/src/lib.rs#L87)
by implementing the[FileSystem](https://github.com/wetware/ww/blob/7f78a2ff0e97573e98bfa6b999a283cd62deb5f8/lib/fs/src/lib.rs#L33)
,[FileOpener](https://github.com/wetware/ww/blob/7f78a2ff0e97573e98bfa6b999a283cd62deb5f8/lib/fs/src/lib.rs#L92)
and[VirtualFile](https://github.com/wetware/ww/blob/7f78a2ff0e97573e98bfa6b999a283cd62deb5f8/lib/fs/src/lib.rs#L198)
traits. The custom file system is configured in this line.The file system is just a wrapper that allows WASM guest programs to read (and only read) from IPFS. Here is the guest program I am using for testing.
When examining the calls made in Wasmer, I find I am getting to this error branch in
path_open
, but I am unsure of why.Is there anything I am not implementing, configuring properly...? I'm attaching a segment of the logs at the end of this post.
Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions