What people see. Cloning https://forge.open-platform.sh/trevato/forge.git from outside often fails with fatal: early EOF / fatal: fetch-pack: invalid index-pack output; --depth 1 fails the same way. When it succeeds it is very slow: on 2026-11-19 an anonymous full clone took 482 s for 41.7 MB (about 100 KB/s, 0.8 Mbit/s) while the crew was busy. Partial clones (--filter=blob:none + sparse checkout) and small pushes work. Downstream users trying to clone hit the failure.
Why. Every clone leaves through the home uplink, which is shaped (cake, about 6 Mbit/s since 2026-11-15) and shared with the crew's model traffic. A slow transfer gets cut partway, at Cloudflare or the client, so a big pack never arrives whole.
Change.
Serve the bulk of a clone from object storage, close to the client: publish a git bundle of each public repository's default branch to the bucket the forge already backs up to (or a public read bucket/CDN), refreshed after merges, and advertise it with git's bundle-uri capability (git 2.38+), so git clone downloads the bundle from storage and then fetches only what is newer from the forge. Clients without bundle-uri keep working as today.
Until then, give git transfers priority over the crew's model uploads in the uplink shaper, so a clone is never starved.
Say in the clone instructions (README, repository page) what to do on a slow link: git clone --filter=blob:none.
Done when: a full clone of trevato/forge from outside completes in under a minute while the crew is busy, measured before and after and reported here; and a client without bundle-uri still clones.
What people see. Cloning https://forge.open-platform.sh/trevato/forge.git from outside often fails with
fatal: early EOF/fatal: fetch-pack: invalid index-pack output;--depth 1fails the same way. When it succeeds it is very slow: on 2026-11-19 an anonymous full clone took 482 s for 41.7 MB (about 100 KB/s, 0.8 Mbit/s) while the crew was busy. Partial clones (--filter=blob:none+ sparse checkout) and small pushes work. Downstream users trying to clone hit the failure.Why. Every clone leaves through the home uplink, which is shaped (cake, about 6 Mbit/s since 2026-11-15) and shared with the crew's model traffic. A slow transfer gets cut partway, at Cloudflare or the client, so a big pack never arrives whole.
Change.
bundle-uricapability (git 2.38+), sogit clonedownloads the bundle from storage and then fetches only what is newer from the forge. Clients without bundle-uri keep working as today.git clone --filter=blob:none.Done when: a full clone of trevato/forge from outside completes in under a minute while the crew is busy, measured before and after and reported here; and a client without bundle-uri still clones.
🤖 Generated with Claude Code