composefs / composefs/composefs-rs
gc doesn't know about by-sha256
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 93
- Forks
- 30
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 13
Description
Running gc in the presence of by-sha256 splitstreams gives:
Error: category directory contains non-symlink
Which is probably for the best, because it doesn't know about them and would probably decide to delete them if it could find them.
We should do something sensible there. I wonder if we should take a more generic approach to symlink handling: all symlinks reachable from anything under */refs/** get to live. We can better do the checking about if the structure is correct from fsck.
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.
Research direction
Start by reproducing gc with by-sha256 splitstreams and inspect how it handles non-symlinks in category directories. Determine how symlinks reachable from /refs/* should be preserved, and use fsck to check whether the resulting structure is valid.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100