Make zero-length in-memory writes leave file size unchanged

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

Nobody has claimed this yet.

Assessment

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

Research direction

First confirm the intended compatibility behavior with the original fs author, then inspect the InMem positioned-write path. Add focused sparse-write coverage if appropriate; done means a zero-length write beyond EOF leaves the file size unchanged and does not zero-fill the gap.

Written by the indexing model from the issue text.

Description

An empty positioned write beyond EOF currently grows an InMem file and zero-fills the gap. Confirm the intended compatibility behavior with the original fs author, then make zero-length writes no-ops and add focused sparse-write coverage if appropriate. Deferred from #1318 to avoid changing observable fs semantics in the 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.