[Lume] Push Optimizations
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 23.1k
- Forks
- 1.6k
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 190
Description
In libs/lume/scripts/push-ghcr.sh, we are not taking advantage of Apple sparse filesystem and also uploading the '0-bytes' during fragmentation of the disk.img.
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 by reading libs/lume/scripts/push-ghcr.sh and trace how disk.img is fragmented and uploaded to GHCR. Investigate the Apple sparse filesystem handling and identify where 0-byte regions are included; done means the push avoids uploading those regions while preserving the image contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, macos, shell
- Domain
- cloud, devops, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100