Repository navigation
macos: record renames - #30
Draft
LalitMaganti wants to merge 1 commit into
Draft
LalitMaganti wants to merge 1 commit into
LalitMaganti wants to merge 1 commit into
Conversation
LalitMaganti
added this pull request to stack #32
September 16, 2026 12:57
LalitMaganti
force-pushed
the
macos-record-4
branch
from
September 16, 2026 13:04
b989d56 to
a243ec7
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
September 16, 2026 13:11
a243ec7 to
f7ee33d
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
September 16, 2026 13:17
f7ee33d to
5ead0e1
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
September 16, 2026 13:19
5ead0e1 to
c5c9351
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
September 16, 2026 13:22
c5c9351 to
266455b
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
2 times, most recently
from
September 16, 2026 13:31
d9001e2 to
cd0bb4d
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
October 18, 2026 02:20
cd0bb4d to
64c91cf
Compare
LalitMaganti
removed this pull request from stack #32
October 18, 2026 02:40
LalitMaganti
added this pull request to stack #48
October 18, 2026 02:40
This was referenced Oct 18, 2026
LalitMaganti
force-pushed
the
macos-record-4
branch
from
October 18, 2026 02:42
64c91cf to
9f6476d
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
2 times, most recently
from
October 18, 2026 04:44
867d0bf to
ee8e230
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
October 18, 2026 05:06
ee8e230 to
b581c66
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
October 18, 2026 06:13
b581c66 to
28f4687
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
2 times, most recently
from
October 18, 2026 06:52
5048b83 to
64a189f
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
October 18, 2026 06:57
64a189f to
5048b83
Compare
LalitMaganti
force-pushed
the
macos-record-4
branch
from
October 18, 2026 08:23
5048b83 to
9190be4
Compare
Build tools often write an output under a temporary name and then rename it into place. Without renames, the output appears only under a name that nothing reads. The kernel reports a rename as a lookup of the source and then one of the destination. Both are resolved the same way as an open.
LalitMaganti
force-pushed
the
macos-record-4
branch
from
October 18, 2026 08:45
9190be4 to
ea52eeb
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Records renames on macOS.
Fourth of seven steps towards #2. Stacked on #29.
Why
Build tools often write an output under a temporary name and then rename it into place. Without renames, the output would only appear under a name that nothing reads.
Changes
Testing
A unit test checks that a rename is reported with both paths resolved.