[bug] Stock install ships 17 launchd jobs and 3 Pulse crons outside Workflows
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start with LIFEOS/TOOLS/Services.ts lines 144–255 and the Workflows.ts attention command described in the report; trace how the listed launchd jobs and Pulse crons are registered and reported. The issue offers two possible remedies, so first determine which approach fits the project’s workflow design. Done means a fresh stock install no longer reports these jobs as uncleared high findings.
Written by the indexing model from the issue text.
Description
What happened
a stock install starts with 20 'runs outside Workflows' findings it cannot clear. WorkflowsSystem says nothing runs outside Workflows and that every scheduled job is a typed definition, and /ic blocks on every high outside-workflows finding. But LIFEOS/TOOLS/Services.ts (lines 144-255) still registers atlas, coach, commitmentsweep, conduit, conduit.insight, derivedsync, deriver, distill, interviewdue, modelsync, orphanreaper, socrates, synthesis, usage-aggregator, vigil, worksweep and the dispatcher as launchd plists, Pulse keeps three crons (cost-aggregation, memory-consolidation, proposal-gc), and the installer's shipped WORKFLOWS folder holds only statusline-refresh.workflow.yaml; a search for *.workflow.yaml over LIFEOS finds only the cloud example fixture. So 'bun LIFEOS/WORKFLOWS/Workflows.ts attention' on LifeOS 8.761.0 lists 17 launchd jobs and 3 Pulse crons as 'runs outside Workflows (launchd); it must become a typed definition', plus the two always-on Pulse services, and a user cannot clear them without authoring the definitions upstream owns. Suggested fix: ship the typed definitions for the stock jobs (and have Services.ts install them through the dispatcher), or mark the stock jobs as known migration debt so the finding is info, not high, until they ship.
Summary
The docs say nothing runs outside Workflows, yet the shipped installer still registers the core jobs as launchd plists and Pulse crons, and ships one workflow definition. A fresh install therefore opens with twenty high "outside Workflows" findings it cannot clear without writing the typed definitions itself. Shipping those definitions (or exempting the stock jobs until they exist) would make the docs true on day one.
Details
- Kind: bug
- LifeOS version: 8.761.0
Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
danielmiessler/LifeOS#2894 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
danielmiessler/LifeOS#2891 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
danielmiessler/LifeOS#2888 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danielmiessler/LifeOS#2886 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
danielmiessler/LifeOS#2848 ·
Maintainers usually reply within 5 days
All issues in danielmiessler/LifeOS
Similar issues
-
ready-for-agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
LucasSantana-Dev/Lucky#3257 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement frontend good first issue help wanted testing-infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
Maintainers usually reply within 1 day