microsoft / microsoft/vscode-debugadapter-node
LoggingDebugSession: does not create log file when running inline in vscode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 306
- Forks
- 90
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 3
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).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- node.js, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100