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
Run the Native Windows Check for the Bootstrap Dash-Name Refusal #3161
#3156 (for #3129) makes both bootstrap loaders refuse an -Agents name that starts with a dash. On the PowerShell side, that includes the U+2013, U+2014, and U+2015 dashes, because PowerShell binds those as a parameter prefix. CI's Windows unit-test job and a local pwsh 7 run pass. Neither one covers native Windows PowerShell 5.1 or the en dash case on real Windows.
Check
In an unelevated pwsh 7 window on Windows, paste the whole block below. It clones the repository into $env:TEMP at #3156's squash commit on develop. It runs every case with -DryRun, so nothing installs even if a refusal fails, and it runs the cases under both pwsh and powershell. Then it deletes the clone. Expect about a minute.
Every printed line starts with PASS: each dash-led name exits nonzero, and the plain herdr name exits 0. A single dash-led value may be stopped by pwsh with "Missing an argument for parameter 'Agents'" instead of the new message, which still counts as refused. Post the printed lines as a comment, then close this issue if all of them pass.
Activity
ptr727 commentedon Oct 16, 2026
ptr727 commentedon Oct 16, 2026
All ten cases pass natively under pwsh 7 and Windows PowerShell 5.1, the en dash case included, so #3156 is verified on Windows.
Promote the Write Guard's Remaining gh Target Reads and the Bootstrap…