[#5886] feat (gvfs-fuse): Implement an in-memory file system #5915
Conversation
|
I think it's time to organize the code hierarchy not flatten all the code in the |
| // `XXXFileSystem is a filesystem that allows you to implement file access through your own extensions. | ||
| let _ = signal::ctrl_c().await; | ||
| info!("Received Ctrl+C, Unmounting gvfs..."); | ||
| gvfs_unmount().await; |
There was a problem hiding this comment.
what will happen if the process crashed without invoking gvfs_unmount?
There was a problem hiding this comment.
The mount point does't unmounted, users need to umount the directory manually.
Typical FUSE programs do not run in the foreground, and exiting with Ctrl+C is not the standard practice.
This mode is used for testing and debugging.
|
|
||
| let results: Vec<FileStat> = file_map | ||
| .iter() | ||
| .filter(|x| path_in_dir(path, x.0)) |
There was a problem hiding this comment.
please filter out the files in sub directory
Wait until the subsequent PRs are merged before organizing. Doing the later PRs now would lead to significant conflicts. |
What changes were proposed in this pull request?
Implement an in-memory filesystem for testing and validating the FUSE framework. You need to implement the PathFilesystem trait and support basic file and directory operations:
Why are the changes needed?
Fix: #5886
Does this PR introduce any user-facing change?
No
How was this patch tested?
IT