fix(vscuse): Auto-fix Feature_LocalDebug_Custom_API_without_AzureOpenAI_Keys (progress 2→57 steps, not a plan issue) - #16691
Closed
Tian Yuan (xiaolang124) wants to merge 5 commits into
Conversation
…2254` so the Welcome-dialog close step waits up to 60 seconds for its preconditions instead of force-clicking while VS Code is still loading.
…2254` to wait for the exact VS Code Welcome sign-in overlay before force-running its close click, preventing the startup race where the click ran before the dialog appeared.
…_012254` from the unreliable Welcome-dialog X to the captured “Continue without Signing In” action at (850, 634), removing stale target preconditions.
…e click in shared startup group `plan_r_0928_012254` with an Esc key press so the modal closes before the M365 sidebar step.
…l assertion to shared startup group `plan_r_0928_012254`, ensuring the VS Code Welcome dialog is closed before opening the M365 panel.
Tian Yuan (xiaolang124)
temporarily deployed
to
engineering
September 3, 2026 03:15 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Tian Yuan (xiaolang124)
temporarily deployed
to
engineering
September 3, 2026 03:15 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
❌ VscUse Test Plan — Tests failureWhy these tests: Selected 61 impacted test plan(s) changed in this PR (no product code modified). Branch diff: Results: ✅ 38 passed · ❌ 23 failed (of 61 plans) Plans run:
ℹ️ How were these tests selected?GitHub Copilot (GPT-5.6-sol, high reasoning) analysed the PR title, description, and the diff between |
Contributor
E2E Test Selection — AI SelectedWhy these tests: All changed files are under packages/tests/vscuse/**, which are handled by the separate vscuse pipeline and require no e2e tests. Cases selected (0): Need to run more tests?Comment on this PR:
Then re-run the workflow. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #16691 +/- ##
=======================================
Coverage 88.26% 88.26%
=======================================
Files 659 659
Lines 35786 35786
Branches 8618 8618
=======================================
Hits 31587 31587
Misses 2316 2316
Partials 1883 1883 🚀 New features to boost your workflow:
|
This branch was previously deployed
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.
VscUse Auto-Fix Results
Plan:
Feature_LocalDebug_Custom_API_without_AzureOpenAI_KeysStatus: 🔍 NOT A PLAN ISSUE (AI diagnosis after 6 attempt(s))
Initial Report: Link
Final Report: Link
Iteration Summary
plan_r_0928_012254so the Welcome-dialog close stplan_r_0928_012254to wait for the exact VS Codeplan_r_0928_012254from the unreliable WelcomeAI Diagnosis
How to Review
plans/Feature_LocalDebug_Custom_API_without_AzureOpenAI_Keys.jsonChanges Made to Test Plan
View diff
Generated by
vscuse-auto-fix.yml| model:gpt-5.6-sol