Renaud Paquay

``` jsfs:/> import Error: Runtime {message: "Overlay cannot be found on stdio (required for drag-and-drop import)"} ```

Refactor content of axiom/stream directory

2

axiom/stream contains too much stuff right now - utility classes (e.g. `queue.js`) - low-level stream interfaces (e.g. `ReadableStream`) - various stream implementation (e.g. `MemoryBufferStream`) - stuff related to remote file...

mount command should use its own path to find sub-commands

1

See https://github.com/chromium/axiom/blob/master/lib/wash/exe/mount.js#L88 ``` var fsMountCmd = new Path('jsfs:/exe/mount.' + fsType); ``` The code currently a hard-coded path. It should use `cx.path` as the basis for creating the name of the...

Inconsistent behavior of openContext for Jsfs, nodefs and domfs

1

There is a difference in behavior between jsfs and (domfs, nodefs) wrt to calling `openContext`when path points to a non existent file: - jsfs returns a rejected promise, where as...

DataType vs mime type vs encoding

2

We seem to be keep running into issue with the way we read and write files wrt to the "DataType" usage. For example, jsfs always returns `DataType.Value` when reading files,...

Add a "umount" command

1

This would be useful for stream file systems

TTYRequest should not be an event, it should be part of the signal stream. This is required to correctly support execute context over remote file systems.

Repro steps: ``` jsfs:/> echo "hello" >foo.txt jsfs:/> mv foo.txt foo2.txt Error: Duplicate {type: "directory-name", value: "foo.txt"} jsfs:/> ``` The issue is somewhere inside the implementation of JsFileSystem.alias()

Support for named streams

1

- [ ] yhyyhy