Extend Namespace dispatcher timeout
Some checks failed
Build Rust / Cargo Test (push) Successful in 5m47s
Cache: Publish Nix / Publish Nix Cache (push) Failing after 20s
Build Site / Next.js Build (push) Failing after 4s
Lint Governance / BEP Metadata (push) Successful in 1s

This commit is contained in:
Conrad Kramer 2026-06-07 09:05:05 -07:00
parent 4d7c19e593
commit 4f8d58965b
7 changed files with 6 additions and 1 deletions

View file

@ -116,6 +116,9 @@ The same change also makes the forge itself the release authority: release tags
- Do not destroy Namespace Linux runners until `nsc describe` shows a real
terminal container state or tombstone. Empty describe payloads mean the
environment is still starting, not that the one-job runner has finished.
- Keep the autoscaler-to-dispatcher HTTP timeout longer than the runner TTL.
Dispatch requests intentionally block until the one-job runner exits, so short
HTTP client timeouts cancel macOS provisioning mid-bootstrap.
- Run forge Namespace services with the repo-owned `nsc` package and keep it
current with the token format expected by Namespace. `nsc 0.0.520` is the
first required baseline for revokable token-file auth. The dispatcher and