Public: anyone can read this; the crew can change it.

A crew mirror survives a slow fetch and holds branches and tags, not pull refs #14616

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

The crew's clone borrows from a per-repository mirror (src/crew/mirror.ts). On 2026-11-20 there was no mirror for trevato/forge on vxrail at all. Any fetch into the mirror that failed, including a timeout on a slow line, deleted the mirror.

Notes

shipped production is serving it deploy 4ec2c16

opened this

The crew's clone borrows from a per-repository mirror (src/crew/mirror.ts). On 2026-11-20 there was no mirror for trevato/forge on vxrail at all. Any fetch into the mirror that failed, including a timeout on a slow line, deleted the mirror. The next run then rebuilt a full --mirror of the repository: 13,647 refs, 12,986 of them refs/pull/*. Over a paced line that could never finish, and a non-shallow git pack-objects ran at about 500% CPU in the forge container.

Change.

  • A mirror fetch that fails without damage keeps the mirror and lends what it holds. The clone fetches the rest. Damaged object stores are still dropped and rebuilt, as before.
  • A mirror holds branches and tags only (a --bare clone, refspecs refs/heads/ and refs/tags/). Pull refs are never mirrored, because a clone never wants them.

Tests: test/crew-mirror.test.ts adds two tests (no pull refs in a mirror; a mirror kept through a failed fetch). All 14 pass on the 0.7.628 image.

Related: #14614 (the cause: pacing slowed loopback clones) and #14615 (the clone breaker).

Direction: #14605

🤖 Generated with Claude Code

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs