Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
tailscale: pollWatchdog kills healthy in-flight status polls, panel shows TAILSCALE IS DISCONNECTED
Reported by iskakaushik · filed Aug 22, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Surfaced during review of #7623 (credit to the review bot's probing there — it tripped this three times against a deliberately slow status stub) but pre-existing and independent of that PR; git blame puts the lines with the Taildrop change.
pollWatchdog in shell/plugins/panels/tailscale/Service.qml is armed when a poll launches and is never stopped when the poll completes:
if (launched && !pollWatchdog.running) pollWatchdog.start()Fifteen seconds later it fires unconditionally and kills whatever status/accounts/exit-node process happens to be in flight at that moment — not the poll it was armed for. On a fast tailnet there is usually nothing in flight, so it goes unnoticed. On a tailnet where tailscale status --json takes more than a few seconds (large tailnets are the premise of #7623 — 4.6 MB of JSON there), it reliably murders a healthy poll: statusProcess.running = false → non-zero exit path → resetUnavailable("Disconnected") → the panel shows "TAILSCALE IS DISCONNECTED" while the tailnet is fine.
The watchdog's stated purpose (reap a genuinely hung poll so refreshing doesn't stop forever) is good; it just needs to stand down when the poll it guards exits — e.g. stop it in the process onExited handlers, or restart-per-launch and track which launch it belongs to.
🤖 Generated with Claude Code
View raw text
Surfaced during review of #7623 (credit to the review bot's probing there — it tripped this three times against a deliberately slow status stub) but pre-existing and independent of that PR; git blame puts the lines with the Taildrop change.
`pollWatchdog` in `shell/plugins/panels/tailscale/Service.qml` is armed when a poll launches and is never stopped when the poll completes:
```qml
if (launched && !pollWatchdog.running) pollWatchdog.start()
```
Fifteen seconds later it fires unconditionally and kills whatever status/accounts/exit-node process happens to be in flight *at that moment* — not the poll it was armed for. On a fast tailnet there is usually nothing in flight, so it goes unnoticed. On a tailnet where `tailscale status --json` takes more than a few seconds (large tailnets are the premise of #7623 — 4.6 MB of JSON there), it reliably murders a healthy poll: `statusProcess.running = false` → non-zero exit path → `resetUnavailable("Disconnected")` → the panel shows "TAILSCALE IS DISCONNECTED" while the tailnet is fine.
The watchdog's stated purpose (reap a genuinely hung poll so refreshing doesn't stop forever) is good; it just needs to stand down when the poll it guards exits — e.g. stop it in the process `onExited` handlers, or restart-per-launch and track which launch it belongs to.
🤖 Generated with [Claude Code](https://claude.com/claude-code)Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 08:22 UTC