test: guard Cursor status polling SDK path - #83
Merged
Conversation
Co-authored-by: Parvez Kose <koseparvez@gmail.com>
Co-authored-by: Parvez Kose <koseparvez@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
parvezk
marked this pull request as ready for review
August 12, 2026 02:16
Author
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Owner
|
Internal change — no release note. Generated by Claude Code |
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
2 participants
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.
Risky behavior now covered
Agent.get(agentId, { apiKey })metadata instead of the streaminglistRuns/getRunpath that previously emitted uncaughtTransformErrors.running.Tests added
test/cursor-port.test.tsRegression value
These tests exercise the real port boundary rather than the adapter's fake port, so reverting the production polling fix or dropping the status fallback fails deterministically. A mutation to the streaming API path made both focused tests fail.
Validation
npm test— 37/37 passednpm run build— passednpx prettier --check test/cursor-port.test.ts— passed