vscode: Elements in args-list does not update when restarting debug session
Issue Type: Bug
- Create a launch.js for a node.js script.
- Set an args-field, like this in your launch.json: “args”: [“–update”, “filename.json”, “filename2.json”]
- Set a breakpoint somewhere in your js-script.
- Run the debug-session, let VS Code stop at the breakpoint.
- Now, make a change to the update the args-list: “args”: [“–update”, “someOtherFile.json”, “filename2.json”]
- Restart the debug-session (Ctrl+Shift+F5)
- The script still uses the old parameter-list.
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z) OS version: Windows_NT x64 10.0.18363
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i9-9900K CPU @ 3.60GHz (16 x 3600) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.89GB (23.69GB free) |
| Process Argv | –crash-reporter-id 4f8c59a8-5f72-44b3-a421-86f3d9ddce35 |
| Screen Reader | no |
| VM | 0% |
Extensions (16)
| Extension | Author (truncated) | Version |
|---|---|---|
| Bookmarks | ale | 13.0.3 |
| xml | Dot | 2.5.1 |
| haxe-hl | Hax | 1.1.1 |
| template-string-converter | meg | 0.4.7 |
| prettify-json | moh | 0.0.3 |
| vscode-docker | ms- | 1.10.0 |
| remote-wsl | ms- | 0.53.4 |
| cmake-tools | ms- | 1.6.0 |
| vscode-js-profile-flame | ms- | 0.0.14 |
| vshaxe | nad | 2.22.1 |
| lime-vscode-extension | ope | 1.4.2 |
| cmake | twx | 0.0.17 |
| hxcpp-debugger | vsh | 1.2.4 |
| gitblame | wad | 6.0.2 |
| codedox | wig | 1.3.1 |
| propertylist | zho | 0.0.2 |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244cf:30256637
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
dockersubset:30265998
pythontb:30265425
vspre833cf:30267465
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 35 (34 by maintainers)
Commits related to this issue
- debug session: pass configuration as args for restart #118196 — committed to microsoft/vscode by isidorn 3 years ago
- debug: restart should be sent to parent session #118196 — committed to microsoft/vscode by isidorn 3 years ago
- debug: restart should be sent to parent session #118196 — committed to gjsjohnmurray/vscode by isidorn 3 years ago
- debug session: respect lifecycleManagedByParent #118196 — committed to microsoft/vscode by isidorn 3 years ago
@vscode-triage-bot I hate you bot!
@isidorn yes, only if
lifecycleManagedByParentis true,disconnectandrestartrequests are sent to the parent session.@connor4312 that’s OK with you?
I’ll add the
manageByParentproperty to theDebugSessionOptionsin July. Please see https://github.com/microsoft/vscode/issues/128058.@connor4312 @isidorn since parent/child relations between debug sessions are not part of the DAP, I think the
supportsLifecycleflag is more an option on thestartDebuggingextension API, right?Name suggestion:
manageByParentThinking some more, I don’t believe
supportsLifecyclewould be a terrible flag, as a default-true capability to indicate that a session doesn’t independently manage its own lifecycle, implying it is instead a component of its parent…Ok, great. I’ll tackle this next iteration.