Repository navigation
docs(troubleshooting): explain job/registered history load failure on pre-0.2.1-alpha.3 hosts - #20
Merged
Conversation
… pre-0.2.1-alpha.3 hosts Sessions written by a >= 0.2.1-alpha.3 host contain required job/registered and job/settled events that older persistence readers refuse as unknown, surfacing as a gateway/internal history-load error. This is the upstream forward-compatibility guard, not a plugin defect — record the diagnosis and the verified remedies so the 0.2.0-rc.2 support claim is not mistaken for coverage of newer-written logs.
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.
Summary
0.2.0-rc.2failure "历史加载失败： failed to observe session ... contains event type "job/registered" (seq 24) unknown to this harness" as an upstream forward-compatibility guard, not a plugin defect.job/registered/job/settledenteredKNOWN_SESSION_EVENT_TYPESinf899e87a1e(first shipped indsh-v0.2.1-alpha.3); they are written as required events with noignorablemarker (confirmed in the realsession.v4.jsonl.zstdat seq 24,kind:"bash").0.2.0-rc.2,0.2.1-alpha.1, andalpha.2lack both types, sovalidateStoredEventsthrowsSessionFormatUnsupportedError→SESSION_QUERY_PERSISTENCE_FAILED→gateway/internal→ chat history load error.SESSION_FORMAT_VERSIONis 4 on both sides; the failure is in event admission, not the version check.docs/troubleshooting/session-log-newer-harness.{md,en.md}, README index links, and a "session log read-back boundary" section indocs/reference/dsh-compatibility.mdclarifying that the declared0.2.0-rc.2support does not cover logs written by newer harnesses.0.2.1-alpha.3; no plugin-side fix is possible or safe.Test plan
pnpm docs:checkpasses (52 files, 502 links)pnpm compat:checkpasses — supported list, peer ORs, dev pins and installed packages agreejob/*absent fromKNOWN_SESSION_EVENT_TYPESondsh-v0.2.0-rc.2/dsh-v0.2.1-alpha.1/alpha.2, present ondsh-v0.2.1-alpha.3job/registeredat seq 24, noignorable)