@ai-ecoverse/slicc-kernel 1.164.2 → 1.164.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (19) hide show
  1. package/README.md +1 -0
  2. package/dist/index.js.map +1 -1
  3. package/dist/kernel-worker.js +65 -69
  4. package/dist/kernel-worker.js.map +3 -3
  5. package/dist/meta.js.map +2 -2
  6. package/dist/node-process-worker.js +33 -13
  7. package/dist/node-process-worker.js.map +3 -3
  8. package/dist/node.js +65 -69
  9. package/dist/node.js.map +3 -3
  10. package/dist/process-worker.js +33 -13
  11. package/dist/process-worker.js.map +3 -3
  12. package/dist/types/fs/changes.d.ts +2 -0
  13. package/dist/types/fs/remote.d.ts +0 -2
  14. package/dist/types/fs/types.d.ts +0 -2
  15. package/dist/types/fs/unlinked.d.ts +1 -0
  16. package/dist/types/launcher.d.ts +0 -1
  17. package/dist/types/mount/mount-fs.d.ts +0 -1
  18. package/dist/types/process/wasi/wasi-fds.d.ts +1 -0
  19. package/package.json +1 -1
package/README.md CHANGED
@@ -818,6 +818,7 @@ The proxy answers `200` with `Content-Type: application/vnd.slicc.raw-fetch`: a
818
818
  - **Limits:**
819
819
  - A kernel without `/proc/sys/kernel/slicc_rename_acks` (older than #1140) doesn't answer and isn't waited for ([#1309](https://github.com/ai-ecoverse/slicc-kernel/issues/1309)). It can still see a tree mid-move, and a write it has in flight when the rename starts can land in the old copy and be lost.
820
820
  - An open descriptor follows a rename by another process, of its file or of a directory above it ([#1257](https://github.com/ai-ecoverse/slicc-kernel/issues/1257), see "A rename by another process" above), also when the rename was in another tab.
821
+ - While another tab shares the root, an op through a descriptor that finds its name empty waits up to 1 s (100 ms alone) for the other tab's move to arrive, and keeps following moves for up to 2 s, so a file moved back and forth isn't lost ([#1442](https://github.com/ai-ecoverse/slicc-kernel/issues/1442)). A file that was really removed, not moved, so fails with `ENOENT` after up to 1 s instead of 100 ms, or up to about 3 s in a root where other files keep being renamed meanwhile, since any rename seen counts as a move to follow.
821
822
  - A peer's call that is already in flight and then reaches into the renaming tree through a call of its own (a rename removing the name it replaces) waits for the rename, while the rename waits for that peer's answer. After the 10 s cap the rename fails with `EBUSY`, nothing has moved, and the peer's call goes on.
822
823
 
823
824
  A lookup follows at most 40 symlinks, as Linux does: the 41st is `ELOOP`, for WASI programs, JS programs and the kernel API alike, with or without `..` in a link's target. Emscripten programs resolve paths in their glue, which stops one link earlier, at 40.