nodejs / nodejs/node

UV_USE_IO_URING does not update file handle position

Open
#55,113 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

confirmed-bug fs libuv linux
Dominant language
JavaScript
Stars
122k
Forks
37.3k
Avg merge
4d 2h
Merged PRs (30d)
283

Description

I suspect possible regression. Not sure what version but must have been recent:

await stream.promises.pipeline(src, fs.createWriteStream(dstPath))

Will not create a full sized file. I suspect that since createWriteStream doesn't explicitly set position during writes it expects the file handle position to be properly updated, which does not seem to be the case with URING.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the stream.promises.pipeline example with UV_USE_IO_URING enabled and compare the resulting file size with the expected size. Trace how fs.createWriteStream performs writes without an explicit position and verify whether the file handle position advances correctly. Done means the pipeline creates a complete file and maintains the expected handle position.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.