Skip to content

Bundle Accord 0.6.2 - #114

Merged
data-angel merged 1 commit into
mainfrom
chore/accord-0.6.2
Nov 6, 2026
Merged

data-angel merged 1 commit into
mainfrom
chore/accord-0.6.2

Conversation

@data-angel

Copy link
Copy Markdown
Contributor

Bundles Accord 0.6.2 (Enntity/accord#4). An Accord coordinator restart, such as systemd recovering from an OOM kill, no longer revokes an unexpired reservation window. Before, the managed provider stopped the holder's hold and restored LLooM's own serving hours before the window's deadline.

  • Vendored with scripts/vendor-accord.py from the qualified package: sha256 f69cc6aff759278551e33e2f44ca8e1e910fd90b2f09db98fe48e016df1a97b9, 287 Accord tests plus recovery demos, all 7 CI jobs green.
  • LLooM's provider already answers a repeat prepare for an active generation with success, so no LLooM code changes.
  • Only the coordinator and driver changed in the vendored code. The client, bootstrap and telemetry modules LLooM imports are unchanged.
  • python3 scripts/check-vendor.py OK.
  • node --test test/accord-install.test.mjs test/schedule.test.mjs test/schedule-integration.test.mjs test/workload-cli.test.mjs test/workload-runner.test.mjs passes 20/20, and test/host-memory.test.mjs passes.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@data-angel
data-angel merged commit f50ca9c into main Nov 6, 2026
2 checks passed
@data-angel
data-angel deleted the chore/accord-0.6.2 branch November 6, 2026 16:13
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