Commit a528bbb
committed
fix(miner): handle CHALLENGE_UNAVAILABLE without burning LLM retries
When the LLM verifier is temporarily down, skill-inscribe returns
CHALLENGE_UNAVAILABLE with a new challenge. Previously this code
entered the standard challenge retry loop (maxChallengeRetries=5),
which immediately called answerChallenge 5 times while the verifier
was still unavailable — wasting LLM calls and leaving miners stuck.
Fix: remove CHALLENGE_UNAVAILABLE from IsChallenge(). Instead, handle
it explicitly before the retry loop: save the new challenge to state
and return an error so the outer loop applies networkBackoff. On the
next cycle, the saved challenge is answered and submitted normally.
This prevents the cascading failure mode where all miners enter an
infinite loop of requesting new challenges without submitting answers.1 parent 1e16d55 commit a528bbb
2 files changed
+20
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
180 | 180 | | |
181 | 181 | | |
182 | 182 | | |
183 | | - | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
184 | 188 | | |
185 | 189 | | |
186 | 190 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
377 | 377 | | |
378 | 378 | | |
379 | 379 | | |
| 380 | + | |
| 381 | + | |
| 382 | + | |
| 383 | + | |
| 384 | + | |
| 385 | + | |
| 386 | + | |
| 387 | + | |
| 388 | + | |
| 389 | + | |
| 390 | + | |
| 391 | + | |
| 392 | + | |
| 393 | + | |
| 394 | + | |
380 | 395 | | |
381 | 396 | | |
382 | 397 | | |
| |||
0 commit comments