Path resolution should be consistent with WASI spec
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- operating-systems
Research direction
Start with the WASI path-resolution documentation and the suggested path forward in issue #269. Inspect path_open and related path-handling functions before the underlying OS syscall. Done means path components are resolved one by one, including cases such as creating a file at a/. , so behavior matches the WASI specification.
Written by the indexing model from the issue text.
Description
Currently, in functions such as path_open, uvwasi first normalizes the path. For example, a path such as a/./../a/b would be normalized to a/b before calling the underlying OS syscall.
This behavior is inconsistent with the WASI documentation, which specifies that path components should be resolved one by one.
This causes seemingly simple WASI calls to behave differently on Node (uvwasi) and many other runtimes like Wasmtime, WasmEdge, etc. For example, a path_open call that tries to create a file a/. will fail on Wasmtime while it succeeds on Node.
@cjihrig has previously suggested a path forward in #269. I just want to open a dedicated issue to track this.
- Dominant language
- C
- Stars
- 272
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/uvwasi
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Similar issues
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
EchoTools/nevr-runtime#653 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
InfiniTimeOrg/InfiniTime#2492 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
base-files: 82_config_generate: regenerate /etc/board.json if 0-bytes / truncated after power cutOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openwrt/openwrt#25940 · 5 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day