Make in-memory fs growth allocation-fallible

Open
#1,324 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

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.

Dominant language
Rust
Stars
2.7k
Forks
144
Avg merge
12h 21m
Merged PRs (30d)
146

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/litebox

All issues in microsoft/litebox

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.