You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b9da528
Browse filesBrowse the repository at this point in the historyBrowse files
Require ignore rules to prove exclusion before recording
excluded_records recorded every present tracked file that the walk had
not listed, as if ignore rules excluded it. A tracked file restored
after the walk is unlisted too, so it could get a record. If its create
notification was missed, a later Modify that left it unchanged was
dropped as unchanged, although the published state did not contain it.
A candidate now gets a record only when the ignore rules the walk
applied exclude it or a parent directory:
- The metadata walk returns the point-query matcher it already builds
for visibility, and a controlled walk keeps its input control alive
with it.
- When the walk built no matcher, one is built from the walk's rule
files, only once a candidate is found on disk.
- Under a permit, as managed views always walk, both matchers parse
the rule-file contents the walk read through its input control, so
nothing is read again and a rule changed since the walk proves
nothing. A rebuilt matcher leaves out the case-insensitive
tracked-file layer, which only adds exclusions.
The input control's charge for those snapshots and patterns is now
held until the records are built, then released. Tracked files that
the walk skipped only for other reasons get no record, so their
notifications keep invalidating.
Co-authored-by: Copilot App <[email protected]>
0 commit comments