# fix\(server\): call stall candidates leads and keep 1000 stalls · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/869c51b248e88c8faccf61cf14979da45f686a20)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 869c51b248e88c8faccf61cf14979da45f686a20

Requested commit: 869c51b248e88c8faccf61cf14979da45f686a20

Commit: 869c51b248e88c8faccf61cf14979da45f686a20

Tree: 2d33da4dfb4b522b078afb1e322cc848e099e234

Author: Victor Vogel

Committer: Victor Vogel

## Message

```
fix(server): call stall candidates leads and keep 1000 stalls

The docs and the stallCandidates comment said the first candidate is
the span that blocked. The match is against the whole sample window, so
a slow span that ended before the stall can rank first. Describe the
candidates as leads, shortest first.

A line with candidates is about 1.5 KB, so a 1 MB stall log held about
700 per file and broke the documented last 1000 or more stalls. Raise
the cap to 1.5 MB, about 1,000 per file, and restore that promise.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [bef882cfef03c071e116be78287ba203ad46d5ff](https://git.cafe/pingdotgg/t3code/commit/bef882cfef03c071e116be78287ba203ad46d5ff?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/869c51b248e88c8faccf61cf14979da45f686a20?format=markdown)