test(app-control): update stop test for idempotent no-proxy behavior#30086
Merged
Conversation
… no proxy attached PR #30079 moved the app_control_stop short-circuit BEFORE the isAvailable() gate so a disconnected client cannot strand the singleton lock. After that change, stop succeeds as a no-op even when no proxy is attached, but this test still asserted the old isError behavior. Update the assertion to match the new contract (stop is idempotent).
This was referenced May 9, 2026
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
Original prompt
Fix the specific CI issue in this failing job only: https://github.com/vellum-ai/vellum-assistant/actions/runs/25591538830/job/75129999980
The failing job's only red signal was `conversation-surfaces-app-control.test.ts:140` — a stale assertion left behind when #30079 moved the `app_control_stop` short-circuit ahead of the `isAvailable()` gate to keep a disconnected client from stranding the singleton lock. Scope is intentionally limited to that one test.