Pulse reports healthy things as failing after upgrading to 8.761

Abierto
#2,887 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 5 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start by locating the code for the Workflows, Running, Hooks, Work board, SchedulerWatch, and CloudPager checks, then trace how each check determines and logs its status. The report describes several separate symptoms but names no files or tests, so first map each symptom to its implementation and existing coverage. Done means healthy or uncheckable states are reported accurately and recurring expected failures do not flood the logs.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

After upgrading from 7.40.4 to 8.761.0 on macOS, several Pulse pages flag things as broken that are working. The real problems get buried under them.

What I see:

  1. Workflows page: a job is labelled "failing" when the only issue is that it's an old-style scheduled job waiting to be migrated. The jobs themselves ran fine.

  2. Running page: background services started by other apps (for example the Codex desktop app's own service) are flagged "probably stuck" because no session started them.

  3. Hooks page: a hook that lives under USER/HOOKS is reported as "registered but missing from disk". The check seems to look only in the system hooks folder. The "declared but not registered" list also includes hooks that run inside PostToolObserver or through the plugin.

  4. Work board: every issue's age shows as "just now".

  5. Logs: SchedulerWatch writes an error every 5 minutes because log show needs admin rights on macOS and the account isn't an admin, so it can never succeed. CloudPager does the same when no cloud heartbeat Worker is deployed. Both show honestly as "unknown" on the page, but each still logs an error every tick. I have about 5,500 of these lines so far.

What I'd expect: a state that can't be checked, or a job that's only waiting on migration, shows as unknown or "needs migration" rather than failing, and is logged once instead of every 5 minutes.

Environment: 8.761.0, macOS, standard (non-admin) account.

Happy to test a fix.

Lenguaje dominante
TypeScript
Estrellas
19.9k
Forks
2.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 danielmiessler/LifeOS

Todos los issues de danielmiessler/LifeOS

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.