text:
Developing for multi-core and heterogeneous devices

Hello guys,
is there a possibility to use vs-code as IDE for multi-core and heterogeneous devices? So I could use a single IDE for Cortex-M, Cortex-A for heterogeneous devices such as arm-development-studio

VS Code doesn't support C and C debugging out of the box, however it's extensible and you can look for corresponding extensions in Marketplace: https://marketplace.visualstudio.com/vscode
Also check https://code.visualstudio.com/docs/languages/cpp for more info

Closing the issue since this as @IllusionMH mentioned is an extension opportunity.

source: gharchive/issue

authors: IllusionMH dbaeumer onyx22574

repo: microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
Code Helper (renderer) consuming 300-400% cpu

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
Just opening a rails-ember folder trigger the cpu throttling taking the whole system down. The mac activity monitor shows its code helper(renderer) and the vscode process show its watcherServices.
I am very bad to execute the commands from github issue pages as none is promising and i dont want to mess up with anything unnecassrily.
VS Code version: Code 1.56.2 (Universal) (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:44:30.902Z)
OS version: Darwin x64 20.5.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
5, 3, 3

Memory (System)
16.00GB (0.09GB free)

Process Argv
--crash-reporter-id bdc44446-94b8-4d2c-a254-75d195e62cbd

Screen Reader
no

VM
0%

Extensions (46)

Extension
Author (truncated)
Version

better-comments
aar
2.1.0

vscode-css-formatter
aes
1.0.1

TabOut
alb
0.2.0

Bookmarks
ale
13.0.4

vscode-erb-beautify
ali
0.2.0

vscode-color
ans
0.4.5

code-gnu-global
aus
0.2.2

solargraph
cas
0.23.0

bracket-pair-colorizer
Coe
1.0.61

erb
Cra
0.0.1

dart-code
Dar
3.23.0

flutter
Dar
3.23.0

vscode-faker
dee
1.5.0

githistory
don
0.6.16

auto-close-tag
for
0.5.10

auto-rename-tag
for
0.1.6

code-runner
for
0.11.4

codespaces
Git
0.10.4

vscode-pull-request-github
Git
0.26.0

ruby
gro
0.1.0

ember-snippets
Hri
1.0.0

better-cpp-syntax
jef
1.15.5

vscode-rufo
jnb
0.0.4

vscode-gutter-preview
kis
0.27.1

vscode-leetcode
Lee
0.17.0

vscode-ember-unstable
lif
2.0.24

cpptools
ms-
1.4.0

cpptools-extension-pack
ms-
1.0.0

vscode-paste-image
mus
1.0.4

color-highlight
nau
2.3.0

live-server-preview
neg
0.1.4

material-icon-theme
PKi
4.7.0

heroku-command
pko
0.0.8

ruby
reb
0.28.1

vscode-commons
red
0.0.6

vscode-yaml
red
0.19.2

LiveServer
rit
5.6.1

swdc-vscode
sof
2.5.15

code-spell-checker
str
1.10.2

bootstrap4-vscode
the
6.1.0

errorlens
use
3.2.7

highlight-matching-tag
vin
0.10.0

vscode-icons
vsc
11.4.0

bootstrap-3-snippets
wcw
0.1.0

vscode-ruby
win
0.28.0

JavaScriptSnippets
xab
1.8.0

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30311712
vspre833cf:30267465
pythonptprofiler:30281270
vshan820:30294714
vscorecescf:30290706
pythondataviewer:30285071
vscus158:30286553
vscgsv2:30307504
vscorehov:30309549
bridgeflightcf:30302070
vscod805:30301674

@krsinghshubham can you follow the wiki https://github.com/microsoft/vscode/wiki/Performance-Issues to help provide more info about what's going on? We would like to know more info about that particular process

code --status is not working for me , why it can't be simply exported in logs while registering a bug from vsc extension.
Although i already mentioned its coming from watcherService, which is troubling when the project folder is too big.
If anyone want to know more , please mail me at shubhamk604@gmail.com, will share a meeting link to show live demo.

@bpasero this is not done man, atleast provide the refrence to the duplicated issue or more specifically a solution for the issue. Yes i saw many similar issue but those were because of extensions, mine is with vscode itself.
And if no solutions exist then you should not mark it as closed.

Also i noticed that in each of those issue pages you guys are asking for additional information , what additional information is required if the bug is being posted from issue reporter too ? I can't find a working solutions anywhere .

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

authors: bpasero krsinghshubham rebornix


text:
Collapsed notebook cells are rotated 270 degrees in Codespaces

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

VS Code Version: 1.59-Insider b805d2e94937976bb17d0439f57fcd3a9d423c31
OS Version: Windows 10

Steps to Reproduce:

Create a notebook
Collapse a cell
🐛 cells are rotated 270 degrees. Seems to be because we use the 'collapsed' classname for cell collapse, and xterm.js loads a stylesheet which applies transform: rotate(270deg) to the collapsed classname. This stylesheet is not loaded in desktop VS Code so the problem seems to only impact Codespaces

This is particularly unfortunate for the interactive window because all code cell inputs are collapsed by default, but it also impacts any collapsed cell in native notebooks all up.

https://github.com/github/codespaces/issues/2871 I filed this a long time ago, but this is pretty bad, I will just change the styles to work around it in the meantime

@roblourens https://github.com/microsoft/vscode/pull/129091 fix proposal from @joyceerhl

authors: joyceerhl rebornix roblourens


text:
Manual check for extension updates sometimes states no updates when some are available

Issue Type: Bug
Manual check for extension updates sometimes states no updates when some are available.
Manual check for extensions.
VS Code version: Code 1.60.2 (7f6ab5485bbc008386c4386d08766667e155244e, 2021-09-22T12:01:43.795Z)
OS version: Linux x64 4.18.0-305.19.1.el8_4.x86_64
Restricted Mode: No

System Info

Item
Value

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

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
30.92GB (21.02GB free)

Process Argv
--unity-launch --crash-reporter-id d4183a8a-8990-4b53-ba92-9008841a16d1

Screen Reader
no

VM
0%

DESKTOP_SESSION
gnome-xorg

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
gnome-xorg

XDG_SESSION_TYPE
x11

Extensions (21)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.25

gitlens
eam
11.6.0

remotehub
Git
0.14.0

vscode-pull-request-github
Git
0.30.0

gitlab-workflow
Git
3.31.0

rpm-spec
Lau
0.3.2

python
ms-
2021.9.1246542782

vscode-pylance
ms-
2021.9.3

jupyter
ms-
2021.8.2041215044

jupyter-keymap
ms-
1.0.0

remote-containers
ms-
0.194.3

remote-ssh
ms-
0.65.8

remote-ssh-edit
ms-
0.65.8

remote-wsl
ms-
0.58.2

vscode-remote-extensionpack
ms-
0.21.0

cpptools
ms-
1.6.0

hexeditor
ms-
1.8.2

vscode-commons
red
0.0.6

vscode-xml
red
0.18.0

vscode-yaml
red
0.22.0

shellcheck
tim
0.16.2

(1 theme extensions excluded)

I can't repro it, can you please provide steps? Is there any particular scenario when this happens?

I have auto updating of extensions disabled.

I access extensions via the extensions icon at screen left.
Access "..." "View and More Actons...".
Click on "Check for Extension Updates".

This issue does not always happen and is very hard to reproduce.


text:
Terminal doesn't take editor background color into account

