LoggingDebugSession: does not create log file when running inline in vscode

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the LoggingDebugSession entry point and reproduce a trace:true launch from VS Code using the Mock Debug setup. Compare it with standalone Node and vscode-electron-run-as-node runs, checking the expected path.join(os.tmpdir(), "fmtk.log") location. Done means the inline VS Code launch creates the log file as expected.

Written by the indexing model from the issue text.

Description

LoggingDebugSession does not appear to ever create a log file (for trace:true launches) when running from vscode. Running standalone under node, or vscode-electron-run-as-node works fine.

I first ran into this issue in https://github.com/justarandomgeek/vscode-factoriomod-debug, which creates the trace log in path.join(os.tmpdir(), "fmtk.log"). Testing with Mock Debug, I was unable to find where its log should have been, and thus unable to determine for sure if it was creating it or not (but I believe not).

Dominant language
TypeScript
Stars
306
Forks
90
Avg merge
8h 36m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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.

More from microsoft/vscode-debugadapter-node

All issues in microsoft/vscode-debugadapter-node

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.