Pulse reports healthy things as failing after upgrading to 8.761

Open
#2,887 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
19.9k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.