Pulse reports healthy things as failing after upgrading to 8.761

Aperta
#2,887 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 5 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
19.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di danielmiessler/LifeOS

Tutte le issue di danielmiessler/LifeOS

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.