The docs hero is sometimes drawn before the system pill's first reading
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 56/100
Línea de trabajo
Start with Sources/StableBar/DocsImages.swift, especially DocsImages.snapshot and its readiness check, then trace how the system widget’s first output reaches the bar presentation. Reproduce with taskpolicy -b StableBar --render-docs-images DIR and compare repeated docs/hero-dark renders. Done when every widget shows its sample output before capture and repeated renders produce the same pixels.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happens
docs/hero-dark is sometimes drawn before the system pill's first reading reaches the bar. The pill then shows … and …% instead of the sample's 18% and 54%. The pill is narrower, so the bar's right end and the calendar popup under it sit further right than in a good drawing.
When it happens in Draw main's screens, every pull request based on that commit gets a false changed screen in its before/after comparison. A maintainer has to tell it apart from a real change before adding visual-ok. The Docs images job draws the same image, so a stable release could also commit a README hero showing … …%.
Steps to reproduce
Seen on CI only, twice so far (2026-11-01 and 2026-11-18):
- A push to
mainruns Draw main's screens (StableBar --render-docs-images). - A pull request based on that commit draws its own docs images and compares them with
main's. - One side's
hero-darkhas… …%in the system pill; the other side has18%and54%.
taskpolicy -b StableBar --render-docs-images DIR, run a few times, may reproduce it locally by slowing the drawing down.
Expected
The docs images wait until every widget on the bar shows its sample output, so two runs of one commit draw the same pixels, as CONTRIBUTING's Docs images section says they do.
Environment
CI, macos-26 runner (Apple silicon, 3 cores), Xcode 26.6. main at 937c40e.
Evidence
- #793, which changes only CI files, reported one changed screen,
docs/hero-dark(151,469 pixels, region 954,12 · 807×525), comparingmainat 937c40e with the pull request at af3e727: https://github.com/Seb-GRAF/StableBar/pull/793#issuecomment-6962907256. The "before" image comes frommain's ownscreens-main-937c40e…artifact and shows… …%. The "after" image, drawn from the same app code, shows18%and54%. - #432 (2026-11-01) saw the same thing the other way round: "in
docs/hero-darkthe system monitor had its first reading on this run (18% and 54%) but not onmain's (…)".
Diagnosis
DocsImages.renderdraws the hero fromsampleStore(…)(Sources/StableBar/DocsImages.swift). Itssystem-monitorwidget is the"type": "system"widget setup adds (SetupPreferences.WidgetSet.system). The sample configuration defines asystemcommand provider that runs/bin/cat "$CONFIG_DIR/system.json", withinterval: 3600.DocsImages.snapshotpassesOffscreenSnapshot.writea readiness check and a fixed 3-second settle. The check waits until the sample workspaces exist and nostore.scriptsentry hasoutputNumber == 0.- The bad drawing shows the pill's placeholders, so that check, or the settle after it, didn't cover the pill's first reading. Either the system widget's output isn't among the
store.scriptsentries the check reads, or the reading arrived but the bar hadn't shown it within the settle on a busy runner. Which one is unverified. - A fix would wait on what the bar shows for each widget, for example its presentation having received an output, rather than on the time a settle allows.
Related
- #395 made the docs images draw the same on every run (fixed date, offline Store, sample app). This is a remaining source of difference between runs.
- #432 noticed the same difference in its description, but no issue was filed.
- #794 (draft) found the same kind of race in scenes, where a fixed settle ends before a view's data loads. This one is in the docs images and happens without parallel drawing.
Triaged by Claude Code (Claude Opus 5.5).
- Lenguaje dominante
- Swift
- Estrellas
- 184
- Forks
- 12
- Merge medio
- 3 h 50 min
- PR fusionados (30 d)
- 387
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Seb-GRAF/StableBar
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
Los mantenedores suelen responder en 1 día
-
Menu bar items drawn as in the menu bar show the wrong part of the menu bar after a display changePosiblemente ocupada @Jonathanm10 la tomó hoy. Abiertoneeds-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
Los mantenedores suelen responder en 1 día
-
Allow the App Menu to display the frontmost app iconPosiblemente ocupada @khatami10 la tomó hoy. Abiertoenhancement needs-triage
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de Seb-GRAF/StableBar
Issues similares
-
good first issue help wanted testing
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
-
area:cli documentation good first issue priority:low
Dificultad 1/5 Menos de una hora Aptitud para principiantes 94/100
isaaclins/freesnitch#430 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día