Forked off case from @sagebind in https://github.com/microsoft/vscode/issues/128295#issuecomment-952194513
I can consistently reproduce this today specifically with terminals in the editor area (similar to https://github.com/microsoft/vscode/issues/127156) as I experience it every day for the past few months. Here's full reproduction steps:

Install a fresh copy of VS Code Insiders (no extensions or customizations). At time of writing I reproduced this with commit dc1a6699060423b8c4d2ced736ad70195378fddf.
Install a theme with a different background color for panel terminal and editor. In this case, https://marketplace.visualstudio.com/items?itemName=swashata.beautiful-ui. Note that this is a theme pack, but can be reproduced with most themes in this pack. The theme shown below is βui - One Dark.
Create a new terminal in the editor area.
Ensure that GPU acceleration is on (terminal.integrated.gpuAcceleration).
Observe the background color discrepancy:

Using the developer tools, you can see that while .editor-container has an inline style of background-color: rgb(38, 42, 49);, the inner element .xterm-viewport has the inline style of background-color: rgb(24, 26, 30);, which does not match the editor area.

Somehow the setting terminal.integrated.gpuAcceleration is actually involved here, because when changed to off, suddenly everything looks correct:

Though the background color of the inner element .xterm-viewport is still the wrong value, it seems to no longer have an impact. I am presuming this is still a VS Code bug, but I suppose that somehow this could be an issue with the theme itself though I'm not sure how.
This test was done on macOS 11.6.

Same here on apple silicon (MBP 2020 m2).
"terminal.integrated.gpuAcceleration": "off"

fixed problem, but for sure it's not best solution :(

Same here :/ MBP Pro 2018.
It was ok until the last update.

For anyone who still cares about this and wants to use terminal editors with a theme that has two different colors for the editor area and the panel area, you can fix this yourself by adding this to your settings:
{
    "workbench.colorCustomizations": {
        "terminal.background": "#00000000"
    }
}

This forces the terminal background color to be transparent, and to inherit whatever background color of the area where the terminal is shown. So terminal editors will have the same color as normal editors, and the terminal in the panel will have the same color as the panel. This is maybe not as nice as having terminal editors being a different color, but at least there's no ugly border where the colors clash against each other.
Note that I still consider this an active bug.

@Tyriar I'm not sure you are understanding the bug. To illustrate:

In this diagram, the ugly margin is what I am calling the bug, not any of the colors being used. I would expect the margin to match the color of the terminal for visual consistency. I can't see how the current behavior is useful to anyone, neither users nor theme developers.
I decided to look at this again to see if I could figure out more about what is going on and I think I did. I think the problem is actually demonstrated by this visualization:

The underlying theme already has editor.background set, but I've changed it to a more obvious color to show the problem. This theme actually does not have terminal.background set at all. Note how everything inherits editor.background as the background color, and aside from the garish color, it looks "normal", except for terminal tabs.
The green border around the terminal itself is actually apparently editorPane.background, which is bleeding through the padding around the terminal renderer. Except again, this happens only for terminal tabs. editorPane.background does not "bleed through" on any other kind of tab that I tested. You can see in my screenshot that there is no green anywhere else (representing editorPane.background).
I suspect this is what causes the ugly mismatched color border around terminal tabs on some themes, because theme developers do not expect the color of editorPane.background has to be the same as either editor.background or terminal.background in order to look consistent, which it isn't the case anywhere else in VSCode.
So it seems like the fix is that the margin/padding area that surrounds the terminal in a terminal tab should be the color of terminal.background if set, otherwise should definitely be the color of editor.background, same as other editors.
I realize I sound like a stick in the mud, but as a heavy user of terminal tabs this visual bug has always bothered me, and I did not expect to see resistance for it being fixed. If I opened a PR myself to fix this, would the VSCode team be interested in accepting it? Because unless I'm missing something it seems to me just a bug, plain and simple, and not a design problem of particular themes.

So basically, the only reason that setting terminal.background "fixes" the problem is because it causes the terminal to use terminal.background as the background color instead of editor.background, and causes it to actually become the same as editorPane.background via alpha transparency. But if the terminal defaults to editor.background in a terminal editor, I would expect the margin around the terminal to also be editor.background, not editorPane.background.
I think enabling Zen Mode helps visually show why the current behavior is wrong:

Oh I couldn't reproduce it before but can now by dragging and dropping into the editor area, reopening 😅

Repro:

Install the Sapphire theme - has editorPane.background and panel.background defined, but not terminal.background
Open the terminal panel
Create a second tab
Drag the tab into the editor, 🐛 the border around the terminal should be the same color

This was meant to be handled here: https://github.com/microsoft/vscode/blob/1784a7ed34aeddc9b4d21bbfa1531496e5873657/src/vs/workbench/contrib/terminal/browser/xterm/xtermTerminal.ts#L279-L280

PR fixing it https://github.com/microsoft/vscode/pull/182557

authors: Tyriar cyntler gukandrew jeanp413 sagebind


text:
The window has crashed (reason: 'oom', code: '-536870904')

Issue Type: Bug
just wait few minutes after opening project
VS Code version: Code 1.62.3 (ccbaa2d27e38e5afa3e5c21c1c7bef4657064247, 2021-11-17T08:11:14.551Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 x 1896)

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)
15.84GB (5.73GB free)

Process Argv
--crash-reporter-id 4e0da4f9-ceb1-45b4-af5b-b3b57fbb3e52

Screen Reader
no

VM
0%

Extensions (22)

Extension
Author (truncated)
Version

markdown-preview-github-styles
bie
0.2.0

npm-intellisense
chr
1.4.0

vscode-eslint
dba
2.2.2

xml
Dot
2.5.1

vscode-generate-getter-setter
DSK
0.5.0

vscode-html-css
ecm
1.10.2

prettier-vscode
esb
9.0.0

vscode-docker
ms-
1.18.0

vscode-language-pack-fr
MS-
1.62.4

python
ms-
2021.11.1422169775

vscode-pylance
ms-
2021.11.2

jupyter
ms-
2021.10.1101450599

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.3

remote-wsl
ms-
0.58.5

vetur
oct
0.35.0

perl
ric
2.3.0

blank-line-organizer
rin
0.1.5

autoimport
ste
1.5.4

vscode-todo-highlight
way
1.0.5

JavaScriptSnippets
xab
1.8.0

markdown-all-in-one
yzh
3.4.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis200cf:30402084
vsaa593cf:30376535
vssld246:30401890
vscop804cf:30404767
vscop940:30404999

reports.zip
Here is the crash report :

Is the issue present when you run with --disable-extensions ? Can you also test with latest stable 1.73

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


text:
question:_snippet suffix implement

Before：
public class Foo {
void m(boolean b) {
b.sout
}
}
after：
public class Foo {
void m(boolean b) {
System.out.println(b);
}
}

@liu904-61 please confirm/clarify


text:
Request RDLC Designer Extension on VS Code Mac

I see there is release of RDLC Designer for VS2022.
Since VS Code is microsoft popular product for cross platform. Should be considering to have its support RDLC cross platform as well. This is very good tool

Why did it close?

Because this issue tracker doesn't accept extension request.

authors: chhinsras yume-chan


text:
Hover. Run not found

Issue Type: Bug
I clicked on command palette and pressed Hover. Run and it says it cannot be found
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
AMD Ryzen 5 1600 Six-Core Processor             (12 x 3200)

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)
15.95GB (8.16GB free)

Process Argv
D:\Unity2D\Delivery Driver\Assets\Delivery.cs --crash-reporter-id b5da5952-d66d-4aef-b6b6-85137b606c76

Screen Reader
no

VM
0%

Extensions (19)

Extension
Author (truncated)
Version

project-manager
ale
12.5.0

path-intellisense
chr
2.8.0

gitignore
cod
0.7.0

bracket-pair-colorizer
Coe
1.0.62

dart-code
Dar
3.36.0

flutter
Dar
3.36.0

git-extension-pack
don
0.1.3

githistory
don
0.6.19

gitlens
eam
12.0.5

prettier-vscode
esb
9.5.0

auto-rename-tag
for
0.1.10

hover
go-
0.1.0

unity-code-snippets
kle
1.3.0

csharp
ms-
1.24.1

python
ms-
2022.2.1924087327

vscode-pylance
ms-
2022.3.3

advanced-new-file
pat
1.2.2

code-settings-sync
Sha
3.4.3

vscode-open-in-github
ziy
1.3.6

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmt:30438805
pynewfile477cf:30450039

/causedByExtension

authors: UVCW gjsjohnmurray


text:
The TypeScript language service died unexpectedly 5 times in the last 5 Minutes.

We have written the needed data into your clipboard because it wa
Issue Type: Bug
Just work with VScode for some period, and after while you'll have this bug with notebook overheating
VS Code version: Code 1.66.2 (Universal) (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:20.994Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

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

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.29GB free)

Process Argv
--crash-reporter-id d2169464-4985-44e8-8620-00eaa14ab00a

Screen Reader
no

VM
0%

Extensions (31)

Extension
Author (truncated)
Version

better-comments
aar
3.0.0

Bookmarks
ale
13.2.4

project-manager
ale
12.5.0

vscode-angular2-files
ale
1.6.4

vscode-intelephense-client
bme
1.8.2

phpserver
bra
3.0.2

bracket-pair-colorizer
Coe
1.0.62

vscode-eslint
dba
2.2.2

es7-react-js-snippets
dsz
4.4.3

gitlens
eam
12.0.6

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.5.0

linter
fna
0.0.11

code-runner
for
0.11.7

rest-client
hum
0.24.6

vscode-react-typescript
inf
1.3.1

graphql-for-vscode
kum
1.15.3

blockman
leo
1.5.7

vscode-docker
ms-
1.21.0

remote-wsl
ms-
0.66.0

vscode-typescript-tslint-plugin
ms-
1.3.4

debugger-for-chrome
msj
4.13.0

vetur
oct
0.35.0

vscode-graphql
ors
0.3.18

quicktype
qui
12.0.46

LiveServer
rit
5.7.5

vscode-javascript-booster
sbu
14.0.1

markdown-preview-enhanced
shd
0.6.2

sapling
tea
1.2.0

vscode-icons
vsc
11.10.0

quokka-vscode
Wal
1.0.457

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebugcf:30466690

s too large to send. Please paste.

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

authors: mjbvz paulkotov


text:
Undo replacement performed in search

From #47166
@Eskibear

Multiselect in Search works well! One feedback is that I cannot batch undo the replacement in different files. Imagine I replaced multiple files with wrong text, it's painful for me to undo the changes one by one.

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


text:
Extension issue

Issue Type: Bug
Extension Name: git
Extension Version: 1.0.0
OS Version: Windows_NT x64 10.0.19043
VS Code version: 1.71.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

What issue are you having with the git extension?

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

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

authors: ArturoDent Hossamhelmyy VSCodeTriageBot


text:
Please update architecture declarators

In the VSCode download page, please consider updating the architecture declarators to a more consistent, less ambiguous common nomenclature:

May I suggest for your consideration (very open to others' suggestions here, too):

Current
New

32-bit
32-bit x86

64-bit
64-bit x64

Arm
Arm*

ARM64
64-bit Arm**

* Arm (the company) prefers we use this Camel-cased "Arm", not all-caps "ARM".
** Arm64 is likely going to be unnecessary moving forward since Arm are deprecating 32-bit Arm Cores/SoCs starting with current generation Arm processors/SoCs.
Thanks withinrafael for the original suggestion.

Recommend you align with other prior art in the Microsoft ecosystem. That is Arm64 or ARM64.
I do not recommend you try to use generic Arm usage as dev tooling can still target both 32-bit and 64-bit ARM targets and Microsoft already used this term for 32-bit targets.
Think we all agree ARM 64 and ARM on this page are bad. 🙃
Arm64
https://dotnet.microsoft.com/download/dotnet/6.0
https://learn.microsoft.com/windows-hardware/drivers/develop/building-arm64-drivers
https://devblogs.microsoft.com/visualstudio/arm64-visual-studio/
https://learn.microsoft.com/windows-hardware/drivers/debugger/debugging-arm64
https://learn.microsoft.com/powershell/scripting/install/powershell-on-arm?view=powershell-7.2
https://blogs.windows.com/windowsdeveloper/2022/06/14/arm64-visual-studio/
ARM64
https://learn.microsoft.com/en-us/java/openjdk/download
https://learn.microsoft.com/visualstudio/extensibility/arm64/target-arm64-visual-studio-extension?view=vs-2022
https://devblogs.microsoft.com/cppblog/visual-studio-code-c-extension-arm-and-arm64-support/

@joaomoreno can i take a swing at this one?

@chrisdias Be my guest!

Can you share the direction you went? (The live site doesn't look any different, guessing the change hasn't deployed yet.)

The original 64-bit x64 etc suggestions made the pages unreadable, so I went with what I saw on the .NET page https://dotnet.microsoft.com/download/dotnet/6.0

@chrisdias Looks great and consistent now, thanks!

authors: bitcrazed chrisdias joaomoreno riverar


text:
This arrow has no hover, so I have no idea what it does

Open diff editor in a PR
See right arrow in the gutter
Hover to discover what it does

🐛 => no hover

There is an issue for this already.

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!

authors: VSCodeTriageBot hediet sbatten


text:
Output Panel missing Window channel

I believe that there used to be a Window option right under Task, but it isn't there anymore. Is this intentional?

I see it

Can you please check if it is true for all VS Code windows?

Strange, I see that it's there for only the first vscode window that I've opened, but not for the others.

I think this happens only for empty window, can you please check?

I can also repro it. Thanks for reporting and info. Will investigate.


text:
Task not found

Error: Task not found
at k.$getTaskExecution in src/vs/workbench/api/browser/mainThreadTask.ts:562:11

Go to Errors Site

a lot has been fixed with tasks since this time, I think it's safe to close this.

authors: VSCodeTriageBot meganrogge


text:
"tab.activeBorderTop" color hidden under "editorGroup.border"

Type: Bug
Steps to Reproduce:

Configure "tab.activeBorderTop": "#ff0000" and "editorGroup.border": "#454545" (or any other colors)
Split the editor horizontally (up or below)
The "tab.activeBorderTop" is not show in lower editor groups.

Additional info:
It seems that "editorGroup.border" is rendered over the "tab.activeBorderTop", as using a color with transparency lets the "tab.activeBorderTop" to be seen.
A similar bug was previously reported (and closed) as https://github.com/microsoft/vscode/issues/140685
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx   (4 x 2495)

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)
11.55GB (6.88GB free)

Process Argv

Screen Reader
no

VM
0%

@jrieken this is caused by https://github.com/microsoft/vscode/commit/1c5ea5a7266cc0286bf803adf6a50b320c6b0a91. z-index is painful because it cannot be scoped to the component. There are carefully crafted z-index rules for the tabs control as you can see from the comment:
https://github.com/microsoft/vscode/blob/e1967e9d0b4eea25aca3f870695ee40a67c354ae/src/vs/workbench/browser/parts/editor/media/tabstitlecontrol.css#L6-L40
Can sticky scroll have a different solution that does not require the entire split view to be lifted to 20?
//cc @joaomoreno for split views, not sure this change might have an impact elsewhere

Oh, this is not lifting the entire split view up, just the border. So the impact is probably less visible, but here in this case it causes the tab border to fall below.

Can sticky scroll have a different solution that does not require the entire split view to be lifted to 20?

I am open for suggestions but I didn't find a better way to tackle this

@jrieken @aiday-mar is there a reason the sticky-widget needs a z-index of 11? If we would make that 4, the issue would be solved and I still see the sticky widget floating above.
https://github.com/microsoft/vscode/blob/14f639fb9e5aa509ea13da6c1a3416844581ab4c/src/vs/editor/contrib/stickyScroll/browser/stickyScroll.css#L35-L40

Hey I dug in the code, and it comes from this: https://github.com/microsoft/vscode/pull/158730, placing the sticky scroll on top of the zone widget. However this is perhaps not that important, and the z-index can be reduced.

Yes, I would prefer if sticky widget could go below 5, otherwise a lot of other things would have to lift above the new 20 from split view.

Sounds good, there is a PR which should soon be merged

I assume this is the issue:

If so I still think we need to fix this somehow. At least so that either the zone is fully above the sticky scroll or fully below, but not intermingled.

This bug has been fixed in the latest release of VS Code Insiders!
@theNestruo, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version bbc87d8ec2453f12c0066e1c30b41cd5bd2aa021 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

/verified
Thank you!

authors: VSCodeTriageBot aiday-mar bpasero jrieken theNestruo


text:
GitHub query limit revealed in Issue Reporter

Type: Bug
Trying to log a bug and see a "GitHub query limit exceeded. Please wait."

Wait for what? What am I, as a user supposed to do, not log the issue?
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 5.4.0-1103-azure

System Info

Item
Value

CPUs
AMD Ryzen 9 3900X 12-Core Processor             (24 x 3793)

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)
127.92GB (94.39GB free)

Process Argv
--crash-reporter-id d2c91f49-7cf5-4a88-bfb8-425825bf92ad

Screen Reader
no

VM
0%

Item
Value

Remote
Codespaces

OS
Linux x64 5.4.0-1103-azure

CPUs
Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz (2 x 2793)

Memory (System)
3.84GB (1.31GB free)

VM
0%

Extensions (56)

Extension
Author (truncated)
Version

codespaces
Git
1.13.8

remotehub
Git
0.50.0

fluent-icons
mig
0.0.18

vscode-edge-devtools
ms-
2.1.1

remote-containers
ms-
0.275.1

remote-wsl
ms-
0.75.2

azure-repos
ms-
0.26.0

remote-repositories
ms-
0.28.0

vscode-icons
vsc
12.2.0

npm-intellisense
chr
1.4.4

vscode-github-actions
csc
0.24.4

dscodegpt
Dan
1.0.15

vscode-eslint
dba
2.4.0

npm-browser
den
1.1.4

gitlens
eam
13.2.0

azure-storage-explorer
for
0.1.2

codespaces
Git
1.13.8

copilot
Git
1.73.8685

copilot-labs
Git
0.9.668

remotehub
Git
0.50.0

vscode-pull-request-github
Git
0.58.1

fluent-icons
mig
0.0.18

lipsum-generator
MrA
1.2.3

azure-pipelines
ms-
1.208.0

azure-dev
ms-
0.3.0

vscode-azureappservice
ms-
0.24.7

vscode-azurefunctions
ms-
1.10.1

vscode-azureresourcegroups
ms-
0.5.6

vscode-azurestaticwebapps
ms-
0.11.4

vscode-azurestorage
ms-
0.15.1

vscode-bicep
ms-
0.14.46

vscode-cosmosdb
ms-
0.19.2

vscode-docker
ms-
1.23.3

csharp
ms-
2.0.0

visual-studio-green
ms-
0.0.312-alpha

vscode-dotnet-pack
ms-
1.0.12

vscode-dotnet-runtime
ms-
1.6.0

vscode-dotnet-sdk
ms-
0.8.0

aks-devx-tools
ms-
0.1.1

vscode-aks-tools
ms-
1.3.10

vscode-kubernetes-tools
ms-
1.3.11

playwright
ms-
1.0.7

azure-account
ms-
0.11.3

azure-repos
ms-
0.26.0

azurecli
ms-
0.5.0

powershell
ms-
2023.1.0

remote-repositories
ms-
0.28.0

vsliveshare
ms-
1.0.5828

azurerm-vscode-tools
msa
0.15.8

vscode-jest
Ort
5.2.3

quicktype
qui
12.0.46

vscode-thunder-client
ran
2.4.1

vscode-yaml
red
1.11.0

dotnet-containerizer
Tim
0.0.20

application-insights
Vis
0.4.2

vscode-icons
vsc
12.2.0

(2 theme extensions excluded)

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
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848:30662994
nodejswelcome1:30587005
2e4cg342:30602488
pyind779cf:30662993
89544117:30613380
pythonsymbol12:30657548
vsctsb:30662444
vscodeenable:30660116

I believe this is (wrongfully) shown when we are unable to show the possible duplicate issues (that typically appears in that space).
You should have no problem actually creating the issue.

authors: TylerLeonhardt timheuer


text:
Search results don't refresh when opening notebook from Explorer or File picker

Testing #174724
Steps to repro:

open VS Code repo
search for repo:microsoft/vscode (see results)
open api.github-issues either from the Explorer or cmd/ctrl+p file picker

Search results don't refresh to the rich search:

Strange, I can't seem to repro. Am I doing this correctly?

That's exactly what I'm doing on macOS.

that's so strange... I just tried on Linux too and I'm not seeing this bug. Is it happening with other notebook types?

authors: TylerLeonhardt andreamah


text:
TS Server fatal error:  Debug Failure. False expression.

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

Global TypeScript Server Plugins
❗ Please test with extensions disabled. Extensions are the root cause of most TypeScript server crashes

typescript-svelte-plugin
typescript-vue-plugin-forward

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: syntax
Error: Debug Failure. False expression.
    at _loop_3 (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:176508:34)
    at ProjectService.assignOrphanScriptInfoToInferredProject (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:176516:25)
    at ProjectService.assignProjectToOpenedScriptInfo (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:178185:26)
    at d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:178459:97
    at Object.flatMap (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:524:25)
    at ProjectService.applyChangesInOpenFiles (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:178459:41)
    at Session.handlers.ts.Map.ts.getEntries._a.<computed> (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:179831:46)
    at d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:182024:96
    at Session.executeWithRequestId (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:182015:28)
    at Session.executeCommand (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:182024:41)
    at Session.onMessage (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:182052:35)
    at process.<anonymous> (d:\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:186208:31)
    at process.emit (node:events:526:28)
    at emit (node:internal/child_process:938:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:84:21)

VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

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

Process Argv
--crash-reporter-id cbb22b1f-d738-4f89-bd1d-f6dddf9086b1

Screen Reader
no

VM
0%

Extensions (33)

Extension
Author (truncated)
Version

nodejs-bundle
1Yi
1.0.0

svelte-bundle
1Yi
1.0.0

icones
afz
0.0.9

iconify
ant
0.5.1

unocss
ant
0.50.4

svelte-intellisense
ard
0.7.1

path-intellisense
chr
2.8.4

vscode-eslint
dba
2.4.0

gitlens
eam
13.3.2

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.10.4

vscode-svelte-snippets
fiv
0.5.0

auto-close-tag
for
0.5.14

auto-complete-tag
for
0.1.0

auto-rename-tag
for
0.1.10

svg
joc
1.5.1

vscode-gutter-preview
kis
0.30.0

i18n-ally
lok
2.8.1

json-to-ts
Mar
1.7.5

git-graph
mhu
1.30.0

dotenv
mik
1.0.1

makefile-tools
ms-
0.6.0

color-highlight
nau
2.5.0

material-icon-theme
PKi
4.24.0

vs-code-prettier-eslint
rve
5.1.0

vue-vscode-snippets
sdr
3.1.1

vscode-standard
sta
2.1.3

svelte-vscode
sve
107.2.5

volar
Vue
1.2.0

vscode-typescript-vue-plugin
Vue
1.2.0

vscode-js-console-utils
wht
0.7.0

vscode-surround
yat
1.5.0

material-theme
zhu
3.15.6

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewvextcfv2:30681851
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848:30662994
nodejswelcome1:30587005
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
a9j8j154:30646983
6233i204:30672705
pythonb192:30669360
funwalk2cf:30682975

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

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

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

authors: VSCodeTriageBot telehot


text:
I can't use ftp

Hi. I code with tablet like 5 years. I was using poor ide but vscode is awesome. I just need ftp for connect wia hosting. Thanks

Please use available extensions to do that. VS Code doesn't support FTP out of the box.
Last request didn't have enough support https://github.com/microsoft/vscode/issues/176156

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!

authors: IllusionMH VSCodeTriageBot eminwork


text:
Title and menu location takes up too much vertical space

Testing #183532
This may not be related to TPI. But I noticed this since I was looking at menus and tabs more closely.
Actual (linux): (Title and Menu are on different lines)

IT looks right on windows:

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!

This is because custom title is not enabled by default on Linux. I have suggested numerous times that we should really change the default.
//cc @sbatten

authors: VSCodeTriageBot bpasero karthiknadig


text:
Hovering the checkbox and then the label has overlapping tooltips

Testing #183549

I hovered over the checkbox, which rendered Checked then I hovered over the tree item label, and it rendered underneath.

This will be fixed by adopting the custom hover: https://github.com/microsoft/vscode/issues/183918


text:
Using custom names for identical folder names in workspace confuses search

Type: Bug
I have to maintain several projects both on git and SVN but they are separate copies. I have added both copies to the workspace and then manually edited the "name" field in the workspace file to add the respective location e.g. "project (git)" and "project (SVN)". Now when I try to perform a search (Find in Folder) of one of these projects I will get search results for any and all files from all projects across the workspace. It seems the search can not handle the added parentheses in the name field and instead shows all search results across all projects in the workspace.
If changing the repo "name" manually isn't intended then please consider this a feature request to support this.

VS Code version: Code 1.79.0 (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:26:35.552Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 2712)

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.61GB (5.50GB free)

Process Argv
--crash-reporter-id e4090bd3-edd6-49af-8d84-8d1687ea6c20

Screen Reader
no

VM
0%

Extensions (22)

Extension
Author (truncated)
Version

asciidoctor-vscode
asc
2.9.8

xml
Dot
2.5.1

auto-close-tag
for
0.5.14

selected-lines-count
gur
1.4.0

output-colorizer
IBM
0.1.2

code-eol
jef
1.0.12

endwise
kai
1.5.1

vsc-python-indent
Kev
1.18.0

ruby-symbols
mig
0.1.8

pylint
ms-
2023.4.0

python
ms-
2023.10.0

vscode-pylance
ms-
2023.6.10

cpptools
ms-
1.16.0

material-icon-theme
PKi
4.28.0

synthwave-vscode
Rob
0.1.15

multi-command
ryu
1.6.0

code-spell-checker
str
2.20.5

code-spell-checker-german
str
2.2.1

open-in-browser
tec
2.0.0

pdf
tom
1.2.2

gitblame
wad
10.2.0

vscode-ruby
win
0.28.0

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
2i9eh265:30646982
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
24365598:30736109
pythonfmttext:30731395
pythoncmv:30756943
fixhidewlkth:30730051
showsbindicator:30760979
pythongtdpathcf:30739705
dh2dc718:30763024
pythonnosm12tcf:30757130

Does it behave better if you avoid all types of bracket in the folder name override?

Does it behave better if you avoid all types of bracket in the folder name override?

Yes, if I just use a dash as a separator it shows only results from the selected folder.

#166318 fixed Find in Folder in cases where the folder name contains some special characters, but not the ( and ) brackets.

https://github.com/microsoft/vscode/pull/166318 should have already been released, but I see that this persists in the current latest.

This is actually a duplicate of https://github.com/microsoft/vscode/issues/175063

authors: andreamah gjsjohnmurray r0ckarong


text:
bash: indoor.py command not found

ADD ISSUE DESCRIPTION HERE
Version: 1.80.1
Commit: 74f6148eb9ea00507ec113ec51c489d6ffb4b771
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
Embedder: codespaces

/needsMoreInfo

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

Please contact the course provider. This GitHub repository isn't the right channel.


text:
The extension thumbnail should have an empty ALT

Type: Bug
WCAG 2.0 recommends that every  tag must have an ALT attribute. The value should be empty if the image is purely decorative.
https://www.w3.org/TR/WCAG20-TECHS/H37.html
Extension thumbnails are decorative, so they should have empty ALT.
VS Code version: Code 1.78.0 (252e5463d60e63238250799aef7375787f68b4ee, 2023-05-03T20:09:46.685Z)
OS version: Linux x64 6.3.11-1rodete1-amd64
Modes:
Sandboxed: No

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

Can you please mention the reason behind the empty alt text?

It's added in the original bug description. Repeating her for convenience -
WCAG 2.0 recommends that every tag must have an ALT attribute. The value should be empty if the image is purely decorative.  https://www.w3.org/TR/WCAG20-TECHS/H37.html

I read your description, but I could not find it in the link you provided (I might missed it). Can you please point me to the exact section where it is mentioned. Thanks.

Oh the exact wording isn't there on that link. But it points to the HTML 4.01 alt attribute which says the following:
The alt attribute must be specified for the IMG and AREA elements...
...In such cases, the alternate text should be the empty string ("")
The general idea is that the alt text helps the screen readers to understand that the image is decorative. If there is no alt attribute, then the Screen readers will try to read the file name. Here are a few links that explain this, with the appropriate text quoted:

https://a11y-101.com/development/the-alt-attribute - "Screen readers can’t read the alternative because there isn’t one. Instead the screen reader will read the file name."
https://accessibility.huit.harvard.edu/describe-content-images - "Leave alt text blank if the image is purely descriptive"
https://accessibility.asu.edu/articles/images - "all images must have alternative text that describes them, except for decorative images, which should have an empty ALT tag."
https://accessibility.psu.edu/images/imageshtml/#empty - "With no ALT tag,  screen reader says 'Image' which leaves the user wondering if they are missing anything important

Thanks for the explanation.

authors: VSCodeTriageBot neeleshb sandy081


text:
Enhance Tab Arrangement Animation for a Polished User Experience

Currently, the tab arrangement animation in VSCode is functional but lacks a smooth and visually pleasing transition similar to browser tabs. This enhancement aims to introduce a more elegant and fluid animation, providing users with a refined and enjoyable experience when managing their workspace. This could include smoother transitions between tab positions and a visually appealing easing effect. Let's elevate the user interface by incorporating a touch of sophistication into the tab arrangement animation.

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!


text:
not able to run code

Type: Bug
I am not able to run a code in c++ .
Its showing :
[Running] cd "c:\Users\HP\Desktop\C++ Youtube" && g++ helloworld.cpp -o helloworld && "c:\Users\HP\Desktop\C++ Youtube"helloworld
'g++' is not recognized as an internal or external command,
operable program or batch file.
But I have installed GCC.
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 7 5800H with Radeon Graphics          (16 x 3194)

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)
15.35GB (6.93GB free)

Process Argv
--crash-reporter-id 540bfea2-be9b-49b7-9d3a-5e56688c44cf

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

code-runner
for
0.12.1

cmake-tools
ms-
1.15.31

cpptools
ms-
1.17.5

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30880072
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialog:30887143
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixtcf:30871695
pythonregdiag2:30871582
pyreplss2:30886141
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:30885897
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30886110
dsvsc017:30886112
dsvsc018:30886114
aa_t_chat:30882232

I tried it in Ubuntu 23.04(Bash), it worked using VSCode, so it's between the OS or the extensions you installed. If it's the OS, [robably because gcc isn't installed globaly

I tried on Ubuntu 23.04(Bash), it worked with vscode's terminal. Probably, its either the OS or the extensions. I don't have any extensions related to C++.  If it's the OS, you probably forgot to install GCC globally

This sounds like an issue with your code or configuration

authors: Keys87 aravindanaswar roblourens


text:
TextModelPart is disposed!: Error: TextModelPart is disposed

I see hundreds of these stack traces in my insiders dev tools:
ERR TextModelPart is disposed!: Error: TextModelPart is disposed!
    at d.g (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:121:22452)
    at d.getWordAtPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:631:119115)
    at x.getWordAtPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:736:9054)
    at a.h (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:68461)
    at new $ (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:68336)
    at new a (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:68912)
    at T (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:69710)
    at R.F (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:74266)
    at R.E (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:74001)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:70454)
    at f.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at f.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at f.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2036)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:744:16156)
    at f.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at f.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at I.s (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:132:108045)
    at I.emitOutgoingEvent (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:132:107799)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:741:28673)
    at f.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at f.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at oe.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:736:16028)
    at oe.endDeferredEmit (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:736:15493)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:727:14628)
    at f.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at f.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:723:24948)
    at f.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at f.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at p.m (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:618:44312)
    at p.getBracketsInRange (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:618:44667)
    at v.getDecorationsInRange (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:723:25134)

ERR TextModelPart is disposed!: Error: TextModelPart is disposed!
    at u.g (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:121:22470)
    at u.getWordAtPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:631:119111)
    at x.getWordAtPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:736:9054)
    at a.h (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:68464)
    at new $ (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:68339)
    at new a (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:68915)
    at T (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:69713)
    at M.F (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:74269)
    at M.E (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:74066)
    at new M (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:70674)
    at q (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:75141)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:75286)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at U.setModel (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:744:400)
    at M.setInput (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2142:23711)
    at async g.S (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2140:22982)
    at async g.L (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2140:21569)
    at async g.openEditor (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2140:20535)
    at async vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2269:23030
    at async Se.open (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2709:42781)
log.ts:441   ERR Model is disposed!: Error: Model is disposed!
    at x.ib (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:728:263)
    at x.getLineCount (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:730:4302)
    at p.computeDiff (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:41538)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:47007
    at b._runFn (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:11404)
    at b.k (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:12292)
    at b.endUpdate (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:12631)
    at i.finish (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:8946)
    at p (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:8381)
    at o.trigger (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:18896)
    at A.a (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:44530)
    at A.h (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:149:19212)
    at A.g (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:149:19196)

Same here, every time I click to place the cursor inside any document, doesn't matter if it is .js, .sh, .json, etc I get an stack exception in devtools. The same happens if I try to move the cursor to the right.
I have VSCode Version: 1.84.2 (Universal) running on MacOS Sonoma.
Here is the stack dump:
ERR TextModelPart is disposed!: Error: TextModelPart is disposed!
    at d.g (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:121:22451)
    at d.getWordAtPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:631:119008)
    at W.getWordAtPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:736:9056)
    at O.D (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:72863)
    at O.F (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:73546)
    at O.C (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:72775)
    at u.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:760:70339)
    at f.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at f.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at f.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at u.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:744:15864)
    at f.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at f.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at I.s (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:132:108107)
    at I.endEmitViewEvents (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:132:108608)
    at $.S (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:742:4025)
    at $.setCursorStates (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:742:2012)
    at V.runCoreEditorCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:16099)
    at V.runEditorCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:8301)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:3547
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:3458
    at g.invokeFunction (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:640:326)
    at x.invokeWithinContext (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:742:12493)
    at r.runEditorCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:3380)
    at V.runCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:3494)
    at handler (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:2042)
    at g.invokeFunction (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:640:326)
    at y.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1537:12423)
    at y.executeCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1537:12011)
    at W.L (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:644:14254)
    at W.I (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:644:11953)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2376:90613

I think this is fixed now. Please reopen if you see this again.

authors: bpasero efreibe hediet


text:
Unexpected lock and close button in empty window

Testing #199023
Repro:

Open untitled file
Drag out to new window
Close untitled file, 🐛 2 buttons remain

This may be by design, if so I don't think the x should be there as is duplicates the regular title bar close button.

Showing the lock icon was an explicit decision specifically for floating windows: https://github.com/microsoft/vscode/issues/182265
The close icon appears because floating windows naturally extend the editor groups concept: once you have a floating window, you have more than one editor group and thus we show actions to close editor groups. We do not show a close icon for the main editor group because you cannot close the main editor group.
I think this is ok as it is, people using multiple editor groups will find this to be familiar I think.

authors: Tyriar bpasero


text:
[Code Lens] F# not showing "Type Signature"

Here are my settings:

Here is the editor:

Also I can't get the new "value inlay int" Ionide feature: link
Thank you for your help.

[Settings] > FSharp > Line Lens: Enabled = Never
did the trick.


text:
Hovers on Linux don't have a proper accessibility view

Testing #213342
Hovers on Linux don't have a proper accessibility view, it always shows:

Same when binding it to Ctrl + Shift + A.

/duplicate #213685

authors: chrmarti meganrogge


text:
report

Type: Performance Issue
event report generator
VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:49:37.021Z)
OS version: Windows_NT x64 10.0.22000
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz (4 x 2304)

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)
3.87GB (0.36GB free)

Process Argv
--crash-reporter-id e573c539-f419-4cb3-adff-96700070f63c

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    1	    89	  7392	code main
    0	     4	  3876	   C:\Users\Hello\AppData\Local\Temp\vscode-stable-user-x64\CodeSetup-stable-dc96b837cf6bb4af9cd736aa3af08cf8279f7685.exe /verysilent /log /update="C:\Users\Hello\AppData\Local\Temp\vscode-stable-user-x64\CodeSetup-stable-dc96b837cf6bb4af9cd736aa3af08cf8279f7685.flag" /nocloseapplications /mergetasks=runcode,!desktopicon,!quicklaunchicon
    0	     5	 21656	     "C:\Users\Hello\AppData\Local\Temp\is-1FHCG.tmp\CodeSetup-stable-dc96b837cf6bb4af9cd736aa3af08cf8279f7685.tmp" /SL5="$705C6,98528185,828416,C:\Users\Hello\AppData\Local\Temp\vscode-stable-user-x64\CodeSetup-stable-dc96b837cf6bb4af9cd736aa3af08cf8279f7685.exe" /verysilent /log /update="C:\Users\Hello\AppData\Local\Temp\vscode-stable-user-x64\CodeSetup-stable-dc96b837cf6bb4af9cd736aa3af08cf8279f7685.flag" /nocloseapplications /mergetasks=runcode,!desktopicon,!quicklaunchicon
    0	    13	  5536	   utility-network-service
    2	    36	 12744	shared-process
    0	    39	 13600	extensionHost [1]
    0	    10	 21784	     electron-nodejs ("C:\Users\Hello\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node "c:\Users\Hello\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\html-language-features\server\dist\node\htmlServerMain" --node-ipc --clientProcessId=13600)
    0	     3	 14320	   crashpad-handler
    0	   164	 16612	window [3] (Issue Reporter)
    5	   248	 21476	   gpu-process
    2	    46	 23136	   window
    0	     9	 23828	fileWatcher [1]
    0	    98	 24520	window [1] (Extension: GitHub Pull Requests - zip file1 - Visual Studio Code)

Workspace Info
|  Window (Extension: GitHub Pull Requests - zip file1 - Visual Studio Code)
|    Folder (zip file1): 44 files
|      File types: png(22) jpg(12) css(1) html(1) js(1) md(1)
|      Conf files:;

Extensions (8)

Extension
Author (truncated)
Version

prettier-vscode
esb
10.4.0

code-runner
for
0.12.2

vscode-pull-request-github
Git
0.78.1

cmake-tools
ms-
1.18.41

cpptools
ms-
1.20.5

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
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31064719
chatpanelc:31048052
dsvsc021:30996838
f3je6385:31013174
a69g1124:31058053
dvdeprecation:31061160
pythonprt:31056678
dwnewjupyter:31046869
26j00206:31048877

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


text:
Preserve unknown unicode characters when saving

EDITED: I've updated this top comment to contain the most relevant information. This is still present in the most recent VSCode version 1.22.2.
I didn't see an existing one like this so here we are.

VSCode Version: 1.22.2
OS Version: Win10 Enterprise

Steps to Reproduce:

Have a UTF-8 file with unicode U+0091 in it.
Open file in VS code to have it displayed as �
Make change somewhere in file other than the hex 91 character and save file
Open in notepad++ to see the character is now different as the hex in the file for U+0091 has been rewritten as � (0xEFBFBD) from the 0x91 it was previously.

Reproduces without extensions: Yes
Weird_Character.zip
Here is an example that I've encountered with most of the file cut out.
This is what it looks like in both editors prior to making the change:

Here is what it looks like after adding the 4th line of text from VS Code:

As I was guessing, it looks like VS Code is normalizing the encoding of the file to UTF-8 and modifying the underlying hex in the file to the '?' character in "there's". Is this expected behavior to implicitly normalize the underlying file whenever it's saved like this?
I tried the same edit but from notepad++ first and it doesn't seem to normalize the file.

Further investigation and asking around seems to indicate that the quote character is a 1252 encoded character that's being displayed weirdly and then normalized to utf-8 and saved back.

Is it expected that VS Code will normalize your file to whatever encoding it detects the file as? If so, what I'm describing might be expected behavior. I'm coming from notepad++ though which doesn't normalize files by default so it seemed wrong.

@Captainohair I could not reproduce.
Here is what I have tried:
A program that generates such a file:
var fs = require('fs');
fs.writeFileSync('file.txt', 'world <<' + '\u0091' + '>>');

The generated file in a hex viewer:

I then proceed to open the file in VS Code and type "Hello" before "world". I hit save. Here is the file on disk:

Perhaps there is something else specific about your file, that makes VS Code open it with a different encoding than utf8?
@bpasero can help with our settings around encodings

@bpasero can help with our settings around encodings

files.encoding: <the encoding>

Weird_Character.zip
Here is an example that I've encountered with most of the file cut out.
This is what it looks like in both editors prior to making the change:

Here is what it looks like after adding the 4th line of text from VS Code:

As I was guessing, it looks like VS Code is normalizing the encoding of the file to UTF-8 and modifying the underlying hex in the file to the '?' character in "there's". Is this expected behavior to implicitly normalize the underlying file whenever it's saved like this?
I tried the same edit but from notepad++ first and it doesn't seem to normalize the file.

Please fix this critical bug. It can't stay that VS Code is silently changing data. Working with ANSI files is unnecessarily stupid with VS Code.

I haven't seen a response yet. Is this normalization that occurs expected behavior?

I've edited the first comment with the better summary of the issue and that this is still occurring in the most recent version.

@bpasero Any update on this? Is this apparent normalization to the detected encoding expected behavior?

If a file contains a character that is not valid UTF-8, it will end up garbled as described in this issue. The underlying reason for this is that the encoding is set to UTF-8 and we encode the entire file as UTF-8 upon saving. If someone has a better idea what to do here, please comment.

well it is pretty easy imho:
if the file is opened as unicode AND saved as unicode, keep unchanged chunks as-is.
the problem of the current behaviour is that i change something in line 2 and vscode changes the hex somewhere down in line 4327 which i can't recognize.
if a file is opened in non-unicode and saved in unicode, encode it all in unicode as you do now.
another possibility:
open and save the file like now but warn if there are unknown characters that aren't the unicode unknown character, such as the ANSI codes for 'ä', 'ö', 'ü', 'ß'.

Ideally, normalizing behaviors like this would be an option I can opt out of. Maybe I want it to normalize files for something, but then I need to work with files where I need them to remain unchanged except for the exact bits I've directly modified. This is currently the default behavior of Notepad++, it saves only what I've changed in the file.
So, if it would be possible to have two modes, or a mode I could disable. Have it normalize by default to be consistent with existing behavior, but then have an option to turn off the normalization and have VS Code save only the changes to the file that I've made.
I just don't like knowing that my text editor might up and modify other parts of the file on me as @WorldofBay mentions. Whether or not my file is consistent with itself is a problem for me to decide, not my editor. I would like for my editor to have the tools available to make the file consistent with itself if I deem it necessary however.

There is literally nothing I can do from the file service, this needs support from the editor. I am asking the snapshot to return me a value for the contents of the editor (here) and this value will be UTF encoded and already converted. So at that point in time it is too late to fix the conversion.

I think this is a challenging change and not sure worth the efford.

This issue has cut down on my use of VS Code for editing random files, because I can't trust it. As pointed out other editors handle this in a much nicer way. It's even worse if you use autosave by default, as simply opening a file to inspect it can lead to changes in the file without your knowledge.
The display of invalid characters can look however it needs to. Please don't change bytes in the file that I didn't type anything into.

@bpasero Thank you for routing this to the appropriate party. @rebornix, please consider implementing a fix as we have described here. It would make VS Code much more robust and it would feel much more reliable. I agree with @billwert that I just can't trust the editor. As I've mentioned, it probably shouldn't matter most of the time whether your files are normalized or not, but sometimes I absolutely can't have a file get normalized based on what the editor thought it determined the file encoding to be. I do a lot of data transformation tasks and I need to know that what I'm seeing in my editor is exactly what is in the file.

Technically we read the buffer from nodejs and then convert it into js string for later manipulation, in which it's being decoded (by guessing and we think it's UTF8 in this case) and then encoded as UTF16. That's why we see � when it's shown in the editor. When we attempt to save, we are decoding the string with � and then try to encode it with proper encoding for saving the disk. If I understand correctly, it went wrong when we do the encoding conversion from the buffer at the very beginning.
I labelled it as Help wanted as my knowledge of encoding/decoding doesn't give me any hint of how to properly fix this issue and if I can get any help, it would be highly appreciated.

I unfortunately don't have nodejs experience but I will see if I can get more eyes on this who do.

I would say that if the editor fails to decode the file in the chosen encoding, you should a warning about the encoding being wrong. At least if you try to edit it.

In my case, vim finds the right encoding for the file and doesn't garble the characters.
Definitely a bug that should be addressed, no editor should change characters in a file without user consent or a issuing a warning at the very least.

This is a huge pain.  VScode needs to have a dialog warning before saving a file that contains any "�".

Yes i have been bitten by this as well because i used VSCode as merge editor without configuring the encoding options first, creating a ton of work.
In my opinion, a good enough and hopefully much easier solution is to simply warn the user when a file is opened with unknown symbols, telling the user to configure the encoding options correctly and reopen the file (on saving would work as well).
In addition, the auto-detection option could maybe be enabled by default instead of UTF-8 (that option hopefully defaults to UT-8 anyway in most cases without ANSI characters).

The bug didn't seem to be fixed for me.  Today I was editing the pm.lua file in the Lua 5.3.4 test suite (https://www.lua.org/tests/#files).  vscode silently made a number of changes when saving, breaking the tests.  The file was detected as UTF8-encoded.
To reproduce:

download and unarchive https://www.lua.org/tests/lua-5.4.3-tests.tar.gz
open pm.lua and save as pm2.lua
observe the difference between pm.lua and pm2.lua

If I reopen the file pm.lua with windows 1252 encoding explicitly then it appears to behave well.
I've uploaded pm.lua for convenience (as pm.txt because .lua files cannot be uploaded):
pm.txt.
I was using vscode version 1.62.3 on macos.  Here are the details:
Version: 1.62.3 (Universal)
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T07:59:13.865Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0

@arnodel do you have "files.autoGuessEncoding": true set?

@arnodel do you have "files.autoGuessEncoding": true set?

No, thanks for pointing out this setting.  If I turn that setting on, then the file encoding is correctly guessed, therefore there are no silent changes when saving it.
However I don't think the default behaviour should lead to potential file corruption.

authors: Captainohair JacksonKearl Jan-Thes LinAGKar WorldofBay alexandrudima arnodel billwert bpasero planetwarevince rebornix xavierrobitaille


text:
Slow syntax highlighting

VSCode Version: Insider 1.30
OS Version: Windows 10 1607 LTSB x64

Steps to Reproduce:

Load large C++ file (60k LOC)
Observe the slowness. Takes like 10s to highlight the code.

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

Today, syntax highlighting is running on the main thread and is implemented by constantly yielding in order to keep the thread responsive. The speed is further influenced by the grammar. This can be improved if we move the tokenization to a separate thread.

Excellent. Hope to see it implemented ASAP.

Is fix coming? @bpasero

Has this been fixed?! It's been almost 9 freaking months!!!

@optomux I co-maintain the C++ grammar if this still appears broken, could you create an issue in https://github.com/jeff-hykin/cpp-textmate-grammar with an example file that reproduces. Alternatively, if the file is confidential, I can provide steps to collect performance information without revealing the file.

Open sqlite3 which is pretty large.

@optomux After processing the 223k loc sqlite.c There does not seem to be much that can be done on the grammar side. While it did take 11.7 seconds to evaluate the patterns inside the grammar, no individual pattern took an unexpectedly long amount of time.
If you are having similarly long times on significantly shorter files, there may still be an issue in the grammar, however.

Today, syntax highlighting is running on the main thread and is implemented by constantly yielding in order to keep the thread responsive. The speed is further influenced by the grammar. This can be improved if we move the tokenization to a separate thread.

are there plans to do this?

It would be great to improve this with multi-threading, quite annoying to wait for syntax update in large amalgamated source code after every tiny change by an external application.

I have the same issue after updating the C++ extension to version 0.28.*. I reinstall it back to version 0.27.1 and it fixes the issue partly. The color isn't still rendered too fast but at least version 0.27 is much better.

It looks like the work in https://github.com/microsoft/vscode/issues/77140 may help solve this but I’m not 100% sure

for me still not working here ...

If I'm not mistaken VS Code extended syntax coloring behaviour by including the extension "Better C++ Syntax" to the base program. Well, I have observed that this problem only occurs with tokens that are not colorised with the standard VS Code syntax highlighting. In the next gif one can observed how the Strings in the cout get quickly green color when the line gets commented but, on the other hand, the rest of the tokens in the line take much longer.

Thus, I think this issue is strongly related to the way  "Better C++ Syntax" extension works internally so the fix goes by adding the behaviour the extension provides to the base program in the way it is done with the base syntax highlighting.

I just installed VS Code to try it.
Typing code . in the directory of a project (of a really small size, about 10 000 lines) in JS. And I first wait about 3 seconds to see the text and then 2 seconds more to get the text from plain white to highlighted.
So, 2021 and the issue is still not solved at all. Giving the pace of solving so basic problems, I do not know what to think about that editor tbh...

I just installed VS Code to try it.
When I typing code . in the directory of a project (of a really small size, about 10 000 lines in JS) I first wait about 3 seconds to see the text and then 2 seconds more to get the text from plain white to highlighted.
So, 2021 and the issue is still not solved at all. Giving the pace of solving so basic problems, I do not know what to think about this editor tbh...

The highlighting starts doing like in Balrrach's GIF for me when I activate CPP intelisense

Is there a plan to fix this problem?
If so, how long will it take?
Is it a hard problem to solve or a design problem?

Is there a plan to fix this problem?
If so, how long will it take?
Is it a hard problem to solve or a design problem?

As I mentioned in my comment above it looks like the work to fix this was moved to this thread https://github.com/microsoft/vscode/issues/77140 it might be worth asking there. It looks to have gone dark.

@Balrrach
I found easy quick fix ! Go to settings (ctrl + ,) , type "intellisense enhanced colorization" , set to "Disabled" .
I don't know what this feature is suppose to offere, but without it code is colored and Intellisense is still doing it's job at linting & such . I'm happy now

a 78KB HTML file takes FIFTEEN MINUTES to color code in which VSCode is completely unresponsive and my OS wants to kill the task.
ARE YOU FOR REAL.

If I'm not mistaken VS Code extended syntax coloring behaviour by including the extension "Better C++ Syntax" to the base program. Well, I have observed that this problem only occurs with tokens that are not colorised with the standard VS Code syntax highlighting. In the next gif one can observed how the Strings in the cout get quickly green color when the line gets commented but, on the other hand, the rest of the tokens in the line take much longer.

Thus, I think this issue is strongly related to the way "Better C++ Syntax" extension works internally so the fix goes by adding the behaviour the extension provides to the base program in the way it is done with the base syntax highlighting.

Is there a solution yet? i really like my custom theme.

Has anyone managed to fix this?

Has anyone managed to fix this?

2 (somewhat works) approach

as @ebkgne mentioned: turning off the enhanced color ( form setting Ctrl +, ) And search for enhanced colorization. disable that.
If enhanced colorization is so damn necessary consider increasing the IntelliSense speed . in setting search for Intelli Sense Update Delay and make it 500 (minimum possible)

how to fix this issue 😭, happened to me too
https://github.com/microsoft/vscode/assets/49369600/bf23e52b-7839-4461-8e47-532815cad1df

Turn off enhanced colonization.
On Thu, Mar 28, 2024, 6:02 PM xhttp.res @.***> wrote:

how to fix this issue 😭, happened to me too
https://github.com/microsoft/vscode/assets/49369600/bf23e52b-7839-4461-8e47-532815cad1df
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/64681#issuecomment-2025076523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHBODQCNKZZF2AHCF4LTSDY2QEWBAVCNFSM4GJIENV2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBSGUYDONRVGIZQ
.
You are receiving this because you commented.Message ID:
@.***>

Turn off enhanced colonization.

where ? i can't found it  😭

i'm work with javascript btw

I am working with C++, and the option to disable enhanced colonization is
available under the C/C++ extension.
On Thu, Mar 28, 2024, 6:32 PM xhttp.res @.***> wrote:

i'm work with javascript btw
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/64681#issuecomment-2025130354,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHBODRGLWYCHHFBCCT7XTLY2QIFBAVCNFSM4GJIENV2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBSGUYTGMBTGU2A
.
You are receiving this because you commented.Message ID:
@.***>

authors: Balrrach RabiulAwalOvi SebiTimeWaster alexandrudima bpGusar ci70 ebkgne jasonwilliams marktimarev matter123 nhuhoang0701 nxrighthere optomux shubhamvermaa xhttp-res


text:
VS Code crashes when trying to open 1,8GB file

Issue Type: Bug

I try to open 1,8GB txt file
Appliction asks me to set up more memory (up to 8192MB) I choose to "Restart with 8192"
Application restarts and crashes

When I check what is current memory limit, it is already 8192MB but then when I try to open file again I got asked to "Restart with 8192MB" again.. and it goes on like this...
VS Code version: Code 1.33.0 (0dd516dd412d42323fc3464531b1c715d51c4c1a, 2019-04-04T15:14:28.026Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

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

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.62GB (8.13GB free)

Process Argv
C:\Temp!\msmdsrv.log

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

xml
Dot
2.4.0

EditorConfig
Edi
0.13.0

graphviz-preview
EFa
1.3.1

mssql
ms-
1.5.0

@rebornix This is tricky bit. I know how important this is for you to test, but it's customer's log file from Microsoft SSAS (msmdsrv.log) and this is actually my last day on site. Nevertheless I'll try check with them if it's OK that I take a log outside organisation.

Close it for now and we can reopen once we have more data to troubleshoot.

authors: morriekken rebornix