test(langgraph): characterize checkpoint replay and write uncertainty - #1142
Merged
Merged
Conversation
Forward the existing AbortSignal to LangGraph state writes and cover cancellation through normal and protected transports with real HTTP regressions. Include the generated API documentation and parity inventory update.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
marked this pull request as ready for review
September 23, 2026 20:37
blove
enabled auto-merge (squash)
September 23, 2026 20:37
Contributor
Contributor
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
1 participant
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.
Checkpoint replay, reconnect, and a failed write response have different execution consequences. Add three tests against the existing local client-tools graph and locked LangGraph API to make those consequences explicit before implementing a neutral checkpoint command.
The setup exposes local API/journal URLs to test workers. Fixtures stay local; threads and the fault-injection proxy are cleaned up. This changes only three e2e files and adds no production API.
Validation: the native client-tools e2e target passes all 7 tests, including the 3 new protocol tests and 4 existing browser tests. Repeated implementation runs and a separate parent run passed. New-spec ESLint, standalone TypeScript, and diff checks pass; the setup's preexisting relative ports import still triggers a direct Nx boundary lint error. Independent spec and code-quality reviews approved.
Provenance: LangGraph API 0.9.0, LangGraph 1.2.4, in-memory runtime 0.29.0, JavaScript SDK 1.10.0, and published middleware 0.1.0 from the existing lock. These tests establish final persistence after reconnect, not immediate durability of every event or retention across server restarts. They do not exercise browser tool execution or durable execution-store claims.
Based on main after #1138 merged. The signed integration head has the identical complete tree as the previously CI-tested head, and a fresh full native e2e run passes all 7 tests. Require current-head CI before merging.