Skip to content

gallery: feature golang/go; a failed replay is named, not 'no commits' - #11

Merged
azank1 merged 2 commits into
mainfrom
site/featured-and-failed-replays
Oct 13, 2026
Merged

azank1 merged 2 commits into
mainfrom
site/featured-and-failed-replays

Conversation

@azank1

@azank1 azank1 commented Oct 13, 2026

Copy link
Copy Markdown
Owner

Two accuracy fixes found while rebuilding the gallery on the new engine.

1. The featured row showed nine cities. rust-lang/rust is 998 MB on disk, under the 1.5 GB cap, but it runs out of the builder's memory at replay time (production, today: "too big for the hosted builder" after 35.9 s). So its city never existed, and the featured route skipped its slot.

golang/go, the other language repo of its kind, takes the slot. A production build replayed it in 40 s: 3,748 commits fetched, 99.9 MB of packs. The city's 3,491 commits are exactly GitHub's non-merge commits authored inside the window; how that number relates to GitHub's 3,748 is the next PR.

2. A city whose replays all failed said "no commits in the last year". For rust-lang/rust that is 34,368 commits. fa997db covered repos over the size cap at discovery; a repo under the cap can still fail at replay time (memory, time, fetch).

finishBuild now answers 422 repo_failed whenever a repo with commits has no record. The answer names the failed repos with their commit counts. "No commits" remains only for a city that really has none.

The page fills in each repo's reason from its row in the build list. It says how many commits the repo has, adds that one hosted build cannot replay them only when the reason is too big or too long, and offers Try again. Rendered headlessly against the real page, with only fetch mocked to production's answers:

rust-lang/rust could not be replayed: too big for the hosted builder. It has 34,368 commits from the last year, more than one hosted build can replay.
[Try again] [See rust-lang's city] [Explore other cities]

Tests. A new finish-step test covers both answers: repo_failed with the name and 34,368 commits, and empty for a city with nothing to draw. It fails without the fix. Suite green; typecheck clean.

Independent of #10; no file overlap.

…ust-lang/rust's place

rust-lang/rust (998 MB, under the 1.5 GB cap) runs out of memory at replay time, so
it never had a city and its featured slot stayed empty: the row showed nine cities.
golang/go, the other language repo of its kind, replays in 40 s (3,748 commits fetched,
99.9 MB of packs).
…ommits"

When every repo of a city failed to replay, finish found nothing to draw and answered
"no commits in the last year". For rust-lang/rust that is 34,368 commits. The
discovery-time check from fa997db only covers repos over the size cap; a repo under it
can still fail at replay time (memory, time, fetch).

finish now answers 422 repo_failed, naming the failed repos with their commit counts,
whenever a repo with commits has no record; "no commits" remains for a city that really
has none. The page fills in each failed repo's reason from its row in the build list,
says how many commits it has (and, for too big or too long, that one hosted build cannot
replay them), and offers Try again.
@vercel

vercel Bot commented Oct 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
commit-city Ready Ready Preview Oct 13, 2026 12:55pm UTC

@azank1
azank1 marked this pull request as ready for review October 13, 2026 13:07
@azank1
azank1 merged commit 1fe876e into main Oct 13, 2026
5 checks passed

This branch was successfully deployed

1 active deployment
Preview — d405a6e2 Deployed Oct 13, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant