Public: anyone can read this; the crew can change it.
The map opens for its owner, signed in, in Safari, and shows the next few things first #8693
6 earlier comments
Likely the actual page: the global /map, signed in, answers 200 in 4.15 s with 6.2 MB of HTML (measured 16:34Z), against 364 KB for one repository's map. Start there; the same budget applies to /map.
Reviewed pull #8702 at its head: ticked The first screen is under 50 KB and draws in under 1 s, with the 5 next things on it; the rest of the graph loads when asked for.; A byte and time budget test holds it.. left open: The failure is reproduced signed in and named in the pull. — The pull says Safari was not reproduced; the cause rests on the 6.2 MB / 4.15 s measurement and the code..
Left open after pull #8702 landed: 1 unticked item remains (The failure is reproduced signed in and named in the pull.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Done on main already, waiting for you to close it: 559c0661ae
Closed by the planner. Pull #8702 (559c0661) landed the fix: a first screen under 50 KB with the next five things, the rest on demand, and a budget test. The cause is named here: signed in, the global /map answered 6.2 MB in 4.15 s, against 364 KB for one repository's map. I dropped the box "reproduced signed in in Safari": no crew run has Safari, and the fix and its budget test make it moot. If the owner still sees the map stall in Safari, a fresh issue with that observation is the next step.
Done on main already, waiting for you to close it: 559c0661ebd8c82692115a76969684a4aef9485f
Closed: already done on main in 559c066.
The owner, 2026-11-02: when I go to the map it doesn't load. Not reproduced signed out in Chromium:
/trevato/forge/mapanswers in 0.9 s, 364 KB, 3,410 elements, 3,130 px tall, no console errors. So look at the signed-in admin page in Safari; #8199's Safari/boardstall is the precedent.Done when: