The docs hero is sometimes drawn before the system pill's first reading

Abierto
#802 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
macos, swift
Área
desktop, testing

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

bug

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):

  1. A push to main runs Draw main's screens (StableBar --render-docs-images).
  2. A pull request based on that commit draws its own docs images and compares them with main's.
  3. One side's hero-dark has … …% in the system pill; the other side has 18% and 54%.

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

Diagnosis

  • DocsImages.render draws the hero from sampleStore(…) (Sources/StableBar/DocsImages.swift). Its system-monitor widget is the "type": "system" widget setup adds (SetupPreferences.WidgetSet.system). The sample configuration defines a system command provider that runs /bin/cat "$CONFIG_DIR/system.json", with interval: 3600.
  • DocsImages.snapshot passes OffscreenSnapshot.write a readiness check and a fixed 3-second settle. The check waits until the sample workspaces exist and no store.scripts entry has outputNumber == 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.scripts entries 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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Seb-GRAF/StableBar

Todos los issues de Seb-GRAF/StableBar

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.