Implemented Node.js fs API on top of File System Access API (an the other way around), PR: https://github.com/streamich/memfs/pull/916

Live demo: https://streamich.github.io/memfs/ - in the demo if you open dev console, there will be exposed fs global, which allows you to perform all Node.js file system calls, including streams (createWriteStream) and synchronous calls. It runs on top of OPFS. One can use OPFS Explorer to verify: https://chrome.google.com/webstore/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd

Help. Using bikeshed v3.12.1, when I add an Issue Tracking value, that causes bikeshed to fail with this:

Traceback (most recent call last):
  File "/opt/homebrew/bin/bikeshed", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/mike/workspace/bikeshed/bikeshed/cli.py", line 439, in main
    handleSpec(options, extras)
  File "/Users/mike/workspace/bikeshed/bikeshed/cli.py", line 496, in handleSpec
    doc.preprocess()
  File "/Users/mike/workspace/bikeshed/bikeshed/Spec.py", line 144, in preprocess
    self.assembleDocument()
  File "/Users/mike/workspace/bikeshed/bikeshed/Spec.py", line 156, in assembleDocument
    self.lines, self.mdDocument = metadata.parse(lines=self.lines)
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mike/workspace/bikeshed/bikeshed/metadata.py", line 1007, in parse
    md.addData(match.group(1), match.group(2), lineNum=line.i)
  File "/Users/mike/workspace/bikeshed/bikeshed/metadata.py", line 169, in addData
    val = md.parse(key, val, lineNum=lineNum)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mike/workspace/bikeshed/bikeshed/metadata.py", line 719, in parseLinkedText
    entries.append((pieces[0], pieces[1]))
                               ~~~~~~^^^
IndexError: list index out of range

Look familiar to anybody?

Stepping through it and debugging, I can see there is in fact no pieces[1] there, because bikeshed is doing this:

    for v in vals:
        pieces = v.rsplit(" ", 1)
        entries.append((pieces[0], pieces[1]))

…where

• vals is ['https://github.com/WebAssembly/spec/issues']
• v is https://github.com/WebAssembly/spec/issues
• pieces is ['https://github.com/WebAssembly/spec/issues']

So, the source seems to be assuming v contains at least one space character. But it doesn’t.

Now struggling with trying to figure out where bikeshed picks up boilerplate from.

I’m changing the bikeshed/spec-data/readonly/boilerplate/wasm/status-WD.include in my local bikeshed clone, then running pip3 install -e . and bikeshed update — but bikeshed doesn’t seem to be using that boilerplate file. Instead, it seems to be picking up the boilerplate from somewhere else.

Thanks. But if I’m just running bikeshed locally, and if I don’t have any bikeshed-boilerplate clone, then I can’t see what it’s doing.

Well, apparently, I can see that it seems to be completely ignoring any changes I make to the bikeshed/spec-data/readonly/boilerplate files in my clone of the bikeshed. So I don’t understand what the purpose of having those bikeshed/spec-data/readonly/boilerplate would be to begin with…

Anyway, I now see that bikeshed is creating a bikeshed/spec-data/boilerplate/ directory (that is, without the readonly), and I guess it does that by downloading the https://github.com/speced/bikeshed-boilerplate/ sources. And I don’t see any way to prevent it from doing that.

So I guess the only way to make local changes is to edit the bikeshed/spec-data/boilerplate/ files after it downloads them, and change those, and then hope I don’t accidentally run something that causes them to be re-downloaded so that my local changes get clobbered.