skills: make the samply and drive.sh harnesses work with the systemd-run daemon hand-off #394
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis#394
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two agent-facing harness scripts assume that the auto-spawned daemon is a forked child whose stderr reaches the caller. On a systemd Linux desktop, autospawn hands the daemon off to
systemd-run --user(crates/felis-client-core/src/spawn.rs~45-50,spawn/systemd.rs), and a forked daemon's stderr is/dev/null(spawn.rs ~96-98)..agents/skills/perf-trace/scripts/samply-profile.sh: samply's launch mode cannot follow a daemon started in a transient unit. The docs consistency audit added a caveat and corrected the parse-thread name (felis-pty-parser). A real fix is to startfelis-daemon serve --socket $SOCKunder samply itself and point the client at that socket, withSHELLset on the client, since the session shell comes from the client'senv_base..agents/skills/producer-traffic-debug/scripts/drive.sh: the audit rewrote it to startfelis-daemon serve --socketitself, with stderr sent to$LOG. It passesbash -nbut has not been run end to end under niri.Both need a runtime check on the Linux desktop before they can be trusted.
natsukium referenced this issue2026-09-25 01:35:05 +09:00