[bug] Stock install ships 17 launchd jobs and 3 Pulse crons outside Workflows

Abierto
#2,685 1 comentario 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
42/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, devops

Línea de trabajo

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.

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

Descripción

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.

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.