From 0e469f846194e34513b35deeffbbf2ca87653c57 Mon Sep 17 00:00:00 2001 From: dmmdea Date: Wed, 11 Nov 2026 14:42:56 -0500 Subject: [PATCH] release: 0.231.0 One change, merged to main through its own pull request (#852) after one security pass and green CI: - A text lease on a node's GPUs no longer refuses an accel job: an NPU or TPU is not a card a lease names. - The owner of a shared accelerator tool is tried first, and when it cannot take the call the next device that serves the name answers through its own tool row; the result carries fallback{from,reason,served_by}. An embedding moves to another device only with any_space:true. - out_path is checked before a fallback runs, and the Coral sidecar guards its own writes (the two findings of the security pass). - ADR 0102, which supersedes one consequence of ADR 0068. Deletes: changes/unreleased/fix-accel-independent-and-fallback.md --- .printing-press.json | 2 +- CHANGELOG.md | 13 +++++++++++++ VERSION | 2 +- .../fix-accel-independent-and-fallback.md | 10 ---------- internal/buildinfo/buildinfo.go | 2 +- 5 files changed, 16 insertions(+), 13 deletions(-) delete mode 100644 changes/unreleased/fix-accel-independent-and-fallback.md diff --git a/.printing-press.json b/.printing-press.json index 4a4c28ad3..47a525dc0 100644 --- a/.printing-press.json +++ b/.printing-press.json @@ -1,7 +1,7 @@ { "api_name": "local-offload", "cli_name": "local-offload", - "version": "0.230.0", + "version": "0.231.0", "printing_press_version": "hand-built-2026-06-12", "generated_at": "2026-06-12", "description": "Local offload harness - delegate grunt work (summarize/classify/extract/triage, plus vision, OCR, transcription and media generation) to a free local Gemma-family cascade via llama.cpp; MCP + CLI; the cascade never calls cloud and defers to the caller instead. The opt-in offload_nim tool is the only remote model surface; the opt-in offload_browse lane drives the operator's own browser with typed choices from a loopback decision endpoint the operator runs.", diff --git a/CHANGELOG.md b/CHANGELOG.md index 5da5038b5..d281ccf0e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,19 @@ Releases before 0.190.0 are archived verbatim under [docs/changelog/](docs/chang ## [Unreleased] +## [0.231.0] - 2026-11-11 - an accelerator answers while the node's GPUs are leased, and a shared accelerator tool falls back to the next device + +### Fixed - an accelerator answers while the node's GPUs are leased, and a shared accelerator tool falls back to the next device + +- **Why.** Two rules kept accelerators idle while callers waited, both seen 2026-11-11. A text lease on a node's GPUs made `/fleet/dispatch` refuse every forwarded accelerator call with `node leased` for the whole measurement window, although an `accel` job runs on an NPU or TPU and never on a leased card. And a shared tool (`offload_object_detect`, `offload_classify_image`, `offload_image_embed`, `offload_semantic_segment`) had one owner and no second choice (ADR 0068: "nothing falls back at call time"), so with the owner's node off or refusing the tool deferred while two other devices that serve the same name were reachable. +- **What it does: the lease.** A GPU lease never refuses an `accel` job (`fleetnode.textLeaseAgainst`). Every other task type keeps its reading, and the lease is published in health as before. +- **What it does: the fallback.** The owner of a shared tool is tried first. When it cannot take the call (a defer, or a sidecar refusal about the device such as a missing model or a disabled NPU), the call runs on the next device that serves the name, in the listed order, through that device's own tool row and with only the arguments its schema declares. The answer carries `fallback: {from, reason, served_by}`; when no device answers, the owner's defer carries `fallback_tried`. A refusal of the caller's input is the answer and is not retried elsewhere. Nothing is remembered between calls. Both surfaces (the MCP tools and the agent loop) use one function, `agent.AccelFallback`, and a node running a forwarded job still cannot forward again. +- **Embeddings.** `offload_image_embed` and `offload_text_embed` move to another device only when the caller passes `any_space: true`, because that vector is in another space; without it the defer carries `fallback_withheld`. The argument is added to the schema only on a box where a fallback device exists. +- **Safety.** One security pass ran on the change; both findings are fixed here. A fallback could hand `out_path` to a device whose sidecar checks nothing: the Coral's `semantic_segment` overwrote any path it was given, the caller's own image included. The fallback now applies the lane's rule before any device runs (`out_path` is never the input image, its directory must exist, an existing target is replaced only when it is a regular PNG file; otherwise the defer carries `fallback_withheld`), and the Coral sidecar applies the same rule itself and writes through a temporary file. A fallback device that answers JSON `null` is a defer, not a crash. +- **What a caller sees.** A tool with a fallback device carries a `FALLBACK:` sentence in its description (kept by the compact tools profile), and `offload_status.accelerators..fallback_for` lists the names a device answers for another owner. A box with one device, or with no shared name, advertises exactly what it did. +- **Check.** Two tests, one per incident: an `accel` dispatch under a text lease is admitted while an image job on the same node is still refused, and through the MCP surface a tool whose owner has no node to reach runs on the next device with the owner named, an embedding stays put without `any_space`, and `any_space` never reaches a sidecar. +- **Docs.** ADR 0102 (supersedes one consequence of ADR 0068), `docs/systems/accelerators.md`, `docs/systems/gpu-lease.md`, the operator guide's lease paragraph. + ## [0.230.0] - 2026-11-11 - release: 0.230.0 ### Fixed - a Windows swap sees a node started through a junction diff --git a/VERSION b/VERSION index cd52fec52..fd611fd75 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.230.0 +0.231.0 diff --git a/changes/unreleased/fix-accel-independent-and-fallback.md b/changes/unreleased/fix-accel-independent-and-fallback.md deleted file mode 100644 index 603adc4d0..000000000 --- a/changes/unreleased/fix-accel-independent-and-fallback.md +++ /dev/null @@ -1,10 +0,0 @@ -### Fixed - an accelerator answers while the node's GPUs are leased, and a shared accelerator tool falls back to the next device - -- **Why.** Two rules kept accelerators idle while callers waited, both seen 2026-11-11. A text lease on a node's GPUs made `/fleet/dispatch` refuse every forwarded accelerator call with `node leased` for the whole measurement window, although an `accel` job runs on an NPU or TPU and never on a leased card. And a shared tool (`offload_object_detect`, `offload_classify_image`, `offload_image_embed`, `offload_semantic_segment`) had one owner and no second choice (ADR 0068: "nothing falls back at call time"), so with the owner's node off or refusing the tool deferred while two other devices that serve the same name were reachable. -- **What it does: the lease.** A GPU lease never refuses an `accel` job (`fleetnode.textLeaseAgainst`). Every other task type keeps its reading, and the lease is published in health as before. -- **What it does: the fallback.** The owner of a shared tool is tried first. When it cannot take the call (a defer, or a sidecar refusal about the device such as a missing model or a disabled NPU), the call runs on the next device that serves the name, in the listed order, through that device's own tool row and with only the arguments its schema declares. The answer carries `fallback: {from, reason, served_by}`; when no device answers, the owner's defer carries `fallback_tried`. A refusal of the caller's input is the answer and is not retried elsewhere. Nothing is remembered between calls. Both surfaces (the MCP tools and the agent loop) use one function, `agent.AccelFallback`, and a node running a forwarded job still cannot forward again. -- **Embeddings.** `offload_image_embed` and `offload_text_embed` move to another device only when the caller passes `any_space: true`, because that vector is in another space; without it the defer carries `fallback_withheld`. The argument is added to the schema only on a box where a fallback device exists. -- **Safety.** One security pass ran on the change; both findings are fixed here. A fallback could hand `out_path` to a device whose sidecar checks nothing: the Coral's `semantic_segment` overwrote any path it was given, the caller's own image included. The fallback now applies the lane's rule before any device runs (`out_path` is never the input image, its directory must exist, an existing target is replaced only when it is a regular PNG file; otherwise the defer carries `fallback_withheld`), and the Coral sidecar applies the same rule itself and writes through a temporary file. A fallback device that answers JSON `null` is a defer, not a crash. -- **What a caller sees.** A tool with a fallback device carries a `FALLBACK:` sentence in its description (kept by the compact tools profile), and `offload_status.accelerators..fallback_for` lists the names a device answers for another owner. A box with one device, or with no shared name, advertises exactly what it did. -- **Check.** Two tests, one per incident: an `accel` dispatch under a text lease is admitted while an image job on the same node is still refused, and through the MCP surface a tool whose owner has no node to reach runs on the next device with the owner named, an embedding stays put without `any_space`, and `any_space` never reaches a sidecar. -- **Docs.** ADR 0102 (supersedes one consequence of ADR 0068), `docs/systems/accelerators.md`, `docs/systems/gpu-lease.md`, the operator guide's lease paragraph. diff --git a/internal/buildinfo/buildinfo.go b/internal/buildinfo/buildinfo.go index 8fdeef54d..363f6036c 100644 --- a/internal/buildinfo/buildinfo.go +++ b/internal/buildinfo/buildinfo.go @@ -29,7 +29,7 @@ import ( // `version` const aliases it (keeping the VERSION-file agreement test in // main_test.go binding), and fleet/pipeline stampers read it directly so no // plumbing carries it through config. -const Version = "0.230.0" +const Version = "0.231.0" var ( buildOnce sync.Once