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

Remote Launch from SSH don't work on 1.51 #110253

Closed
bobaoapae opened this issue Nov 9, 2020 · 18 comments
Closed

Remote Launch from SSH don't work on 1.51 #110253

bobaoapae opened this issue Nov 9, 2020 · 18 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders regression Something that used to work is now broken remote Remote system operations issues terminal Integrated terminal issues verified Verification succeeded
Milestone

Comments

@bobaoapae
Copy link

bobaoapae commented Nov 9, 2020

  • VSCode Version:1.51
  • OS Version: Windows 10 20h2

Version 1.51 Remote Start: https://prnt.sc/vg9tm2 (10 minutes waiting)
Version 1.50.1 Remote Start: https://prnt.sc/vg9wpp (work as expected)

Launch.json: https://prnt.sc/vg9vuw

Does this issue occur when all extensions are disabled?: Yes

@roblourens
Copy link
Member

Need more details, but please file an issue on the repo for the debug extension that you are using. You can also check developer tools (Help > Toggle Developer Tools) for possible errors.

@bobaoapae
Copy link
Author

This only happen on version 1.51, downgrade to 1.50.1 fix this issue

@bobaoapae
Copy link
Author

bobaoapae commented Nov 11, 2020

Developer Tools Log:

ERR Cannot read property 'scheme' of null: TypeError: Cannot read property 'scheme' of null
    at Object.transformIncoming (c:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\uriTransformer.js:4:76)
    at t.URITransformer.transformIncoming (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:244:220)
    at I._createTerminalProcess (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:781:351)
    at I.call (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:780:328)
    at x.onPromise (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:266:142)
    at x.onRawMessage (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:265:615)
    at C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:264:877
    at l.fire (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:48:801)
    at v.fire (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:281:381)
    at t.PersistentProtocol._receiveMessage (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:286:451)
    at C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:283:489
    at l.fire (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:48:801)
    at f.acceptChunk (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:278:851)
    at C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:278:203
    at Socket.t (C:\Users\Administrador\.vscode-server\bin\fcac248b077b55bae4ba5bab613fd6e9156c2f0c\out\vs\server\remoteExtensionHostAgent.js:288:226)
    at Socket.emit (events.js:223:5)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:290:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:181:23)

@roblourens
Copy link
Member

Does a normal terminal work? Does that error only show up when you click the button to start debugging?

@roblourens roblourens reopened this Nov 11, 2020
@roblourens roblourens added the info-needed Issue requires more information from poster label Nov 11, 2020
@bobaoapae
Copy link
Author

bobaoapae commented Nov 11, 2020

Normal terminal works, even the build task work, only remote start hangs forever. Yes this error show only when i click the button to start

@roblourens
Copy link
Member

Does setting "terminal.integrated.serverSpawn": false fix it?

@roblourens
Copy link
Member

@alexdima seems that we have args.shellLaunchConfig.cwd as null, when we only check for undefined

@roblourens
Copy link
Member

I can repro this just with vscode.window.createTerminal({ cwd: null, name: 'extension terminal' }); in a remote extension

@roblourens roblourens added bug Issue identified by VS Code Team member as probable bug terminal Integrated terminal issues and removed info-needed Issue requires more information from poster labels Nov 11, 2020
@roblourens roblourens added this to the November 2020 milestone Nov 11, 2020
@roblourens
Copy link
Member

Can you share your launch config too @bobaoapae?

@bobaoapae
Copy link
Author

bobaoapae commented Nov 11, 2020

Can you share your launch config too @bobaoapae?

