vscode cannot read property 'trim' of null error with vscode insider 1.35

[ttbug]

Issue Type: Bug

when i debug python file, set breakpoint and F5 ,vscode cannot read property 'trim' of null error occured in vscode insider 1.35, while 1.34.20 works well，so i install 1.34.20 again.

VS Code version: Code - Insiders 1.34.20-insider (e83e24a, 2019-05-15T18:06:45.467Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.9.0-9-amd64

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.87GB (5.42GB free)
Process Argv
Screen Reader	no
VM	50%

Item	Value
Remote	SSH: alias
OS	Linux x64 4.9.0-9-amd64
CPUs	Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (2 x 2807)
Memory (System)	3.85GB (0.55GB free)
VM	100%

Extensions (14)

Extension	Author (truncated)	Version
code-runner	for	0.9.9
pyright	ms-	1.0.28
python	ms-	2019.4.12954
Go	ms-	0.10.2
autoimport	ste	1.5.3
vscodeintellicode	Vis	1.1.6
vscode-language-pack-zh-hans	MS-	1.34.2
remote-containers	ms-	0.53.0
remote-ssh	ms-	0.37.0
remote-ssh-edit	ms-	0.37.0
remote-ssh-explorer	ms-	0.37.0
remote-wsl	ms-	0.35.0
vscode-remote-extensionpack	ms-	0.14.0
material-icon-theme	PKi	3.7.0

(1 theme extensions excluded)

[zzzJH]

the same problem after update 1.35.0-insider

[jerrylususu]

same bug too, on 1.35.0-insider, appears whenever I start debugging on Java.
Local OS: Windows 10 1903, x64
Remote OS: WSL - Ubuntu 18.04

[ypapouin]

Link to previous version:
https://update.code.visualstudio.com/1.34.20-insider/win32-x64-user/insider

[magic-k]

It worked yesterday with 1.35 so this problem came with todays update

[AeneasZhu]

I also have this problem too on the 'Exploration' Version. So I switch to Insider Version of 1.34, but when it update today, the same bug happened again.

[allenwu5]

Link to previous version:
https://update.code.visualstudio.com/1.34.20-insider/win32-x64-user/insider

Mac ver. https://vscode.cdn.azure.cn/insider/d6aa8eaf30c71df32d4543290675808440def630/VSCode-darwin-insider.zip

[beachbc]

You can work around this issue by updating your launch.json with "console": "internalConsole"

Python: Current File example:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "internalConsole"
        }
    ]
}

[katsos]

Is anyone working on this one? I can give it a try

[bevo009]

FYI the console workaround "console": "internalConsole" doesn't work with any input(), otherwise I would just use code runner until this was fixed.
A bit maddening that any restart reinstalls the borked 1.35.0, now I have to reinstall 3.4 AGAIN to get around this bug? Why don't you flag borked upgrades as incompatible so vscode-insiders ignores them? Forcing buggy installs doesn't seem a positive path to take...

[rchinna]

Hit the same issue, thanks to @beachbc for the workaround.

[Sherlock92]

same issue here, dg to 1.35 for now. I'm not so familiar with vscode otherwise i would like to contribute

[roblourens]

Another possible workaround: set the terminal to bash: microsoft/vscode-remote-release#350 (comment)

[Cow258]

Same issue here...
Unable to debug any Node.js project for now.
And some log can't display on "internalConsole".
So I switch back to VSCode for this moment.

{
    "version": "0.2.0",
    "configurations": [
     {
            "name": "New Debug",
            "type": "node",
            "request": "launch",
            "runtimeExecutable": "nodemon",
            "runtimeArgs": ["--inspect=9229", "--expose-gc", "--gc_global", "--nouse-idle-notification", "--max-old-space-size=250", "app.js"],
            "restart": true,
            "console": "integratedTerminal",
            "protocol": "inspector",
            "port": 9229
        }
    ]
}

[guyhuang]

You can work around this issue by updating your launch.json with "console": "internalConsole"

Python: Current File example:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "internalConsole"
        }
    ]
}

That's the answer. But I donnot know why. Maybe corrected in release version.

[egamma]

Adding the important label since the breaks the 'vscode-remote-try-python' sample.

[Tyriar]

@isidorn please review 15a0e88

[norbinsh]

You can work around this issue by updating your launch.json with "console": "internalConsole"

Python: Current File example:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "internalConsole"
        }
    ]
}

This works - changing to internal console.

Thanks.

[liedav]

I have the same issue: vscode cannot read property 'trim' of null when running python code with/without debug in version 1.35, whereas 1.34.20 works. I have tried the workaround of replacing "console": "integratedTerminal" with "console": "internalConsole" in the launch.json file and it did NOT work for me. I have reverted back to 1.34.20.

[PeterJPRoche]

Having the same issue debugging Python code. VS Code - Insiders 1.35.0. The workaround of replacing "console": "integratedTerminal" with "console": "internalConsole" worked for me (thankfully!)

[yamcenutzer]

which commit fixes this? I don't see any change.

[weinand]

@yamcenutzer Commit 15a0e88. See 4 comments above:

I've verified that all issues resolved as duplicates now work with the fix.

[yamcenutzer]

either that commit isn't in 1.35.0

• or it doesn't help with remote cpp debug with gdb.
• or the cpp exension needs to know about "console" (which it doesn't)
• or the remote extension doesn't know about it

Like I said, I have no idea whether my original issue, which was about remote cpp debugging on real linux (not WSL, ever), is the same as this one. There are 3 teams involved, which in the, past, seem to not know of each other: vscode, cpp, and as of recently: remote-ssh.

So I ask again, do I need to ask someone else, or simply wait until my insiders build offers me an update beyond 1.35.0?

[weinand]

@yamcenutzer but you are setting the externalConsole in your launch config to false, correct?

BTW, vscode and remote-ssh are the same team.

[yamcenutzer]

yes,
and that's nice...

If you say it should be in 1.35.0, then I'll reinstall from scratch..

[weinand]

@yamcenutzer and you are seeing the "cannot read property 'trim' of null error" or the never ending progress indicator?

[yamcenutzer]

never ending progress...

hangon...
I'm installing again, I believe I'm getting updates now...

got updates to a new commit dated yesterday , this could work:
Version: 1.35.0-insider (user setup)
Commit: 4ca38ce
Date: 2019-05-21T05:18:31.618Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 6.1.7601
....

and it does...
seems a bit flaky, as it sometimes gets funny characters ~~~ and then complains about them.
but if it gets past that stage, it works at least on the simple 'hello' example I have right here

OK Thx

[bevo009]

' updating your launch.json with "console": "internalConsole" ' Not an answer if your code is interactive ie using input(), the internal console doesn't work with that The internal console is much neater in output though, if it worked with input() I'd always use it...debugger output always makes a mess of the terminal

…

On Mon, May 20, 2019 at 5:18 PM guyhuang ***@***.***> wrote: You can work around this issue by updating your launch.json with "console": "internalConsole" Python: Current File example: { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "name": "Python: Current File", "type": "python", "request": "launch", "program": "${file}", "console": "internalConsole" } ] } That's the answer. But I donnot know why. Maybe corrected in release version. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#73867?email_source=notifications&email_token=AD6QVZNISXXQYVXGXOW3ZX3PWJGFFA5CNFSM4HNSO7D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVX4Z4Q#issuecomment-493866226>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD6QVZJCOKOGWE5K6UZKQZDPWJGFFANCNFSM4HNSO7DQ> .

[isidorn]

@Tyriar thanks for fixing. The fix looks good.