text:
Testing: MarkdownString in vscode.TestMessage is always sanitized (strips color styles)

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

VS Code Version: all
OS Version: alll

Following code snippet:
    const mds = new vscode.MarkdownString();
    mds.supportHtml = true;
    mds.value = `
# Title
## Title
### Title
RED
`;
    mds.isTrusted = true;
    const message = new vscode.TestMessage(mds);

Results in:

Expected: RED should be red.
// @connor4312

This is by-design. We only allow a one or two css properties for security and presentation reasons
Marking as a feature request to gauge interest in broadening the subset of css that is supported

While I'm not certain that we want to do this, eventually we will probably add webview-like capabilities to testing output, as we've had asks for more complex scenarios, and it's easy to imagine even more advanced ones like image diffing.

authors: connor4312 mjbvz pavelfeldman


text:
Can no longer add folder to VSCode workspace, Finder does not pop up

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug

Open an existing workspace/ OR Try to add "Open Folder"
Select "add folder to workspace"
Expected: Finder to pop up and allow to add folder
Happens: Finder doesn't pop up

VS Code version: Code 1.66.2 (Universal) (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:20.994Z)
OS version: Darwin arm64 21.6.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 Pro (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.11GB free)

Process Argv
--crash-reporter-id 6d3427cd-e4eb-4ae9-9687-d9428e8e69c9

Screen Reader
no

VM
0%

Extensions (22)

Extension
Author (truncated)
Version

doxdocgen
csc
1.4.0

better-cpp-syntax
jef
1.15.19

cmake-language-support-vscode
jos
0.0.4

vscode-docker
ms-
1.22.1

vscode-dotnet-runtime
ms-
1.5.0

python
ms-
2022.4.1

vscode-pylance
ms-
2022.5.1

jupyter
ms-
2022.3.1000901801

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.9

cmake-tools
ms-
1.11.26

cpptools
ms-
1.11.4

cpptools-extension-pack
ms-
1.2.0

vetur
oct
0.35.0

java
red
1.9.0

cmake
twx
0.0.17

vscodeintellicode
Vis
1.2.22

vscode-java-debug
vsc
0.43.0

vscode-java-dependency
vsc
0.20.0

vscode-java-pack
vsc
0.25.0

vscode-java-test
vsc
0.35.2

vscode-maven
vsc
0.37.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
pylanb8912:30529769
vsclangdf:30486550
c4g48928:30535728

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.69.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Cool!

source: gharchive/issue

authors: Brendahnyaringita VSCodeTriageBot

repo: microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
Typescript keeps crashing

Type: Bug
Not matter if i am on MacBook Air M1 or MacBook Pro 2020,  I even tried with VSC preview and no plugin
VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:38:59.695Z)
OS version: Darwin arm64 21.6.0
Modes:

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
5, 4, 4

Memory (System)
16.00GB (1.74GB free)

Process Argv
. . --crash-reporter-id d22153d2-13bf-41f6-a02b-487a8f0462f1

Screen Reader
yes

VM
0%

Extensions (49)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

markdown-preview-github-styles
bie
1.0.1

vscode-tailwindcss
bra
0.8.6

indented-block-highlighting
byi
1.0.7

npm-intellisense
chr
1.4.2

path-intellisense
chr
2.8.1

cypress-snippets
Cli
0.0.5

vscode-eslint
dba
2.2.6

githistory
don
0.6.19

vscode-remark-lint
dre
1.0.0

es7-react-js-snippets
dsz
4.4.3

vscode-docker-syntax
dun
0.1.5

EditorConfig
Edi
0.16.4

vscode-npm-script
eg2
0.3.28

prettier-vscode
esb
9.8.0

vscode-firefox-debug
fir
2.9.8

auto-complete-tag
for
0.1.0

auto-rename-tag
for
0.1.10

vscode-sql-tagged-template-literals-syntax-only
fri
0.0.19

copilot
Git
1.43.6621

vscode-sort
hen
0.2.5

cypress-fixture-intellisense
Jos
1.2.0

cornflakes-linter
kev
0.5.1

code-beautifier
mic
2.3.3

dotenv
mik
1.0.1

vscode-postgresql
ms-
0.3.0

python
ms-
2022.12.1

vscode-pylance
ms-
2022.8.50

jupyter
ms-
2022.7.1102252217

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.9

remote-containers
ms-
0.245.2

cpptools
ms-
1.12.4

color-highlight
nau
2.5.0

prisma
Pri
4.3.0

vscode-xml
red
0.21.2022062916

vscode-yaml
red
1.10.1

LiveServer
rit
5.7.9

vscode-extension-open-cypress
tnr
0.0.14

lorem-ipsum
Tyr
1.3.1

vscode-mdx
uni
1.0.3

vscode-remark
uni
2.1.0

errorlens
use
3.6.0

highlight-matching-tag
vin
0.10.1

vscode-postcss
vun
0.2.0

file-icons-mac
way
1.0.1

fig
wit
0.0.6

vscode-import-cost
wix
3.3.0

change-case
wma
1.0.0

(1 theme extensions excluded)

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.71.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Yes the issue remains

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

yes it does! I already tried

Please try collecting the TS Server log from the crashed instance:

Set "typescript.tsserver.log": "verbose"

Restart VS Code and reproduce the problem

Open the TypeScript section of the output panel

At the very top, find the first line that prints to path to the semantic error log file. It should look something like:
[Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log

That file contains the typescript logs.

Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

I am still trying to reproduce the problem

tsserver.log

authors: VSCodeTriageBot blasterbug mjbvz


text:
sourceFileMap when debugging externally built binary

When debugging externally built binary (for example using attach on binary built on some server) paths of source files may not match paths in local project as workspaces may be different. It would be nice if we can have one of:

function which try to map path ignoring workspace part (i.e. matching backwards up to workspace part of path), or
some masks in sourceFileMap setting, so we could mask part of the path.

What debugger are you using?

Default for Visual Studio (2017) on Windows.

This repository is for Visual Studio Code, and not for Visual Studio.

Just thought it is VS Code responsibility to translate paths from pdb to current workspace (i.e. what sourceFileMap is for). Sorry!

@lukaszgdula6 May be I was confused but your statement "Default for Visual Studio (2017) on Windows."

I was assuming that you are using "Visual Studio (2017)", correct?
I don't understand the "Default". Neither Visual Studio nor Visual Studio Code have a default debugger. They might have a built-in debugger, but this is not a "default". So may be I should have asked "what language are you debugging?".

I'm sorry for confusing response. I'm not an Windows/VS expert, I didn't apt get gdb or so - I just installed C++ section in Visual Studio 2017. It is not like they provide exe name or something in the installer, or give any choice... VS Code detected debugger itself without asking too... If you can guide me how to get actual debugger name for you I'll be more than happy to help. The only distinct thing I can see is "type": "cppvsdbg" in launch.json.
C++ of course.
The other thing I noticed is that when debug in VS it correctly map files. For example something like g:\a3423a\main.cpp is mapped to c:\myenv\main.cpp without any extra configuration. It woks both for stack walking and breakpoints setting. In VS Code I have to add entry sourceFileMap in my launch.json.

/extCpp


text:
I try to use the '#pragma region/endregion' to fold my C++ code freely, but it not work!

Type: Bug
I try to use the '#pragma region/endregion' to fold my C++ code freely, but it not work! There is no folding button.
this is my code example:
// #pragma region
my code line1
my code line2
...
my code line n
// #pragma endregion
Please help me!
Dose the Chinese mode has influence？
VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:35:13.448Z)
OS version: Windows_NT x64 10.0.18362
Modes:
Remote OS version: Linux x64 5.3.0-28-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.78GB (16.52GB free)

Process Argv
--crash-reporter-id dc52aa6b-a150-4593-b413-8c704d1eeb4a

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: 10.118.28.95

OS
Linux x64 5.3.0-28-generic

CPUs
Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz (48 x 1200)

Memory (System)
125.57GB (36.83GB free)

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

better-cpp-syntax
jef
1.15.19

vscode-language-pack-zh-hans
MS-
1.70.8170916

remote-ssh
ms-
0.84.0

remote-ssh-edit
ms-
0.80.0

better-cpp-syntax
jef
1.15.19

vscode-language-pack-zh-hans
MS-
1.70.8170916

cpptools
ms-
1.11.4

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012:30540252
azure-dev_surveyone:30548225
2144e591:30553903
fc301958:30567733

please！

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.71.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

The folding regions would come from the C++ extension. Can you file the issue there?
https://github.com/Microsoft/vscode-cpptools/issues

authors: VSCodeTriageBot aeschli zyqhnu


text:
VS Code Server for WSL closed unexpectedly

Type: Bug
Launching C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 6261075646f055b99068d3688932416f2346dd3b stable code-server .vscode-server --host=127.0.0.1 --port=0 --connection-token=3106673047-4057529159-4036989076-3159467342 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all'
[2022-11-14 00:44:08.786] The Windows Subsystem for Linux instance has terminated.
VS Code version: Code 1.73.1 (6261075646f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No
Connection to 'WSL: Ubuntu-20.04' could not be established  VS Code Server for WSL closed unexpectedly.
Check WSL terminal for more details.

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz (4 x 2494)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.90GB (0.27GB free)

Process Argv
--folder-uri=vscode-remote://wsl+Ubuntu-20.04/root/DevOps_Microservices/project-ml-microservice-kubernetes --remote=wsl+Ubuntu-20.04 --crash-reporter-id f59e6b5f-9099-490b-9301-306780caf8d5

Screen Reader
no

VM
0%

Connection to 'WSL: Ubuntu-20.04' could not be established  VS Code Server for WSL closed unexpectedly.
Check WSL terminal for more details.
Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaac:30438847
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyonecf:30548226
pyindex848:30577860
nodejswelcome1:30587005
fc301958:30595537
3biah626:30602489
gswce2:30605431
3d0df643:30608728
dbltrim-noruby:30604474
89544117:30607850

Does it always reproduce?
Does wsl --shutdown help?

authors: aeschli iyketheintrovert


text:
Terminal quick fix provider is called many times when the window reloads

Testing #166762

Use the example git provider
Have a terminal with a bunch of misspelled git commands
Reload the window
The provider is called for all the stuff in the reconnected terminal

I think there isn't any way to access the quick fixes for old commands anyway, right? So it seems like we shouldn't do this, especially during window startup if it may be expensive

Verified via code review.

authors: karrtikr roblourens


text:
Python 3.6 Syntax highlighting of imports no longer works.

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

VS Code Version:  1.74.2
OS Version:  windows 10

Steps to Reproduce:

Open VScode with python 3.6.x as python interpreter

When using python 3.6 the highlighting of imports does not occur leaving them as white text strings. This also impacts all instances of imported elements.

This is also happening to me after updating on Ubuntu 18.04 LTS - I believe it's because the interpreter is not being discovered and set?

This appears to be an issue with the vscode-python. Please use the Python: Report issue command to report this issue.
cc: @karrtikr
Related: https://github.com/microsoft/vscode/issues/170592

authors: Rumbelows bhavyaus jlotthammer


text:
Terminal tab colors don't look correct in Light+

No clue whether this has changed, I just wasn't sure this was correct. Should there be a background color on all tabs? When hovering the active tab, the text and icon color is white which makes it hard to read

Do you have color customizations? This is what it looks like for me:

I get the blue highlight when it's focused, but in my gif it's not focused

Ah, I can repro this in Light+ v2:

Not sure how to get the text to go white though

I think this is all related to https://github.com/microsoft/vscode/pull/172668

Should be fixed as part of https://github.com/microsoft/vscode/issues/173238

authors: Tyriar daviddossett roblourens


text:
Have terminal support Unicode version 14

I'm working on a terminal app and i noticed that the width of some characters e.g. the red heart emoji "❤" is only one character, whilst in Unicode 14 it takes up 2 columns, and this messes up the cursor position for me as I'm using a package to calculate the character width based on the latest standard.
I can read in the settings that you only support Unicode version 6 and 11 and would like to suggest that you also support Unicode version 14 (or even 15?).
Relevant setting:
terminal.integrated.unicodeVersion

@erf
In powershell console I have

but in integrated VS one I see

Is there a chance it is connected with this issue?

Unicode v15 support is likely coming with https://github.com/xtermjs/xterm.js/pull/4519
@luv-deluxe the unicode version only determines the width of the characters, your issue is tracked in https://github.com/xtermjs/xterm.js/issues/2693

Let's track this upstream: https://github.com/xtermjs/xterm.js/issues/2693
/duplicate

authors: Tyriar erf luv-deluxe


text:
Settings Sync providers

Type: Bug
When attempting to enable settings sync for the first time, I get the error:
Error while turning on Settings Sync. No authentication providers are available.
VS Code version: Code 1.80.0 (660393deaaa6d1996740ff4880f1bad43768c814, 2023-07-04T15:06:02.407Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz (8 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.73GB (23.02GB free)

Process Argv
--crash-reporter-id 1c81ac70-b442-428a-aafb-ca41d7f025cf

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

vscode-nuget-package-manager-improved
max
2.1.0

powershell
ms-
2023.6.0

colorful-comments
Par
1.0.0

vscode-nuget-gallery
pat
0.0.24

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30610678
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30785052
pythongtdpath:30769146
i26e3531:30780429
pythonnosmt12:30779714
pythonidxpt:30784022
pythonnocebcf:30776496
e537b577:30786199

They were not! And now we're good.  Thanks!! I had found so many past instances of this occurring, but never such an easy fix.


text:
Navigate accessible buffer doesn't give feedback when there are no commands to navigate

Repro:

Run some commands in a terminal
Reload (which will remove all shell integration decorations atm)
Shift+tab in terminal
ctrl+shift+g, 🐛 nothing happens

Maybe a notification should show saying there are no commands found to navigate between?

I feel like notifications are noisy. If we're thinking about screen reader users here being disoriented with the no-op, we could use alert instead?

Sometimes for no-ops like this, we show the quick pick with only one item or placeholder - maybe we could do that instead?

That would just mean more work as the user needs to exit with enter or escape?

I haven't heard feedback about this from screen reader users. I think we can close this.

authors: Tyriar meganrogge


text:
Support Profile Inheritance

Can something like inheritance or import be added?
global
├── web dev
│ ├── vue
│ ├── react
│ └── vanilla
├── python
│ ├── data mining
│ └── deep learning
└── c/cpp

When adding a plugin to global, it means that a plugin is installed globally.
When certain settings are added in web dev, this applies to all web development.
Originally posted by @tbontb-iaq in https://github.com/microsoft/vscode/issues/190856#issuecomment-1685975772

Hello, developers of vscode. Thank you so much for your work.
I want to be able to add more functionality to profile, like this:
{
   "references": ["settings-1.json", "settings-2.json"]
}

This will allow profile to automatically import and synchronize other profile files. Developers can freely combine these configuration files according to their needs, and make the configuration of vscode more flexible.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

Very sad news.

If you want this behaviour only for settings here is the issue tracking this - https://github.com/microsoft/vscode/issues/188612
Here is the explanation why we do not want to support profile hierarchy - https://github.com/microsoft/vscode/issues/156144#issuecomment-1616012963

I read the following issue threads.
Profile inheritance:

#182261
#191025
#191516

Settings inheritance:

#156144
#188612

Extension groups:

#174685
#195542
#20599

Many comments above are related to profiles not addressing their XY problem:

Same settings in every project
Same layout in every project
Different extensions in every project
Same extensions per category (for example related to Markdown, JS, a framework, or combination of categories)
Same changes everywhere when any of the above are updated

Profiles allow quickly applying layout to a new project but not extensions:

Every project uniquely mixes extension categories.
Creating a unique profile for every project sacrifices shared layout and settings.
There's no way to inspect what's included in a profile's JSON config.

In reality extension packs were a better fit but their issues are:

No native way (only an extension) to manage local packs
No visual grouping to manage installed extensions by cattegory

Profile inheritance (not only on creation) combined with exposing their JSON config would be 1 solution. Enhancing extension packs would be another. I just want an open issue for what's a nearly universal XY problem regarless of the solution.

Since it was mentioned that "general profile inheritance" is not planned, I think extension inheritance is very helpful. I have a lot of extension I use across all my profiles, like "Code Spell Checker" or "Markdown all in One". It would be very nice when I remove or add extensions to the base profile I can click a button in other profiles to always use base-as-base and any other extension is just for that profile.

authors: VSCodeTriageBot muuvmuuv sandy081 tbontb-iaq texastoland


text:
Shell Command Uninstall 'code' from PATH nukes shell PATH

Does this issue occur when all extensions are disabled?: Don't know

VS Code Version: 1.83.0
OS Version: Apple M1 Pro Ventura Version 13.5.2

Steps to Reproduce:

Run Shell Command: Install 'code' from PATH
Run Shell Command: Uninstall 'code' from PATH

This nuked my PATH completely. I had nothing but builtin commands to recover my shell. The request for elevated permission should have been a red flag to abort.
I'm happy to take a look at this repo and find out how/if it happened via vscode if someone can helped me get started. I searched this repo and couldn't find anything related to that command. I don't even know what files vscode manipulated to edit the PATH in the first place.

I figured this out. Copied and pasted these instructions into my zshrc and didn't see the forward slash. PEBCAK.


text:
Cursor in terminal is smaller than a character

Type: Bug
Steps to Reproduce:

Type some character in the terminal and observe that the cursor is smaller than the entered character.

Here's what it looks like:

A
B

VS Code version: Code - Insiders 1.84.0-insider (7dff07893ac160244db210e574eccc05f1cba2cb, 2023-10-24T05:33:19.453Z)
OS version: Linux x64 6.2.0-35-generic snap
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (8 x 3093)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
7.63GB (4.33GB free)

Process Argv
--no-sandbox --force-user-env --unity-launch --crash-reporter-id a7ecc774-f9b4-45e2-8a73-490f4d1c756d

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions: none
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30404738
py29gd2263:30784851
vscaat:30438846
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
a9j8j154:30646983
showlangstatbar:30737417
57b77579:30687741
pythonfmttext:30716741
fixshowwlkth:30771523
showindicator:30805243
pythongtdpath:30726887
i26e3531:30792625
welcomedialog:30812478
pythonnosmt12:30779711
pythonidxpt:30768918
pythonnoceb:30776497
copilotsettingt:30808721
asynctok:30869155
dsvsc013:30777762
dsvsc014:30777825
pythonmhint1:30859868
dsvsc015:30821418
pythontestfixt:30866404
pyreplss1:30865275
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30864172
accentitlementst:30870582

What are your settings?

It's clean Visual Studio Code - Insiders installation to fill a report. I have observed it in regular 1.83.1 version.

Great, pls provide your settings.json file

Okay, but like I said, in the case of Visual Studio Code - Insiders it's an empty file (I have no modified settings): settings.json

In the case of my regular Visual Studio Code installation, it is: settings.json.

I initially identified a bug in the regular 1.83.1 version of Visual Studio Code. To confirm its presence, I conducted further testing with a clean installation of Visual Studio Code - Insiders and observed that the issue persists in the Insiders version as well.
Apologies if my initial explanation was unclear.

It also occurs in the editor as well. Steps to reproduce:

Use settings.json.
Write some characters in the editor.

Here's what it looks like:

A
B

This is fine, the font that you happen to be using just isn't truly monospace and the & is larger than the letters. Nothing we should do to workaround this as either the char would get clipped or each char would be wider than necessary.

For example, here the JetBrains Mono font is used:

A
B

For example, here the Cascadia Mono font is used:

A
B

authors: Tyriar meganrogge uRohan


text:
Prevent setting sticky scroll at workspace level

Sticky scroll added initially in https://github.com/microsoft/vscode/pull/197558
Verify:

Disable sticky scroll at user level
Enable sticky scroll at workspace level
Open a terminal
Run a command such that sticky scroll would show
Verify sticky scroll does not show

As mentioned in https://github.com/microsoft/vscode/issues/199395 that's not what we normally do.
We give users / workspaces the freedom to have view settings also in a workspace. There are valid use cases for this, as demonstrated by the terminal sticky scroll setting.
I also discussed this with @alexdima and @sandy081

Partial revert: https://github.com/microsoft/vscode/pull/199712

authors: Tyriar aeschli


text:
Focused search buttons border color update

Hi thanks for everything that's been done so far. I'd like to request a quick style update in SEARCH. When Match Case and Match Whole Word  focused border-color/outline is the same color as their background-color which makes the focused item very difficult to distinguish as can be seen in the screenshot below. I think we'd all benefit from this quick update (keyboard users and users with visual impairments).

Thanks, makes sense. Looks like we don't change the border color on focus. We should do so.

authors: daviddossett tdiluzio


text:
wont run

Type: Bug
so ive been working on a personal project (in python) and while i was editng my code. the script started to not run, i tested this out buy typing a print command at the top to see if it would print. it did not. i dont know how i could fix this, ive done so much research in the past week but nothing has helped. Can you?
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 5 5500                                (12 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.80GB (1.06GB free)

Process Argv
--crash-reporter-id 921a181b-98a6-4dec-aac0-d6972acb7218

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

debugpy
ms-
2024.4.0

python
ms-
2024.4.1

vscode-pylance
ms-
2024.4.1

cmake-tools
ms-
1.17.17

cpptools
ms-
1.19.9

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
fegfb526:30981948
bg6jg535:30979843
ccp1r6:30993540
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
724cj586:31013169
pythoncenvptcf:31022791

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


text:
code-insiders don't want to work

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

VS Code Version:  1.90.0-insider
26c4a07b47a2bd34480a5e4cba2c2384c590b039
x64

OS Version: Ubuntu 23.10

Steps to Reproduce:

idk, but i have screen record
https://drive.google.com/file/d/1hWm7oWDOEE0SHO-ZbPccvjcDMV2WxLLg/view?usp=sharing

I have no idea how it happened.
All my life vscode insiders has been working
, everything was ok this morning too
and then he abruptly took it and broke down

the new release they pushed out that day was what caused the issue. i myself am facing this issue. for now, i have switched to vs code release version.

@igorar666 thanks for the recording, can you check for .dmp files inside the pending folder and attach them to this issue.

Hi @igorar666, I finally found some time to symbolicate the crash dumps.
Several of the crash dumps were related to l10n_util, such as symbolicated-f0.log
symbolicated-f0.log
One of the crash dumps was related to the GPU. I'm including it here for completeness.
symbolicated-b5.log


text:
Typescript and JavaScript Language Features

Type: Bug
The JS/TS language service crashed 5 times in the last 5 Minutes.
VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
Connection to 'wsl+Ubuntu-20.04' could not be established
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.85GB (0.39GB free)

Process Argv
--crash-reporter-id c0df8a83-9e9e-4d96-8bb8-7a35d3b0f292

Screen Reader
no

VM
29%

Item
Value

Remote
WSL: Ubuntu-20.04

OS
Linux x64 5.15.146.1-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1799)

Memory (System)
3.75GB (0.08GB free)

VM
0%

Connection to 'wsl+Ubuntu-20.04' could not be established

Item
Value

Remote
WSL: Ubuntu-20.04

OS
Linux x64 5.15.146.1-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1799)

Memory (System)
3.75GB (0.08GB free)

VM
0%

Extensions (35)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

apt-source-list-syntax
dei
0.1.6

javascript-ejs-support
Dig
1.3.3

dotenv
mik
1.0.1

remote-containers
ms-
0.362.0

remote-ssh
ms-
0.110.1

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.88.2

vscode-remote-extensionpack
ms-
0.25.0

remote-explorer
ms-
0.4.3

remote-server
ms-
1.5.1

material-icon-theme
PKi
5.3.0

better-comments
aar
3.0.2

node-json-autocomplete
bhs
0.1.3

js-codeformer
cms
2.6.1

jsrefactor
cms
3.0.1

codeium
Cod
1.8.40

vscode-eslint
dba
2.4.4

apt-source-list-syntax
dei
0.1.6

prettier-vscode
esb
10.4.0

rest-client
hum
0.25.1

search-node-modules
jas
1.3.0

node-module-intellisense
lei
1.5.0

vscode-exec-node
mir
0.5.6

debugpy
ms-
2024.6.0

python
ms-
2024.6.0

vscode-pylance
ms-
2024.5.1

live-server
ms-
0.4.13

node-debug2
ms-
1.43.0

live-server-preview
neg
0.1.4

phind
phi
0.25.2

material-icon-theme
PKi
5.3.0

LiveServer
rit
5.7.9

NodeJS-extension-pack
wal
1.0.0

five-server
yan
0.3.1

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
666c4381:30973075
chatpanelt:31048053
dsvsc021:30996838
0ee40948:31013168
pythoncenvptcf:31049071
a69g1124:31046351
88717513:31044517
dvdeprecation:31052039
pythonprt:31047983
dwnewjupytercf:31046870
26j00206:31048877

Does this reproduce in the latest VS Code insiders build with all extensions disabled (besides the remote extension)?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

authors: Mulih VSCodeTriageBot mjbvz


text:
Oatef4313@gmail.com

Type: Bug
Liuyvxdvhjudw
VS Code version: Code 1.90.1 (611f9bfce64f25108829dd295f54a6894e87339d, 2024-06-11T21:03:21.441Z)
OS version:
Modes:
System Info: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Mobile Safari/537.36Extensions (2)

Extension
Author (truncated)
Version

codespaces
Git
1.16.23

vscode-pull-request-github
Git
0.88.1

(1 theme extensions excluded)

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


text:
jjmace7

adb shell pm grant com.netvor.settings.database.editor android.permission.WRITE_SECURE_SETTINGS
### Tasks
- [ ] https://github.com/microsoft/vscode/issues/218340
- [ ] https://github.com/microsoft/vscode/issues/218343
- [ ] https://github.com/microsoft/vscode/issues/218339

### Tasks
- [ ] https://github.com/microsoft/vscode/issues/218343
- [ ] https://github.com/microsoft/vscode/issues/218341

/duplicate of https://github.com/microsoft/vscode/issues/218340

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


text:
running delay

Type: Performance Issue
when i try to run a program it has a really slow, i even tried with a hello world program and its still slow
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 5 PRO 4650G with Radeon Graphics (12 x 3693)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
13.90GB (6.29GB free)

Process Argv
--crash-reporter-id e33572c2-6d6f-4a58-90df-61b3af8d33c7

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	   108	 15760	code main
    0	   104	  1072	shared-process
    0	   103	 11432	window [2] (Issue Reporter)
    0	   143	 12272	   gpu-process
    0	    41	 12280	   utility-network-service
    0	   273	 13076	window [1] (test - Visual Studio Code)
    0	    96	 13708	ptyHost
    0	     6	  4372	     conpty-agent
    0	    63	  4392	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\browser\media\shellIntegration.ps1\" } catch {}"
    0	    63	  8372	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\browser\media\shellIntegration.ps1\" } catch {}"
    0	     6	 15436	     conpty-agent
    0	    66	 17564	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\browser\media\shellIntegration.ps1\" } catch {}"
    0	     6	 18396	     conpty-agent
    0	    88	 14212	fileWatcher [1]
    0	   179	 16908	extensionHost [1]
    0	     6	  4500	     "c:\Users\USUARIO 2\.vscode\extensions\ms-python.python-2024.10.0-win32-x64\python-env-tools\bin\pet.exe" server
    0	    10	  1556	       C:\WINDOWS\system32\conhost.exe 0x4
    0	    21	  4564	     "c:\Users\USUARIO 2\AppData\Roaming\Code\User\globalStorage\tabnine.tabnine-vscode\binaries\4.177.0\x86_64-pc-windows-gnu\TabNine.exe" --tls_config insecure=false --no-lsp=true --client=vscode --client-metadata clientVersion=1.91.1 pluginVersion=3.126.0 t9-vscode-AutoImportEnabled=true t9-vscode-TSAutoImportEnabled=true t9-vscode-JSAutoImportEnabled=true vscode-telemetry-enabled=true vscode-remote=false vscode-extension-kind=1 "vscode-theme-name=Default Dark+" vscode-theme-kind=Dark vscode-machine-id=b54609c44dbe92d9b2e2dbb492f73312a8d262cd3eeb106d2187865e5202caec vscode-is-new-app-install=false vscode-session-id=a3ce8858-d34e-4fda-b2fe-58ecb44e1c871720918554072 vscode-language=en "vscode-app-name=Visual Studio Code" vscode-beta-channel-enabled=false vscode-status-customization=unknown vscode-inline-api-enabled=true vscode-code-lens-enabled=true vscode-found-intellicode=false ide-restart-counter=0
    0	    10	  9376	       C:\WINDOWS\system32\conhost.exe 0x4
    0	    19	 17628	       "C:\Users\USUARIO 2\AppData\Roaming\Code\User\globalStorage\tabnine.tabnine-vscode\binaries\4.177.0\x86_64-pc-windows-gnu\WD-TabNine.exe" --tls_config insecure=false --client vscode --client-metadata clientVersion=1.91.1 pluginVersion=3.126.0 t9-vscode-AutoImportEnabled=true t9-vscode-TSAutoImportEnabled=true t9-vscode-JSAutoImportEnabled=true vscode-telemetry-enabled=true vscode-remote=false vscode-extension-kind=1 "vscode-theme-name=Default Dark+" vscode-theme-kind=Dark vscode-machine-id=b54609c44dbe92d9b2e2dbb492f73312a8d262cd3eeb106d2187865e5202caec vscode-is-new-app-install=false vscode-session-id=a3ce8858-d34e-4fda-b2fe-58ecb44e1c871720918554072 vscode-language=en "vscode-app-name=Visual Studio Code" vscode-beta-channel-enabled=false vscode-status-customization=unknown vscode-inline-api-enabled=true vscode-code-lens-enabled=true vscode-found-intellicode=false ide-restart-counter=0
    0	    69	 17760	       "c:\Users\USUARIO 2\AppData\Roaming\Code\User\globalStorage\tabnine.tabnine-vscode\binaries\4.177.0\x86_64-pc-windows-gnu\TabNine.exe" --tls_config insecure=false --no-lsp=true --client=vscode --client-metadata clientVersion=1.91.1 pluginVersion=3.126.0 t9-vscode-AutoImportEnabled=true t9-vscode-TSAutoImportEnabled=true t9-vscode-JSAutoImportEnabled=true vscode-telemetry-enabled=true vscode-remote=false vscode-extension-kind=1 "vscode-theme-name=Default Dark+" vscode-theme-kind=Dark vscode-machine-id=b54609c44dbe92d9b2e2dbb492f73312a8d262cd3eeb106d2187865e5202caec vscode-is-new-app-install=false vscode-session-id=a3ce8858-d34e-4fda-b2fe-58ecb44e1c871720918554072 vscode-language=en "vscode-app-name=Visual Studio Code" vscode-beta-channel-enabled=false vscode-status-customization=unknown vscode-inline-api-enabled=true vscode-code-lens-enabled=true vscode-found-intellicode=false ide-restart-counter=0 --no_bootstrap
    0	    13	  3136	         "c:\Users\USUARIO 2\AppData\Roaming\Code\User\globalStorage\tabnine.tabnine-vscode\binaries\4.177.0\x86_64-pc-windows-gnu\TabNine-server-runner.exe" vdb 1.7.3-fix.1 --tls_config insecure=false --port_env_var QDRANT__SERVICE__GRPC_PORT -- --config-path {BINARY_DIR}/config.yaml
    0	    28	  6568	           "C:\Users\USUARIO 2\AppData\Roaming\TabNine\servers\vdb\1.7.3-fix.1\download\vdb.exe" --config-path "C:\Users\USUARIO 2\AppData\Roaming\TabNine\servers\vdb\1.7.3-fix.1\download/config.yaml"
    0	   454	 18364	         "c:\Users\USUARIO 2\AppData\Roaming\Code\User\globalStorage\tabnine.tabnine-vscode\binaries\4.177.0\x86_64-pc-windows-gnu\TabNine-deep-local.exe" --settings "C:\Users\USUARIO 2\AppData\Roaming\TabNine\local.settingsce94127bSmall" --settings-version 1 --client vscode --client-metadata clientVersion=1.91.1 pluginVersion=3.126.0 t9-vscode-AutoImportEnabled=true t9-vscode-TSAutoImportEnabled=true t9-vscode-JSAutoImportEnabled=true vscode-telemetry-enabled=true vscode-remote=false vscode-extension-kind=1 "vscode-theme-name=Default Dark+" vscode-theme-kind=Dark vscode-machine-id=b54609c44dbe92d9b2e2dbb492f73312a8d262cd3eeb106d2187865e5202caec vscode-is-new-app-install=false vscode-session-id=a3ce8858-d34e-4fda-b2fe-58ecb44e1c871720918554072 vscode-language=en "vscode-app-name=Visual Studio Code" vscode-beta-channel-enabled=false vscode-status-customization=unknown vscode-inline-api-enabled=true vscode-code-lens-enabled=true vscode-found-intellicode=false ide-restart-counter=0 --tls_config insecure=false
    0	    89	  6900	     "C:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=16908
    0	   156	  7928	     electron-nodejs (tsserver.js )
    0	   110	  7132	       electron-nodejs (typingsInstaller.js typesMap.js )
    0	    94	  8924	     "C:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\css-language-features\server\dist\node\cssServerMain" --node-ipc --clientProcessId=16908
    0	   145	 10644	     electron-nodejs (tsserver.js )
    0	   174	 13960	     electron-nodejs (bundle.js )
    0	   113	 17656	     "C:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\USUARIO 2\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\html-language-features\server\dist\node\htmlServerMain" --node-ipc --clientProcessId=16908
    0	    28	 17260	   crashpad-handler

Workspace Info
|  Window (test - Visual Studio Code)
|    Folder (test): 3 files
|      File types: py(2) json(1)
|      Conf files:;

Extensions (12)

Extension
Author (truncated)
Version

hmmm-language-support
Coo
2.0.3

prettier-vscode
esb
10.4.0

vscode-vibrancy-continued
ill
1.1.35

vsc-python-indent
Kev
1.18.0

prettify-json
moh
0.0.3

debugpy
ms-
2024.8.0

python
ms-
2024.10.0

vscode-pylance
ms-
2024.7.1

material-icon-theme
PKi
5.4.2

LiveServer
rit
5.7.9

tabnine-vscode
Tab
3.126.0

vscode-todo-highlight
way
1.0.5

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelc:31048052
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
legacy_priority:31094926
pythonrstrctxt:31093869

nvm i just had to uninstall git

nvm it still happening


text:
Asking password everytime while remote server connection

Type: Bug
Top panel always ask for password everytime while establishing remote server connection.
if we enter, it will ask for reload window.. and then asks for password..
can we have auto save option like winSCP? and avoid asking password multiple times
VS Code version: Code 1.92.1 (eaa41d57266683296de7d118f574d0c2652e1fc4, 2024-08-07T20:16:39.455Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 4.18.0-348.7.1.el8_5.x86_64

System Info

Item
Value

CPUs
AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics   (16 x 3294)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
30.72GB (19.44GB free)

Process Argv
--crash-reporter-id a4ac3709-3654-487b-9e7c-eedb632d6f56

Screen Reader
no

VM
0%

Extension
Author (truncated)
Version

remotehub
Git
0.62.0

remote-ssh
ms-
0.113.1

remote-ssh-edit
ms-
0.86.0

azure-repos
ms-
0.38.0

remote-explorer
ms-
0.4.3

remote-repositories
ms-
0.40.0

copilot
Git
1.221.0

copilot-chat
Git
0.18.1

cmake-tools
ms-
1.18.44

cpptools
ms-
1.21.6

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

(2 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl2:31104044
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-c:31111717
wkspc-ranged-c:31111712

What kind of remote connection is this?

Linux server (connected with private VPN only), connecting remotely using MS VSCode from Windows OS.
Is there any option to save passwords of remote servers in VSCode?

@mopathan this is a Remote SSH connection, yes?

Yes, it is SSH remote connection.

@mopathan This extension leverages your system's built-in ssh program and configuration file.  Sounds like in this instance you may want to set up SSH key auth between your local machine and your server.  This will be set up outside of the extension.  See this blog post as a starting point.

authors: TylerLeonhardt bpasero joshspicer mopathan


text:
way to identify code action that are requested from extension in order to disable the unnecessary and time consuming ones.

Type: Bug
While saving file vscode gets a lot of code actions from various extensions.
if i want to disable any of the code action there is no clear document as to what needs to be configured in order to avoid specific code action.
for example. while saving file the code action from Intellicode API Usage Examples extension is shown in the notification.
If i want to disable this i do not know what needs to be cofigured in the "editor.codeActionsOnSave": { section to avoid this.
some way to identify such code action in order to disable them would be great

VS Code version: Code - Insiders 1.94.0-insider (8b7eb51f54d7e1492d9baf70454ab6547a4ff9df, 2024-09-10T05:04:21.546Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 4.4.0-22621-Microsoft

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
15.82GB (1.22GB free)

Process Argv
--folder-uri=vscode-remote://wsl+Ubuntu/home/sanket/code/dps-fabric-ui --remote=wsl+Ubuntu

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 4.4.0-22621-Microsoft

CPUs
Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 0)

Memory (System)
15.82GB (1.22GB free)

VM
0%

Extensions (25)

Extension
Author (truncated)
Version

vscode-drawio
hed
1.6.6

output-colorizer
IBM
0.1.2

remote-wsl
ms-
0.88.2

ng-template
Ang
18.2.0

vscode-markdownlint
Dav
0.55.0

vscode-eslint
dba
3.0.10

gitlens
eam
15.4.0

EditorConfig
Edi
0.16.4

prettier-vscode
esb
11.0.0

mongodb-vscode
mon
1.8.1

vscode-scss
mrm
0.10.0

vscode-dotnet-runtime
ms-
2.1.5

data-workspace-vscode
ms-
0.5.0

live-server
ms-
0.4.14

vscode-typescript-next
ms-
5.7.20240904

angular-console
nrw
18.27.0

vscode-xml
red
0.27.2024082510

vscode-yaml
red
1.15.0

sonarlint-vscode
Son
4.10.0

code-spell-checker
str
3.0.1

vscode-stylelint
sty
1.4.0

win-ca
uko
3.5.1

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.3.1

vscodeintellicode-completions
Vis
2.0.0

We don't know what specific code actions an extension will return until it actually returns them. That's why we show the extension names instead
Please try going through those extensions and disabling them until you find which one causes the problem

i am just venting out my frustration below. i am not frustrated with VSCode just the extension (which are not supposed to be there) coming in and delaying my file saving, i love VSCode and and the extensions mentioned. this is not a rude comment. (i read it a few times, it felt rude, asked bing copilot to reword, still feel it being rude)
@mjbvz, here are a few points to consider:

The issue isn't identifying the problematic extension; I'm aware it's the Intellicode API Usage Examples.
Since the extension is beneficial during coding, simply disabling it isn't an ideal solution. This isn't limited to this extension; I've noticed similar behavior with the Microsoft Edge DevTools extension as well.
I'm content with the extension until it interferes during file saving. I don't see any reason for Intellicode API Usage Examples to activate while saving a file.

Stylelint? Yes, please correct my styles.
ESLint? Certainly, address my linting issues.
SonarLint? Absolutely, point out or correct errors.
TypeScript language service? Definitely.
Intellicode API Usage Examples? Why does it appear when I'm saving my file? I don't need it then. Please leave.

How do I disable the auto-fix on save? I know it can be done with:
 "editor.codeActionsOnSave": {
    "source.action.organizeImports": "explicit",
    "source.fixAll": "explicit",
    "source.organizeImports": "explicit"
  },

But how do I specifically disable it for Intellicode API Usage Examples? I couldn't find this information.
Does the extensions page display this information? No, it doesn't.

Should the extension even intervene when I'm saving a file? I can't see why it should, or rather, I prefer it didn't.
Why am I addressing this bug/feature request to VSCode rather than the extension itself?

With the multitude of extensions available, addressing each one individually would be overwhelming.

My expectation from VSCode:

Please log the code action whenever possible, without requiring them in advance. Just log them at any convenient time, so I can identify the culprit that's been delaying my file-saving process.

@mjbvz any thoughts?

started getting code action for extension authoring while saving file now.

authors: mjbvz sanket-bhalerao


text:
[Chat] Tree element not found: [object Object]

 ERR TreeError [Chat] Tree element not found: [object Object]: Error: TreeError [Chat] Tree element not found: [object Object]
    at ObjectTreeModel.getElementLocation (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/base/browser/ui/tree/objectTreeModel.js:218:19)
    at ObjectTreeModel.expandTo (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/base/browser/ui/tree/objectTreeModel.js:180:31)
    at WorkbenchObjectTree.reveal (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/base/browser/ui/tree/abstractTree.js:2281:20)
    at ChatWidget.scrollToEnd (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/contrib/chat/browser/chatWidget.js:337:23)
    at ChatWidget.layout (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/contrib/chat/browser/chatWidget.js:908:18)
    at EditorBasedInlineChatWidget._doLayout (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/contrib/inlineChat/browser/inlineChatWidget.js:249:26)
    at EditorBasedInlineChatWidget._doLayout (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/contrib/inlineChat/browser/inlineChatWidget.js:424:15)
    at EditorBasedInlineChatWidget.layout (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/contrib/inlineChat/browser/inlineChatWidget.js:234:18)
    at InlineChatZoneWidget._doLayout (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/contrib/inlineChat/browser/inlineChatZoneWidget.js:141:21)
    at InlineChatZoneWidget._onViewZoneHeight (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/contrib/zoneWidget/browser/zoneWidget.js:203:18)

To verify

use inline chat, accept its change
use inline chat again
make sure the error above isn't printed on the console


text:
Save proxy authentication

Issue Type
Feature Request
Description
Each time I open VS Code, it displays a form asking for my proxy settings. Isn't there a way I could check some box and it would repropose the form filled,  at least?
Thanks!

VS Code Info
VS Code version: Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:34:36.336Z)
OS version: Windows_NT x64 6.1.7601

Will it come one day?

Same issue for me, the pop-up appers twice (once for the Extensions I guess).
Windows 10, 64-bit
VS Code 1.33.1 (user setup)
I tried lots of things in the GUI settings and settings.json for User Settings and Workspace Settings, also both as mentioned in https://github.com/microsoft/vscode/issues/32566#issuecomment-480692463
    "http.proxy": "http://user:password@proxy-ip:port" (with password, without, username only, ...)
    "http.proxyStrictSSL": false or true
    "http.proxySupport": "on (override, off, ...)

The environment variables are set (lowercase) and work fine for other programs
https_proxy=http://user:password@proxy-ip:port
http_proxy=http://user:password@proxy-ip:port

What is the expected behaviour? Is VS Code always supposed to ask for the password even if it is stored in the URL in the settings or the environment variables?
Could there be a "store password" in this pop-up which puts it to the settings.json if authentication works?

I found this issue https://github.com/Microsoft/vscode/issues/38888
They mention that supplying the proxy parameters on the command line works, even if setting it in VS Code doesn't. And this works for me. Still not beautiful, as the password is clear text, but for the other options (environment variables, settings.json) this would also be the case.
So I added this to my desktop shortcut and the two popups are gone:
"C:\Path\To\Code.exe" --proxy-server=http://user:password@123.123.123.123:8080

that supplying the proxy parameters on the command line works, even if setting it in VS Code doesn't.

Then you'll have to edit all reference to code.exe in the HKCU branck of registry too (shell\open\command  for several object types)

True, and there was another response https://github.com/microsoft/vscode/issues/32566#issuecomment-530294695 that it doesn't work.
Just the popup is gone.
Is there a way to see which proxy settings are being used when VCS is connecting somewhere? I checked the developer tools but they only state the errors.

I tried the workaround using node here and it works fine: https://github.com/microsoft/vscode/issues/32566#issuecomment-530995464

@joaomoreno Is there any plan to do something about it?

No plan so far.

No plan so far.

Sad. Time to expect a closed issue with a "won't fix" status then  :-/

No plan so far.

Can't believe no one @microsoft care about such an issue which is in 2020 rather a core design issue than anything else... VSCode was meant for developers and developers mainly work in organisations with most of the big ones using proxies since like 20 years, at least.

/duplicate #32566

authors: gpion joaomoreno solarjoe willemavjc


text:
VS Code changes indention of current line

I am using VS Code 1.28.2 on Windows 10. I'm editing an HTML file indented with tabs. But I have HTML
 sections which I want indented with spaces.
Let's say I have the following code:

  foo //I press <Enter> at the end of this line

When I open the file VS Code detects I use tabs. Fine.
When I hit <Enter> at the end of the line that says "foo", VS Code indents the next line. Fine.
VS Code isn't smart enough to realize that I want to indent the next line with spaces instead of a tab, because it already got into its head that I want to use tabs everywhere. It's not smart enough to realize that the previous line   foo was indented with spaces. It uses a tab for the next line. But OK, I can live with that, too. It's understandable.
Bug: What isn't acceptable is that VS Code changes the indention of the existing line from spaces to tabs!!

Yes, when I hit <Enter> after "foo", it not only indents the next line but changes the indention that comes before foo from spaces to tabs.

  foo //bug: the two spaces have been converted to a tab!
  //this new line also has a tab, which I don't want but can accept for now

VS Code has no business of changing the existing line. I simply hit <Enter> to go to the next time. This is a huge problem, and it has likely corrupted a bunch of lines in this file because I didn't catch on to what it was doing.
Sure, we have auto-indent features to try to automatically insert indent on the following line, but please don't mess with the line I already have.
How can I turn this off?

No, the bug I'm filing is not covered by those existing tickets.
I'm filing a bug where VS Code changes the existing indentation of an existing line. The issue is not about what default indention to use on a new line (although I could quibble about that, too—but that's a separate issue).

You can now turn off editor.autoIndent to workaround for now.

You can now turn off editor.autoIndent to workaround for now.

Please clarify the exact steps to do this? Please see also issue #109382

Hi @garretwilson thank you for posting the issue. I am trying to reproduce the behavior on the latest insiders. In the GIF below, the whitespaces are rendered in the editor to better understand what is happening. Spaces are rendered as dots and tabs are rendered as arrows. When I press Enter after the end of the second line, the spaces don't seem to be changed to tabs, and spaces are inserted at the beginning of the new line (not tabs). Granted there is one more indentation level on the next line, which I will look into. It only seems to happen when the // are used however.
https://github.com/microsoft/vscode/assets/61460952/fbb9ab78-90a3-4327-a3eb-fc53f35fa549

@aiday-mar , one thing you seem to have missed in my report is this:

I'm editing an HTML file indented with tabs.

I can't see the bottom of your screen to know for sure, but I'll bet you have the file set up so that VS Code thinks you are indenting with tabs. Tell VS Code that you are using tabs for indention.
Better yet, create an entire HTML file (you can find gajillions on the web) that is indented using tabs, or convert it to use tabs. (I can see you're only using three lines, not an entire HTML file.) Then close and open the file so that VS Code detects you're using tabs. Then type those lines from the example, but use spaces do indent.
(Why do I want to use spaces to indent inside
? Because of many reasons. The point of
 is that it maintains the formatting, and VS Code should know that when editing in HTML mode.)
As of 2024-06-08, VS Code no longer converts the first line to tabs, so that is an improvement. However it still indents on the next line using tabs, even though the
 section is using spaces to indent.
Converting the original line (already indented) from spaces to tabs seems to have been fixed, so this ticket can be closed. (Indenting the following line with tabs when the
 indents using spaces is a separate issue.)

authors: aiday-mar garretwilson rebornix sohrabsaran


text:
Editor width changes when toggling sidebar, breaking auto-expand of focused editor functionality.

VSCode Version:

$ code --version
1.36.1
2213894ea0415ee8c85c5eea0d0ff81ecc191529
x64

OS Version:

$ uname -v
Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64

Steps to Reproduce:

Open VS Code and close all editors.
Close/Hide the sidebar.
Create two side-by-side editor panes.
Resize the editor panes so that one is as small as it can be / the other is as big as it can be.
4a. Sanity-check that when you enter focus in an editor pane that it auto-maximizes the pane.
Open/Reveal the sidebar.
Focus on an editor pane that is not currently in focus. It will auto-maximize the pane. This step is required to cause the bug in step 8 to manifest.
Close/Hide the sidebar.
Focus on an editor pane that is not currently in focus; it does not auto-maximize anymore, as the editor panes are no longer the minimum/maximum relative size.

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

Can you link which issue this is a duplicate of? I have searched for this issue and could not find it. Thank you.

@bpasero Can you please link the issue you believe this is a duplicate of?


text:
Typescript: unused variable false warning and incorrect Quick Fix option

VSCode Version: 1.36.1
OS Version: Windows 10 (x64)

tsconfig.json
"noUnusedLocals": true
Declaring multiple variables in typescript in a single let statement, produces a warning that variable is declared but never used. Now even after writing line further lines where variable is used, still the error persists.

Add to it on clicking Quick Fix,  VS Code displays option of Remove Declaration for that variable. Selecting that option removes all lines containing reference of that variable, which is a destructive action which may result to deletion of legible code too.

Kindly refer screen-clipping of warning and GIF of Quick Fix action

This is correct warning because variable is block scoped (declared with let) and there are no instances where it is used to calculate anything other - only reassignment later.
This error will go away as soon as you use it in expression, pass as an argument to a function etc.
If you look from other perspective - you remove come unnecessary call to a function from block. TS marks all variables that were passes to the function and not used anymore.


text:
Unable to find definition from index file while on the same folder

Issue Type: Bug
VSCode is not able to navigate to the definition from an index file to a file that is on the same folder.
Here is a little but simple example:
index.js
import Conversation from './Conversation.component';

export default Conversation;

Folder structure
Conversation
 \_ index.js
 |_ Conversation.component.jsx

When you try to go to the definition of the only import on the index file it just goes to the index itself.
VS Code version: Code 1.37.1 (f06011ac164ae4dc8e753a3fe7f9549844d15e35, 2019-08-15T16:16:34.800Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2900)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
32.00GB (0.10GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (52)

Extension
Author (truncated)
Version

yaml2json
ahe
0.0.3

auto-add-brackets
ali
0.10.0

Handlebars
and
0.4.1

jest-snippets
and
1.7.0

better-toml
bun
0.3.2

npm-intellisense
chr
1.3.0

vscode-devtools-for-chrome
cod
0.0.5

danielo-node-snippets
dan
1.8.1

danielo-vsc-tools
dan
1.0.1

vscode-eslint
dba
1.9.1

jest-test-language-support
dpl
1.30.2

es7-react-js-snippets
dsz
2.4.3

gitlens
eam
9.9.3

EditorConfig
Edi
0.13.0

vimL
fal
0.0.3

auto-rename-tag
for
0.1.0

lintlens
ghm
2.4.0

vscode-pull-request-github
Git
0.10.0

githd
hui
2.1.0

vscode-peacock
joh
3.1.4

styled-components-snippets
jon
0.4.0

open-in-vim
jon
0.5.0

vscode-styled-components
jpo
0.0.26

expand-region
let
0.1.2

vscode-wrap-console-log
mid
1.7.2

dotenv
mik
1.0.1

vscode-docker
ms-
0.7.0

debugger-for-chrome
msj
4.11.7

color-highlight
nau
2.3.0

incrementor
nms
0.1.0

indent-rainbow
ode
7.4.0

advanced-new-file
pat
1.2.0

vscode-quick-spec
rau
0.1.0

vscode-yaml
red
0.5.1

partial-diff
ryu
1.4.0

vscode-javascript-booster
sbu
0.11.0

bash-beautify
sha
0.1.1

code-settings-sync
Sha
3.4.2

addDocComments
ste
0.0.8

code-spell-checker
str
1.7.18

control-snippets
svi
1.3.0

json-schema-validator
tbe
0.1.0

highlight-matching-tag
vin
0.9.3

template-strings
vit
0.0.5

vscode-icons
vsc
9.2.0

vscode-wakatime
Wak
2.2.0

vscode-import-cost
wix
2.12.0

change-case
wma
1.0.0

vscode-jumpy
wma
0.3.1

disable-eslint-rule
Woo
0.0.2

vscode-open-in-github
ziy
1.3.6

es6-string-javascript
zjc
1.0.1

Where exactly are you running go to definition?
Also does this reproduce in the latest VS Code insiders build with all extensions disabled?

I'm running it on any place of the codebase, same result.
I am not running the insiders build, but I cant try with all the extensions disabled to see if that makes a difference.
If it does, I may try to provide a small reproduction repo

It still happens with extensions disabled.
However, I tried to create a small reproduction and it works fine on my example. Is there any way I can debug how this happens in some repos? Some console output explaining the steps tried to find the definition that failed?

Did you have a change to test using the insiders build?
You generally cannot debug this type of issue on your own. The best option is for you to provide a small example project so we can debug it, or you could try sending us detailed logs. Are either of those possible?

As I said I tried to create a small reproduction without success, it only happens on my big project. So I think the best option will be to use the insiders build and provide detailed logs. How can I fetch such logs? What should they include?

To collect the TS Server log:

Set "typescript.tsserver.log": "verbose",
Restart VS Code and reproduce the problem
In VS Code with a ts file open, run the TypeScript: Open TS Server log command
This should open a large log file called tsserver.log

Look through that log file for errors or stack traces. If you can share the log, I can take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

Sorry for the late response.
It is still happening, but on a different fashion. Instead of redirecting you again to the same index file it simple does nothing.
I have the (huge) log. I'm not worried about paths, but I don't want to expose src if there is any.
Is there a way that I can send it to you?

Well, I can always remove it later.
tsserver.log

Please try upgrading your workspace to use typescript@next by installing this extension
Do you still see the issue in that case?


text:
Many Different Extensions Frequently Crash All Others on Startup with Reoccurring "Extension host terminated unexpectedly" – Extension Sandboxing / Isolation, Missing Error Log Fixes and Host Auto-Restart Needed

There have been far too may reports (800+ now) of the VSCode Extension Host crashing with "Extension host terminated unexpectedly" like shown in the below screenshot:

When this happens, one extension ends up crashing all other extensions and even crashing core VSCode services as well as apparently preventing logging of the errors, and then requires users to manually restart all extensions.
These issues affect a wide range of popular extensions, including core Microsoft ones like Live Share Audio, as well as frequent third party ones like Live Chat (karigari.chat) and Live Server. And there are 800+ reports of the critical "Extension host terminated unexpectedly" errors, and this issue becoming far more frequent of late.
It's not even possible to determine the problematic extension (so that you can disable it and submit a bug report) – even if you were to startup 170 times with a different extension disabled each time, as, for some reason, the original extension error and even the extension host crash itself, as well as what extension was starting to be activated or updated, often fail to ever get logged when such crashes occur.
This has become more frequent and has been reoccurring for extensions even after fixing it, breaking again even when no extension updates were released.  It has been causing VS Code to crash on startup much of the time for many months now without any way to identify and disable the extension causing it. Then, after finally disabling one that fixed for a while, another extension started causing the same thing all over again. And, on each VSCode startup, repeated manual user intervention is often required to resolve what could be auto-repaired.
Therefore, it seems that VSCode changes are needed to minimize these issues (vs many repeated workarounds for each extension) – both short-term and long-term – as outlined further below.
The Case for Extension Sandboxing
I believe these widespread reoccurring critical issues also indicate the need for Extension Sandboxing (like proposed in #52116). Among other benefits, that would prevent extensions from crashing any (or at least not all) other extensions as well as core VSCode services, make it possible to determine which extensions are crashing, and also open the door to security benefits with extension permission management. I've
Repeated Critical Crashes on Startup I've Encountered For Months with Multiple Different Extensions
I have had to manually restart extension host nearly every time I started VSCode for months now. Then, finally, after identifying and disabling the problematic extension (only possible by reading through may bug reports to determine most likely causes), the issue started happening again, with another extension (equally difficult to determine which one).
And that was for an extension where the issue had been fixed several times already, with no update released since the last version fixing it, yet the issue started occurring again (possibly due to VS Code or other extensions changing). Considering that as well as how it seems to almost be randomly occurring, always on startup (eg. as if timing related or while other extensions are being updated), then it may be
that something in VSCode needs to change to minimize these issues.
Related Bug Report with Log Files
You can find details regarding my own most experiences with VS Code host crashes for the most recent extension, Live Server, at ritwickdey/vscode-live-server#552.
There, I've provided zips of log files when crashes do and do not occur (as needed for comparison due to lack of detailed logging when crashes occur).
I've also referenced to a number of related issues in that report, as well as further below.
That does not include my earlier months of VS Code crashing on startup with other extensions, such as what I'd eventually identified (despite lack of any indication in log files) as being caused by Live Share Chat, which I'd fixed just a week or so before encountering with Live Server as well.
Suggested VSCode Fixes / Changes (to Minimize Host Crashes, Allow Identifying Problem Extensions, and Prevent Crashing All Extensions)

Extensions should not be frequently crashing other extensions (especially not crashing ALL of them)
Extensions should not be crashing core VS Code services like the shared Extension Host (and potentially even logging services, etc.)
VS Code Extension Host should be auto-restarted when that occurs within seconds of startup, where there is no risk of data loss (especially since has been 100% successful so far when doing so)
VS Code should also identify the extension causing the error, when possible, report to the user, log it, and prompt the user to disable it.
Fixes for issues preventing both the crash and original errors from ever getting logged should be fixed.
Extensions shouldn't be crashing the
VSCode or Extension Host changes should be made to minimize such frequent and reoccurring host crashes
Extension Sandboxing / Isolation should be considered, for both Reliability (so as to avoid not crashing all extensions and core services) at the very least, make it possible to determine which extension is the one crashing, and even open the door to security benefits (with permission management being the norm for browser, etc. extensions these days)
Sandboxing would also opening the door to security benefits with extension permission management (as is common)

Identifying and Addressing the Root Cause vs. Repeated Per-Extension Temporary Workarounds
It would be helpful if someone could investigate what, if any, common denominator there may be between the different extension host crash causing extension issue (such as use of binary dependencies or how extensions are updated or activated) or such as the various extensions starting with "Live" in their name (if not a coincide with them being the most frequent offenders).
The root cause should be addressed – with changes made to VSCode (or the extension host) to minimize them instead of requiring extension developers to have to keep (clearly unreliably, temporarily) implementing workarounds for each extension. Whether changes to how extensions are
800+ Outstanding Issue Reports and Many (Even Official) Extensions with Frequent, Reoccurring Extension Host Crashes
Many others are reporting the same, such as my recent report (ritwickdey/vscode-live-server#285) as well as #72476, #75267, MicrosoftDocs/live-share#1510, ritwickdey/vscode-live-server#285, Live Share Chat review, and 250+ other "Extension host terminated" bug reports just in the VSCode repo, 133 open issues under chrmarti/testissues and 850+ "Extension host terminated unexpectedly" bug reports across all GitHub VSCode extension repos
Other recent reports in VSCode repo:
#77099, #79177, #78524, #78196, #77917, #77780, #78809, #78331, #78196, #77768, #77547, #77505
Other issues related to extension crashing affecting other extensions:
#73041, #24441, #76178
Many Different Extensions Frequently Crash ALL Other Extensions with Issue Reoccurring or Unable to Be Fixed
Just a few of the highly popular, and even Microsoft official VSCode extensions which this occurs for includes:
Live Share Audio, Live Server, Live Share Chat (karigari.chat), Live Share, Live SASS Compiler, Typed Test, Java Language Server, Peacock, and Mocha Sidebar
Not only are these issues widespread across a large number of popular extensions, but they are reoccurring. The issue keeps coming back for the same extensions not long after each fix is released.
Extension Host Crash Reappears After Fixing even when Extension Weren't Updated Since
With Live Server, as well as other extensions, such extension host crashing on VSCode startup has come back every time it gets (temporarily) fixed.
In that issue I'd just reported for Live Server, for example, the crashing started occurring again for the very same extension version (5.6.1) which was released specifically to fix the issue and which had been confirmed (for a little while) as having done so, as seen in
vscode-live-server#431 the issue is back not months after the last update which was released specifically to address that issue.
Accordingly, it seems like changes to VSCode itself (or possibly frequently arising conflicts between extensions may be the cause) may be part of the issue preventing reliable fixes or avoidance of such crashes.
And before that was report "Extension host terminated unexpectedly is back" (ritwickdey/vscode-live-server#399) about how the issue had come back after having been fixed a number of times before even that.
Crashes ALL Extensions and Core VSCode Services
Worse yet, such crashes don't just affect the problematic extension, they crash ALL extensions.  Even worse, they crash a core VSCode service, the Extension Host, and require the user to manually restart the host to reload all extensions.
Especially considering that, it seems like some kind of core VSCode or Extension Host changes may be needed to reduce, avoid or at least isolate the effect of the errors which are currently causing frequent reoccurring Extension Host crashes.
Some of the Popular Extensions Most Frequently Causing Extension Host Crashes
This issue is well known to often occur with Live Share Chat (karigari.chat) like reported in #77099 and mentioned in dozens of other VSCode issues. And it remains an open known issue, again, which is still unable to be addressed, like seen at vsls-contrib#410.
Even Microsoft's own Live Share Audio extension (as well as Live Share itself) frequently causes Extension Host crashes. And there is no plan to fix it any time soon, according to its developers.
Possible Causes of Frequent Extension Host Crashes (eg. Timing or Dependencies)?
Can anyone clarify what the common causes of such crashes are? I've seen reference to use of binary dependencies as a common case. Is that so? Why would such crashes start occurring again, with the same version where it was fixed previously, despite no new updates to such fixed extensions?
Whatever the cause, this seems widespread enough and critical enough that I would suggest something be done to minimize the frequency of such Extension host crashes, if possible.
Does anyone have any ideas on what might be able to be done to help reduce the frequency of Extension Host crashes?
If the most recent fixes for Live Share Chat (which was causing months of issues prior to Live Server) are any indication (where "Add Live Share as an extension dependency to fix timing issues during activation" is mentioned as the primary fix in v0.21.0 released on 2019-08-19), then interdependency between extensions and timing related issues might be one type of common cause in Extension Host crashes, especially considering how the crashes don't occur on every startup (just seemingly randomly ones).
I'd also seen extension a number of "Deleted from disk" entries in sharedprocess.log (one of the few non-empty log files) as well as "Starting to clean up unused language packs.", which I mention in case the timing of such extension updates/cleanups might be a factor.
Extension Sandboxing / Isolation Needed for Reliability (as well as Security) (+ Link to Detailed Proposal/Ways to Implement with Electron)
In any case, this is a good example of why Extension Sandboxing / Isolation is needed.
I had previously proposed in #52116 several options for implementing Extension Sandboxing / Isolation for reliability and security (as well as Chrome/Firefox-like Permission Management). There are several projects, like I'd summarized there, which could be utilized or which have successfully implemented such extension sandboxing, even with Electron-based apps like VSCode and Electron options/APIs now available, which could be used as a model or incorporated directly.
Need to Auto Restart Host If Occurs Immediately Upon Startup
Also, at the very least, I believe that there should be an option to automatically recover.
Ideally this can occur after logging the crash itself, trying to identify which extension may have caused the crash and logging and reporting that to the user, and then flushing the logs (without waiting for any user interaction).
Then the Extension Host should be automatically restarted when Extension Host crashes on startup.
This is important and reasonable to do because, in each of the many dozens of crashes I've encountered, this crash occurs within seconds of VSCode startup, and restarting always fixes the issue successfully (which my never encountering another host crash afterward during that session).
Therefore, IMO, the extension host should always be automatically restarted if it crashes within a configurable number of seconds (which could default to 5 or 10) such apparently expected. This seems reasonable handling for what is apparently far from exceptional and repeated issues, especially when automated recovery/restarting without any impact on the user can occur and even more so if this might be related to auto extension downloading/updating/install which may be occurring prior to the crash.
The user should be notified still, but there should be an option to hide such future notifications (at least showing such an option if another crash notification occurs within X days or Y number of startups since the last one) to avoid nagging the user. Especially when, at one point, I had to see annoying crash notifications and manually restart as prompted nearly every time I launched VS Code, without any indication of what extension caused or way for me to stop this occurring for months on end.
Need to Report the Extension Causing the Crash & Prompt to Disable
Also, VSCode should try to determine which extension caused (or set of extensions may have likely caused) the crash. If a specific extension can be identified as the cause, that should be shown to the user together with the host crash notification, and with a suggestion (at least for repeat offender extensions) and in-notification button (together with the Show Developer Tools and Restart Extension Host buttons) or 1-click disabling of that extension. Most often so far, the extensions causing such crashes are ones I can live without.
Currently Impossible to Identify Extension Causing Crash (Due to Logging Issues and Lack of Isolation)
However, the most important problem of all, is that it, as it stands now, it is nearly impossible to identify which extension is causing the problem.
It's not feasible for users to test startups by disabling extensions one-by-one to determine which extension or combination of extensions is causing the issue. In fact, that becomes virtually impossible when you consider that such crashes on startups don't happen every time (just every day or two in many cases). And even more so, when it might be a conflict between multiple extensions (as I've seen reference to in other issue reports) or there are multiple extensions causing such crashes at the same time (which I have also encountered).
Extension Error and Even Host Crash Itself Fail to Get Logged or Flushed
Even after finding and reading through (as well as searching) every single log file under Roaming/Code/Logs for the session (including the annoying number of empty folders to search through which are created on each startup, which I would suggest be created as-needed instead) there was absolutely no logged error. Even the activation of the extension which ended up seeming to be the cause of the crashes didn't end up in the logs or flushed to disk. And restarting the extension host or showing Developer Tools ended up obscuring the log entries and can occur 20 minutes after the actual crash (as was the case for me).
However, the only time I saw an actual error logged related to the host crash was after Restarting the Extension Host and showing Developer Tools, in which case it either failed to show anything from before that or it obscured it with many more entries. Even then, it was just a generic extension host crash error, without any indication of the original cause (neither extension or the error that caused it).
When trying to look for the relevant errors to identify which extension may have caused them and therefore which to try to disable to avoid these crashes, it was always the case that almost all log files were empty (extensions.log, tasks.log, essentially main.log for most part, and nearly all files in the few created "output_" subfolders).  No errors appeared (except for a few clearly unrelated warnings which occurred even in non-crash cases).  Only by comparing to non-crash startup logs could I get an idea of what might have caused the issue, and only by looking at what log entries were missing such as for extension activations that occurred immediately after where the log file was cutoff.
Logging Fixes Needed So Crash or Extension Error Is Actually Logged
As the host crash error itself doesn't end up in the log files in many cases under Roaming/Code/Logs or visibly elsewhere (other than the notification box shown to the user) the following might be helpful:

Flushing logs more frequently and/or after crash occurs
Log host crash error sooner (before waiting for user to possibly restart the host)
Ensure original log entries are shown even after restarting the host and then showing developer tools
Changes to logging so not affected by extension host crashes
Log "Starting ..." for more operations (and flushing to disk) like "Downloading/Deleting/Extracting extension/update started" vs. just after "Downloaded/Deleted" etc. so know which extension may have caused the crash

My Platform and Configuration

Visual Studio Code v1.37.1 (user setup)
Windows 10 x64 Pro (Windows NT x64 10.0.18362)
Startup Command line args: "C:\Users\Dan\AppData\Local\Programs\Microsoft VS Code\Code.exe" "C:{My Project Path}\README.md"
Electron: 4.27
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
Live Server (ritwickdey.liveserver) extension v5.6.1

I know my extension causes the host to crash, but I have no way of find our where or how. :disappointed:
Please address this somehow vscode team!

@RMacfarlane and @kieferrm, please see the crash report which I just submitted, #80165 for additional details and logs likely useful for debugging this.
That provides detailed logs that may help in debugging this issue, with logs both for sessions with and without this issue occurring, despite same steps to reproduce (needed since doesn't seem to log any extension-specific errors related just to the crash case), as well as logs for session preceding the crash (in case related to extension updating/cleanup) and log files saved from Developer Tools (which show some errors, which otherwise don't get saved to log folders on disk).

Why is this not a higher priority?
I recommend the sandboxing solution (#52116) Without it, VS Code looks like a liability to the IT departments that might consider approving it! (think about trying to determine the risks of a wide variety of addons, and whether they will be stealing company secrets like proprietary code)

On kinda related note, Chat Session from VS Live Share is randomly closing after 2 minutes of inactivity. I don't know how to catch it, but it just happened a lot today, when I tried it out with my student.

authors: Gruntfuggly Narvey PowerAccess PowerSheetAI vintprox


text:
How to make incognito like sessions for code-runner terminal?

Hey theres this thing I can't solve where any command you run inside vscode terminal like python3 -u "/home/linux/Documents/Piethon/Exercise2.py" it gets stored in the gnome-terminal history file. How can I turn this off or disable?

code runner is an extension

authors: Tyriar sidbelbase


text:
MRU list contains some files but certainly not the last ones that I closed

Issue Type: Bug
MRU list is never never up to date. I dont even know if and when I opened the files that it contains. If I close a file I'm sure it won't be listed, I have to find it back in my hard drive. Very annoying for such a simple feature.
VS Code version: Code 1.41.0 (9579eda04fdb3a9bba2750f15193e5fafe16b959, 2019-12-11T18:37:42.077Z)
OS version: Windows_NT x64 10.0.18362

@par4dise which "MRU list" are you talking about


text:
Pull request icon (git-pull-request) is the same as compare

I think it should be more like the octicons one: https://octicons.github.com/icon/git-pull-request/
Here is a version that adapts the current to the octicon structure:
<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
<path fill-rule="evenodd" clip-rule="evenodd" d="M4.03893 4.99056C4.03893 4.99056 4.35057 4.91224 4.49892 4.85054C4.95516 4.6608 5.34497 4.34017 5.61906 3.92903C5.89316 3.51789 6.03926 3.03474 6.03893 2.54061C6.0463 2.19765 5.98157 1.85696 5.84892 1.54061C5.72425 1.23755 5.54075 0.962142 5.30904 0.730425C5.07732 0.498708 4.80197 0.315179 4.49892 0.190508C4.18256 0.0578651 3.84188 -0.00680644 3.49892 0.000566441C3.00479 0.000236948 2.52166 0.146394 2.11052 0.420488C1.69938 0.694583 1.37867 1.08436 1.18892 1.54061C1.00092 1.9984 0.951865 2.50141 1.0479 2.98689C1.14393 3.47238 1.3808 3.91884 1.72893 4.27059C2.07944 4.61279 2.5198 4.84851 2.99892 4.95052V10.04C2.5198 10.142 2.07944 10.3778 1.72893 10.72C1.3808 11.0717 1.14393 11.5182 1.0479 12.0037C0.951865 12.4891 1.00092 12.9922 1.18892 13.45C1.37867 13.9062 1.69938 14.296 2.11052 14.5701C2.52166 14.8442 3.00479 14.9903 3.49892 14.99C3.84188 14.9974 4.18256 14.9327 4.49892 14.8001C4.80197 14.6754 5.07732 14.4919 5.30904 14.2601C5.54075 14.0284 5.72425 13.753 5.84892 13.45C5.98157 13.1336 6.0463 12.7929 6.03893 12.45C6.03926 11.9558 5.89316 11.4727 5.61906 11.0615C5.34497 10.6504 4.95516 10.3298 4.49892 10.14C4.35057 10.0783 4.19649 10.0314 4.03893 10V4.99056ZM2.70894 3.74056C2.95497 3.90376 3.24368 3.99072 3.53893 3.99056C3.81026 3.99066 4.07654 3.91718 4.3094 3.77791C4.54227 3.63864 4.73301 3.43877 4.86128 3.19966C4.98956 2.96056 5.05057 2.69116 5.03783 2.42012C5.02508 2.14908 4.93907 1.88661 4.78893 1.6606C4.62119 1.4121 4.38499 1.21751 4.10893 1.10054C3.83645 0.989551 3.53719 0.961759 3.24892 1.02059C2.95693 1.07705 2.68852 1.2196 2.47823 1.42989C2.26793 1.64018 2.12539 1.90853 2.06892 2.20052C2.0101 2.4888 2.03792 2.78802 2.14891 3.0605C2.26588 3.33656 2.46043 3.57282 2.70894 3.74056ZM2.70894 11.25C2.95497 11.0868 3.24368 10.9998 3.53893 11C3.81026 10.9999 4.07654 11.0734 4.3094 11.2127C4.54227 11.3519 4.73301 11.5518 4.86128 11.7909C4.98956 12.03 5.05057 12.2994 5.03783 12.5704C5.02508 12.8415 4.93907 13.1039 4.78893 13.33C4.62119 13.5785 4.38499 13.7731 4.10893 13.89C3.83645 14.001 3.53719 14.0288 3.24892 13.97C2.95693 13.9135 2.68852 13.771 2.47823 13.5607C2.26793 13.3504 2.12539 13.082 2.06892 12.79C2.0101 12.5018 2.03792 12.2025 2.14891 11.9301C2.26588 11.654 2.46043 11.4177 2.70894 11.25Z" fill="#C5C5C5"/>
<path d="M14.309 10.7206C13.9612 10.3747 13.5196 10.1384 13.0389 10.0406V4.4906C13.0403 4.16193 12.9765 3.83626 12.8513 3.53235C12.7262 3.22844 12.542 2.95226 12.3096 2.71985C12.0772 2.48744 11.8011 2.30339 11.4972 2.17822C11.1933 2.05305 10.8676 1.98928 10.5389 1.9906H8.68899L9.95895 0.720581L9.24899 0.0106201L7.11896 2.14062V2.84058L9.24899 4.97058L9.95895 4.26062L8.68899 2.9906H10.5389C10.9368 2.9906 11.3183 3.14863 11.5996 3.42993C11.8809 3.71124 12.0389 4.09278 12.0389 4.4906V10.0406C11.7204 10.1028 11.4177 10.2286 11.1489 10.4106C10.7412 10.688 10.4218 11.0768 10.2289 11.5306C10.0381 11.988 9.98749 12.4917 10.0835 12.9779C10.1795 13.4641 10.4179 13.9108 10.7683 14.2612C11.1187 14.6117 11.5654 14.85 12.0516 14.946C12.5378 15.0421 13.0416 14.9915 13.499 14.8007C13.9552 14.6109 14.345 14.2902 14.6191 13.879C14.8932 13.4679 15.0393 12.9847 15.0389 12.4906C15.039 11.8273 14.7766 11.191 14.309 10.7206ZM13.5989 13.5507C13.3542 13.7956 13.0324 13.9483 12.6879 13.9829C12.3434 14.0175 11.9975 13.9319 11.7089 13.7406C11.4604 13.5729 11.2659 13.3366 11.1489 13.0605C11.0379 12.7881 11.0101 12.4888 11.069 12.2006C11.1254 11.9086 11.268 11.6402 11.4783 11.4299C11.6886 11.2196 11.957 11.0771 12.249 11.0206C12.5372 10.9618 12.8365 10.9896 13.1089 11.1006C13.385 11.2176 13.6212 11.4121 13.7889 11.6606C13.9803 11.9492 14.0659 12.295 14.0312 12.6395C13.9966 12.984 13.8439 13.306 13.5989 13.5507Z" fill="#C5C5C5"/>
</svg>

Good catch and thanks for making the icon! I'll update it with your proposal.

This is now updated:

This had to get reverted due to some conflicts. Re-opening so that I can follow up.

authors: eamodio misolori


text:
Can't run Selenium python file

Issue Type: Bug
Hello
Please kindly take a look at this issue: https://stackoverflow.com/questions/58455234/running-selenium-from-visual-studio-code-terminal-with-virtualenv
Basically, the code works when I execute it outside of VSCode in my terminal, but the same code cannot be executed from VSCode. It only works in VSCode in headless mode (Firefox window doesn't show up).
Please kindly read Mike's question in the above link. I have the very same issue.
VS Code version: Code - Insiders 1.42.0-insider (cba31b819ea99836daf51cee56299348e9c6d20b, 2020-01-08T05:33:44.740Z)
OS version: Linux x64 5.4.6-2-MANJARO snap

System Info

Item
Value

CPUs
AMD Ryzen 5 2600X Six-Core Processor (12 x 2686)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
0, 0, 0

Memory (System)
15.65GB (9.71GB free)

Process Argv
--force-user-env --no-sandbox --unity-launch --no-sandbox

Screen Reader
no

VM
0%

Extensions (22)

Extension
Author (truncated)
Version

bracket-pair-colorizer-2
Coe
0.0.29

vsc-material-theme
Equ
31.12.0

vscode-firefox-debug
fir
2.6.1

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.1.1

vscode-test-explorer
hbe
2.15.0

vscode-peacock
joh
3.2.0

chat
kar
0.31.0

vscode-python-test-adapter
lit
0.3.15

vscode-docker
ms-
0.9.0

python
ms-
2020.1.57595-dev

vsliveshare
ms-
1.0.1456

vsliveshare-audio
ms-
0.1.80

vsliveshare-pack
ms-
0.3.4

debugger-for-chrome
msj
4.12.4

color-highlight
nau
2.3.0

material-icon-theme
PKi
3.9.2

vscode-css-peek
pra
3.0.2

LiveServer
rit
5.6.1

code-settings-sync
Sha
3.4.3

vscode-maven
vsc
0.20.1

vim
vsc
1.12.4

venv queries should be directed to the Python extension https://github.com/microsoft/vscode-python

I am able to execute Python code with my venv / installed librairies in VSCode. Did you think I couldn't do this?

@djalan you're reporting a bug from what I can tell is about the Python extension, not VS Code core.

authors: Tyriar djalan