Plugin load race, fork checkpoint, compression fixes
Cluster 131496. Data as of
Nothing open on GitHub. Fix merged in #133054 on 5 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #133054. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #133032. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a race condition in plugin loading, incorrect checkpoint requirements for certain fork types, and a telemetry miscategorization of compression outcomes. The fixes span agent, compression, and telemetry components but share a common thread around plugin initialization and checkpoint API errors.
Open issues0
Open PRs0
Fixes on record
-
#133032 fix(compression): serialize plugin loads and exempt persistence-isolated forks from checkpoint_required (salvage #131509)
files:
agent/conversation_compression.py,gateway/run_agent_cache.py,plugins/plugin_loader.py,tests/agent/test_pre_compress_checkpoint_contract.py,tests/plugins/test_plugin_loader.py -
#133054 fix(telemetry): compression attempts that could not fail count as skipped, not failed
files:
agent/conversation_compression.py,agent/conversation_compression_telemetry.py,hermes_cli/observability/shared_metrics_events.py,tests/agent/test_compression_attempt_telemetry.py,tests/agent/test_compression_stall_interrupt.py,website/docs/developer-guide/relay-shared-metrics.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#131509 fix(agent): serialize plugin loads and skip fork checkpoints · merged via another change →
3a6d709,#133032
Closed issues · 1
- Closed#131496Compaction fails with 'no active provider implements checkpoint API v2': plugin-loader race and review forks
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab