On Mon, 15 Sept 2025 at 06:49, Bastian Blank <[email protected]> wrote: > > Found it. It is an optiomization for inode number 0: > > | // When building to wasip1, the host runtime might be > running on Windows > | // or might expose a remote file system which does not have > the concept > | // of inodes. Therefore, we cannot make the assumption that > it is safe > | // to skip entries with zero inodes. > | if ino == 0 && runtime.GOOS != "wasip1" { > | //panic("ino == 0") > | continue > | } > > I don't see anything that mandates this number to be set.
So this is an upstream bug (or perhaps even feature), right? If nothing else, I think this is firmly in the "working as intended" category and if you want it to work differently you probably need to convince upstream. 🙈 (So I think we should probably close the BTS bug - at the very least, "grave" definitely isn't accurate, especially if it only affects wasm/wasi builds. The "p" in "wasip1" stands for "preview" after all. 😅) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
