text:
Functional tests could use the same jupyter server for all tests

I believe the slowdown in our functional tests is the searching for interpreters and starting a new jupyter for every test.
What if we didn't do that?
Seems to me no user would ever shutdown and startup the server so many times (so it's not a realistic version of a user problem). However users would run tons of code on top of the same server (so running all of the tests against the same server is a reasonable impersonation of a real user).
This would hopefully speed up all of our tests dramatically.
How to do this when all of the tests assume otherwise?
I think it would have to be on a test by test basis. Some of the tests are actually testing shutdown/startup. Ideally we'd use the same notebook for each test too, depending upon if it fits with the test.

I think the change proposed by Jim to select a single interpreter as containing jupyter should probably help here.
Also, I believe running functional tests within VS Code will help as well. In this case we can rely on caching and the like to kick in avoiding the need for look ups.

I'd consider re-visiting how we run the functional tests for Jupyter.

Will running some tests hosted in VS Code help?
Some parts need searching (ignoring the caching).
Other parts don't need searching & can use caching.
Can we speed up some tests by simply connecting to a an existing (remote) session (re-use existing jupyter session). This will bypass starting everytime.

I don't think starting VS code up for every test works, although I think you're proposing running them all within the same VS code. However this causes problems with stubbing output and controlling input. We'd have to rewrite how we force the tests to talk to the UI. I also think that adds unnecessary overhead (VS code startup/load extension) to the tests too.
The remote idea sounds like it could work well. Although we'd then be testing with the remote path exclusively and I'm not sure I like that idea.
I think we can modify the tests to just cache the server/interpreters. We could possibly move them all into the same suite, or make some singleton object that manages them.

I don't think starting VS code up for every test works

Today a single VS Code instance is used for the other tests.

I think we can modify the tests to just cache the server/interpreters. We could possibly move them all into the same suite, or make some singleton object that manages them.

Yes. A singleton would work. However I'm not sure how it would work with other dependencies.
E.g. We mock the IFileSystem, however these are low level dependencies used in higher order components that implemernt caching (which could be singletons). Anyways, can discuss.

Although we'd then be testing with the remote path exclusively and I'm not sure I like that idea.

On the flip side, today our tests are exclusively focused on local launch.
This is why I suggested we have some tests (focused on startup) to test local and remote launch.
Other tests that focus on other parts such as selection of cells, enter key, intellisense, latex, should not be concerned with how jupyter is launched, hence could use a remote jupyter session.

I think we can modify the tests to just cache the server/interpreters. We could possibly move them all into the same suite, or make some singleton object that manages them.

What ever we do, I'd like it to be much simpler and less error prone than what we have today.
I say this because in my opinion we spend too much time on addressing functional test issues.

On a mac:
Functional tests for native editor, 82 tests

With auto start enabled
With auto start enabled
With already running jupyter server

6 minutes
7 minutes
6 minutes

Didn't see an improvement hence not exploring this further, until I try on Windows.
Will need to test on Windows machine

I think we can just punt this bug. The interpreter caching is likely sufficient to not need to further complicate things.


text:
Test Only Not to be merged - Dev/jimgries

For #

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[ ] Title summarizes what is changing
[ ] Has a news entry file (remember to thank yourself!)
[ ] Appropriate comments and documentation strings in the code
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated
[ ] Test plan is updated as appropriate
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #8672 into master will decrease coverage by 32.97%.
The diff coverage is 20%.

@@             Coverage Diff             @@
##           master    #8672       +/-   ##
===========================================
- Coverage   59.17%   26.19%   -32.98%
===========================================
  Files         521      344      -177
  Lines       23981    15280     -8701
  Branches     3874     2426     -1448
===========================================
- Hits        14190     4003    -10187
- Misses       8874    11243     +2369
+ Partials      917       34      -883

Impacted Files
Coverage Δ

src/client/datascience/gather/gather.ts
2.12% <20%> (-60.92%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
0% <0%> (-100%)
:arrow_down:

src/client/debugger/extension/serviceRegistry.ts
0% <0%> (-100%)
:arrow_down:

...ience/jupyter/jupyterDebuggerRemoteNotSupported.ts
0% <0%> (-100%)
:arrow_down:

src/client/linters/serviceRegistry.ts
0% <0%> (-100%)
:arrow_down:

src/client/interpreter/serviceRegistry.ts
0% <0%> (-100%)
:arrow_down:

src/client/common/utils/icons.ts
0% <0%> (-100%)
:arrow_down:

src/client/formatters/serviceRegistry.ts
0% <0%> (-100%)
:arrow_down:

src/client/language/languageConfiguration.ts
0% <0%> (-100%)
:arrow_down:

src/client/testing/navigation/serviceRegistry.ts
0% <0%> (-100%)
:arrow_down:

... and 388 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f4dafff...031f3a6. Read the comment docs.

source: gharchive/pull-request

authors: codecov-io greazer

repo: microsoft/vscode-python

license: MIT

license_type: permissive

license_source: github-api


text:
Add title for the kernel selector

For #8866

Codecov Report

Merging #9024 into master will increase coverage by 0.33%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master    #9024      +/-   ##
==========================================
+ Coverage   56.65%   56.98%   +0.33%
==========================================
  Files         550      550
  Lines       28959    28968       +9
  Branches     4370     4378       +8
==========================================
+ Hits        16407    16508     +101
+ Misses      11651    11566      -85
+ Partials      901      894       -7

Impacted Files
Coverage Δ

...nt/datascience/jupyter/kernels/kernelSelections.ts
98.03% <100%> (-0.04%)
:arrow_down:

src/client/common/utils/localize.ts
94.6% <100%> (ø)
:arrow_up:

...ient/datascience/jupyter/kernels/kernelSelector.ts
82.43% <80%> (-0.39%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
75% <0%> (ø)
:arrow_up:

src/client/constants.ts
80% <0%> (ø)
:arrow_up:

src/client/common/utils/platform.ts
70.58% <0%> (ø)
:arrow_up:

src/datascience-ui/react-common/logger.ts
40% <0%> (ø)
:arrow_up:

src/client/language/characters.ts
37.14% <0%> (+2.85%)
:arrow_up:

src/datascience-ui/history-react/redux/actions.ts
9.67% <0%> (+3.22%)
:arrow_up:

src/client/common/utils/version.ts
81.48% <0%> (+3.7%)
:arrow_up:

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2302553...c3cc9d1. Read the comment docs.

authors: DonJayamanne codecov-io


text:
Consider renaming 'Reopen on the Desktop' option for Continue Working On

@jrieken had feedback that it wasn't clear what this Continue Working On option does, it is somewhat ambiguous. Wondering if something like 'Open in Desktop App' would work.

@jriekenteve comentários de que não estava claro o que essa opção Continuar trabalhando em faz, é um pouco ambíguo. Querendo saber se algo como 'Abrir no aplicativo para desktop' funcionaria.

Please! Place windows Drive in first brackket rather then before hypre link of the uri-e as so

Duplicate of https://github.com/microsoft/vscode/issues/167607, resolved in the November 2022 update.

source: gharchive/issue


text:
Pause on output

Type: Bug Report

OS and Version: Windows 11
VS Code Version: 1.76.0
Serial Monitor Extension Version: Release and Pre-release version
Target embedded device: Pi Pico
I have a loop that prints out numbers every 1000 ms.
But Serial Monitor prints out two numbers, then there is a pause, then next to numbers, then pause and so on. Arduino Ide serial monitor prints it out without delays.

https://user-images.githubusercontent.com/1520326/222948060-86f140d9-96cb-4726-af66-9230902ae1f7.mp4
#include <stdio.h>
#include "pico/stdlib.h"
#include "hardware/uart.h"
#include "radar.h"

#define RADAR_UART uart0
#define RADAR_BAUD_RATE 256000
#define RADAR_DATA_BITS 8
#define RADAR_STOP_BITS 1
#define RADAR_PARITY    UART_PARITY_NONE

#define RADAR_UART_TX_PIN 0
#define RADAR_UART_RX_PIN 1

int i = 0;

int main() {
    stdio_init_all();

    uart_init(RADAR_UART, RADAR_BAUD_RATE);

    gpio_set_function(RADAR_UART_TX_PIN, GPIO_FUNC_UART);
    gpio_set_function(RADAR_UART_RX_PIN, GPIO_FUNC_UART);

    while (true) {
        printf("Hello, %d!\n", i);
        i++;
        sleep_ms(1000);
    }
    return 0;
}

I redid it, and it disappeared

repo: microsoft/vscode-serial-monitor


text:
SCM pannel needs a better interactivity

If there are two repos in one workspace with a same submodule.
git_repo_a
 |_ submodule_c

git_repo_b
 |_ submodule_c

Source control panel looks like
git_repo_a
git_repo_b
submodule_c
submodule_c

I wish it looks like this kind.
git_repo_a
|_ submodule_c
git_repo_b
|_ submodule_c

https://github.com/microsoft/vscode/issues/101859

Duplicated in #101859, PLEASE UPVOTE IT THERE!

authors: Awbmilne joaomoreno wolfsilver

repo: microsoft/vscode


text:
Extensions have no chance to clean up on close

VSCode Version: 1.49.0-insider
OS: Linux x64 5.7.17-200.fc32.x86_64

Steps to Reproduce:

Clone and open in VS Code: https://github.com/zawys/deactivate-test
vsce package
Install manually
→ "activate" is written everywhere as expected
Disable extension
→ "Reload required"
Reload (or Close)

Actual result
$ cat /tmp/deactivate-test/fs_log
init
22217.216092680 activate A
22217.216092680 activate C
22217.216092680 activate E
22223.367494563 deactivateInstant A
22223.367494563 deactivateInstant C
22223.367829940 dispose A
22223.367829940 dispose C

$ grep deactivate-test "$HOME/.config/Code - Insiders/User/settings.json"
    "deactivate-test.deactivate-test-activate": "22217.216092680",
    "deactivate-test.deactivate-test-deactivateInstant": null,
    "deactivate-test.deactivate-test-deactivateEarly": null,
    "deactivate-test.deactivate-test-deactivateLate": null,
    "deactivate-test.deactivate-test-dispose": null,

$ cat /tmp/deactivate-test/tee_log
22217.216092680 activate

Comment out the function call to vscode.workspace.getConfiguration in log and the output is:
$ cat /tmp/deactivate-test/fs_log
init
22109.498115667 activate A
22109.498115667 activate C
22109.498115667 activate E
22133.232153312 deactivateInstant A
22133.232153312 deactivateInstant C
22133.232153312 deactivateInstant E
22133.232600389 dispose A
22133.232600389 dispose C
22133.232600389 dispose E
22133.283829548 deactivateEarly A
22133.283829548 deactivateEarly C
22133.283829548 deactivateEarly E

$ grep deactivate-test "$HOME/.config/Code - Insiders/User/settings.json"
    "deactivate-test.deactivate-test-activate": null,
    "deactivate-test.deactivate-test-deactivateInstant": null,
    "deactivate-test.deactivate-test-deactivateEarly": null,
    "deactivate-test.deactivate-test-deactivateLate": null,
    "deactivate-test.deactivate-test-dispose": null,

$ cat /tmp/deactivate-test/tee_log
22109.498115667 activate

Observations:

(1) Terminal processes are killed before extensions have any chance to do it themselves (more properly).
(2) Setting configurations on exit/reload is not possible.
(3) Trying to set configurations on exit/reload somehow stalls setTimeout handlers afterward.
(4) The extension host process seems to be terminated instantly on reload when debugging an extension.
(5) When not debugging, it seems to have around 5s of time until forcibly terminated, so the deactivateLate part is never executed.
(6) Disposing and deactivate are executed in parallel.

Expected result

(1) & (2). Give extensions time to do finishing operations on the UI, like closing windows, exiting terminal process, changing configuration.
(3). Operations should fail with an expressive exception when not available.
(4). Maybe ok, but that leads to workspace pollution while debugging.
(5). Ok, but should be documented.
(6). (Sync) disposing should be executed before (async) deactivate.

Remarks
I need it for an extension’s cleanup tasks, else some temporary files will pollute the repository.

Did you verify that your extension was actually activated?

Hi!

Did you verify that your extension was actually activated?
Now yes. I created a test extension and updated the description.

The current workaround for my extension is to use ExtensionContext.globalState to keep continuously stored what should be cleaned up under what circumstances and do that when VS Code starts. However, that does only limitedly work for terminal processes and requires that the extension is activated at startup.

@zawys Your observations are correct, but the behaviours you have noticed are as designed.
A VS Code window is backed by a renderer process and an extension host process. Terminal processes are spawned from the renderer process via the extension host API (vscode.d.ts). Most of the extension host API is actually serviced by the renderer, so for example when an extension wants to create a new terminal, a message is sent to the renderer and the renderer does it. Or when an extension wants to write to the user settings.json, a message is sent to the renderer and the renderer does it, etc.
When closing the window, the renderer process goes down immediately. The extension host process becomes orphaned and has 5 seconds to go down. The renderer process does not wait for extensions in any way.
This is an intentional design decision we took. When we designed this, we have suffered multiple times as operating systems would not shut down, especially when needing to leave and catch a train, etc. Always the reasons appear to be important: an update had to be applied, an application would veto the shutdown, etc. But in comparison with missing the train, that is not so important at that time. We have decided that VS Code should not be like that. As a user, if I close VS Code, it must go down ASAP.
This requirement hits extensions and it means that extensions must be authored with this constraint in mind. Deactivate is not a time to write to user settings. To be honest, the reason we have deactivate is for e.g. cleaning up costly things, like e.g. suppose a server is up and running somewhere and must be shut down, a quick http request can be made, etc. All the rest of the things must be resilient to crashes anyway, so spawned processes must be ready that the extension host process is brutally killed anyways.

Thank you very much for your detailed reasonable explanations!
Now I found createTerminal(options: ExtensionTerminalOptions): Terminal, which allows to spawn the "fragile" process on the extension host and forward in and output between the renderer and the fragile process (via the extension host). I think, that should do it.
The documentation on the exit procedure could be extended, though.

@alexdima Could you please remote the “needs more info”?

authors: alexdima weinand zawys


text:
Save prompt is shown while saving from settings split json editor

Running from Sources

Enable Settings split json UI "workbench.settings.useSplitJSON": true,
Open the Split JSON editor
Do some changes and type cmd+s

🐛 Default settings resource is opened and save dialog is shown

Rather than reverting the support for being able to save readonly editors via Cmd+S I went ahead and added a condition under which a side by side editor will not save both sides: if any of the 2 sides is untitled, it will not save both. This fixes this issue while still allowing to e.g. Cmd+S on the "Default Settings (JSON)" editor, which I think is fine.
The only downside is that when you now compare 2 untitled files and hit Cmd+S you can no longer save both sides. Let's see how this goes.


text:
Upgrading to 1.49.1 through the built-in process breaks some features

Issue Type: Bug
After having updated VSCode through the built-in update process, git-lfs was reported as missing from my path and .csproj files from unity where not opened correctly.
But if I download the 1.49.1 version directly from the website and replace the app in my /Applications folder, everything works as expected.
VS Code version: Code 1.49.1 (58bb7b2331731bf72587010e943852e13e6fd3cf, 2020-09-16T23:21:17.533Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 x 3200)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 2, 2

Memory (System)
16.00GB (1.45GB free)

Process Argv
-psn_0_573580 --crash-reporter-id 00349874-3afd-40e8-9b60-5ec182ab8100

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

gitlens
eam
10.2.2

eppz-code
epp
1.2.52

prettier-vscode
esb
5.6.0

csharpextensions
jch
1.3.1

jiracode
alt
0.0.1

unity-code-snippets
kle
1.3.0

csharp
ms-
1.23.0

unity-tools
Tob
1.2.12

unity-debug
Uni
2.7.5

I'm glad to know you are unblocked now. Not sure what could've caused that temporary situation.

Sure, I've found a workaround but it is reproductible every single time. So there is definitely something wrong with the built-in upgrade process, probably related to execution rights.

authors: cs-altshift joaomoreno


text:
Opens much slower + g++ default build task issue

Issue Type: Performance Issue
with one of the recent updates (like 1-2 days ago) vs code started to take much more time to open even the simplest projects, now gotta wait for quite some time for it to pop up
also, idk why, but i started having an issue with default build task using mingw's g++. earlier I used to set the task.json file by changing "${file}" in "args" to "*.cpp" so instead of one file it would compile all of them, now it doesn't work for some reason, getting errors saying that everything in the other files is undefined (meaning it only compiles 1 file). works from command line tho (if using "g++ - g *.cpp -o out"), so it's definitely not a compiler issue
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T15:06:15.712Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.85GB (8.65GB free)

Screen Reader
no

VM
0%

figured out the task.json g++ issue. with the new update task.json file started using ""type": "cppbuild" instead of "type": "shell", like it used to.  changing the "type" to "shell" manually fixes the issue and the build process works perfectly. a minor inconvenience, but at least works, so not that big of a deal. although would be great not having to manually change task.json everytime :)

I had the same problem (same vscode and windows versions) and it worked after I changed "cppbuild" to "shell". Thanks a lot.


text:
The git commit message field is cropped with negative zoom

Issue Type: Bug
Here's what I get with "window.zoomLevel": -0.71,:

I know there are some bugs with non integer zoom levels, but this is a regression! It used to display correctly in previous versions.
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

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

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.89GB (1.27GB free)

Process Argv
--crash-reporter-id f21ed382-d472-4360-9cb5-a6e51078377b

Screen Reader
no

VM
0%

(4 theme extensions excluded)

The reason it's cropped is because the parent node is set overflow: Hidden.

To not affect other nodes of the same type, I only set overflow: unset for the .scm-input. just like the  PR. please help check that @joaomoreno
.

Yes, that's related to the fact that it's hidden. But the real problem here is CSS unit rounding. The contents of that div should never escape its bounding box and when zomming out that is happening. We should not change the overflow rule.

Yes, you are right. I try to change margin to padding. And it work. @joaomoreno Please see if that's ok

authors: chenjigeng joaomoreno phgmacedo


text:
Anaconda can't work when open a terminal in vs code

Issue Type: Bug
Mac 10.15.7
step01:
install anaconda in my mac and create a evn for python. like python3.8
step02:
open a project in vscode
step03:
open a terminal in vscode
step04:
in the termainal:run anaconda command "conda active env_python3.8" to activate my python env
my problem :
It can active my python env,but can't use . I run the command 'python --version' in the env,it tell me the python version is 2.7........;if open a termainal in my mac os ,acitve the env,my python version is 3.8.
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-11T01:11:34.018Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz (4 x 2900)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 3, 4

Memory (System)
8.00GB (0.48GB free)

Process Argv
-psn_0_57358 --crash-reporter-id 347e21d9-0594-4f89-ac80-fe86e4ae5961

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

vscode-django
bat
1.0.0

bracket-pair-colorizer
Coe
1.0.61

es7-react-js-snippets
dsz
3.0.0

cloudcode
goo
1.7.0

vscode-docker
ms-
1.8.1

vscode-language-pack-zh-hans
MS-
1.51.2

csharp
ms-
1.23.6

vscode-kubernetes-tools
ms-
1.2.1

python
ms-
2020.11.371526539

vscode-pylance
ms-
2020.11.2

jupyter
ms-
2020.11.372831992

cpptools
ms-
1.1.2

vscode-react-native
msj
1.1.1

vscode-yaml
red
0.13.0

(1 theme extensions excluded)

another question:If me create a new env for python;The env can't work in vs code,unless i restart the vs code


text:
Add a 'Focus Assist' toggle, that works roughly the same as Windows 10's 'Focus Assist'.

This is not the same as #104098, #103376.  I couldn't find anything else similar - apologies if I missed anything.

I would like to be able to temporarily suppress notifications while I work, in the same general way that Windows 10 'Focus Assist' works.
The functionality I want actually already exists in Visual Studio Code - it is "Zen Mode - Silent Notifications".  However, currently, you can only enable this in Zen Mode.  I'd like the ability to just toggle it on and off, independent of Zen Mode.  (command palette or preference would be fine)
I'm happy to submit a PR, if people are comfortable with the idea.

dupe of #46676


text:
Warn for unknown configuration settings

Currently, unknown configuration settings in settings.json are greyed out, it's hard to find them if I don't read settings.json line by line. It would be better if they are warned and shown in the problems panel, this way, I could quickly find them.

They used to, but got changed in #33931
I guess there is no way to differentiate between "settings from disabled extensions" and "deprecated settings from enabled extensions"

It would be a great feature to be able to see all the hints in one place. Problems panel is missing only hint level diagnostics and they would be just disabled by default

@usernamehw Same problem, Code doesn't recognize configurations from disabled extensions, when you have several extensions disabled there can be tens or even hundreds of "hint" level errors.

Well, I guess we are talking about different features.

Acknowledge disabled extensions and do not show Unknown for such extensions
Ability to see all hint level diagnostics (disabled by default)

Both would be improvements over the current system.

There's a way to make them warnings, though. Extension author can add "deprecationMessage" or "markdownDeprecationMessage" and the setting will be of warning level.

My bad, I thought it might be a purely invalid setting ID, but in fact "esbenp.prettier-vscode" extension has removed this setting several versions ago.

Ability to see all hint level diagnostics (disabled by default)

I mean these "hint"s are not that useful today, you may get many of them and all of them says "unknown configuration settings", it doesn't matter whether they are scattered or grouped.
It still requires "1. Acknowledge disabled extensions and do not show Unknown for such extensions" to function porperly. But with 1. implementated, Code can confidently tell you it's an "Invalid" setting, there is no such thing as "Unknown" settings anymore.

There are also hidden settings, such as editor.disableMonospaceOptimizations or editor.scrollbar.verticalScrollbarSize and the issue about showing different warning for them was closed with the solution of using hint diagnostics: https://github.com/microsoft/vscode/issues/40070#issuecomment-513953921

I mean these "hint"s are not that useful today

They are useful, and often have a quick fix. Disabled by default and with the ability to show them on demand (filter icon) and the ability to filter them (filter input already there) they would be useful.

It seems there are too many things discussed in one issue which actually deviating or distracting the issue. So I would focus about the issue reported in the description. Since it is designed to represent unconfigured settings like this I am closing this as designed.
I would request to file separate issue for each of the requirements you are asking for, so that it will be easy to see if ti is already reported or not and track it

authors: sandy081 usernamehw wenfangdu yume-chan


text:
Permission for microphon

missing permission for microphon an mac big sur

Can you provide a bit more of an explanation? Perhaps a screenshot?
/needsMoreInfo

#95062 ?

Yeah, I think you're right @yume-chan. Dupe of #95062

Yeah, I think you're right @yume-chan. Dupe of #95062

Thank's @yume-chan . for your link :)

authors: HoBu23 TylerLeonhardt yume-chan


text:
Open with: allow to open the same file in different editors

I find it confusing today that an editor is being replaced when I select "Open with...". I would expect that the original editor remains when I open with another editor.
Maybe there is a limitation I am not aware of but I think this should be supported. This is especially weird when the file to reopen is dirty and I am being asked to save it.
//cc @mjbvz

Especially in cases where a custom editor is text based, this works pretty cool actually because the same model is shared:

The general conversation has been Reopen with.... is opening the current file in a different editor and therefore it's replaced. Where if you right click in the explorer and do Open With.... it should keep the current tab.

Yes I do agree about that statement.

Related code (I think): https://github.com/microsoft/vscode/blob/fc191749834ceea13e1be76c81c14430ce152dc6/src/vs/workbench/services/editor/browser/editorOverrideService.ts#L299-L311

I believe this was fixed when I fixed https://github.com/microsoft/vscode/issues/121793. If you can still reproduce this issue please feel free to reopen it.

👏

Any chances to have "Open with..." as alternative action for "Reopen Editor with..." in context menu?
So I'll be able to open custom editor for current tab side by side instead of looking for same file in Explorer to open it again.
Or is there a command to open current editor in new tab with different custom editor?

@IllusionMH I don't believe there is anything right now besides the explorer context menu and extension APIs that allow for Open With.... However, when you focus a tab it should focus the respective explorer item so you don't have to go looking for it.

authors: IllusionMH bpasero lramos15


text:
vs code stopped showing syntax errors, I work in laravel, vs code inbuilt IntelliSense stopped working when I downgrade my vs code to JAN 2021 version it throws error the problem is with the new version of vs code only

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

VS Code Version:  April 2021 version 1.56
OS Version: Windows 10 Home 20H2

vs code stopped validating the syntax errors when I degrade it to March 2021 version it shows errors automatically. The problem is with the vs code April 2021 version. I work in laravel framework later this week i got an vs code update and i did it but suddenly vs code stopped validating the syntax error and again i degraded my vs code to the last version and it started validating the problem is with the the new version of vs code now i'm using php extensions to validate the syntax errors

/needsMoreInfo

Same problem, PHP syntax error stopped working after updating to 1.56.2. I downgrade to 1.55.2 and syntax error is working again.
Problem with:
Version: 1.56.2
OS: Linux x64 5.8.0-50-generic

Confirm the issue on Debian/Linux 9.13 (stretch) and PHP 7.0.33. VSCode version is 1.56.2

Confirm the issue both using the php installed from the repository and using php by xampp 7.4 and 8.0.6.
My OS is Linux Mint 20.1 (Ulyssa)
Vscode info:
Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T16:45:26.313Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Linux x64 5.4.0-73-generic

@roblourens Now I am using 1.61.0, and it's working without problems.

authors: Liakoni egamma lucatacconi mukhilanelangovan underr-ua


text:
Wrong .vscode folder picked up, cannot

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

VS Code Version:

1.56.2
054a9295330880ed74ceaedda236253b4f39a335
x64

OS Version:

5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce:

Open a solution with two .vscode folders (specifically, in this case, the repo has a submodule with another .vscode folder)
Ctrl-Shift-P to run Tasks: Run Test Task
The tests displayed are from the .vscode folder in the subdirectory, not the parent.

Now, try deleting the folder in the subdirectory.

Open a solution with two .vscode folders (specifically, in this case, the repo has a submodule with another .vscode folder)
Ctrl-Shift-P to run Tasks: Run Test Task
The tests displayed are from the DELETED .vscode folder in the subdirectory, not the parent.

This is driving me nuts, I just want to run tests.

Okay the Tasks it's getting are not from the tasks.json in the subdirectory, they're not even defined there. I think it's auto-discovering something, and I don't want it to auto-discover anything, I want it to use the defined tasks.

Okay so I manually turned discovery off, and now here's what happens:
Ctrl-Shift-P: Tasks: Run Test Task
"No test task to run found. Configure tasks..."
So I hit enter, and select the test task I want, and it takes me to the editor window for the .vscode/tasks.json file, which is already configured.
Seems circular.

"group": "test" is now necessary in the JSON, as it wasn't before


text:
Unclear Terminology: Settings / Preferences / Configure / Customize

Testing #127319.
We now use the terms Settings, Preferences, Configure and Customize in commands.
They all refer to the same thing, which makes searching for the right Command hard.
Also see #95202.

Similar to https://github.com/microsoft/vscode/issues/127303

probably needs a solution with better command palette search since the names are what they are for a while

authors: hediet sbatten


text:
Native Notebooks - Drag and drop movement have low discoverability

Customer feedback on our survey indicates that cell/markdown folding and drag and drop movement have low discoverability.
Would be great if we could find a way to increase discoverability for these two capabilities in notebooks

Would be great if we could find a way to increase discoverability for these two capabilities in notebooks

Not sure if we want to increase their discoverability significantly, I personally see them as secondary actions which might not be used by majority of users, especially drag and drop.

I think drag and drop is fine since most UIs don't have much of a visual cue for drag and drop beyond the cursor changing which we have but hmm for folding I agree isn't that obvious. @misolori do you have any ideas for UI indications for folding?
I wouldn't think to double click here:

Ah @tanhakabir, sorry if I wasn't clear, the feedback actually indicates markdown folding, not output folding. People don't seem to be discovering the chevron to the left of markdown cells that appears on hover that then collapses cells under the markdown.

I acknowledge an issue based on those reviews but I have no clue how to make dnd more discoverable. We use the grabbing hand cursor on all dnd regions. I'm open to suggestions. There is another issue to allow users to have the ⬆ ⬇ buttons in the cell toolbar, and I wouldn't mind doing that although it wouldn't be on by default. If that would address the issue, then I'd close this in favor of that.

@roblourens I agree with you that increasing discoverability is hard. I'd love to close this in favor having up and down buttons to move the cells instead. (Even if discoverability is improved, I ran into #145605 quite often, it isn't a very smooth experience).
When you say "it wouldn't be on by default" do you mean DND would be the experience a new user would get, and to get the arrows a user might have to change a setting?

to get the arrows a user might have to change a setting?

Yeah, that's what I would expect off the top of my head. I feel that there's a lot of stuff in the toolbar already, and adding too many buttons on the screen can increase confusion too.

I will close this in favor of having arrow buttons in the toolbar

https://github.com/microsoft/vscode/issues/168954

authors: claudiaregio rebornix roblourens tanhakabir


text:
Align notebook layout commands

ipynb-notebooks have toggle breadcrumbs, outline and variables but GHI-notebooks only have toggle breadcrumbs. I understand that toggle variables makes no sense for them (lack of support) but there is outline and the same rules should apply for these different notebook types

Seems like this one can be handled by core VS Code notebook support (at least toggling outline). So leaving in this repo.

Let's track it in #137185

authors: greazer jrieken rebornix


text:
HTML file is not working

Issue Type: Bug
Hello , When I try to run a HTML file normally it will ask me to save it but once I save it , it stop working and the error says 'You don't have extention for Django HTML ' But I am using HTML file not Django HTML file
Please contact me with : @mjbvz note — REMOVED user's email
If you got a soultion
VS Code version: Code 1.61.2 (6cba118ac49a1b88332f312a8f67186f7f3c1643, 2021-10-19T14:57:20.575Z)
OS version: Windows_NT x64 10.0.18363
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz (8 x 1190)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.71GB (1.63GB free)

Process Argv
--crash-reporter-id 1cd21b5b-68b9-4764-8885-b66a126eab25

Screen Reader
no

VM
0%

Extensions (36)

Extension
Author (truncated)
Version

html-snippets
abu
0.2.1

shaderlabvscodefree
aml
1.2.8

vscode-django
bat
1.6.0

htmlplay
bia
0.0.9

csharp-extentions-pack
bou
0.3.0

debugger-for-mainframe
Bro
1.5.1

python-preview
don
0.0.4

prettier-vscode
esb
9.0.0

dotnet
for
0.0.4

vscode-javac
geo
0.2.39

batch-rename-extension
Jan
0.0.4

csharpextensions
jch
1.3.1

vscode-csharp-snippets
jor
1.1.0

unity-code-snippets
kle
1.3.0

csharpextensions
kre
1.5.2

csharp
ms-
1.23.16

vscode-dotnet-runtime
ms-
1.3.0

vscode-edge-devtools
ms-
1.3.1

python
ms-
2021.10.1365161279

vscode-pylance
ms-
2021.10.2

jupyter
ms-
2021.9.1101343141

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.3

mono-debug
ms-
0.16.2

godot-csharp-vscode
nei
0.1.3

java
red
1.0.0

LiveServer
rit
5.6.1

shader
sle
1.1.5

unity-debug
Uni
3.0.2

vscodeintellicode
Vis
1.2.14

vscode-java-debug
vsc
0.36.0

vscode-java-dependency
vsc
0.18.8

vscode-java-pack
vsc
0.18.6

vscode-java-test
vsc
0.32.0

vscode-maven
vsc
0.34.0

cors-browser
Wsc
1.0.11

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30384385
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
vsccppwtct:30382698
pythonvssor306:30344512
bridge0708:30335490
pygetstartedt3:30385195
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedc:30364665
pythonvspyt187:30373474
vsqsis400:30381677
vsaa593:30376534
vssld246cf:30379912
vscrecpromptt1:30385803

Please file this issue against the Django extension


text:
Extension failing on start

Applies To

[ ] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
On launch of VS-code I get this error and no extension functionality

VS Code Version
Version: 1.64.2 Commit: f80445acd5a3dadef24aa209168452a3d97cc326 Date: 2022-02-10T22:49:45+00:00 Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.14.21-210.current
Jupyter Extension Version
v2022.1.1301854968
Jupyter logs
Visual Studio Code (1.64.2, undefined, desktop)
Jupyter Extension Version: 2022.1.1301854968.
Python Extension Version: 2022.0.1814523869.
Info 10:54:36: ZMQ install verified.
Error 10:54:36: extension activation failed [Error: Extension 'ms-toolsai.jupyter' CANNOT use API proposal: notebookEditor.
Its package.json#enabledApiProposals-property declares:  but NOT notebookEditor.
 The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.jupyter
	at checkProposedApiEnabled (/usr/share/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:47580:19)
	at Object.onDidChangeCellMetadata (/usr/share/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:69592:62)
	at u.addEventHandlers (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:795058)
	at new u (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:793723)
	at Object.t.resolveInstance (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:237383)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236588
	at Array.map (<anonymous>)
	at Object.t.resolveInstance (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:237153)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236588
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:235536
	at Array.map (<anonymous>)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:235508
	at Array.map (<anonymous>)
	at Object.t.resolveInstance (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:237153)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236588
	at Object.t.resolve (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236851)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:227948
	at e._get (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:227714)
	at e.get (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:226426)
	at a.get (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:124:61150)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:275368
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:51:785282
	at async t.activate (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:51:784961)]
Error 10:54:36: Failed to active the Jupyter Extension [Error: Extension 'ms-toolsai.jupyter' CANNOT use API proposal: notebookEditor.
Its package.json#enabledApiProposals-property declares:  but NOT notebookEditor.
 The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.jupyter
	at checkProposedApiEnabled (/usr/share/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:47580:19)
	at Object.onDidChangeCellMetadata (/usr/share/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:69592:62)
	at u.addEventHandlers (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:795058)
	at new u (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:793723)
	at Object.t.resolveInstance (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:237383)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236588
	at Array.map (<anonymous>)
	at Object.t.resolveInstance (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:237153)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236588
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:235536
	at Array.map (<anonymous>)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:235508
	at Array.map (<anonymous>)
	at Object.t.resolveInstance (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:237153)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236588
	at Object.t.resolve (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:236851)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:227948
	at e._get (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:227714)
	at e.get (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:226426)
	at a.get (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:124:61150)
	at /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:275368
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async /home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:51:785282
	at async t.activate (/home/fulton/.vscode/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:51:784961)]

Coding Language and Runtime Version
Python 3.9.9,  $ jupyter --version Selected Jupyter core packages... IPython          : 8.1.0 ipykernel        : 6.9.1 ipywidgets       : not installed jupyter_client   : 7.1.2 jupyter_core     : 4.9.2 jupyter_server   : 1.13.5 jupyterlab       : 3.2.9 nbclient         : 0.5.11 nbconvert        : 6.4.2 nbformat         : 5.1.3 notebook         : 6.4.8 qtconsole        : not installed traitlets        : 5.1.1
Language Extension Version (if applicable)
Python v2022.0.1814523869
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Apparently the Python extension is suffering a similar (if not duplicate) issue

Probably similar to https://github.com/microsoft/vscode/issues/143834

@jrieken
this isn't a duplicate. on this case the extension id is different, the other issues was related to the python extension.
dinner hours this is taking in stable vscode using the attached version of the extension.
reopening as is not a duplicate

Thanks for clarifying.. Tho, now I am really puzzled, stable is out since quite a while and I am sure that there is more than one user... Also, for 1.64 the product.json-file spells out the correct proposals. @FultonBrowne Is this VS Code the product and a different build like Codium?

This the OSS build packaged for Solus Linux. You can check this out for more info on the build they use

Ok, thanks for clarifying. Please raise this issue against them. Allowing extensions to use proposed API is a product configuration and it seems this didn't happen for the flavour that you are using.

authors: DonJayamanne FultonBrowne greazer jrieken


text:
Move generally useful hover bits from IconLabelHover into Hover

After a quick look, it seems like UpdatableHoverWidget.update should move into HoverWidget and setupCustomHover should go to hover/hover.ts to avoid a weird dep on iconLabel when icon label isn't used. Anything to make it easier to use IHoverService would also be good when the consumer is a workbench component.
Something else to keep in mind is if the hover is used directly here instead of from workbench, global features like hover lock will not work. Should we be injecting the service's function into icon label?

Can reopen this if it comes up again


text:
Emmet's inline completions works unintentionally in JSX strings literal

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

VS Code Version: Version: 1.69.0-insider (Universal) Commit: f361c5b71d6676cfc6de97cdb1cc40b08bf7d994
OS Version: macOS 12.4

Steps to Reproduce:

Create JSX (TSX) File
type import Hoge from '../../a'
type ../ between / and a

https://user-images.githubusercontent.com/1955233/175196045-837742fd-fb4b-4ab1-a5a1-b66dbcdd10e4.mp4
Emmet's inline-completions works even in areas enclosed by quotes and seems a little noisy.
This happens not only in import from statement, but also when writing simple strings and spread operators.
ref: https://github.com/microsoft/vscode/pull/151559

The completions are the same as those suggested by the completion item provider aka the non-inline completion provider. But, with inline completions on, it's even more likely for users to see noisy suggestions if they only see one completion rather than a list of completions.

Labelling this as a duplicate of #51537


text:
VSCode Task or .csproj PostBuild event using the "reg" command does not work

VS Code Version: 1.70.2
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS Version: Windows_NT x64 10.0.19042

Steps to Reproduce:

Create a file that contains registry keys
Create a shell task in VSCode that imports the file:

{
    "label": "Import Registry Entries",
    "type": "shell",
    "command": "reg import fullfilepath",
    "group": "build"
}

Alternatively I have this as a build event in a .csproj:

powershell.exe -ExecutionPolicy Bypass -NoProfile -NonInteractive -File $(ProjectDir)RegisterDll.ps1 -targetPath $(TargetDir) -targetName $(TargetName)

The RegisterDll script:
Param(
     [Parameter()]
     [string]$targetPath
     [Parameter()]
     [string]$targetName
)
$regToCreate = $targetPath + $targetName + ".dll"
$regToLoad = $targetPath + $targetName + ".reg"

$regStringToReplace = "HKEY_CLASSES_ROOT"
$newRegString = "HKEY_CURRENT_USER\Software\Classes"

Get-Command reg | Out-Null

Write-Output "Creating new registry keys from dll: $($regToCreate)"

# This creates the registry file as expected both in VSCode and VS2022
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe /codebase /regfile $regToCreate

# This modifies the keys that were created
(Get-Content $regToLoad).Replace($regStringToReplace, $newRegString) | Set-Content $regToLoad

# From VSCode, this fails to import the keys from the file created above, I can import it manually just fine
# From VS2022, the entire script works fine
reg import $regToLoad

I'm not able to verify my log in at work so I made an alt account. I forgot to point out that the VSCode terminal window reports "The operation completed successfully." for the reg import. Opening up the registry however makes it pretty clear that that is not the case. I get the same print out when it actually is successful in VS2022.

are you seeing an error associated with running that task - in the console or otherwise? any task errors in the output channel for tasks?

@meganrogge - There is nothing to indicate there's an error with the task - in fact the build makes it to the Post-Build step, and displays the default "The operation completed successfully." text. The reg command also returns "0" which is supposed to indicate success.
I see no log in the "Tasks" output channel - errors or otherwise.

Is this a new issue or have you seen it in the past too?

Is this a new issue or have you seen it in the past too?

This is a new way of registering our COM interop DLL, so unfortunately I can't say. Previously we relied on RegAsm and/or the .csproj setting "Register for COM interop". Unfortunately both of those methods require admin privileges, and we needed something that would work without that requirement. That led me down this path of creating a .reg file, and replacing the ROOT keys, then importing it. This method works great with VS2022, but most of our developers use VSCode.

@meganrogge - I'd like to follow up on this, is there any additional information I could provide?

@BBoldenow I notice you use Get-Command reg in the script. Does it work if you pass Get-Command into the task "command" too?

@BBoldenow I notice you use Get-Command reg in the script. Does it work if you pass Get-Command into the task "command" too?

@meganrogge I'm not sure I'm doing this as you expected, but I made two tasks to test what you're asking. One that does:
{     "label": "Import Registry Entries",     "type": "shell",     "command": "reg import fullfilepath",     "group": "build",     "dependsOn": [ "firstTask" ] }
And another that does:
{     "label": "Import Registry Entries",     "type": "shell",     "command": "reg import fullfilepath",     "group": "build" }
This still doesn't work, but it's definitely "getting" the reg command (you can see it print out in the console).

Just saw this part

From VSCode, this fails to import the keys from the file created above, I can import it manually just fine
From VS2022, the entire script works fine
reg import $regToLoad

seems like probably a permissions issue
could you log/ print after the line in your script where the file gets created to check if that file gets produced/exists?

Just saw this part

From VSCode, this fails to import the keys from the file created above, I can import it manually just fine
From VS2022, the entire script works fine
reg import $regToLoad

seems like probably a permissions issue
could you log/ print after the line in your script where the file gets created to check if that file gets produced/exists?

@meganrogge - Yes, I put comments in the powershell script, but probably should have called it out more explicitly:
The file gets created, and the keys get modified to be HKEY_CURRENT_USER keys instead of HKEY_CLASSES_ROOT keys - this all works fine. The key import even appears to "work" as the reg import command prints out "The operation completed successfully." However in VSCode these keys fail to make it into the registry despite the successful print. I also thought it was a permissions issue, and have tried running VSCode as admin, but this doesn't seem to have any effect.

@meganrogge - Do you need any additional information? I'm pretty stumped as to how to get this working in VS Code.

@meganrogge - For what it's worth I did get this working as a task instead of a PostBuild event. I still think the PostBuild event should be resolved, but it let's me work around the issue in the meantime:
{     "label": "Register COM Interop (Options Prompted)",         "type": "process",     "command": "PowerShell.exe",      "args": [         "${workspaceFolder}/Source/COM_UI/RegisterCOMInterop.ps1 -targetPath ${workspaceFolder}/.output/${input:debugOrRelease}/ -targetName COM_UI"     ],     "group": "build" }

authors: BBoldenow BBoldenow-Alt meganrogge


text:
Would it be better if we can write TextMate grammar in JSON5?

I have seen comments in TextMate grammar files, but they are written inside the match string, which is quite not readable. I guess this is probably because the grammar files are directly transformed from .plist used by TextMate itself. I think maybe we can support JSON5, so that we move them and write new comment directly in the document.

IMO, many of match rules are quite hard to understand, so if we can have bettter comments, it will surely make us easier to develop and refine the document.

Vscode's textmate uses a custom parser
https://github.com/microsoft/vscode-textmate/blob/main/src/json.ts
It is possible to use string comments
any invalid textmate string is ignored

(don't have to use "comment": "". Can even do something like "&&match-2": "")
Only problem I can think of is line comments wont work very well in minified code
as everything is on one line

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

authors: RedCMD StephenChips VSCodeTriageBot


text:
Missing colors in icons for suggestions, breadcrumbs, etc

I think these used to be blue:

vs

Version: 1.75.0-insider
Commit: d957d2ca58ded0ab70ed7fadc8a1f6a36fcf2d1e
Date: 2022-12-20T10:01:06.990Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: Yes

Ran into the same issue with my theme. After a recent vscode update the coloring of the icons is gone. I'm using the Afterglow Remastered theme.

I also cannot reproduce from source, but it still reproduces in latest Insiders using "workbench.colorTheme": "Default Light+":
Version: 1.75.0-insider
Commit: c437ec2497ccd6b5ff5b2f6da86a8042e1ed951a
Date: 2022-12-21T05:43:03.162Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin arm64 22.2.0
Sandboxed: Yes

Today's insiders also doesn't have colors for me, so this might be a packaging issue or something specific to my setup. @jrieken Are you able to reproduce with Insiders?

Version: 1.75.0-insider
Commit: 42814d18a7d46adfb1c24e1349b7ab18833ec6ac
Date: 2022-12-22T05:24:06.357Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin arm64 22.2.0
Sandboxed: Yes

Yeah, I can repro in insiders with an empty profile

This also happens in other places that show symbol icons and is only happening because of how things are ordered in the packages CSS. @alexdima what's the procedure to fix this?

While the CSS rules in a single file will remain in order when being loaded or packaged, there are unfortunately no guarantees to the CSS rules order of multiple files. That is because CSS files can't express dependencies on other CSS files, so they will be loaded or packaged in any order. The exact order depends on the internals of the AMD loader/bundler, but it isn't guaranteed to be consistent, as it can depend on fs read times, etc.
I think it is a coincidence that this works every time when running from source. The correct way to fix this is to use CSS specificity to ensure the desired rule wins.

authors: alexdima jrieken marvinhagemeister


text:
Merge the menubar and titlebar of VS Code for Linux together

Currently, for Windows and Mac users, I can see that the UI of VS Code is quite beautiful. Menubar is merged with Titlebar. But no attention has been given to the UI for Linux. The famous menubar is still the same as it was 2 years ago.
Hope the VS code team takes a look at VS Code UI for linux soon

Did you try to configure "window.titleBarStyle": "custom" in settings?

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: Arpon-svg VSCodeTriageBot bpasero


text:
prefix profile folder name with profile name

In order to recogonize the profile by it's folder name

@sandy081

I am not sure it is a good idea as the name can be renamed.

@sandy081 Or we can add some description like:

May I know the purpose?

In order to identify current profile easily

For now, there is no way to extend the profile. When I need to change a setting, I may open multiple setting in different profile:

Why not switch the profile and update it from UI?

I'm one of those who like use json to adjust settings🥲

I'm one of those who like use json to adjust settings🥲

I see. May I know the purpose of updating settings in other profiles? Are you missing something in profiles feature?

For now, profile doesn't support extend, when I change a base setting, I need switch all profile to change that setting. I have 6 profiles

Please subscribe to this issue for that support - https://github.com/microsoft/vscode/issues/156144


text:
Code language not supported or defined.

Type: Bug
how to fix this problem? I have choose python manually but the problem still exist
VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

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.79GB (1.25GB free)

Process Argv
--crash-reporter-id 86227fa8-a7fa-4199-bd2e-eaf21f9c9e4d

Screen Reader
no

VM
0%

Extensions (27)

Extension
Author (truncated)
Version

vscode-sqlite
ale
0.14.1

jsoncrack-vscode
Ayk
1.0.8

code-runner
for
0.12.0

prettier-sql-vscode
inf
1.6.0

import-doc-link
Mat
1.0.1

python
ms-
2023.4.1

vscode-pylance
ms-
2023.3.20

jupyter
ms-
2023.2.1200692131

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

go-doc
msy
1.0.1

sqltools
mtx
0.27.1

sqltools-driver-sqlite
mtx
0.5.0

data
oki
0.0.1

sqlite-viewer
qwt
0.2.3

vscode-data-table
Ran
1.12.0

atlasmap-viewer
red
0.2.2

java
red
1.15.0

sqlite-snippet
roh
2.0.1

errorlens
use
3.7.0

vscode-java-debug
vsc
0.49.0

vscode-java-dependency
vsc
0.21.1

vscode-java-pack
vsc
0.25.8

vscode-java-test
vsc
0.38.1

vscode-maven
vsc
0.40.4

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewvextcfv2:30681851
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848:30662994
nodejswelcome1:30587005
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
vsccsb:30677849
pythonb192:30669360
funwalk2cf:30682975
pythonms35cf:30680985

/extJupyter

It looks like this is caused by the Jupyter extension. Please file the issue to the Jupyter extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!

authors: Aleks19ua VSCodeTriageBot gjsjohnmurray


text:
Place caret at same position in symbol when F2 (rename) is pressed

Currently when you hit F2 to rename something in VSCode, the entire text of the symbol at the caret is selected, unless a sub-range of the symbol text was selected before F2 was pressed.
This is pretty annoying in the very common case where you want to edit a symbol, but not fully replace it.
For example, I have the symbol ProfileDivider, and I want to rename it to ProfileItemDivider.
I place the caret after Profile, i.e. Profile|Divider, then I hit F2. A field pops up with ProfileDivider, with the whole symbol selected.
Then I have to move the caret back to the position right after Profile in the pop-up text field, to start typing Item. If I just start typing Item, all of ProfileDivider is replaced by Item.
I would say it's more common to want to tweak a name than totally replace it. I suggest selecting nothing in the pop-up text field, if nothing was selected in the text, and placing the caret in the pop-up text field at the same position the caret was in in the text. In the example I gave above, if the caret is positioned as Profile|Divider in the text, then when you hit F2, it should be positioned at the same place, with nothing selected.
Double-clicking on a symbol to select it, then hitting F2, would follow the current behavior of selecting everything in the pop-up text field, since already selection ranges are respected.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I would prefer F2 to behave as it currently does
but maybe setting to change it or maybe ctrl+F2?

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

authors: RedCMD VSCodeTriageBot lukehutch


text:
'this.b.extensions is not iterable' on opening welcome page

Testing #177702
Not sure if actually caused by #177702

Open welcome page

bug
In dev tools, see:
this.b.extensions is not iterable: TypeError: this.b.extensions is not iterable
    at Or.l (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1199:3608)
    at async Or.getExtensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1199:2961)

I can't repro this on my mac.
Please feel free to reopen this issue if you see this again on your machine.

Yes I still see this every time I open the welcome page. Maybe it's because of an extension I have installed that is getting parsed oddly or an experiment?
The exception is thrown here:
https://github.com/microsoft/vscode/blob/beb23739aa5fbb011124a39df83171fe4cbf51be/src/vs/workbench/contrib/welcomeGettingStarted/browser/featuredExtensionService.ts#L102

authors: bhavyaus mjbvz


text:
Allow saving the difference view when using Compare With Selected as a patch file

Hi!
I would like to suggest the Cmd+S keyboard shortcut and the content menu of the tab that gets opened when using Select For Compare and then Compare With Selected on two files to view their differences are implemented for this tab and allow the user to save the displayed differences as a patch file, like the one that gets created when using git diff -u a.txt b.txt.
This would make it very convenient to use this UI feature to generate pieces of text that can get highlighted when using in MarkDown using the diff or patch language codes like so:
```diff
+ new
  existing
- old
```

This ends up looking like this:
+ new
  existing
- old

This sort of syntax is also very useful for sending to colleagues who can then apply it via patch < change.patch. It is similar to the GitHub feature where the reviewer during a PR review can suggest changes the PR author can apply at a press of a button, but would be handy in the pre-PR context where suggestions and questions are being tossed around in the chat but no PR exists yet. Instead of explaining the suggested edits in English or just copy-pasting the edited code back and forth (with no indication of what was change), people could exchange diffs easily if they were possible to create from the VS Code UI.
I have not found an existing feature request issue for this but there is a Stack Overflow post asking about this that is about 2 years old:
https://stackoverflow.com/q/68464878/2715716
Thanks for considering this feature.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I don't think this feature has enough demand to justify its implementation.
However, it should be very easy to implement this utility in the monaco editor playground.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

authors: TomasHubelbauer VSCodeTriageBot hediet


text:
working very slow

Type: Performance Issue
If vs code is opening then it show window not responding and open very slowly
VS Code version: Code 1.79.0 (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:26:35.552Z)
OS version: Windows_NT x64 6.2.9200
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-1255U (12 x 2611)

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)
15.69GB (7.33GB free)

Process Argv
--crash-reporter-id 112193c4-8840-480c-b22c-b007e3056bc4

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	   115	 10284	code main
    0	    52	  1388	   utility-network-service
    0	   107	  4112	shared-process
    0	   102	  5812	window [2] (Issue Reporter)
    0	   165	 10384	extensionHost [1]
    0	   123	  9740	     electron-nodejs ("C:\Users\raush\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node "c:\Users\raush\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\html-language-features\server\dist\node\htmlServerMain" --node-ipc --clientProcessId=10384)
    0	    84	 11236	     electron-nodejs ("C:\Users\raush\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node "c:\Users\raush\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=10384)
    0	    82	 14824	     electron-nodejs ("C:\Users\raush\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node c:\Users\raush\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.2\node_modules\vscode-webhint\dist\src\server.js c:\Users\raush\AppData\Roaming\Code\User\globalStorage\ms-edgedevtools.vscode-edge-devtools "Microsoft Edge Tools" --node-ipc --clientProcessId=10384)
    0	    85	 10460	ptyHost
    0	    88	 11220	fileWatcher [1]
    0	   200	 12404	window [1] (2index.html - INDEX.HTML - Visual Studio Code)
    0	    87	 18132	ptyHost
    0	    30	 20468	   crashpad-handler
    0	   201	 20880	   gpu-process

Workspace Info
|  Window (2index.html - INDEX.HTML - Visual Studio Code)
|    Folder (INDEX.HTML): 23 files
|      File types: html(12) HTML(2) png(2) json(1) webp(1) pdf(1) docx(1)
|                  odt(1) jpg(1)
|      Conf files: launch.json(1)
|      Launch Configs: pwa-msedge(2) vscode-edge-devtools.debug;

Extensions (8)

Extension
Author (truncated)
Version

prettier-vscode
esb
9.13.0

copilot
Git
1.88.132

vscode-edge-devtools
ms-
2.1.2

cmake-tools
ms-
1.14.33

cpptools
ms-
1.15.4

cpptools-extension-pack
ms-
1.3.0

LiveServer
rit
5.7.9

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes516:30244333
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
a9j8j154:30646983
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixhidewlkth:30730051
showsbindicator:30760979
pythongtdpath:30739704
bgfeh915:30763804
dh2dc718:30763024

please resolve quickly

/duplicate of #184879 which already asks you if you use McAfee. If you do, it points to a related issue containing advice.

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:
TS Server fatal error:  Maximum call stack size exceeded

Type: Bug
❗❗❗ Please fill in the sections below to help us diagnose the issue ❗❗❗
TypeScript Version: 5.1.6
Steps to reproduce crash

TS Server Log
❗ Server logging disabled. To help us fix crashes like this, please enable logging by setting:
"typescript.tsserver.log": "verbose"

After enabling this setting, future crash reports will include the server log.
TS Server Error Stack
Server: semantic
RangeError: Maximum call stack size exceeded
    at parseType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33183:21)
    at parseTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32731:18)
    at parseTupleElementNameOrTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32761:12)
    at parseListElement (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31736:12)
    at parseDelimitedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31977:24)
    at parseBracketedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32029:22)
    at parseTupleType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32767:9)
    at parseNonArrayType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32919:16)
    at parsePostfixTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32990:16)
    at doOutsideOfContext (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30955:12)
    at allowConditionalTypesAnd (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30982:12)
    at parseTypeOperatorOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33069:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseIntersectionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33100:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseUnionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33103:12)
    at parseType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33191:18)
    at parseTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32731:18)
    at parseTupleElementNameOrTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32761:12)
    at parseListElement (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31736:12)
    at parseDelimitedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31977:24)
    at parseBracketedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32029:22)
    at parseTupleType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32767:9)
    at parseNonArrayType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32919:16)
    at parsePostfixTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32990:16)
    at doOutsideOfContext (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30955:12)
    at allowConditionalTypesAnd (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30982:12)
    at parseTypeOperatorOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33069:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseIntersectionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33100:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseUnionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33103:12)
    at parseType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33191:18)
    at parseTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32731:18)
    at parseTupleElementNameOrTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32761:12)
    at parseListElement (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31736:12)
    at parseDelimitedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31977:24)
    at parseBracketedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32029:22)
    at parseTupleType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32767:9)
    at parseNonArrayType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32919:16)
    at parsePostfixTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32990:16)
    at doOutsideOfContext (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30955:12)
    at allowConditionalTypesAnd (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30982:12)
    at parseTypeOperatorOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33069:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseIntersectionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33100:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseUnionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33103:12)
    at parseType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33191:18)
    at parseTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32731:18)
    at parseTupleElementNameOrTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32761:12)
    at parseListElement (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31736:12)
    at parseDelimitedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31977:24)
    at parseBracketedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32029:22)
    at parseTupleType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32767:9)
    at parseNonArrayType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32919:16)
    at parsePostfixTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32990:16)
    at doOutsideOfContext (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30955:12)
    at allowConditionalTypesAnd (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30982:12)
    at parseTypeOperatorOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33069:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseIntersectionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33100:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseUnionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33103:12)
    at parseType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33191:18)
    at parseTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32731:18)
    at parseTupleElementNameOrTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32761:12)
    at parseListElement (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31736:12)
    at parseDelimitedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31977:24)
    at parseBracketedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32029:22)
    at parseTupleType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32767:9)
    at parseNonArrayType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32919:16)
    at parsePostfixTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32990:16)
    at doOutsideOfContext (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30955:12)
    at allowConditionalTypesAnd (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30982:12)
    at parseTypeOperatorOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33069:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseIntersectionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33100:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseUnionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33103:12)
    at parseType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33191:18)
    at parseTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32731:18)
    at parseTupleElementNameOrTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32761:12)
    at parseListElement (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31736:12)
    at parseDelimitedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31977:24)
    at parseBracketedList (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32029:22)
    at parseTupleType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32767:9)
    at parseNonArrayType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32919:16)
    at parsePostfixTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32990:16)
    at doOutsideOfContext (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30955:12)
    at allowConditionalTypesAnd (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:30982:12)
    at parseTypeOperatorOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33069:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseIntersectionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33100:12)
    at parseUnionOrIntersectionType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33089:92)
    at parseUnionTypeOrHigher (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33103:12)
    at parseType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:33191:18)
    at parseTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32731:18)
    at parseTupleElementNameOrTupleElementType (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:32761:12)
    at parseListElement (c:\Users\wando\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:31736:12)

VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i5-1235U (12 x 2496)

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)
7.71GB (0.73GB free)

Process Argv
--folder-uri file:///c%3A/Users/wando/Documents/GitHub/service-payment --crash-reporter-id 54b785b2-32e0-4d4c-835c-4637eba9e442

Screen Reader
no

VM
0%

Extensions (11)

Extension
Author (truncated)
Version

npm-intellisense
chr
1.4.4

gitlens
eam
2023.8.1505

env-switcher
Eck
0.4.3

vscode-pull-request-github
Git
0.70.0

vscode-env
Iro
0.1.0

vs-deploy
mkl
14.0.0

vscode-language-pack-pt-BR
MS-
1.81.2023081609

powershell
ms-
2023.6.0

vsliveshare
ms-
1.0.5877

material-icon-theme
PKi
4.29.0

vscode-thunder-client
ran
2.10.2

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
2e4cg342:30602488
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofb:30804716
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv1:30812748

Does this reproduce in the latest VS Code insiders build with all extensions disabled?
If it does, please share an example project which causes this issue

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: VSCodeTriageBot mjbvz wando15


text:
DevContainers: net::ERR_CONTENT_LENGTH_MISMATCH through forwarded ports

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

Version: 1.83.0-insider (system setup)
Commit: 4268e464763087044d0c1b5bdd37ebbe683cadfa (latest)
Date: 2023-09-29T20:42:50.630Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

⚠ DevContainer in use! See example repository for reproduction.
While creating a new vue project, I noticed severe issues trying to see the page in action. Some (more or less random) resources can't seem to get fetched, the requests fail with net::ERR_CONTENT_LENGTH_MISMATCH.
Steps to Reproduce:

Clone and launch the devcontainer in linked repository.
Run bun i (or yarn i)
Start dev server using bun run dev
Launch browser on forwarded port 3000.
Open your browsers devtools, switch to network tab, disable cache and hit reload.

The issue is recognizable by looking for (failed) in the status column.
I was not able to provoke the error using curl from inside the container, so I suspect vscode to actually cause the issue here.
For cross reference with the nuxt project, in case it's an issue with one of their changes: https://github.com/nuxt/cli/issues/181

Could you check if it works when using "appPort": 3000 instead of "forwardPorts"?


text:
Not able to install typescirpt compiler

Type: Bug
I am not able to install the typescript globally or locally in a project.  Here is a snippet of terminal.  Please help
PS C:\Users\237160\ACSMaximusSoftphoneApp> npm install -g typescript
changed 1 package in 2s
PS C:\Users\237160\ACSMaximusSoftphoneApp> tsc --version
tsc : The term 'tsc' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
try again.
At line:1 char:1

tsc --version

  + CategoryInfo          : ObjectNotFound: (tsc:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:48:05.904Z)
OS version: Windows_NT x64 10.0.19044
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz (16 x 2496)

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_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.73GB (19.41GB free)

Process Argv
--crash-reporter-id c52ff71d-b95b-45b8-a100-088894fabea9

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

copilot
Git
1.128.0

copilot-chat
Git
0.8.0

console-manager
Hua
0.0.7

powerplatform-vscode
mic
2.0.11

vscode-azureappservice
ms-
0.25.1

vscode-azurecontainerapps
ms-
0.5.1

vscode-azureresourcegroups
ms-
0.7.5

csdevkit
ms-
0.5.150

csharp
ms-
2.7.25

vscode-dotnet-runtime
ms-
1.8.1

vscodeintellicode-csharp
ms-
0.1.26

azure-account
ms-
0.11.6

LiveServer
rit
5.7.9

vscode-css-custom-properties
Toc
0.0.5

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263cf:30856253
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
962ge761:30841074
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30866041
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
copilotsettingc:30859502
synctok:30821570
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
pythonmhint1:30842940
dsvsc015:30845448
pyreplss1:30865275
pythontbext0:30864172

/question
This doesn't look like a bug with VS Code editor itself.
Moreover tsc won't be in PATH unless you have proper npm config/installation that would add folder with global packages to PATH

Unless it's reproducible only in integrated terminal, and not it PS/cmd opened separately - this is improper place to report issue. Moreover, if it's for all global packages, then you should t try to reinstall node/npm

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


text:
头部菜单的渐变色

Hope the author can add the gradient of the header menu

感谢您创建此问题！
然而，由于您没有使用英语，我们很难进行处理。如果可能，请您将此问题描述修改为英文。请您直接编辑此问题，不要提交回复或新问题。
请注意，机器翻译服务通常无法处理用于讨论软件问题所需的技术性语言，所以我们推荐您寻找一位熟悉相关技术的人来协助翻译。
如果您无法做到，没有关系。此问题已经被标记为需要翻译，等待社区成员志愿进行翻译。

Thanks for creating this issue!
Unfortunately, as the description is not in English, it's hard for us to work on. If possible, please edit the original issue to be in English.
In our experience, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help.
Otherwise, we have marked this as needing translation and a community member may be able to help out.

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: VSCodeTriageBot XVDRAEV