oven-sh/bun

fs.utimesSync sets the time in seconds (so it seems)

Closed

#6,804 opened on Oct 30, 2023

View on GitHubContributor guide
 (2 comments) (0 reactions) (1 assignee)Rust (4,486 forks)batch import
buggood first issuenode.js

Repository metrics

Stars
 (90,348 stars)
PR merge metrics
 (Avg merge 1d 17h) (357 merged PRs in 30d)

Description

What version of Bun is running?

1.0.7+b0393fba6200d8573f3433fb0af258a0e33ac157

What platform is your computer?

Darwin 21.6.0 x86_64 i386

What steps can reproduce the bug?

fs.utimesSync(pathname, atime, mtime)
console.log(fs.statSync(pathname).mtime.valueOf())

result always ends with "000" with no milliseconds

What is the expected behavior?

mtime should be set precisely

What do you see instead?

tested it also with node v18.17.1 and i get the correct results

Additional information

No response

Contributor guide

Research direction
The issue is that `fs.utimesSync` in Bun truncates milliseconds. To fix, locate the implementation of `utimesSync` in Bun's source code (likely in `src/js/internal/fs.js` or `src/bun.js/api/fs.cpp`). Check if it uses the POSIX `utimes` function, which only supports second granularity, and replace it with `utimensat` or `futimens` to support nanosecond precision. The assignee may already be working on this, so review any linked PRs or comments for progress.
Tech stack
javascript
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30