Skip to content

fix(jobs-bridge): allow timeout_ms up to 15 min (v0.3.69) - #368

Merged
ralyodio merged 1 commit into
masterfrom
fix/jobs-bridge-timeout-900s
Nov 14, 2026
Merged

ralyodio merged 1 commit into
masterfrom
fix/jobs-bridge-timeout-900s

Conversation

@ralyodio

Copy link
Copy Markdown
Collaborator

Why

moshcode agents c0mpute aborted after 600 s on every prompt. Every live inference worker is CPU-only; an agent-sized turn takes 3-5 min (bids eta_s 218-301). bonita and vienna both log inference: answered 3-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 with no 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_MS 300 s -> 900 s. The default stays 60 s; the requester picks its own budget.
  • Clamp extracted to request_timeout() + unit test.
  • DIP-0030 range updated.
  • v0.3.69 (the bridge container auto-upgrades).

Companion: Infernet asks 420 s and calls the bridge over node:http (undici dies at 300 s waiting for headers).

🤖 Generated with Claude Code

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>
@github-actions

Copy link
Copy Markdown

ThreatCrush Security Scan

14 finding(s)

HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4

Severity Rule Location
HIGH js-ssrf-outbound-request apps/web/public/sw.js:24
HIGH sh-remote-script-execution scripts/install.sh:606
MEDIUM js-unescaped-html-sink apps/web/src/app/blog/[slug]/page.tsx:53
MEDIUM js-unescaped-html-sink apps/web/src/app/layout.tsx:109
MEDIUM sql-template-interpolation apps/web/src/lib/chat/convo-store.ts:116
MEDIUM sql-template-interpolation apps/web/src/lib/chat/convo-store.ts:117
MEDIUM sql-template-interpolation apps/web/src/lib/chat/push.ts:476
MEDIUM js-dynamic-code-execution apps/web/src/lib/router/verify.ts:91
MEDIUM sh-remote-script-execution scripts/dev-setup.sh:25
MEDIUM sh-eval-expansion scripts/dev-setup.sh:35
LOW py-ssrf-outbound-request examples/business-strategist-agent/chat.py:37
LOW py-ssrf-outbound-request examples/business-strategist-agent/train.py:54
LOW secret-generic-credential node/crates/c0mpute-core/src/webhook.rs:1171
LOW py-path-traversal node/crates/c0mpute-core/tests/fixtures/fake-infernet-text:29

Snippets are redacted; ThreatCrush never prints matched credential material.

@ralyodio
ralyodio merged commit 77faa99 into master Nov 14, 2026
17 checks passed
@ralyodio
ralyodio deleted the fix/jobs-bridge-timeout-900s branch November 14, 2026 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant