Skip to content

Human action 14

Jerry Holland edited this page Sep 29, 2026 · 9 revisions

Run the OneDrive path probe

Canonical work item: #14.

When required: Before claiming OneDrive qualification. The bounded native decision and #83 delivery are complete independently; this measurement opens no wider phase. The issue carries current status, decisions, and completion evidence.

Owner role: Windows host owner.

Status 2026-09-16: Done. The owner confirmed the client was actively syncing the intended root during the 2026-09-15 probe window, so that run is the synced-folder measurement (result, confirmation). No human action remains. The steps below stay for an optional future synced run, whose main value would be listing the fixture leftovers before cleanup.

Prerequisites: #22 is complete; use the identified lab-windows-a baseline. Use a quiet Windows machine with OneDrive signed in and actively syncing and a disposable location approved by its owner. Current task authorization covers the disposable probe. If Get-Process OneDrive returns nothing, start OneDrive from the Windows Start menu and sign in if prompted. Check its tray icon for an active, unpaused sync connection to the intended root before continuing. A directory named OneDrive without a running client is not sufficient.

Resolution retention has a separate Windows path limit, tracked in #67. A path-length-exceeded failure names the absolute ref lock-path length and is not evidence of a sync failure. With Git long paths disabled, the lock path must fit within 259 characters; an ordinary SHA-1 repository root can therefore use at most 113 characters for a blob-result resolution. Linked worktrees use the common Git directory's path. See the current path budgets and recovery instructions.

If this diagnostic occurs, preserve the output, abort any pending cst operation with that operation's --abort command, and repeat in a shorter disposable location. Alternatively, enable git config core.longpaths true locally in the affected fixture and record that setting in the evidence. Do not treat a run that stopped on this path limit as a completed OneDrive qualification.

  1. Confirm the OneDrive client is running with Get-Process OneDrive in PowerShell. Stop if the client is absent or the machine is under substantial load.

  2. Choose a new disposable folder inside the synced tree. Record the original shell TEMP/TMP values, then point both at that folder for this shell only. Expected result: benchmark fixtures are created inside the synced location.

    In the same PowerShell session, from the clean checkout, run:

    if (-not $env:OneDrive) { throw "Choose the actual synced OneDrive root first." }
    $vlabSavedTemp = $env:TEMP
    $vlabSavedTmp = $env:TMP
    $vlabProbe = Join-Path $env:OneDrive ("vp-" + [guid]::NewGuid().ToString('N').Substring(0,8))
    New-Item -ItemType Directory -Path $vlabProbe | Out-Null
    $env:TEMP = $vlabProbe
    $env:TMP = $vlabProbe
  3. Run npm run test:benchmark -- --host <assigned-windows-label> --json from the clean source checkout, using the identified unsynced baseline on that same machine. Preserve output even if the check reports a regression; record the synced/unsynced distinction explicitly.

  4. Compare Git-best-mode phase measurements with the unsynced reference. Record sync state, fixture path length, load conditions, failures, raw samples, and the distinction between the historical 1,000 ms reopening condition and ADR-0027's already accepted bounded native decision. Attach the evidence to #14. A pass in a stopped or paused client is not OneDrive qualification.

Verification: Evidence must come from a running OneDrive client and an identified quiet host, not an ordinary Windows CI runner. A measured miss informs #18; it does not automatically authorize native implementation.

Failure handling and cleanup: Restore the shell TEMP/TMP values in the same PowerShell session, including after a failed run:

$env:TEMP = $vlabSavedTemp
$env:TMP = $vlabSavedTmp

After retaining the evidence, verify $vlabProbe names only this disposable probe, list what the run left behind, then remove it:

Get-ChildItem -LiteralPath $vlabProbe -Recurse -Force | Select-Object FullName, Length, Attributes | Format-Table -AutoSize
Remove-Item -LiteralPath $vlabProbe -Recurse

Expect about 95 items, all under node-compile-cache: Node writes its compile cache to os.tmpdir(), so it lands in the probe folder. That is not a sync effect (verified 2026-09-17 on #14); anything outside that directory is worth reporting. Run with --host <label> or the deterministic check compares against the stale legacy entry and fails (#100).

Clone this wiki locally