Skip to content

Fix selected-frame metadata in debug status - #184

Merged
Oz Zafar (ozzafar) merged 1 commit into
mainfrom
fix/179-selected-frame-status
Oct 25, 2026
Merged

Oz Zafar (ozzafar) merged 1 commit into
mainfrom
fix/179-selected-frame-status

Conversation

@ozzafar

Copy link
Copy Markdown
Contributor

Summary

Validation

  • Both new regression tests failed before the fix.
  • npm run compile: passed.
  • npm run lint: passed.
  • Focused VS Code extension suites (debugStatus, debugSessionTracker, debugState): 72 passing.
  • git diff --check: passed.
  • Live DebugMCP inspection was unavailable because this workspace was not registered with the connected server.

Existing PR check

No open PR addressing #179 was found. Related PR #149 handles sourceless pause detection, not selected-frame metadata.

Not merged; awaiting maintainer confirmation.

Keep frame name and source aligned with the selected evaluation frame instead of the top stack frame. Preserve stack order and leave metadata unavailable when the selected frame is absent.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: a882e001-7e0e-4256-8a20-8eaec9c947f4
@github-actions

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.

get_debug_status mixes the selected frame ID with top-frame source metadata

1 participant