natsukium/felis
Watch
1
Code Issues 27 Pull requests 1 Projects Releases Packages Wiki Activity Actions

test: add fuzz seeds for the Stop/StopReply IPC messages #152

New issue
Closed
opened 2026-09-06 03:14:33 +09:00 by natsukium · 0 comments
natsukium commented 2026-09-06 03:14:33 +09:00
Owner
Copy link

The repository's IPC extension checklist (.agents/skills/extend-ipc/SKILL.md section 5, "Tests") requires dropping a seed for every new message into fuzz/seeds/ipc_body/ and running just fuzz-smoke.

What is missing: no seed was added for OpsMsg::Stop / StopReply (or the DaemonDraining AttachFailure variant) introduced by #25, unlike other recently added arms in that directory (e.g. proto-ops-switch-retarget.bin).

Where: fuzz/seeds/ipc_body/.

Correction: add a minimal encoded Stop/StopReply body seed under fuzz/seeds/ipc_body/ and run just fuzz-smoke.

Why deferred from #25: project checklist hygiene (extend-ipc SKILL.md), not an acceptance criterion of #25; the missing seed does not fail CI, it only reduces fuzz coverage of the new arms.

Split from #25.

The repository's IPC extension checklist (`.agents/skills/extend-ipc/SKILL.md` section 5, "Tests") requires dropping a seed for every new message into `fuzz/seeds/ipc_body/` and running `just fuzz-smoke`. **What is missing:** no seed was added for `OpsMsg::Stop` / `StopReply` (or the `DaemonDraining` `AttachFailure` variant) introduced by #25, unlike other recently added arms in that directory (e.g. `proto-ops-switch-retarget.bin`). **Where:** `fuzz/seeds/ipc_body/`. **Correction:** add a minimal encoded `Stop`/`StopReply` body seed under `fuzz/seeds/ipc_body/` and run `just fuzz-smoke`. **Why deferred from #25:** project checklist hygiene (extend-ipc SKILL.md), not an acceptance criterion of #25; the missing seed does not fail CI, it only reduces fuzz coverage of the new arms. Split from #25.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci/darwin-smoke
No results found.
Labels
Clear labels   
priority/P0
Must be resolved before the v0.1.0 tag

  
priority/P1
Must be settled before the first public contract freezes

  
priority/P2
Explicitly deferred until after v0.1.0

  
release/v0.1.0
Work tracked for the first tagged release

  
status/blocked
Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  
status/planned
Triaged with a source-grounded plan and a passed pi review; ready to implement

  
type/bug
Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  
type/design
An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  
type/test-gap
Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  
type/tracker
Parent issue that tracks child work

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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
natsukium/felis#152
No description provided.