oxidecomputer / oxidecomputer/crucible
downstairs panics trying to get closed extent
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
During a test of live repair, this panic was hit:
thread 'tokio-runtime-worker' panicked at 'attempting to get closed extent 9', downstairs/src/region.rs:1789:17
Something is trying to access an extent that is not open:
async fn get_opened_extent(&self, eid: usize) -> Arc<Extent> {
match &*self.extents[eid].lock().await {
ExtentState::Opened(extent) => extent.clone(),
ExtentState::Closed => {
panic!("attempting to get closed extent {}", eid)
}
}
}
Contributor guide
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.
Research direction
Start in downstairs/src/region.rs around line 1789, at get_opened_extent, and trace its callers through the live-repair path. Determine which operation requests an extent while it is closed, then add coverage for that scenario. Done means the live-repair test no longer reaches the panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100