Skip to content

Fix misleading debug startup errors - #150

Merged
Oz Zafar (ozzafar) merged 1 commit into
mainfrom
fix/144-debug-startup-errors
Sep 9, 2026
Merged

Fix misleading debug startup errors#150
Oz Zafar (ozzafar) merged 1 commit into
mainfrom
fix/144-debug-startup-errors

Conversation

@ozzafar

Copy link
Copy Markdown
Contributor

Summary

Fixes #144.

  • Report the matching pre-launch task name, nonzero exit code, and launch configuration instead of incorrectly suggesting that a language extension is missing.
  • Track newly started task executions within the relevant workspace, including labeled dependencies, and report failures even while VS Code is waiting on its task-error dialog.
  • Preserve startup and Testing API errors. Cancel readiness waits and dispose their listeners when startup finishes or fails.
  • Add regression coverage and update the changelog and architecture documentation.

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.
  • Reproduced the reporter's PowerShell Copy-Item positional-parameter error in a normal, isolated VS Code 1.134.0 window using a real launch.json, tasks.json, and MCP HTTP request through the production routing/control path.
  • MCP returned an error identifying the failed task and exit code 1 in approximately 1.5 seconds while the real task-error dialog remained open.
  • Confirmed Abort leaves no debug session and Debug Anyway starts the real Node debugger and pauses at the fixture breakpoint. Stopped the debugger, cleared fixture breakpoints, and closed the isolated window afterward.

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.

Report scoped pre-launch task failures, preserve startup errors, and cancel abandoned readiness waits.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@ozzafar
Oz Zafar (ozzafar) merged commit 0e097d8 into main Sep 9, 2026
1 check passed
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

✅ Extension Build Successful!

📦 VSIX artifact is ready for download

👉 View artifacts

Scroll down to the "Artifacts" section and download extension-vsix

To install: In VS Code, run Extensions: Install from VSIX... and select the downloaded file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading error messages given to agent

1 participant