NRE when starting debugging with `pipeTransport`
See original GitHub issueEnvironment data
dotnet --info
output:
.NET Core SDK (reflecting any global.json):
Version: 2.1.302
Commit: 9048955601
Runtime Environment:
OS Name: Mac OS X
OS Version: 10.13
OS Platform: Darwin
RID: osx.10.13-x64
Base Path: /usr/local/share/dotnet/sdk/2.1.302/
Host (useful for support):
Version: 2.1.2
Commit: 811c3ce6c0
.NET Core SDKs installed:
2.1.302 [/usr/local/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
VS Code version: 1.26.1 C# Extension version: 1.15.2
Steps to reproduce
Open directory containing a .Net Core solution, hit F5.
Expected behavior
The application to run/debugger properly as usual.
Actual behaviour
NRE
I posted the issue on VSCode repo as it looks to me a VSCode problem as it started to happening after last update of it however, MSFT folks there are saying it is caused by the C# extension as you can see here https://github.com/Microsoft/vscode/issues/57808#issuecomment-418109705
The codebase isn’t changed in months so I doubt it is a code/config problem as it was working perfectly so far until I had VSCode updated.
No errors on Electron console:
And this is what happens when I start an app:
Here is the launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "Kube Debugger",
"type": "coreclr",
"request": "launch",
"program": "/app/EventStore.Kube.dll",
"cwd": "/app",
"sourceFileMap": {
"/src": "${workspaceFolder}"
},
"pipeTransport": {
"debuggerPath": "/root/vsdbg/vsdbg",
"pipeCwd": "${workspaceFolder}",
"windows": {
"pipeProgram": "kubectl",
"pipeArgs": [
"exec",
"-i",
"eventstore",
"--namespace",
"giro",
"--"
],
"quoteArgs": false
}
}
}
]
}
Any clues on how to workaround it is really appreciated as I’m totally blocked now.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top GitHub Comments
Lets leave this open to track fixing the error handling here. But glad you solved the problem.
Oh! Didn’t saw that… It used to work on my old SurfaceBook2, that is why it is not working…
However, now I have this log with a different message:
It wasn’t able to find the application code inside the container but that was a mistake on the kube configMap that was point to the wrong build output directory.
I still think that message could be more user-friendly in case no default nor OS-specific config were found on launch.json.
For now problem solved! Thanks @gregg-miskelly! Enjoy your holiday! 😃