microsoft / microsoft/vscode-java-debug

No step over details in telemetry

Open
#638 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged debt enhancement
Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Description

Environment
  • Operating System: Windows/Mac/Linux
  • JDK version: 8/11/12
  • Visual Studio Code version: 1.37.1
  • Java extension version: 0.47.0
  • Java Debugger extension version: 0.21.0
Steps To Reproduce
  1. Config path VSCODE_LOGS=C:\Users\xx to set local log location by environment variables
  2. Start vscode by command code --verbose under log folder
  3. Open a test project and do something about step over, step in and step out.
  4. Open vscode-java-debug.txt under log folder.
Current Result

Telemetry log no step over details.

Expected Result

Should have step over details in telemetry

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by setting VSCODE_LOGS, starting VS Code with code --verbose, and performing step over, step in, and step out in a test project. Inspect vscode-java-debug.txt and trace how these debugger actions are represented in telemetry. Done means the telemetry log contains step-over details as well as the other stepping actions.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
devtools, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.