Skip to content

6.0.0 installer: DeployComponents leaves __BUN_PATH__ unsubstituted in com.lifeos.pulse.plist (launchd exit 78) #1400

Description

@infinitelyloopy-bt

Component: LifeOS/Tools/DeployComponents.ts (pulse component), LifeOS 6.0.0 skill payload.

What happens: deploying the pulse component materializes ~/Library/LaunchAgents/com.lifeos.pulse.plist with __HOME__ correctly substituted, but ProgramArguments[0] is left as the literal __BUN_PATH__. launchd then fails the service with last exit code = 78: EX_CONFIG and the post-apply healthz probe reports healthz → 000.

Repro: fresh LifeOS 6.0.0 install on macOS (Apple Silicon, bun at ~/.bun/bin/bun) → Setup workflow step 7 → bun Tools/DeployComponents.ts --apply --components pulseplutil -p ~/Library/LaunchAgents/com.lifeos.pulse.plist shows __BUN_PATH__.

Workaround: sed -i '' 's|__BUN_PATH__|'$(which bun)'|' ~/Library/LaunchAgents/com.lifeos.pulse.plist && launchctl bootout gui/$UID/com.lifeos.pulse; launchctl bootstrap gui/$UID ~/Library/LaunchAgents/com.lifeos.pulse.plist — service then runs and healthz returns 200.

Suggested fix: substitute __BUN_PATH__ the same way __HOME__ is handled when materializing the plist.

(Also noticed: Pulse's dashboard 503s until a one-time bun install && bun run build in PULSE/Observability — if the build can't ship prebuilt, the deployer could run it as part of apply.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions