Skip to content

Windows projection wedge persists on managed projection-history paths (resolve-evidence, history append, tree ops) #3192

Open

Description

@gianlorenzomungiovino

Follow-up to #3177 / PR #3176. #3176 degraded the atomicWrite channel only; the native projection-root paths used by /gsd doctor resolve-evidence, the history-log append (recordManagedProjectionPath/File), tree shelter/restore (auto-worktree-milestone-shelter), exact-tree removal (milestone-actions), and legacy/orphan cleanup (/gsd doctor) still wedge deterministically on ERROR_SHARING_VIOLATION (os error 32).

Root cause: Defender opens freshly created staging nodes inside the managed root without FILE_SHARE_DELETE, so the engine's rename primitives exhaust their Windows retry budget (~75 ms) and the same failure returns on every retry — stable staging/destination names across fresh processes, no visible control artifact to move. FILE_SHARE_DELETE cannot be added for external holders, so the degradation (close the native handle, re-run through a fresh-name tmp+rename / unlink) is the only convergence path short of excluding .gsd from Defender.

Traced shape:

Fix: extend the exhausted-sharing degradation to all of these paths (see PR linked below). Structural rejections (#2648) and non-exhausted failures stay fail-closed; loadUnboundProjectionEvidence stays fail-loud so the doctor still emits "could not be assessed" and lists rows via the lock-free preview (#2883); resolveUnboundProjectionEvidence degrades using the caller's lock-free-listed consent, re-validated against the on-disk evidence.

Activity

  1. added
    needs-triageUnlabeled or unassigned — needs maintainer review
    bugSomething isn't working
    and removed
    needs-triageUnlabeled or unassigned — needs maintainer review
    on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions