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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 rewriteself.statuswholesale, 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.