Fix misleading debug startup errors - #150
Merged
Merged
Conversation
Report scoped pre-launch task failures, preserve startup errors, and cancel abandoned readiness waits. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
✅ Extension Build Successful!📦 VSIX artifact is ready for download Scroll down to the "Artifacts" section and download To install: In VS Code, run |
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
Fixes #144.
Validation
npm test -- --code-version 1.134.0 --timeout 15000: 179 passing, including compile, bundle, and lint via pretest. Obsolete generated test output with no corresponding source on this branch was archived before the clean run.Copy-Itempositional-parameter error in a normal, isolated VS Code 1.134.0 window using a reallaunch.json,tasks.json, and MCP HTTP request through the production routing/control path.Limitations
VS Code task events do not expose terminal output and may omit an exit code. Responses point to the task terminal for the original command error and use neutral guidance when no specific failure is available. Reporting a task failure does not dismiss VS Code's dialog or cancel its pending launch request. Task-identifier objects and dynamically supplied task configurations are left to VS Code rather than resolved by the diagnostics observer.