You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(calltree): show where a slow callers search spent its time
- The panel's engine label was a prediction; it now shows what the
response actually used and how long it took, with the breakdown on
hover: index call, file resolution with file count, rg scan, raw hit
count, and the server's build stamp
- A slow corporate machine cannot be reproduced remotely, so one click
there becomes the measurement: a large index number points at the
process-spawn path (EDR scans each attempt; the transport probing is
known to cost seconds), a large resolve number at storage, a scan
number at the rg fallback, and the build stamp settles whether the
fix being tested is even running
- The binary now knows its own commit via the VCS info go build embeds,
shown at startup and in the response header; two rounds of "still
slow" reports have already turned out to be a stale binary
0 commit comments