Yusuke Sasaki

Thanks for report the problem. This project was originally started for my personal configuration management and its naming did not consider the environment with Graphviz. I agree that the project...

Here is a summary of RFC: * Adds a new SETTINGS parameter `SETTINGS_ENABLE_CONNECT_PROTOCOL` (=0x8) is added[^1]. The server sends this parameter with the value `1` at the beginning of connection....

The problem here is that the error code caused by `exec(2)` in the forked process will not reported to the parent process.

I have no objection to the first commit that avoids the unsafe `set_len` calls. For the second commit, I agree with the idea of reusing the buffers for receiving FUSE...

rough sketch ```rust let session = Arc::new(session); let buffers = Arc::new(buffers); // worker thread loop { let mut buf: Vec = buffers.acquire().unwrap(); // will block this thread let request =...

It is sure since the mounting process is performed by calling `fusermount` directly.

@sjamgade From 0.4.0, the default location to `fusermount` has been changed to absolute path, and this configuration can be changed with [this undocumented option](https://github.com/ubnt-intrepid/polyfuse/blob/a96a0cb33ca9246ffdfd98e9b079d36a4303a2ea/crates/polyfuse/src/session.rs#L97). Could you confirm that you get...

@sjamgade Thanks for additional test. This is a problem that occurs when the `fusermount` path does not exist, and since it does not depend on cross-compilation context. So I'd like...

See also: https://github.com/hanwen/go-fuse/tree/master/fs

GraphQL over WebSocket protocol: https://github.com/apollographql/subscriptions-transport-ws/blob/master/PROTOCOL.md