Fix overly restrictive permissions in atomic file writes
Cluster 70856 · agent. Data as of
Nothing open on GitHub. Fix merged in #74918 on 31 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #74918. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #74897. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug report and corresponding fix addressing that _atomic_write in tools/file_operations.py leaves newly created files at 0600 (mkstemp default) without applying the process umask, repeating a known bug class.
Open issues0
Open PRs0
Fixes on record
-
#74897 fix(file_ops): apply umask-default permissions in _atomic_write for new files (#70856)
files:
tests/tools/test_file_operations.py,tools/file_operations.py -
#74918 fix(file_ops): replace umask arithmetic with chmod "=rw" — zsh silently corrupts new-file perms
files:
tests/tools/test_file_operations.py,tools/file_operations.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#70888 fix(file_ops): apply umask-default permissions in _atomic_write for new files (#70856) · merged via another change →
fbfee8e,#74897,#70856,#74918
Closed issues · 1
- Closed#70856tools/file_operations.py::_atomic_write leaves newly-created files at mktemp's 0600, umask never applied (third instance of #14181/#23613's bug class)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab