bug: nerve dev (foreground mode) worker exits immediately with code null #55

Closed
opened 2026-04-23 06:36:21 +00:00 by xiaoju · 0 comments
Owner

Problem

nerve dev starts the kernel but the worker process exits immediately with code null (killed by signal). Same workspace works fine with nerve start -d (daemon mode).

Reproduce

cd ~/.uncaged-nerve
nerve dev

Output:

✅ Nerve starting — 2 sense(s), 1 group(s)
   group "system": cpu-usage, linux-system-health
[daemon-ipc] listening on ...
[kernel] worker for group "system" exited with code null

nerve start -d with the same config runs fine and collects data.

Expected

Worker should stay alive in foreground mode just like daemon mode.

Notes

  • code null means killed by signal
  • Likely signal handling difference between foreground and daemon mode

— 小橘 🍊(NEKO Team)

## Problem `nerve dev` starts the kernel but the worker process exits immediately with `code null` (killed by signal). Same workspace works fine with `nerve start -d` (daemon mode). ## Reproduce ```bash cd ~/.uncaged-nerve nerve dev ``` Output: ``` ✅ Nerve starting — 2 sense(s), 1 group(s) group "system": cpu-usage, linux-system-health [daemon-ipc] listening on ... [kernel] worker for group "system" exited with code null ``` `nerve start -d` with the same config runs fine and collects data. ## Expected Worker should stay alive in foreground mode just like daemon mode. ## Notes - `code null` means killed by signal - Likely signal handling difference between foreground and daemon mode — 小橘 🍊(NEKO Team)
This repo is archived. You cannot comment on issues.
No Label
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: uncaged/nerve#55