the_og/better-claude-config
1
0
Fork 0
Code Issues 8 Pull Requests 3 Actions Packages Projects Releases 4 Wiki Activity

MSIX warning is ephemeral — wiped by the next status-bar update #35

New Issue
Closed
opened 2026-07-12 12:44:41 -04:00 by the_og · 0 comments
the_og commented 2026-07-12 12:44:41 -04:00
Owner
Copy Link
Copy Source

Found in audit of main @ 06326e5. Windows-only surface.

_maybe_warn_msix() (bcc.py ~L1732) appends the MSIX-virtualization warning to the status bar text. But _update_status() / _mark_dirty() / save / import all rewrite self.status wholesale, so the warning vanishes on the user's first interaction — exactly the users who need it (editing the wrong %APPDATA% file) will lose it before reading it.

Proposed fix: dedicated persistent warning label/banner (e.g. below the top bar, WARN color, closable), set once at profile load; keep the tooltip. Alternatively re-append the warning inside _update_status() when the current profile is affected.

Acceptance: on a simulated MSIX detection (monkeypatch msix_warning_text), the warning remains visible after marking dirty, saving, and switching profiles back to the affected one.

**Found in audit of `main` @ 06326e5.** Windows-only surface. `_maybe_warn_msix()` (`bcc.py` ~L1732) appends the MSIX-virtualization warning to the **status bar text**. But `_update_status()` / `_mark_dirty()` / save / import all rewrite `self.status` wholesale, so the warning vanishes on the user's first interaction — exactly the users who need it (editing the wrong `%APPDATA%` file) will lose it before reading it. **Proposed fix**: dedicated persistent warning label/banner (e.g. below the top bar, WARN color, closable), set once at profile load; keep the tooltip. Alternatively re-append the warning inside `_update_status()` when the current profile is affected. **Acceptance**: on a simulated MSIX detection (monkeypatch `msix_warning_text`), the warning remains visible after marking dirty, saving, and switching profiles back to the affected one.
the_og added the P2 label 2026-07-12 12:44:41 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0
P1
P2
blocked
Waiting on an external thing before it can move.
 decision
A decision record (D-007 style) — settled call, referenceable by number from any repo.
 needs-decision
Waiting on AJ's call.
 next
Current focus / next actionable item.
 status
The single pinned STATUS issue for this repo — live state, next action, open items, decisions needed.
No Label P2
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
the_og
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: the_og/better-claude-config#35
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?