microsoft / microsoft/litebox

Make in-memory fs growth allocation-fallible

Open
#1,324 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2.7k
Forks
144
Avg merge
12h 21m
Merged PRs (30d)
146

Description

InMem writes and extending truncates currently rely on infallible Vec/Cow growth, which may panic or abort on capacity or allocation failure. Define failure atomicity and the appropriate fs error, then use fallible reservation before mutation. Deferred from #1318 to keep allocation behavior unchanged during the broker refactor.

Contributor guide

Open the contributing guide

Research direction

The issue identifies InMem writes and extending truncates as entry points; start by tracing those paths and reviewing the allocation behavior context from #1318. Establish failure atomicity and the appropriate filesystem error, then verify that allocation failure leaves state unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.