Repository navigation
fix(jobs-bridge): allow timeout_ms up to 15 min (v0.3.69) - #368
Merged
Merged
Conversation
Every live inference worker is a CPU node. A moshcode `agents c0mpute` turn (~1k tokens on qwen2.5:7b / the 9B) takes 3-5 min: winners bid eta_s 218-301, bonita and vienna both logged `inference: answered` 3-5 min in, and the Infernet bridge had already 504'd, so the result push got "no result expected from this peer". Infernet then re-ran the same job on a provider daemon on the same box, growing a backlog until nothing answered inside the client's 10 min. MAX_TIMEOUT_MS 300 s -> 900 s so Infernet can ask for 7 min (its PR). The default stays 60 s; the requester chooses. Clamp moved into request_timeout() with a unit test. DIP-0030 updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan14 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
moshcode agents c0mputeaborted after 600 s on every prompt. Every live inference worker is CPU-only; an agent-sized turn takes 3-5 min (bidseta_s218-301). bonita and vienna both loginference: answered3-5 min in, but the Infernet jobs bridge had already returned 504 at 180 s (Infernet's ask; the bridge capped at 300 s anyway), so the result push failed withno result expected from this peer. Infernet then re-ran the job on a provider daemon on the same box, so a backlog built up and nothing answered.What
MAX_TIMEOUT_MS300 s -> 900 s. The default stays 60 s; the requester picks its own budget.request_timeout()+ unit test.Companion: Infernet asks 420 s and calls the bridge over node:http (undici dies at 300 s waiting for headers).
🤖 Generated with Claude Code