Skip to content

fix(cli): uffs --status broker section is "not applicable" off Windows#468

Merged
githubrobbi merged 2 commits into
mainfrom
fix/status-broker-section-non-windows
Jun 20, 2026
Merged

fix(cli): uffs --status broker section is "not applicable" off Windows#468
githubrobbi merged 2 commits into
mainfrom
fix/status-broker-section-non-windows

Conversation

@githubrobbi

Copy link
Copy Markdown
Collaborator

Symptom

On macOS/Linux, uffs --status showed:

── Access Broker ──
  Status:      not installed
  Install:     uffs-broker --install  (one-time; removes UAC prompts)

But the Access Broker is Windows-only (it vends elevated NTFS volume handles), and there is no UAC off Windows — so the "not installed / install for no UAC" hint is misleading, and uffs-broker --install there only prints "Windows-only component". The doctor already handled this ("Broker check skipped (non-Windows)"); --status didn't.

Fix

Off Windows, the broker section now prints "not applicable (Windows-only component)" and returns. Windows behavior is unchanged.

Verification

macOS + x86_64-pc-windows-msvc clippy clean; builds on both.

🤖 Generated with Claude Code

On macOS/Linux, `uffs --status` reported the Access Broker as "not installed"
and advertised `uffs-broker --install (one-time; removes UAC prompts)`. But the
broker is a Windows-only component (it vends elevated NTFS volume handles), and
there is no UAC off Windows — so the hint was misleading and `uffs-broker
--install` there only prints "Windows-only component".

Print "not applicable (Windows-only component)" off Windows instead, matching
the doctor's existing "Broker check skipped (non-Windows)". Windows behavior is
unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@githubrobbi githubrobbi enabled auto-merge (squash) June 20, 2026 14:25
@githubrobbi githubrobbi merged commit c3fcfcc into main Jun 20, 2026
27 checks passed
@githubrobbi githubrobbi deleted the fix/status-broker-section-non-windows branch June 20, 2026 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant