-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
vscode cannot read property 'trim' of null error with vscode insider 1.35 #73867
Comments
the same problem after update 1.35.0-insider |
same bug too, on 1.35.0-insider, appears whenever I start debugging on Java. |
Link to previous version: |
It worked yesterday with 1.35 so this problem came with todays update |
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. |
You can work around this issue by updating your launch.json with Python: Current File example:
|
Is anyone working on this one? I can give it a try |
FYI the console workaround "console": "internalConsole" doesn't work with any input(), otherwise I would just use code runner until this was fixed. |
Hit the same issue, thanks to @beachbc for the workaround. |
same issue here, dg to 1.35 for now. I'm not so familiar with vscode otherwise i would like to contribute |
Another possible workaround: set the terminal to bash: microsoft/vscode-remote-release#350 (comment) |
Same issue here... {
"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
}
]
} |
That's the answer. But I donnot know why. Maybe corrected in release version. |
Adding the important label since the breaks the 'vscode-remote-try-python' sample. |
This works - changing to internal console. Thanks. |
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. |
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!) |
which commit fixes this? I don't see any change. |
@yamcenutzer Commit 15a0e88. See 4 comments above: I've verified that all issues resolved as duplicates now work with the fix. |
either that commit isn't in 1.35.0
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? |
@yamcenutzer but you are setting the BTW, vscode and remote-ssh are the same team. |
yes, If you say it should be in 1.35.0, then I'll reinstall from scratch.. |
@yamcenutzer and you are seeing the "cannot read property 'trim' of null error" or the never ending progress indicator? |
never ending progress... hangon... got updates to a new commit dated yesterday , this could work: and it does... OK Thx |
' 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>
.
|
@Tyriar thanks for fixing. The fix looks good. |
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
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
Extensions (14)
(1 theme extensions excluded)
The text was updated successfully, but these errors were encountered: