Repository navigation
fix(harness): reload continuation state after Substrate restore - #2823
Merged
Merged
Conversation
Signed-off-by: Jet Chiang <[email protected]>
github-actions
Bot
added
bug
EItanya
approved these changes
Sep 14, 2026
QuentinBisson
added a commit
to giantswarm/kagent-upstream
that referenced
this pull request
Sep 22, 2026
…drops the rows upstream merged Continuation re-read (kagent-dev#2823), the two controller metrics commits (kagent-dev#2886), the compaction cherry-picks (kagent-dev#2790) and the harness apk upgrade (kagent-dev#2756) leave the table; the chart's harness.compaction row joins it.
QuentinBisson
added a commit
to giantswarm/kagent-upstream
that referenced
this pull request
Sep 22, 2026
…drops the rows upstream merged Continuation re-read (kagent-dev#2823), the two controller metrics commits (kagent-dev#2886), the compaction cherry-picks (kagent-dev#2790) and the harness apk upgrade (kagent-dev#2756) leave the table; the chart's harness.compaction row joins it.
QuentinBisson
added a commit
to giantswarm/kagent-upstream
that referenced
this pull request
Sep 22, 2026
…drops the rows upstream merged Continuation re-read (kagent-dev#2823), the two controller metrics commits (kagent-dev#2886), the compaction cherry-picks (kagent-dev#2790) and the harness apk upgrade (kagent-dev#2756) leave the table; the chart's harness.compaction row joins it.
QuentinBisson
added a commit
to giantswarm/kagent-upstream
that referenced
this pull request
Sep 22, 2026
…drops the rows upstream merged Continuation re-read (kagent-dev#2823), the two controller metrics commits (kagent-dev#2886), the compaction cherry-picks (kagent-dev#2790) and the harness apk upgrade (kagent-dev#2756) leave the table; the chart's harness.compaction row joins it.
QuentinBisson
added a commit
to giantswarm/kagent-upstream
that referenced
this pull request
Sep 22, 2026
…drops the rows upstream merged Continuation re-read (kagent-dev#2823), the two controller metrics commits (kagent-dev#2886), the compaction cherry-picks (kagent-dev#2790) and the harness apk upgrade (kagent-dev#2756) leave the table; the chart's harness.compaction row joins it.
QuentinBisson
pushed a commit
to giantswarm/kagent-upstream
that referenced
this pull request
Sep 22, 2026
| 2026-09-22 18:30 | `800015d` | `844ea06` (2026-09-22) | `5df8ba3` → `9276b46` | 89 + 3 own (the chart's `harness.compaction`, the pin annotation, the Substrate pin on the line's dev build `0.0.0-dev.giantswarm.2026-09-22.13-15-52.hb3137f0` of v0.2.0-beta4) | `3999b3b` fix(harness): re-read the continuation state from /data on every turn — superseded upstream (kagent-dev#2823, `42d3301`); `e66fb5a` `229ae56` `cc11cc9` `646e7fe` the context compaction cherry-picks — superseded upstream (kagent-dev#2790, `7471879`, on the Harness); `79d5300` `7485ebf` the controller metrics — merged upstream squashed (kagent-dev#2886, `844ea06`) | by hand — the sync ([#60](#60)) stopped on the continuation patch; the third step of the 2026-09-22 three-line move (agentgateway `main@08f4563b`, Substrate v0.2.0-beta4); the per-source git credential reshaped onto upstream kagent-dev#2868's gateway injection (kagent-dev#2899), upstream's new `nightly.yaml` publish and its three actions removed in the fork's CI commit; candidate [#64](#64), 35 checks green |
QuentinBisson
added a commit
to giantswarm/kagent-upstream
that referenced
this pull request
Sep 24, 2026
…drops the rows upstream merged Continuation re-read (kagent-dev#2823), the two controller metrics commits (kagent-dev#2886), the compaction cherry-picks (kagent-dev#2790) and the harness apk upgrade (kagent-dev#2756) leave the table; the chart's harness.compaction row joins it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After #2715 , Substrate can restore
/datainto a process resumed from a golden snapshot after the continuation store is initialized. Codex and Claude were reading stale in-memory state that was preserved in the golden snapshot (with an empty initial session ID), despitestate.jsoncontaining the correct native session ID. As a result, each subsequent turn started a new session and overwrote the restored continuation state.This change makes
state.jsonauthoritative by reloading it on everyLoadandBind.