You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pulse Today shows a disabled [modules] entry as an HTTP 404 error in Blockers #2817
LifeOS 8.761.0 · attestation: 3 system file(s) differ from danielmiessler/LifeOS@v8.761.0:
LIFEOS/TOOLS/models.ts
LIFEOS/TOOLS/model-pricing.json
LIFEOS/DOCUMENTATION/ARCHITECTURE_SUMMARY.md
What is broken
When a Pulse module is switched off in USER/CONFIG/PULSE.user.toml under [modules] (for example vigil = false or work = false), its API route stops answering and returns HTTP 404. The Today page's aggregator (/api/today) does not recognise that as "module off": getJson only maps a body with available: false or setup_required: true to an unavailable source, so a plain 404 falls through to throw new Error(...). The result is a red error line in the Blockers panel ("/api/work → HTTP 404 · /api/vigil → HTTP 404") for a module the user deliberately disabled. The [modules] comment in PULSE.toml says disabling a module hides its tab instead of leaving an empty page; Today should treat a disabled module the same way (skip it, or show the designed not-installed state), not as a failure.
Where (file:line)
LIFEOS/PULSE/modules/today.ts:642
Repro on a clean tree
1. On a v8.761.0 install with Pulse running, add `vigil = false` under `[modules]`in`LIFEOS/USER/CONFIG/PULSE.user.toml`.
2. Restart Pulse: `launchctl kickstart -k gui/$(id -u)/com.lifeos.pulse`.
3. `curl -s 'http://localhost:31337/api/today?fresh=1'| jq .errors` shows `{"vigil": "/api/vigil → HTTP 404"}`.
4. Open Pulse → Today: the Blockers panel shows the red error line.
Negative control: the captured probe exits 1 because `.errors` contains an HTTP 404 entry for the disabled module.
Two possible places, maintainer's choice: (a) have a disabled module's routes answer { available: false, reason: "module disabled" } instead of 404, which unavailableFrom already handles; or (b) in modules/today.ts skip the probe for any module that resolveModules reports as off, so it never reaches getJson.
Activity