{
    // Use IntelliSense to find out which attributes exist for C# debugging
    // Use hover for the description of the existing attributes
    // For further information visit https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Center Service",
            "type": "coreclr",
            "preLaunchTask": "build",
            "request": "launch",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/Center.Service/bin/Debug/netcoreapp3.1/win10-x64/Center.Service.dll",
            "args": [],
            "cwd": "${workspaceFolder}/Center.Service/bin/Debug/netcoreapp3.1/win10-x64/",
            // For more information about the 'console' field, see https://aka.ms/VSCode-CS-LaunchJson-Console
            "console": "integratedTerminal",
            "stopAtEntry": false,
            "allowFastEvaluate": true
        },
        {
            "name": "Fight Service",
            "type": "coreclr",
            "preLaunchTask": "build",
            "request": "launch",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/Fighting.Service/bin/Debug/netcoreapp3.1/win10-x64/Fighting.Service.dll",
            "args": [],
            "cwd": "${workspaceFolder}/Fighting.Service/bin/Debug/netcoreapp3.1/win10-x64/",
            // For more information about the 'console' field, see https://aka.ms/VSCode-CS-LaunchJson-Console
            "console": "integratedTerminal",
            "stopAtEntry": false,
            "allowFastEvaluate": true
        },
        {
            "name": "Flash Service",
            "type": "coreclr",
            "preLaunchTask": "build",
            "request": "launch",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/Flash.Service/bin/Debug/netcoreapp3.1/win10-x64/Flash.Service.dll",
            "args": [],
            "cwd": "${workspaceFolder}/Flash.Service/bin/Debug/netcoreapp3.1/win10-x64/",
            // For more information about the 'console' field, see https://aka.ms/VSCode-CS-LaunchJson-Console
            "console": "integratedTerminal",
            "stopAtEntry": false,
            "allowFastEvaluate": true
        },
        {
            "name": "Game Service",
            "type": "coreclr",
            "preLaunchTask": "build",
            "request": "launch",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/Game.Service/bin/Debug/netcoreapp3.1/win10-x64/Game.Service.dll",
            "args": [],
            "cwd": "${workspaceFolder}/Game.Service/bin/Debug/netcoreapp3.1/win10-x64/",
            // For more information about the 'console' field, see https://aka.ms/VSCode-CS-LaunchJson-Console
            "console": "integratedTerminal",
            "stopAtEntry": false,
            "allowFastEvaluate": true
        }
    ],
    "compounds": [
        {
            "name": "Debug All",
            "configurations": [
                "Center Service",
                "Fight Service",
                "Flash Service",
                "Game Service"
            ]
        }
    ]
}

@bobaoapae
Copy link
Author

Does setting "terminal.integrated.serverSpawn": false fix it?

I need try, i cant update vscode to test right now, when i finish coding i will try this

@alexdima alexdima added the regression Something that used to work is now broken label Nov 11, 2020
@alexdima alexdima self-assigned this Nov 11, 2020
@alexdima alexdima added the remote Remote system operations issues label Nov 11, 2020
@alexdima
Copy link
Member

seems that we have args.shellLaunchConfig.cwd as null, when we only check for undefined

I see. This means that

is incorrect and it should be cwd?: string | URI | null

@bobaoapae
Copy link
Author

Does setting "terminal.integrated.serverSpawn": false fix it?

Yes, with this config i don't have issues on start debug

@roblourens
Copy link
Member

If you don't have the right strict option set for your extension, you can always do that. We often don't validate arguments from extension api in code.

@alexdima
Copy link
Member

@roblourens 👍 Thanks for the fix!

@roblourens roblourens added the author-verification-requested Issues potentially verifiable by issue author label Nov 17, 2020
@github-actions
Copy link

This bug has been fixed in to the latest release of VS Code Insiders!

@bobaoapae, you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text /verified to let us know. If not, please ensure you're on version d19c7c5 of Insiders (today's or later - you can use Help: About in the command pallete to check), and leave a comment letting us know what isn't working as expected.

Happy Coding!

@Spongman
Copy link

Spongman commented Nov 20, 2020

/verified

i was seeing this in 1.5.1 (when debugging c# on ubuntu wsl from windows), but not in

Version: 1.52.0-insider (user setup)
Commit: a36c68b
Date: 2020-11-19T05:37:52.577Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

@meganrogge
Copy link
Contributor

/verified

per the above, adding z-author-verified label

@meganrogge meganrogge added z-author-verified and removed author-verification-requested Issues potentially verifiable by issue author labels Dec 4, 2020
@roblourens roblourens added the verified Verification succeeded label Dec 4, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Dec 30, 2020
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 insiders-released Patch has been released in VS Code Insiders regression Something that used to work is now broken remote Remote system operations issues terminal Integrated terminal issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

8 participants
@roblourens @Spongman @weinand @alexdima @chrmarti @meganrogge @bobaoapae and others