Skip to content

[Upstream nexum-runtime] Unconfigured chain_id in a subscription fails open, not at boot #650

Description

@lgahdl

Tracking issue — the bug and its fix live upstream in nullislabs/nexum-runtime, which shepherd-engine depends on as a pinned git dependency.

Upstream issue: nullislabs/nexum-runtime#65

Found during an internal red-team review (operator mistake persona): a module subscription naming a chain_id absent from engine.toml's [chains] table doesn't fail at boot — it boots fine and then retries forever with only a warn-level log, never delivering an event. A config typo in a shepherd deployment's engine.toml would be very easy to miss.

This issue tracks: re-verifying the fix once nexum-runtime ships boot-time validation, and bumping shepherd's pinned dependency revision.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working.component/manifestnexum.toml / nexum-engine.toml parsing + config-value

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions