Add opt-in freshness status for command and stream providers
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- macos, swift
- Área
- desktop, developer-experience
Línea de trabajo
Start with ProviderConfiguration.swift, ScriptWidget.swift and BarStore.widgetStatus in BarStore.swift, then read the Settings → Status and provider guide documentation. Trace how accepted outputs update diagnostics and how suspension affects status before deciding where freshness state belongs. Done when an opt-in per-source limit is reported consistently in Settings and the runtime query, with paused time and existing source states handled as specified.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
A command or stream can leave its last valid value on the bar without reporting a new value for longer than that particular data source allows. For sources that have an expected update cadence, users cannot currently express when that value should be considered stale.
Status already distinguishes failures, missing access, waiting, paused, connected and working sources. It also shows the last successful update. A running connection alone does not establish that a deadline-sensitive value is still fresh.
Silence is not a general bug: an event-driven battery, input-source or other change-only source may correctly send nothing for hours. This request is an explicit per-source freshness contract, disabled by default, not a global silence timeout or an automatic recovery system.
Proposal
Let a command/stream provider opt into a maximum acceptable age for its last successful output. Expose the resulting freshness and age beside its existing source status in Settings → Status and the runtime query.
A provider that needs a liveness contract can use successful repeated output as a heartbeat: the runner already accepts an unchanged valid output without redrawing views. Document that heartbeat/liveness and the age of the underlying external data are different guarantees. Do not mark an old external value fresh merely because its process is still alive.
Keep the last good value available and let the user use the existing Refresh/Restart action. Do not restart, hide or discard a source automatically when the freshness limit expires.
Acceptance
- With no configured freshness contract, existing behavior stays unchanged, including indefinitely quiet change-driven sources.
- A source with a configured limit becomes stale after its last accepted successful update exceeds that limit, even if its stream process remains running. Status/query show the age and configured limit.
- The next accepted valid update clears staleness. An unchanged valid output can renew an explicitly documented heartbeat contract without forcing a redraw.
- Source failures, missing access, initial waiting and intentional suspension remain distinguishable from stale data. Time spent deliberately paused for sleep, lock or visibility must not create a misleading live-connection warning; resume behavior is defined and documented.
- Shared consumers see one source's freshness consistently. This adds no automatic restart policy and does not require every silent source to emit unchanged data.
Possible today
Existing capability / workaround
ScriptDiagnosticsalready recordslastUpdated, running/suspended state, counters and retry information.ScriptWidget.acceptadvanceslastUpdatedfor valid repeated output while avoiding unchanged view assignments.BarStore.widgetStatususes initial-update, error, suspension and connection state, but not a freshness limit.ProviderConfigurationhas no opt-in age/heartbeat setting.- Settings → Status already offers last-update inspection, Refresh/Restart and explicit testing. A custom script can also report its own timestamp or warning. Those require each author or user to implement and interpret the policy separately.
- The provider guide explicitly supports change-driven sources and keeps streams alive until they exit, fail, suspend or stop; command
timeoutis an execution limit, not a freshness contract.
Reviewed main: 01bf12a1a67f6083342421efa090e48213fbe62e. Latest stable reviewed: 0.17.0. This is a capability review, not a claim that a particular user's stream stalled. No app interaction, build or test was performed.
Related
- #17 / #53 introduced common runners and event-driven sources. Their change-only output contract is retained; this request adds an opt-in freshness policy, not polling for all sources.
- #119 introduced the existing Status overview and explicit source testing. The request adds a defined freshness state beside that diagnostic information.
- #694 corrected the workspace connection label after a subscription drops. It does not detect an otherwise running custom source whose accepted output exceeds a user-defined age.
- #307, declined, proposed command-run history and log following. This request adds neither a history/log interface nor a new recovery action.
Triaged by OMP (closerouter/openai/gpt-6.1-sol).
- 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