Cannot reset the debug environment chosen for a file

[ebousse]

Problem

A couple of years ago, a feature (covered in issue #124770) was added to VSCode to remember the last debugging environment chosen when executing a given file without any launch.json. This was a very welcome addition to avoid having to pick an environment at each press of F5 on a file.

However, in a given workspace, there is currently no way to undo such file-environment association. This means that if a user choses the wrong environment on the first debug run, the user is stuck with it. In such a case, I found three ways to "fix" the problem:

1. close VSCode, rename the working folder, open VSCode in the renamed folder — the new workspace will have no file-environment associations which will allow the user to try again,
2. rename the file — the new file will have no file-environment association which will allow the user to try again,
3. create a launch.json file that will override this behavior.

I cannot use Option 3 in my own context of use (which is teaching software development basics to 1st year students, where I need to avoid as much as possible making them modify complex json files). This leaves me Options 1 and 2, which work but are really unsatisfying from a user experience point of view (and my still create confusion in students in my case).

Feature I'd like

A way to simply delete a given file-environment association, for instance with a new command accessible from the palette. There are already many commands to "reset" things (at least for the views), thus I don't think adding a new one will look out of place. This possibility was actually discussed in issue #124770, but discarded.

[roblourens]

Yeah, I have also run into this and it needs more thinking. But I think in this state you can also expand this and find all the dynamic configs still right? Maybe not exactly the same options though.

[ebousse]

Yeah, I have also run into this and it needs more thinking. But I think in this state you can also expand this and find all the dynamic configs still right? Maybe not exactly the same options though.

If I am correct, the menu you are showing in the screenshot is only available if a launch.json file exists, which at least in my case is an option I need to avoid (as explained in my first message).

But actually this would be a way to solve the problem, UI-wise: to make this menu always available, and to show in the drop-down menu the possible available environments to execute the currently opened file, similarly to the choices appearing with CTRL+F5?

[roblourens]

I think that once you have debugged something, then you see the menu. I just tried it and that's what I see.

[ebousse]

I think that once you have debugged something, then you see the menu. I just tried it and that's what I see.

In my case, running a single file without or with debug does not initialize the pane that gives access to said menu:

Capture.video.du.2023-02-01.10-16-31.webm

I can only make it appear if I create a launch.json. Maybe I am missing something?

(Using VSCode 1.74.3)

[roblourens]

I need to review the exact criteria for that menu showing up in this situation, this area is a bit tricky, but you also have the link that says "Show all automatic debug configurations" which gives you the ability to pick an option.

[ebousse]

you also have the link that says "Show all automatic debug configurations" which gives you the ability to pick an option.

If I try to click on "Show all automatic debug configurations", and to select one of the choices there, I get this error:

Cannot read properties of undefined (reading 'fsPath')

I suppose this is because I don't have any launch.json set up?

Here is a video (jump near the end for the error mentioned above):

Capture.video.du.2023-02-02.09-11-17.webm

[roblourens]

Ah there is actually an issue there, I can repro it, seems to come from here https://github.com/microsoft/vscode-js-debug/blob/df2210162933263ec92b73eba560e33bec3eca9d/src/ui/debugNpmScript.ts#L123 @connor4312 I guess if findFiles doesn't return anything.

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[aeschli]

What are the steps to verify?

[connor4312]

1. Have one .js file open in an otherwise empty folder
2. In the empty debug view, "Show all automatic debug configurations"
3. Verify you don't see an error popup when you pick "Node.js..."

[ebousse]

Thank you for the fix, it does solve the problem in my case!

The only strange thing is that the list now provided when clicking on "Show all automatic debug configurations":

(which expands like this when choosing "Run current file" :)

Differs from the list provided when doing "Run without debugging" for the first time: