Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1448GitHub issuePublicFixed

Disk speed test panel shows 0 for ~17s on slower SSDs during staging

Reported by JoeJoeflyn · filed Aug 25, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

Disk speed test panel shows 0 for ~17s on slower SSDs during stagingrevision 1 · captured 2026-09-28 21:24 UTC via poll

Bug

The disk speed test panel shows 0 on both dials during the staging phase. On slower SSDs this can take 17+ seconds with no indication anything is happening — looks broken.

Repro

  1. omarchy-shell shell summon omarchy.disk-speedtest
  2. Watch both dials stay at 0 for ~17 seconds
  3. Numbers eventually appear once staging completes

Root cause

Before measuring, omarchy-disk-speedtest writes 4 × 256MB files with oflag=direct to stage read test data. On a Kingston SSD this takes ~17s. The panel has no "preparing" state — it shows 0 until the first read/write sample arrives.

Suggested fix

Measure the staging write I/O and emit stage <rate> lines so the write dial moves immediately. No extra time added — just report the write throughput that's already happening during staging.

Tested locally: staging outputs stage 25, stage 24, etc. right away instead of silence. The panel QML would need to handle stage as a phase that feeds the write dial.

View raw text
## Bug

The disk speed test panel shows 0 on both dials during the staging phase. On slower SSDs this can take 17+ seconds with no indication anything is happening — looks broken.

## Repro

1. `omarchy-shell shell summon omarchy.disk-speedtest`
2. Watch both dials stay at 0 for ~17 seconds
3. Numbers eventually appear once staging completes

## Root cause

Before measuring, `omarchy-disk-speedtest` writes 4 × 256MB files with `oflag=direct` to stage read test data. On a Kingston SSD this takes ~17s. The panel has no "preparing" state — it shows 0 until the first `read`/`write` sample arrives.

## Suggested fix

Measure the staging write I/O and emit `stage <rate>` lines so the write dial moves immediately. No extra time added — just report the write throughput that's already happening during staging.

Tested locally: staging outputs `stage 25`, `stage 24`, etc. right away instead of silence. The panel QML would need to handle `stage` as a phase that feeds the write dial.

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

  • Fixed bypr/12248· confirmed

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 09:12 UTC