d3vmeh/dsh-turn-doctor

Measures each model request and names which timeout actually fired: dsh's guard, undici's timers, the SDK or the server.

Turns a timeout into a named culprit with evidence, because the UI otherwise shows only a final error message that several different layers can produce. Each report gives a verdict, the evidence behind it — for example no reply bytes in 300.6 seconds — and a fix such as raising a specific setting, installing a specific package, or checking whether the request was queued behind a busy slot on llama.cpp. It also catches failures that are easy to miss entirely, including failed compactions and tool timeouts, which otherwise look like something other than a timeout.

Development & Runtime ★ 1
View on GitHub ↗

Install

dsh plugin --profile web add dsh-turn-doctor

The npm line. It is a diagnostic, so the useful thing to know is what it does with the reading: it measures time to first byte, the longest gap between bytes and the total request time for each attempt, then names the most likely layer and suggests a specific fix rather than a generic one. Some verdicts point at another package, such as dsh-fetch-timeouts for Node's HTTP timers, which the page does not install for you.

Compatibility

It distinguishes layers that produce nearly identical text, which is the whole point: Request timed out. may be the SDK timer or undici's 300-second headers timeout, and terminated may be undici giving up on the body or the model server dying, so changing the wrong setting reproduces the same failure at the same wall-clock mark. The README's verdict table covers the dsh idle watchdog, both undici timers, the SDK request timer, an unreachable or crashed server, context overflow, empty responses, the llm-gate queue, GPU faults and a llama.cpp router reload.

Details

Alternatives

jorinyang/dsh-doctor · moonquake2004/dsh-doctor#plugin · Airmetro/dsh-update-checker

More plugins in Development & Runtime

Browse more in Development & Runtime

Guides for Development & Runtime plugins