-
Notifications
You must be signed in to change notification settings - Fork 263
test(control-plane): stabilize cancel integration test #643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ColeMurray
merged 1 commit into
ColeMurray:main
from
donnfelker:upstream-stabilize-cancel-integration-test
May 17, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extract timeout literals to named constants with unit suffixes.
Lines 36 and 43 use literal timeout values (1000 and 10). As per coding guidelines, TypeScript timeout values should be defined as named constants with
Mssuffix and defined once rather than restated as literals.⏱️ Proposed fix to extract timeout constants
Add constants at the top of the file (after imports):
Then update the function:
async function waitForSandboxSpawn(stub: DurableObjectStub): Promise<void> { - const deadline = Date.now() + 1000; + const deadline = Date.now() + SANDBOX_SPAWN_TIMEOUT_MS; while (Date.now() < deadline) { const rows = await queryDO<{ status: string }>(stub, "SELECT status FROM sandbox LIMIT 1"); if (rows[0]?.status === "connecting") { return; } - await new Promise((resolve) => setTimeout(resolve, 10)); + await new Promise((resolve) => setTimeout(resolve, SANDBOX_SPAWN_POLL_INTERVAL_MS)); } throw new Error("Timed out waiting for sandbox spawn"); }As per coding guidelines: Use seconds for Python timeouts and milliseconds for TypeScript timeouts, encoding the unit in variable names (TypeScript:
timeoutMs,TIMEOUT_MS). Define each default timeout value exactly once as a named constant and import it everywhere rather than restating literal values.🤖 Prompt for AI Agents