oxidecomputer / oxidecomputer/steno
panic in node_exec_state
Open
@sunshowers is already working on this.
Since Jun 2, 2026.
- Dominant language
- Rust
- Stars
- 170
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
See #16 and oxidecomputer/omicron#279 for details.
We saw this panic:
thread 'test_disks' panicked at 'assertion failed: self.node_errors.contains_key(&node_id)', /home/dap/.cargo/git/checkouts/steno-adfbaf4765a4f9e1/8da3eda/src/saga_exec.rs:1351:13
This is pretty reproducible in that issue and we have a core file, but it'll take some time to wade through the state and figure out what's wrong here. omicron was on commit 8da3eda3bd3fd5d077872c687bb2de1a8b326982 at this point so that failure is here:
https://github.com/oxidecomputer/steno/blob/8da3eda3bd3fd5d077872c687bb2de1a8b326982/src/saga_exec.rs#L1351
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.