Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node should not set supportsTerminateRequest on Windows or in EH debugging #55911

Closed
ramya-rao-a opened this issue Aug 6, 2018 · 10 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded windows VS Code on Windows issues
Milestone

Comments

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Aug 6, 2018

  • VSCode Version: Insiders 1.26 dated 6th August, 2018
  • OS Version: Windows 10

Steps to Reproduce:

  1. Have an extension that opens a folder on command
vscode.commands.registerCommand('extension.sayHello', () => {
        vscode.commands.executeCommand('vscode.openFolder', vscode.Uri.parse('C:/some-local-path'));
    })
  1. Debug the extension, run the above command.
  2. Close the debugging session, start again

At this point, a new window for extension host is not launched. Clicking the stop button doesnt stop the process either and throws the below error in the debug console

image

@vscodebot vscodebot bot added the insiders label Aug 6, 2018
@ramya-rao-a ramya-rao-a added debug Debug viewlet, configurations, breakpoints, adapter issues bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release labels Aug 6, 2018
@ramya-rao-a ramya-rao-a added this to the July 2018 milestone Aug 6, 2018
@ramya-rao-a ramya-rao-a added the windows VS Code on Windows issues label Aug 6, 2018
@weinand weinand assigned roblourens and unassigned isidorn Aug 6, 2018
@roblourens
Copy link
Member

Is vscode supposed to be sending terminate here? Should the DA be handling the case differently when terminate is called on windows?

@weinand
Copy link
Contributor

weinand commented Aug 6, 2018

On Windows or for extension host debugging the DA should return false for the supportTerminateRequest because:

  • sending SIGINT isn't supported on Windows,
  • we do not want to have developers interfere with signal handling for extensions.

@roblourens please see the issue I've created against node2: microsoft/vscode-node-debug2#197 (comment)

@roblourens
Copy link
Member

Ok, I don't do that.

On windows, why is the DA not normally getting terminate requests? If I debug a normal node app and press stop, the DA doesn't send terminate like on Mac. If it did, we would see this breaking all the time.

@roblourens
Copy link
Member

Apparently I didn't read your issue carefully, apologies. This is probably a candidate right?

@roblourens
Copy link
Member

That test item should have had a tester assigned for windows...

@weinand
Copy link
Contributor

weinand commented Aug 6, 2018

Yes.

@roblourens
Copy link
Member

I've opened a separate issue for the fact that EH debugging is broken.

@roblourens
Copy link
Member

roblourens added a commit that referenced this issue Aug 6, 2018
@roblourens
Copy link
Member

To answer my question from above, the reason I didn't get terminate on windows is because Live Share causes that capability to be lost. Like https://github.com/Microsoft/vscode-cascade/issues/69 I think.

This means that this change just causes vscode to officially act the way I've been using it for the past couple weeks.

@roblourens roblourens changed the title Debuggin extension doesnt launch window, closing errors with Error processing "terminate": Error: kill ESRCH Node should not set supportsTerminateRequest on Windows or in EH debuggingg Aug 6, 2018
@roblourens roblourens changed the title Node should not set supportsTerminateRequest on Windows or in EH debuggingg Node should not set supportsTerminateRequest on Windows or in EH debugging Aug 6, 2018
roblourens added a commit that referenced this issue Aug 6, 2018
@kieferrm
Copy link
Member

kieferrm commented Aug 8, 2018

Verified using @roblourens' instructions:

Just do this - debug a node app on windows with "trace": true. Click the stop button. Open the log and verify that From client: terminate( doesn’t show up

@kieferrm kieferrm added the verified Verification succeeded label Aug 8, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Sep 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

5 participants