text:
Enable previewing chat codeblocks

Needs https://github.com/microsoft/vscode/pull/224662 for the editor language context key
What do you think of this @andreamah? I think it's a cool scenario but I had to do a couple hacks in the code.
Fixes https://github.com/microsoft/vscode-livepreview/issues/673

This is just to enable the normal editor context menu action for codeblocks, so I can right click an HTML codeblock and click "Preview"

This is just to enable the normal editor context menu action for codeblocks, so I can right click an HTML codeblock and click "Preview"

Ah ok, I didn't think to right click. It doesn't seem to work for me with just these changes. Does it work on your side?

It seemed like it went to the wrong URL for me. Maybe it was a windows thing.

Tried to clean this up a bit, but I'm still not 100% sure I'm doing the right thing. No rush, we can look at it later during debt week.

source: gharchive/pull-request

authors: andreamah roblourens

repo: microsoft/vscode-livepreview

license: MIT

license_type: permissive

license_source: github-api


text:
Language server does not reload on lsif.json changing

If you change the lsif.json file, the language server should reload from the new information.

Even a command for a manual reload would ease testing.

source: gharchive/issue

authors: LukaszMendakiewicz mpickering

repo: microsoft/vscode-lsif-extension


text:
mypy exclude patterns independent of linter-level ignore patterns not supported

The current (soon to be deprecated) vscode mypy linting behavior effectively allows mypy exclude-pattern consideration without depending upon linter-level ignorePatterns.
The resolution to #157 (using the experimental workspace scope) does not replicate the current vscode mypy functionality because it implicitly tethers the mypy ignore patterns to linter-level ignorePatterns which are often divergent. (e.g. one cannot allow ruff to lint 'setup.py' while still allowing a mypy exclude configuration to apply to 'setup.py').
The current functionality is enabled by passing an empty --exclude to python.linting.mypyArgs (i.e. "python.linting.mypyArgs": ["--exclude"]), which effectively suppresses the file-specific overrides of mypy exclude patterns (the behavior described in https://github.com/microsoft/vscode-mypy/issues/157#issuecomment-1730905253) and results in linting at a repo-configured level. This allows linting a superset of the files over which mypy operates.
The current functionality is admittedly a bit of a hack so perhaps this issue is better cast as a feature request. Either way, perhaps porting the current behavior to dmypy by providing the user the ability to add args (such as --exclude) immediately prior to a given file or workspace (depending upon the dmypy reporting scope) would be acceptable? Essentially, I'm asking to reorder the current mypy-type-checker.args to provide them last and in so doing provide the user more control/flexibility to implement workarounds like this. I've verified (in both file and workspace scope) this approach would allow users to replicate the current functionality with dmypy while also avoiding the explicit endorsement of the aforementioned hack :smile:

file scope

python -m mypy.dmypy run -- --show-absolute-path --show-column-numbers --show-error-codes --no-pretty --show-error-end --exclude /home/user/repo/reponame/setup.py
Success: no issues found in 10 source files

workspace scope

python -m mypy.dmypy run -- --show-absolute-path --show-column-numbers --show-error-codes --no-pretty --show-error-end --exclude  /home/user/repo/reponame
Success: no issues found in 10 source files

Thanks for all your work on this valuable extension!

Thanks for adding this functionality! :rocket:

Thanks @karthiknadig, I checked all worked as expected yesterday (including logs indicating detection of the skip directive). I would note and perhaps add to the documentation that setting preferDaemon to false is important for ignorePatterns to function as expected. I noticed that without that, once the daemon encounters issues with one file, the daemon will not register issues with another file (seemingly constrained to within the same top-level folder of the workspace) until issues with that file are resolved.
Thanks again for your work on this valuable extension!

repo: microsoft/vscode-mypy


text:
(Black) Formatter fails with .env in Python

Environment data
VSCode: Most recent non-insider version.
Python: 3.7
Black: Most recent.
Expected behaviour
Black is registered as a formatter.
Code is formatted.
Actual behaviour
Nothing happens.
Steps to reproduce:
Working:

Register black as the formatter of choice.
Create a directory with the following structure:

root
- project
  - file_to_be_formatted.py

Add some code into file_to_be_formatted.py that has formatting issues.
Run black with alt + shift + f. It formats the code!

Failing:

Register black as the formatter of choice.
Create a directory with the following structure:

root
- .env (This contains "PYTHONPATH=./project" to make properly configure package detection, etc.)
- project
  - file_to_be_formatted.py

Add some code into file_to_be_formatted.py that has formatting issues.
Run black with alt + shift + f. It does not format the code

So having a .env file will silently make black fail. Running black from the command line on file_to_be_formatted.py does still work
I follow this: https://github.com/microsoft/python-language-server/blob/master/TROUBLESHOOTING.md#unresolved-import-warnings

Hi @sleighsoft , thank you for reaching out!
Can you please share the following so that I can try to reproduce your issue:

The content of the Python output panel (View→Output, change the drop-down the upper-right of the Output panel to Python) when formatting works and fails;
The content of your .vscode/settings.json file;
The content of your .env file.

Also, does formatting work if you use a different formatter, or if you use jedi instead of the MPLS?
Thanks!

.env
PYTHONPATH=./project

Output of pressing shift + alt + f once
> C:\Progams\Miniconda\envs\project\python.exe -m black --diff --quiet c:\Development\github\project\project\test_decorator.py
cwd: c:\Development\github\project
> C:\Progams\Miniconda\envs\project\python.exe -m black --diff --quiet c:\Development\github\project\project\test_decorator.py
cwd: c:\Development\github\project

.vscode/settings.json
{
    "python.pythonPath": "C:\\Progams\\Miniconda\\envs\\project\\python.exe",
    "python.formatting.provider": "black"
}

autopep8 also fails
output
> C:\Progams\Miniconda\envs\project\python.exe -m autopep8 --diff c:\Development\github\project\project\test_decorator.py
cwd: c:\Development\github\project
> C:\Progams\Miniconda\envs\project\python.exe -m autopep8 --diff c:\Development\github\project\project\test_decorator.py
cwd: c:\Development\github\project

Does formatting work if you run C:\Progams\Miniconda\envs\project\python.exe -m black --diff --quiet c:\Development\github\project\project\test_decorator.py from the c:\Development\github\project directory?

Yes, it outputs a diff with the proper formatting.

Pytest also fails!
I just tried out builtin pytest. It also fails to discover tests when the .env file is set!

Output
> C:\Progams\Miniconda\envs\project\python.exe c:\Users\Me\.vscode\extensions\ms-python.python-2020.2.64397\pythonFiles\testing_tools\run_adapter.py discover pytest -- --rootdir c:\Development\github\project -s --cache-clear
cwd: c:\Development\github\project

Can you try removing PYTHONPATH from the .env file?

Removing PYTHONPATH and reloading VSCode enables black again.
Setting PYTHONPATH within .env breaks the tooling.

I couldn't reproduce your issue with the following structure:
root/
   .venv/ (virtual environment folder)
   .vscode/
   project/
      file_to_format.py
   .env

and the content of the .env file being
PYTHONPATH=./project

Black formats file_to_format.py correctly. Do you have a sample repo I could use to try and replicate your issue?
Also, does the tooling (black and pytest) work correctly if you use the other options for passing the extra roots to the language server, either by specify PYTHONPATH in your env variables directly or using the "python.autoComplete.extraPaths" setting?

I tried setting up a sample project but also cannot reproduce it.
I initially had and still have this problem with the following project: https://github.com/sleighsoft/benchit

OHHH, I think I have a filename conflic with io.py... This took me a while. Maybe the error output within VSCode should not be all silence.

Now I still don't get the intended behavior from my .env. I initially set PYTHONPATH to fix this problem https://stackoverflow.com/questions/53939751/pylint-unresolved-import-error-in-visual-studio-code but I haven't been lucky so far.

Any ideas why settings PYTHONPATH does not fix the issue with unresolved import?

Since dtypes is a sibling of file_to_be_formatted.py, and because you've made project a package (with the __init__.py), you can omit project in the import statement and write from dtypes import classname directly, without needing PYTHONPATH or the .env file:

Oh, thank you very much for helping me out here.
I must have misunderstood how VSCode is searching for packages and then mixed too many different approaches.
Thank you again for troubleshooting this with me!
Feature idea: I hope there is a setting in the future that just disables the silent flag on all commands run by VSCode, so that the Output panel shows proper erros (correct me if I am wrong and this already exists).

No problem, glad we got it sorted out 🙂 Although, I looked a bit further into it (and this helful SO answer), and to make it a relative import you'd have to write from .dtypes import classname (note the extra period):

The existing setting closest to what you describe would be python.analysis.logLevel, which defines the type of log messages the language server writes into the Python Language Server output window, but it's only for the language server.
Other than that, the flags are on a per-tool basis, for example for Black we have:

https://github.com/microsoft/vscode-python/issues/8196
https://github.com/microsoft/vscode-python/issues/3318
https://github.com/microsoft/vscode-python/issues/3228 (this one is about Black timing out silently)

I upvoted all of the above. I'll restructured my project to
.vscode
setup.py
benchit/
   format.py
   dtypes.py uses `import format`
tests/
   test.py uses `import dtypes`

I have no .env and no additional settings in settings.json.
I have jedi disabled.

With this setup VSCode:

properly discovers and runs tests under the Test tab
has proper auto completion and detection of my package
i can properly install the package with pip install -e . from the project root

Sounds good 👍  I'll close this issue as resolved, but you're welcome to comment here if you encounter issues further down the road and we can reopen it 🙂

authors: kimadeline sleighsoft

repo: microsoft/vscode-python


text:
Code navigation does not work in the Jupyter notebooks.

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

Open a notebook (.ipynb file) or create one with some test code (just define a variable and access it from a subsequent cell)

⌘+Click should take you to the variable/function definition and this does not happen.

Actual behavior

⌘+Click does nothing (although the same works in .py files)

Expected behavior

⌘+Click should take you to the variable/function definition and this does not happen.

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running: Local
VS Code version: 1.46.1
Setting python.languageServer: Jedi
Python and/or Anaconda version: 3.6.10
OS: Mac
Virtual environment: conda

Developer Tools Console Output

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

@subhashbylaiah . Thanks for the report on this. As it currently is implemented notebook support is added in as an independent webview, we've tried to make it match the VSCode editors as much as we can, but many code navigation and extension features are currently not supported in it.
The good news is that the VSCode core team is currently in process of adding in full notebook UI support to the main VSCode product. When this comes online, our extension will move over to using that and this issue should be resolved. You can track the main VSCode issue here:
https://github.com/microsoft/vscode/issues/91987

I'm going to close this issue for now as we will not be fixing it in our current implementation, but the new notebook implementation should be releasing soon in preview form soonish, and you can check out this feature when that happens.

Ok, thanks

authors: IanMatthewHuff subhashbylaiah


text:
The code is not executed completely when pick 'Python: Run Current File In Python Interactive Window'.

Environment data

Expected behaviour
The kernel should be restarted and it should run the whole file again.
Actual behaviour
The code is not executed completely.

Steps to reproduce:

Open the file manualTestFile.py in VSCode
Select conda Interpreter as current environment
On the first cell click Run Cell And All Below
Close the Interactive Window then pick Python: Show Python Interactive Window
The kernel should be restarted and pick Python: Run Current File In Python Interactive Window

It's hard to tell from the screenshot if the second run of the file finished? I believe you're saying it didn't?

This issue also occurred on stable build.

I have attached the python file which run and the not fully executed jupyter notebook file.
TestFile.zip

authors: linette-zyy rchiodo


text:
Python

Type: Bug

Behaviour
Expected vs. Actual
XXX
Steps to reproduce:

XXX

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.12.0
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

languageServer: "Pylance"

Extension version: 2023.22.1
VS Code version: Code 1.82.3 (fdb98833154679dbaa7af67a5a29fe19e55c2b73, 2023-10-02T10:51:22.294Z)
OS version: Windows_NT x64 10.0.22621
Modes: Unsupported

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz (4 x 2295)

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)
7.88GB (3.20GB free)

Process Argv
E:\translate --crash-reporter-id c8ab6fe0-2884-4e8f-8f52-544d68da41b0

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30899288
vscaac:30438847
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
282f8724:30602487
89544117:30613380
showlangstatbar:30737416
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialog:30910333
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
cp7184c:30925681

Hello, closing this issue as there is no information attached please create a new issue with all the information on your bug if you still need assistance. Thanks


text:
Option to use (default) light theme for Jupyter figures

Feature: Notebook Editor, Interactive Window, Python Editor cells

Description
Actually, this is the same request as #4640 (but that issue was resolved with a setting ignoreVscodeTheme, which forces the whole Jupyter tab to use the light theme).
It would be great to have an option that prevents the dark theme of Jupyter figures.
If I remember correctly, it is just a parameter when communicating with Jupyter (or Matplotlib config?)
Thanks

You can fix this yourself if you want (not sure if we'll add a setting or not, depends upon how many people ask for it).
Run this in a cell first:
matplotlib.rcParams.update(_VSCode_defaultMatplotlib_Params)

We save the default matplotlib settings in the _VSCode_defaultMatplotlib_Params variable
This should reset all matplotlib output to its default theme.

Actually if you stick that code in this setting here:
python.dataScience.runStartupCommands
It will automatically execute that value before any cells are run.

Thank you. I will try it.

I've tried the suggested method, but could not get the startup commands to work with any of the following settings (in the interactive window):
"python.dataScience.runStartupCommands": "matplotlib.rcParams.update(_VSCode_defaultMatplotlib_Params)",
"python.dataScience.runStartupCommands": "from matplotlib import pyplot\nmatplotlib.rcParams.update(_VSCode_defaultMatplotlib_Params)",
"python.dataScience.runStartupCommands": "matplotlib.style.use(\"default\")",
"python.dataScience.runStartupCommands": "from matplotlib import pyplot\nmatplotlib.style.use(\"default\")"

What did work was to recover the default settings just after the pyplot import. Using the rcParams is deprecated in Python3 and results in some visual issues, however, I could use matplotlib.style.use("default") successfully (see screenshots)

This was on python 3.6.8 64-bit, in vscode 1.39.2 and vscode-python 2019.10.44104

@IanMatthewHuff actually just submitted a fix for this. We didn't realize it actually was fixing some enhancement requests too :)
Our insider's build has his changes.
Essentially we got rid of our theming for plots in dark and made them all have a white background.
You can see a screenshot of his changes in his PR:
https://github.com/microsoft/vscode-python/pull/8177#issuecomment-545625991

Validated

authors: AlexanderBurker rchiodo yzhang-gh


text:
Remove hardcoding of position of connection file in kernelspec args

Currently we're assuming the position of <connection_file> is always the 5th element in the array.
However users can edit the kernel.json files to add additional args to the executable
Ensure the env variables are part of the IJupyterKernelSpec

Codecov Report

Merging #11299 into master will decrease coverage by 34.88%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #11299       +/-   ##
===========================================
- Coverage   61.13%   26.24%   -34.89%
===========================================
  Files         602      324      -278
  Lines       33151    17262    -15889
  Branches     4685     2438     -2247
===========================================
- Hits        20266     4531    -15735
- Misses      11864    12696      +832
+ Partials     1021       35      -986

Impacted Files
Coverage Δ

src/client/datascience/types.ts
100.00% <ø> (ø)

src/client/debugger/constants.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/client/interpreter/autoSelection/constants.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/client/language/braceCounter.ts
5.40% <0.00%> (-94.60%)
:arrow_down:

src/client/language/textBuilder.ts
8.69% <0.00%> (-91.31%)
:arrow_down:

src/client/language/characterStream.ts
4.41% <0.00%> (-89.71%)
:arrow_down:

src/client/language/tokenizer.ts
4.08% <0.00%> (-89.22%)
:arrow_down:

...lient/interpreter/locators/services/condaHelper.ts
7.69% <0.00%> (-87.18%)
:arrow_down:

src/client/common/process/pythonProcess.ts
11.11% <0.00%> (-86.12%)
:arrow_down:

.../interpreterSecurity/interpreterSecurityService.ts
14.28% <0.00%> (-85.72%)
:arrow_down:

... and 484 more

Continue to review full report at Codecov.

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

authors: DonJayamanne codecov-io


text:
Align ref picker with built-in git extension ref picker

@joyceerhl I don't see HEAD, i do see main (default).
Like this from desktop:

Originally posted by @karthiknadig in https://github.com/microsoft/vscode-remote-repositories-github/issues/206#issuecomment-1171514182

Builtin git extension:

RemoteHub:


text:
Support IGrammarRegistration.injectTo and IRawGrammar.injectionSelector

I want to use vscode-textmate for an LSP to highlight parameters in function scopes correctly. The vscode-matlab repo uses a injection grammar for read-write variable tokens, so I need injection grammar support in this package.

@alexdima will a PR get dev time for review

repo: microsoft/vscode-textmate

license: mit

license_source: bigquery


text:
中文注音輸入

Issue Type: Bug
使用微軟注音 - 中文
打注音（如：ㄅ）
切換 (shift) 成英文並按下 backspace
會使閃爍游標變成兩個
並且留下原本中文的黑框
此時無法正常輸入
只能切回 (shift) 中文再次輸入注音並按下 backspace
才能回復正常 (在黑框中打的字會全部被刪除)

(I'm not good at English)
How does it happen?
I use "Microsoft Bopomofo (Traditional) Input" to type bopomofo (ex: ㄅ) and then press backspace after switch (shift) to English.
This doesn't happen every time.
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

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

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.86GB (1.63GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

gitlens
eam
10.2.2

vscode-language-pack-zh-hant
MS-
1.46.3

It seems to be working fine now after the update . (version: 1.47.2)
If it happens again, I will come back and bring description or video.

repo: microsoft/vscode


text:
Notebook folding misplaces cell selection

Issue Type: Bug

Have the keyboard focus on a cell that is a "child" of a foldable markdown cell
2)ArrowLeft
-> I agree that this should fold the section, but now the "parent" should have the keyboard focus. However, it's lost and on ArrowDown keyboard focus goes to the first cell of the notebook.

VS Code version: Code - Insiders 1.50.0-insider (0580328b728a69768558cc8242067cae7b6a1c21, 2020-09-29T09:05:00.729Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)

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

Load (avg)
2, 1, 1

Memory (System)
16.00GB (0.30GB free)

Process Argv
-psn_0_10267082 --crash-reporter-id d4b72415-0109-45b3-a1a7-967fdd12f0f4 --crash-reporter-id d4b72415-0109-45b3-a1a7-967fdd12f0f4 --crash-reporter-id d4b72415-0109-45b3-a1a7-967fdd12f0f4

Screen Reader
no

VM
0%

Extensions (37)

Extension
Author (truncated)
Version

vscode-track-build-errors
aes
0.0.2

git-branch
ale
1.6.0

github-markdown-preview
bie
0.0.2

markdown-checkbox
bie
0.1.3

markdown-emoji
bie
0.0.9

markdown-preview-github-styles
bie
0.1.6

markdown-yaml-preamble
bie
0.0.4

vscode-svgviewer
css
2.0.0

vscode-eslint
dba
2.1.9

gitlens
eam
10.2.2

tsl-problem-matcher
eam
0.3.0

vsc-material-theme
Equ
33.0.0

vsc-material-theme-icons
equ
1.2.0

graphviz-markdown-preview
gee
0.0.8

vscode-pull-request-github-insiders
Git
2020.9.41222

mdmath
goe
2.5.1

crazy
kie
0.0.2

svgpreview
kis
0.2.0

rainbow-csv
mec
1.7.1

theme-monokai-pro-vscode
mon
1.1.17

vscode-docker
ms-
1.6.0

python
ms-
2020.9.112786

remote-containers
ms-
0.143.0

remote-ssh-edit-nightly
ms-
2020.9.41220

remote-ssh-nightly
ms-
2020.9.41220

remote-wsl
ms-
0.50.0

azure-account
ms-
0.9.3

azurecli
ms-
0.5.0

js-debug-nightly
ms-
2020.9.2817

vscode-github-issue-notebooks
ms-
0.0.52

vscode-js-profile-flame
ms-
0.0.10

vscode-markdown-notebook
ms-
0.0.10

vsonline
ms-
1.0.2823

material-icon-theme
PKi
4.3.0

ruby
reb
0.27.0

vscode-xml
red
0.13.0

vscode-ruby
win
0.27.0

(4 theme extensions excluded)

We should focus the markdown cell which contains the folded cell.

authors: kieferrm rebornix


text:
[INSIDERS] After 2020-10-09 upgrade this error happens when logging in using MS acct: "Writing login information to the keychain failed with error 'Error during CryptAcquireContext.'."

Version: 1.51.0-insider (user setup)
Commit: f5d3ba4d61146b78f0c75c82f3f85232d3409bc1
Date: 2020-10-09T05:34:54.647Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19042
Steps to Reproduce:
1.Star CODE-INSIDERS
2.Login with MS account

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

Thank you, closing as a duplicate of https://github.com/microsoft/vscode/issues/108362

authors: RMacfarlane pmsjt


text:
Crash when removing drive

VSCode Version: 1.51.1
OS Version: macOS 11.0.1

Steps to Reproduce:

Open a file on a removable drive
Remove that drive without ejecting it
Observe a crash

Does this issue occur when all extensions are disabled?: Yes
I have tested this both with extensions disabled and on Insiders, as of 12/9/2020 PT

Maybe https://github.com/microsoft/vscode/issues/88101

Yeah, to see whether this is the same issue can you post a crash dump? @ajs256
See https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues for instructions

Yeah, to see whether this is the same issue can you post a crash dump? @ajs256
See https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues for instructions

Here are the full contents of the reporter directory. I have replaced every plain-text instance of my account name with MyUserName, but it is unmodified apart from that.
crash_report.zip

Here are the full contents of the reporter directory. I have replaced every plain-text instance of my account name with MyUserName, but it is unmodified apart from that.
crash_report.zip

Merging to https://github.com/microsoft/vscode/issues/88101


text:
Web: editor does not show colorization

When I open https://vscode-web-test-playground.azurewebsites.net/?enter=true on my native Apple SI machine, I see no colors in the editor:

Unfortunately I am not seeing any error in devtools. I wonder if this could be a WASM problem in the browser I use (Chrome, Edge).
This could be upstream, but I thought I would report it anyway.

Interestingly the scopes seem to be there though:

Interestingly the scopes seem to be there though:

@bpasero Maybe we can do some screen sharing to investigate. Are there any errors in the console? Are there s with mtk colors in the DOM? Are you using a custom font family?

@bpasero Maybe we can do some screen sharing to investigate. Are there any errors in the console? Are there s with mtk colors in the DOM? Are you using a custom font family?

This is so bizarre, once I switched to stable it started to work again, even in insiders. But I can still reproduce from an incognito session.
No errors in the console as far as I can tell. Settings are all empty due to incoginto.
DOM nodes when it does not work (Python file):

And when it works:

This is so bizarre, once I switched to stable it started to work again, even in insiders. But I can still reproduce from an incognito session.
No errors in the console as far as I can tell. Settings are all empty due to incoginto.
DOM nodes when it does not work (Python file):

And when it works:

cc @aeschli this might be themeing related.
@bpasero How does the minimap look like? So if stable works it means it is not a native Apple SI specific problem? Or can you consistently reproduce on the native Apple SI machine and not on a regular machine? It is possible that the native Apple SI machine has different timing characterstics which might expose a timing bug, but otherwise I would expect for things to always fail or to always work.
Can you repro from sources?

cc @aeschli this might be themeing related.
@bpasero How does the minimap look like? So if stable works it means it is not a native Apple SI specific problem? Or can you consistently reproduce on the native Apple SI machine and not on a regular machine? It is possible that the native Apple SI machine has different timing characterstics which might expose a timing bug, but otherwise I would expect for things to always fail or to always work.
Can you repro from sources?

Oh, I can reproduce on my intel based MBP running Big Sur as well, so it indeed seems Si unrelated.
Here is a screenshot including minimap which is also not colored it seems:

Oh, I can reproduce on my intel based MBP running Big Sur as well, so it indeed seems Si unrelated.
Here is a screenshot including minimap which is also not colored it seems:

Here with this machine I actually reproduce this even after trying out stable once and going back to insiders (stable works fine). This is using Edge.

Here with this machine I actually reproduce this even after trying out stable once and going back to insiders (stable works fine). This is using Edge.

I can reproduce on Windows as well, so this is definitely a logical bug.

I can reproduce on Windows as well, so this is definitely a logical bug.

The root problem is :

This might be caused by the extraction of the extensions from the core.

The root problem is :

This might be caused by the extraction of the extensions from the core.

Yes, it looks like the web bits are missing builtin extensions:

@joaomoreno I once figured out exactly how the extension inlining in the web bit works, so we can talk if you need help.

Yes, it looks like the web bits are missing builtin extensions:

@joaomoreno I once figured out exactly how the extension inlining in the web bit works, so we can talk if you need help.

Yup, that's it, didn't even think about checking the language...

Yup, that's it, didn't even think about checking the language...

Unrelated to this problem, I just saw this on my terminal:
➜  vscode-distro git:(distro) yarn gulp vscode-web
yarn run v1.22.4
$ node --max_old_space_size=8192 ./node_modules/gulp/bin/gulp.js vscode-web
[11:59:27] Using gulpfile ~/Work/vscode-distro/gulpfile.js
[11:59:27] Starting 'vscode-web'...
[11:59:27] Starting clean-out-build ...
[11:59:28] Finished clean-out-build after 677 ms
[11:59:28] Starting compile-build ...
[11:59:31] Starting compilation...
[12:01:56] Finished compilation with 0 errors after 144867 ms
[12:01:56] Finished compile-build after 148144 ms
[12:01:56] Starting clean-web-extensions-build ...
[12:01:56] Finished clean-web-extensions-build after 47 ms
[12:01:56] Starting bundle-web-extensions-build ...
Failed to parse dependency: emmet@https://github.com/rzhao271/emmet.git#1b2df677d8925ef5ea6da9df8845968403979a0a

@rzhao271 You might wanna investigate.

Unrelated to this problem, I just saw this on my terminal:
➜  vscode-distro git:(distro) yarn gulp vscode-web
yarn run v1.22.4
$ node --max_old_space_size=8192 ./node_modules/gulp/bin/gulp.js vscode-web
[11:59:27] Using gulpfile ~/Work/vscode-distro/gulpfile.js
[11:59:27] Starting 'vscode-web'...
[11:59:27] Starting clean-out-build ...
[11:59:28] Finished clean-out-build after 677 ms
[11:59:28] Starting compile-build ...
[11:59:31] Starting compilation...
[12:01:56] Finished compilation with 0 errors after 144867 ms
[12:01:56] Finished compile-build after 148144 ms
[12:01:56] Starting clean-web-extensions-build ...
[12:01:56] Finished clean-web-extensions-build after 47 ms
[12:01:56] Starting bundle-web-extensions-build ...
Failed to parse dependency: emmet@https://github.com/rzhao271/emmet.git#1b2df677d8925ef5ea6da9df8845968403979a0a

@rzhao271 You might wanna investigate.

Related to this, here's the problem:
https://github.com/microsoft/vscode-distro/blob/d577c4b18dab088bb55faf48309f65380684aa61/build/lib/extensions.ts#L240-L242
I wonder if we should instead have an opt out list, instead of an opt in list? Those usually stand the test of time more often than not.

Related to this, here's the problem:
https://github.com/microsoft/vscode-distro/blob/d577c4b18dab088bb55faf48309f65380684aa61/build/lib/extensions.ts#L240-L242
I wonder if we should instead have an opt out list, instead of an opt in list? Those usually stand the test of time more often than not.

@joaomoreno :+1: I agree this is fragile.
It would be even better if we could somehow contain this information in the json directly. Like "forWeb": true directly in the product.json for the ones that should be included.

@joaomoreno :+1: I agree this is fragile.
It would be even better if we could somehow contain this information in the json directly. Like "forWeb": true directly in the product.json for the ones that should be included.

Yeah. Doing an easy fix for now.

Yeah. Doing an easy fix for now.

I even found out that web is recompiling extensions: https://github.com/microsoft/vscode/issues/114530

I even found out that web is recompiling extensions: https://github.com/microsoft/vscode/issues/114530

Fixed by: https://github.com/microsoft/vscode/commit/911a54273ce76db30adc591d9c230cf5ff764aa2

Fixed by: https://github.com/microsoft/vscode/commit/911a54273ce76db30adc591d9c230cf5ff764aa2

authors: alexdima bpasero joaomoreno


text:
TS Server fatal error:  Cannot read property 'indexOf' of undefined

TypeScript Version: 4.1.4
Steps to reproduce crash
1.
2.
3.
TS Server Log
❗Server logging disabled. To help us fix crashes like this, please enable logging by setting:
"typescript.tsserver.log": "verbose"

After enabling this setting, future crash reports will include the server log.
TS Server Error Stack
Server: semantic
TypeError: Cannot read property 'indexOf' of undefined
    at Object.parsePackageName (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:39472:30)
    at ConfiguredProject.Project.enablePlugin (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:151962:24)
    at ConfiguredProject.enablePluginsWithOptions (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:152477:30)
    at ProjectService.loadConfiguredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:154206:25)
    at ProjectService.createAndLoadConfiguredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:154145:22)
    at ProjectService.createLoadAndUpdateConfiguredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:154150:36)
    at ProjectService.assignProjectToOpenedScriptInfo (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:155055:44)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:155395:97
    at Object.flatMap (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:513:25)
    at ProjectService.applyChangesInOpenFiles (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:155395:41)
    at Session.handlers.ts.Map.ts.getEntries._a.<computed> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:156413:46)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:158286:88
    at IOSession.Session.executeWithRequestId (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:158277:28)
    at IOSession.Session.executeCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:158286:33)
    at IOSession.Session.onMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:158310:35)
    at Interface.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:160520:27)
    at Interface.emit (events.js:315:20)
    at Interface._onLine (readline.js:329:10)
    at Interface._normalWrite (readline.js:474:12)
    at Socket.ondata (readline.js:186:10)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:271:9)
    at Socket.Readable.push (_stream_readable.js:212:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:186:23)

/duplicate

authors: ArtemiusL gjsjohnmurray


text:
Dragging our webview section into the Explorer and collapsing the sections above it breaks the proper positioning in the menu

We are currently dealing with an issue that seems to be related to the use of webview. If we drag our section of the plugin into the left menu in Explorer tab and collapse any section above it, the positioning breaks, which causes the content of our section to overflow the rest of the content in the left menu.

Changing the horizontal size of the left menu by dragging it seems to temporarily fix this positioning issue.

VS Code Version: Version: 1.55.1.
OS Version: macOS Big Sur 11.2.3 (20D91).

Steps to Reproduce:

Install the Supernova extension (supernovaio.pulsar-vsc-extension).
Drag CURRENT DEVELOPER SESSION section from Supernova tab anywhere into the Explorer tab.
Collapse any section that is above the CURRENT DEVELOPER SESSION section.
The position gets broken and the section overflows the content in the Explorer tab.
If you change the left menu size by dragging it horizontally, the position fixes itself.

Video:
https://user-images.githubusercontent.com/52071520/114523911-0ece2700-9c45-11eb-9fd0-3bb867684484.mov

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

Duplicate of #110450

authors: jan-supernova mjbvz


text:
Semantic token modifiers do not appear to affect colors

The Go language server uses the semantic tokens feature and applies modifiers to certain semantic tokens, such as strings. The goal is to achieve special colorization for formatting directives and special characters, e.g.:

However, these modifiers do not seem to affect the colorization of the tokens. Setting a specific color for the modifier in the VS Code settings via editor.semanticTokenColorCustomizations did work correctly, however.
From https://github.com/microsoft/language-server-protocol/issues/1281:

Yes, this would have to be filed against VSCode. You want VScode to add a TextMate scope mapping for string.modification.
string.modification is not (yet) an established way to represent placeholders in strings, so I'm not sure we will just add that in VSCode. But extensions can also such TextMate scope mappings: https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide#custom-textmate-scope-mappings (second example)

VS Code version:
1.57.0-insider
286b643ecd231f66f3f2e67e1456f3c601838b46
x64
OS version:
Mac OS Big Sur 11.3.1

I tried to reproduce with the go extension, but did not see any semantic tokens.
@stamblerre What semantic tokens is go emitting?
Also can you comment on this:
string.modification is not (yet) an established way to represent placeholders in strings, so I'm not sure we will just add that in VSCode. But extensions can also such TextMate scope mappings: https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide#custom-textmate-scope-mappings (second example)

The Go extension has semantic tokens disabled by default, since we need to resolve these issues before enabling them. This feature can be enabled through the following setting:
"gopls": {
	"ui.semanticTokens": true
}

Also can you comment on this:
string.modification is not (yet) an established way to represent placeholders in strings, so I'm not sure we will just add that in VSCode. But extensions can also such TextMate scope mappings: https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide#custom-textmate-scope-mappings (second example)

I think the larger issue is that none of the modifiers (modification was just an example I chose) appear to have any effect on string colorization, so we're not exactly sure how to correctly provide semantic tokens to distinguish formatting directives and newlines from other characters. Our thinking was that these are still strings, so we should report the whole string as a string token, but is the expectation that we should use a different token type?
We can try to use the customization, but we were just surprised that modifiers would have no effect in the default theme.

Various issues here:
It realize our Dark+/Light+ themes don't colorize string placeholders with TextMate grammars. The constant.other.placeholder scope that is used by the go grammar and other grammars is not covered by the themes.
I fixed that by updating our default color themes (dark+ and light+): 2fb55257fe92789f0927e9babf9cc3e11834da2e
On semantic highlighting:

You can't expect that all combinations of type/modifiers have a meaning and result in different coloring.. We have a set of default types and modifier combinations for which we have a mapping to TextMate theme (see here and in the end it depends on the actual theme if there's a color defined for that scope.
We don't have a type to represent string placeholders. That's a valid request. We have https://github.com/microsoft/vscode/issues/97063 as issue to collect such requests and when there's multiple requests for a given type, we will add it as a new standard token. I'd suggest to call it stringPlaceholder. In the meantime, your extension can define a custom type and scope mapping.
Strings and string placeholders might not be the typical use case for semantic highlighting . I'd recommend to leave that to the TextMate grammar. The semantic highlighting is something to go on top of syntax highlighting and typically focuses on symbols where a full AST and resolution is needed to evaluate the type of a symbol. E.g. only when resolving an identifier in the file or project it's possible to know if its member, parameter, function and so on.
But of course that depends on the language. For some languages it's very hard to have a good TextMate grammar, so doing more with semantic highlighting makes sense.

Thank you for the detailed explanation. We will try to experiment with customizations for our extension and suggest the stringPlaceholder token type.

Closing the issue then. Please reopen if you find something that needs to be fixed.

authors: aeschli stamblerre


text:
Undo view-only mode (go back without accidentally rewriting history)

Accidentally rewriting history sucks
Super common to cmd+z to find snippet one deleted a few minutes ago because it turns out you need it after all, and then cmd+z forward again. This works OK if you make absolutely sure to not accidentally hit a single unintended key in the process, which would make you unable to go forward again.
I propose you add a modifier key to cmd+z, maybe cmd+alt+z that does throws up a dialog that you must accept before overwriting history. Thanks!

Related: #20889.

authors: hediet man-trackunit


text:
Unable to change default terminal for debug mode

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

VS Code Version: 1.60.0

OS Version:

OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22000 N/A Build 22000
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
System Type:               x64-based PC
BIOS Version:              HP Q83 Ver. 01.16.00, 2021/4/20
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Hotfix(s):                 4 Hotfix(s) Installed.

01: KB5004342
02: KB5004567
03: KB5005642
04: KB5005668

Steps to Reproduce:

"ctrl+` " to open terminal
click "select default profile"

change to command prompt

"F5" to start debug mode

it still uses powershell to run debugging & error occurs

In addition, here is my user settings

I can run my code by "func host start", however, without the help of debug mode, things become a bit inconvenient.
Any suggestion would appreciated.

/duplicate #132150

According to https://github.com/microsoft/vscode/issues/132150#issuecomment-913433116
Issue fixed by downgrading to version 1.59

authors: ILunie frankShih


text:
View menu drop down for "render whitespaces"

View menu for "render whitespaces" only has a checkbox. There are 5 options for whitespace rendering: none, all, boundary, selection, trailing. When users first start VSCode the menu item is checked but it doesn't give any clues as to what is turned on. Personally, I thought it was a bug until I looked further into the settings. Could this be a dropdown menu with the 5 different options or are dropdowns only allowed for specific items?

/needsMoreInfo
You forgot to fill issue template and at least provide VS Code version.
In latest Stable build and Insiders as well it has dropdown.

@ill

/needsMoreInfo
You forgot to fill issue template and at least provide VS Code version.
In latest Stable build and Insiders as well it has dropdown.

Actually, I am not talking about the settings menu but the top menu bar.  That's the part I fend confusing.

authors: IllusionMH rayogunjimi


text:
Redundant requests are made to Marketplace

Steps to Reproduce:

Open VS Code (Empty window)

Use empty extensions directory (better to open on fresh user-data-dir using --user-data-dir arg and fresh extensions dir using --extensions-dir arg)
Open extensions view and hide recommendations view

Install pre-release versions of following extensions

github.vscode-pull-request-github
andreweinand.mock-debug

Open network tab in developer tools and filter for extensionsQuery request
Reload VS Code Window

🐛 It is expected to make only 2 requests to Marketplace but 2 additional requests one per each pre-release version are made.
Same can also be seen in VS Code insiders, but at step 2 - you have to install release versions instead of pre-release versions.

Reopening for recovery


text:
content:"; etiketinin içine tek tırnak atadığımız vakit hatayla karşılşılması

İhtiyaç duyulan veri gönde
Issue Type: Bug
animasyonlu login form yapımında syle.css dosyasının içine
.container form title::before{
content:"; burda görüldüğü üzere content etiketinin içersine tek tırnak atamak istediğim vakit bir hatayla karşılaşıyorum
{
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
AMD 3020e with Radeon Graphics                  (2 x 1198)

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

Load (avg)
undefined

Memory (System)
13.88GB (7.35GB free)

Process Argv
--crash-reporter-id bbdb12b6-aca2-4af2-a65e-f5917424ef00

Screen Reader
no

VM
0%

Extensions (32)

Extension
Author (truncated)
Version

spaces-inside-braces
Air
0.4.0

vscode-intelephense-client
bme
1.8.0

doxdocgen
csc
1.3.2

vscode-html-css
ecm
1.10.2

auto-rename-tag
for
0.1.9

live-coder
Fra
1.0.2

live-html-previewer
hdg
0.3.0

beautify
Hoo
1.5.0

tab-indent-space-align
j-z
0.0.3

better-cpp-syntax
jef
1.15.10

kite
kit
0.147.0

flutter-img-sync
Lih
0.1.4

markdown-insert-images
liu
0.0.2

vscode-language-pack-tr
MS-
1.63.3

remote-containers
ms-
0.209.6

remote-ssh
ms-
0.70.0

remote-ssh-edit
ms-
0.70.0

remote-wsl
ms-
0.63.13

cmake-tools
ms-
1.9.2

cpptools
ms-
1.7.1

cpptools-extension-pack
ms-
1.1.0

vsliveshare
ms-
1.0.5273

vsliveshare-audio
ms-
0.1.91

vsliveshare-pack
ms-
0.4.0

live-server-preview
neg
0.1.4

vscode-php-getters-setters
php
1.2.3

live-sass
rit
3.0.0

LiveServer
rit
5.7.4

tabnine-vscode
Tab
3.5.17

code-to-image
tho
0.0.4

cmake
twx
0.0.17

html-css-class-completion
Zig
1.20.0

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392cf:30425750
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dsc:30424895
pythonvs932:30410667
vscop804cf:30404767
vscop341:30404997
vsrem710cf:30416617
vsbas813:30426126
vsic-wlc-tsjs:30426436

rilemeyecek kadar büyük olduğu için, bu veriyi panonuza kopyaladık. Lütfen yapıştırın.

/duplicate of #141415

authors: emrearagun gjsjohnmurray


text:
Autoindent the code block when closing bracket is added

Assume there are some lines of code which you want to wrap into an if condition
if (condition) {
console.log("hello")
}

You write the if condition with an opening bracket at the top and then add the closing bracket at the bottom.
The latter action should auto-indent the wrapped code.

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

authors: VSCodeTriageBot yaugenka


text:
Menus are harder to hit when updated to v1.68

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

VS Code Version: 1.68.0
OS Version: Windows 7

Steps to Reproduce:

Update VS Code for Windows to 1.68 and use the custom title bar style.
Try and click the menu bar.

Before (Code OSS 1.60):

After (VS Code 1.68):

The topmost pixels are not responsive and can no longer trigger menu clicks.

Duplicate of #150170


text:
Powerlevel10k dotted lines colors are all the same

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

VS Code Version: 1.69.2
OS Version: Windows 11 22H2

Windows Terminal:

VS Code:

Steps to Reproduce:

Have a Powerlevel10k shell
Run p10k configure as in the demo below:

https://user-images.githubusercontent.com/29582865/180217454-e61e4003-7e21-42b0-9db6-a4f7e4ee8336.mp4

This is working fine for me now:

FWIW it looks like the change is meant to be pretty subtle based on what colors they chose.

authors: Tyriar felipecrs


text:
Make the terminal word wrapping a setting, not a toggle/command

This is related to issue #74501 to fix terminal width and word wrapping.
It's great that you've added the command to toggle the word wrapping as  workbench.action.terminal.setFixedDimensions, workbench.action.terminal.toggleWrapping, and Alt+z.
However, every time I open VS Code it gets to default and I have to toggle the wrapping or set the dimension again.
Is there a way to make it into settings? For example, the editor has "editor.wordWrap": "off", but there is no one for the terminal.
Some example might be:
"terminal.integrated.wordWrap": "off",
"terminal.integrated.columDimension": 80, and
"terminal.integrated.rowDimension": 100
Thank you so much

Since it's labeled as "Help Wanted", I take this.

I'm not convinced we should have a setting for this, @babakks please hold off on working on this one for now

@Tyriar I think exposing fixed dimensions as configurable parameters (just to be used as default values when creating new terminal instances) could spare users some repeated interactions.
But for the word-wrap feature, I think @DimesRFT suggests that with having the editor's word-wrap feature in mind. But I think in the terminal context it's different. It's more of a history-based content fitting there. Even the command ID is not, deliberately (I think), workbench.action.terminal.toggleWrapping, but it's workbench.action.terminal.sizeToContentWidth.
That is, if you already had no longer than viewport line in your terminal stream then toggling with Alt+Z would have no effect on neither old nor future lines. So, for a new/fresh terminal instance, it's kind of meaningless to enable it.

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

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

authors: DimesRFT Tyriar VSCodeTriageBot babakks


text:
Hover getting disabled automatically by AWS Tookit

Type: Bug
This is driving me nuts.
From time to time (minutes) the hover option got disabled and I ended by turning it on manually.
I don't know how it's supposed to happen, but even when I set the option on settings.json, it disabled too.
I don't know if my extensions are making this behavior or something related to setting sync. But I disabled all unnecessary extensions and even turned setting sync off and the problem persists.
I expect to keep the setting that I choose (always on) and don't disable it automatically.
VS Code version: Code 1.73.1 (6261075646f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No
Remote OS version: Linux x64 5.10.102.1-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (16 x 2904)

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)
23.87GB (8.04GB free)

Process Argv
--crash-reporter-id 442e3911-4623-4ebe-9313-10b256932ade

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 5.10.102.1-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (16 x 2903)

Memory (System)
11.62GB (7.92GB free)

VM
0%

Extensions (39)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

html-snippets
abu
0.2.1

Bookmarks
ale
13.3.1

vscode-browser-preview
auc
0.7.2

codesandbox-projects
Cod
0.2.55

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

remotehub
Git
0.46.0

vscode-graphql-syntax
Gra
1.0.4

vscode-drawio
hed
1.6.4

raml
jep
1.0.1

dotenv
mik
1.0.1

remote-ssh
ms-
0.90.1

remote-ssh-edit
ms-
0.84.0

remote-wsl
ms-
0.72.0

remote-repositories
ms-
0.24.0

material-icon-theme
PKi
4.22.0

rewrap
stk
1.16.3

vscode-icons
vsc
12.0.1

ReactSnippets
xab
2.4.0

vscode-openapi
42C
4.15.9

aws-toolkit-vscode
ama
1.53.0

ng-template
Ang
14.2.0

vscode-tailwindcss
bra
0.9.1

vscode-eslint
dba
2.2.6

gitlens
eam
13.0.4

prettier-vscode
esb
9.9.0

copilot
Git
1.58.7236

todo-tree
Gru
0.0.220

openapi-lint
mer
1.2.0

indent-rainbow
ode
8.3.1

vscode-versionlens
pfl
1.0.10

prisma
Pri
4.6.0

vscode-yaml
red
1.10.1

LiveServer
rit
5.7.9

code-spell-checker
str
2.11.0

code-spell-checker-portuguese-brazilian
str
2.0.9

quokka-vscode
Wal
1.0.509

wallaby-vscode
Wal
1.0.348

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
fc301958:30595537
282f8724:30602487
gswce2:30605431
3d0df643:30604793
dbltrim-noruby:30604474

Exactly which value in your settings.json file is getting changed by something?

Exactly this one: "editor.hover.enabled": true
From time to time even this turned false automatically

I'm facing the same problem. Even asked the same on stackoverflow. Any progress in debugging/resolving the issue?

I don't think there is any code in our source tree which would update editor.hover.enabled specifically in user settings. I am using settings sync and never witnessed settings changing without my doing so, therefore my best guess is that this is caused by one of your installed extensions.
All extensions execute together on a single nodejs process, so in order to narrow down the possible problematic extension, please try the following:

run F1 > Help: Start Extension Bisect
(this will restart VS Code with half of your extensions disabled)
try to do the steps which reproduce the problem
if the problem reproduces, click "This is bad" (this narrows down the problematic extension to the half which was enabled)
if the problem does not reproduce, click "Good now" (this narrows down the problematic extension to the half which was disabled)
these steps will repeat until the problematic extension is found

initial
step
final

@sandy081 Maybe you know, is there some log that could be enabled to see if our configuration service flips a setting and the reason it would do so?

I don't think there is any code in our source tree which would update editor.hover.enabled specifically in user settings. I am using settings sync and never witnessed settings changing without my doing so, therefore my best guess is that this is caused by one of your installed extensions.
All extensions execute together on a single nodejs process, so in order to narrow down the possible problematic extension, please try the following:
* run `F1 > Help: Start Extension Bisect`

* (this will restart VS Code with half of your extensions disabled)

* try to do the steps which reproduce the problem

* if the problem reproduces, click "This is bad" (this narrows down the problematic extension to the half which was enabled)

* if the problem does not reproduce, click "Good now" (this narrows down the problematic extension to the half which was disabled)

* these steps will repeat until the problematic extension is found

initial 	step 	final

Since it's an intermittent issue, it's very difficult to debug it using this method. I can't afford to let extensions get disabled randomly since it would block my development

Doing a code search, this appears to be AWS Tookit. Can everyone else confirm that they also have this extension?

@alexdima Thanks for suggesting the way to rootcause the problem. I could see hover.enabled in many extensions, but AWS Toolkit was definitely one of them. The code pointer you shared is very valuable. Let me cut a ticket for them

https://github.com/aws/aws-toolkit-vscode/issues/3014
They have acknowledge the issue and working it

So strange this is the root cause of the Editor › Hover: Enabled being toggled off. I thought I was just going crazy... Thank you for looking into this and looking forward to a fix! 🙌

Sharing an update on this AWS Toolkit issue (see also https://github.com/aws/aws-toolkit-vscode/issues/3014 ):
AWS Toolkit provides suggestions from CodeWhisperer. To do so, we implement vscode.InlineCompletionItemProvider. We also override "editor.action.inlinesuggest.shownext"  and related commands when CodeWhisperer is providing suggestions so that the inline suggestion popup Next and Previous buttons provide CodeWhisperer suggestions.
@alexdima @hediet is there a better way for vscode extensions to provide inline suggestions without conflicting with other inline suggestions extensions?
Note also that a key problem is that GitHub Copilot overrides the hover popup even when it is not providing suggestions. In this screenshot, CodeWhisperer is providing suggestions but GitHub Copilot adds a button to the inline suggestions hover:

As a short-term solution, we've removed the workaround in AWS Toolkit v1.59 (not released yet) that temporarily disabled the hover popup. But now if user mouse-hovers, they see the Open GitHub Copilot button above (while CodeWhisperer is providing suggestions), which is very confusing.

@justinmk3 can you file a new feature request for this, describing the problem and potential solutions?

can you file a new feature request for this, describing the problem and potential solutions?

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

authors: BrianHHough KTibow alexdima aproli90 brunochirelli gjsjohnmurray hediet justinmk3


text:
Extension installation fails to verify signature on REMOTE release

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

VS Code Version: 1.75.0
OS Version: CentOS Version 7

Steps to Reproduce:

Open up new VScode remote session.
Try to update any extension.

Tagging maintainer per request: @dtivel
Important note: Using identical corporate proxy settings for both environments, which worked before latest VScode update 1.75.
Windows 11 Host (extensions install fine):

Linux Remote SSH Session (extensions not installing, note the python extension):

Facing same issue

Hello! We are seeing a few people facing this issue. The error message is Signature Untrusted. We will keep this issue as the main issue to track the progress here.
Currently, the workaround seems to be to downgrading vscode. As seen from user @inh3 Same issue. Downgraded VSCode to 1.74.3 to restore functionality. in https://github.com/microsoft/vscode/issues/173215.
The issue is also reported on the remote-release extension here: https://github.com/microsoft/vscode/issues/173215

Does the file at /etc/pki/ca-trust/extracted/pem/objsign-ca-bundle.pem contain certificates?

Does the file at /etc/pki/ca-trust/extracted/pem/objsign-ca-bundle.pem contain certificates?

Yes:

Does the file at /etc/pki/ca-trust/extracted/pem/objsign-ca-bundle.pem contain certificates?

Yes, it appears to have my organizations certificate in it based on the comment.

It probably does not have this root certificate.  Can you confirm?
-----BEGIN CERTIFICATE-----
MIIFkDCCA3igAwIBAgIQBZsbV56OITLiOQe9p3d1XDANBgkqhkiG9w0BAQwFADBi
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3
d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2VydCBUcnVzdGVkIFJvb3Qg
RzQwHhcNMTMwODAxMTIwMDAwWhcNMzgwMTE1MTIwMDAwWjBiMQswCQYDVQQGEwJV
UzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQu
Y29tMSEwHwYDVQQDExhEaWdpQ2VydCBUcnVzdGVkIFJvb3QgRzQwggIiMA0GCSqG
SIb3DQEBAQUAA4ICDwAwggIKAoICAQC/5pBzaN675F1KPDAiMGkz7MKnJS7JIT3y
ithZwuEppz1Yq3aaza57G4QNxDAf8xukOBbrVsaXbR2rsnnyyhHS5F/WBTxSD1If
xp4VpX6+n6lXFllVcq9ok3DCsrp1mWpzMpTREEQQLt+C8weE5nQ7bXHiLQwb7iDV
ySAdYyktzuxeTsiT+CFhmzTrBcZe7FsavOvJz82sNEBfsXpm7nfISKhmV1efVFiO
DCu3T6cw2Vbuyntd463JT17lNecxy9qTXtyOj4DatpGYQJB5w3jHtrHEtWoYOAMQ
jdjUN6QuBX2I9YI+EJFwq1WCQTLX2wRzKm6RAXwhTNS8rhsDdV14Ztk6MUSaM0C/
CNdaSaTC5qmgZ92kJ7yhTzm1EVgX9yRcRo9k98FpiHaYdj1ZXUJ2h4mXaXpI8OCi
EhtmmnTK3kse5w5jrubU75KSOp493ADkRSWJtppEGSt+wJS00mFt6zPZxd9LBADM
fRyVw4/3IbKyEbe7f/LVjHAsQWCqsWMYRJUadmJ+9oCw++hkpjPRiQfhvbfmQ6QY
uKZ3AeEPlAwhHbJUKSWJbOUOUlFHdL4mrLZBdd56rF+NP8m800ERElvlEFDrMcXK
chYiCd98THU/Y+whX8QgUWtvsauGi0/C1kVfnSD8oR7FwI+isX4KJpn15GkvmB0t
9dmpsh3lGwIDAQABo0IwQDAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB/wQEAwIB
hjAdBgNVHQ4EFgQU7NfjgtJxXWRM3y5nP+e6mK4cD08wDQYJKoZIhvcNAQEMBQAD
ggIBALth2X2pbL4XxJEbw6GiAI3jZGgPVs93rnD5/ZpKmbnJeFwMDF/k5hQpVgs2
SV1EY+CtnJYYZhsjDT156W1r1lT40jzBQ0CuHVD1UvyQO7uYmWlrx8GnqGikJ9yd
+SeuMIW59mdNOj6PWTkiU0TryF0Dyu1Qen1iIQqAyHNm0aAFYF/opbSnr6j3bTWc
fFqK1qI4mfN4i/RN0iAL3gTujJtHgXINwBQy7zBZLq7gcfJW5GqXb5JQbZaNaHqa
sjYUegbyJLkJEVDXCLG4iXqEI2FCKeWjzaIgQdfRnGTZ6iahixTXTBmyUEFxPT9N
cCOGDErcgdLMMpSEDQgJlxxPwO5rIHQw0uA5NBCFIRUBCOhVMt5xSdkoF1BN5r5N
0XWs0Mr7QbhDparTwwVETyw2m+L64kW4I1NsBm9nVX9GtUw/bihaeSbSpKhil9Ie
4u1Ki7wb/UdKDd9nZn6yW0HQO+T0O/QEY+nvwlQAUaCKKsnOeMzV6ocEGLPOr0mI
r/OSmbaz5mEP0oUA51Aa5BuVnRmhuZyxm7EAHu/QD09CbMkKvO5D+jpxpchNJqU1
/YldvIViHTLSoCtU7ZpXwdv6EM8Zt4tKG48BtieVU+i2iW1bvGjUI+iLUaJW+fCm
gKDWHrO8Dw9TdSmq6hN35N6MgSGtBxBHEa2HPQfRdbzP82Z+
-----END CERTIFICATE-----

It looks like it does not have that one:

The code signing certificate that VS Marketplace uses to repository sign extensions chains to this root, so trusting this root will resolve the Untrusted error you're seeing.
To verify extensions signed with this certificate, VS Code requires a certificate trust store that is valid for code signing.
Linux doesn't reliably have this, so VS Code defaults to using its own built-in trust store.  This built-in trust store is effectively a snapshot of the Windows trust store that is valid for code signing and contains this root certificate.
For the Linux distributions (like Red Hat and CentOS) that do have this established system (root-owned) code signing trust store, we want to respect it.  The intent here is to reuse a system-managed trust store if we can.
/etc/pki/ca-trust/extracted/pem/objsign-ca-bundle.pem
I see a few options:

Add the root certificate to your PEM file.  This is a system-wide change, so you should be comfortable with the change.
Set the extensions.verifySignature option to false in the right setting file (remote, in your case).  This should be considered a short-term workaround, and the option may disappear in the future.
Downgrade to 1.74.3.

For now, I'd choose the 2nd option.
CC @isidorn

@dtivel, thank you for looking into this!  Yeah I don't think my organization would let us tamper with the system root certificate.
I can go with option 2 for now, but if that option disappears in the future, I'm not sure what options we will have down the road.

Set the extensions.verifySignature option to false in the right setting file (remote, in your case).  This should be considered a short-term workaround, and the option may disappear in the future.

Do I have to do anything to enable it?  It does not look like VScode is recognizing it as a "real" setting:

It looks correct.  Make sure you put it in your remote settings if you're having problems on the remote side.  You can leave local settings as-is (enabled).

@dtivel
Thanks for jumping on to this and inspecting the issue.
Immediate Workaround
Disable signing verification manually

Open Settings UI
Go to Remote Settings Tab
Open the Settings file by clicking on the button available on the top right corner
Add this setting "extensions.verifySignature": false

Recovery

Disable signing automatically for the platforms where this can happen

Long term

Come up with a solution where we can verify signing successfully in these cases

This doesn't seem to work here:
❯ cat .vscode-server/data/Machine/settings.json
{
    "extensions.verifySignature": false
}

Also, a better option would be to be able to force VS Code to use its internal certificate store.

@sandy081

That's not a valid setting
It doesn't work

Downloading vscode 1.74.3 can suppress this issue.

Potentially helpful workaround for anyone experiencing the same problem --
Downloading the VSIX of the extension you want to install (say, from their repository), copying over to the remote, and then using the
Extensions: Install from VSIX... command from the command palette to install it seems to work :)
Definitely not a fix to the actual problem, but seems like a reasonably easy way to get extensions onto a remote without having to downgrade.

@zulrang , worked for me after killing a server process on a target machine.
Reload Windows, close/open VS Code did not help. Only after a "power cycling" a VS Code process server worked.

@zulrang Setting should work even without restart / reload. Where are you applying this setting ? I mean in which file?

@sandy081 there's simply no such setting as "extensions.verifySignature".
BTW, I reverted to 1.74.3 but then it turned out ALL MY REMOTE EXTENSIONS WERE GONE. What the... is happening?

@tomba4 Yes, it is not a registered setting. You have to open the file and add this. May I know if you have done what is mentioned in this comment

@sandy081 the screenshot in that comment was explicitly showing the GUI version of the settings, and there the option is not available. I haven't tried it then.

@tomba4  Ok, I will update the comment and screenshot - mentioning to add the setting in the file. Can you please set this setting and let me know if it works.

@sandy081 I managed to restore my environment from backups on 1.74.3, so it's working again for me. But 1.75 itself is completely broken as it seems...

@tomba4 Is it ok, if you can please upgrade to 1.75 using following steps:

Update the remote settings to use extensions.verifySignature and set it to false
Upgrade to 1.75
Try to install extensions and make sure it works

@zulrang Setting should work even without restart / reload. Where are you applying this setting ? I mean in which file?

It doesn't seem to work like that, looks a process on the server side is not picking it up. It worked for me after half an hour or so. I didn't manually kill/restart anything on the server side.

Facing the same problem here on the remote server. I found it first with my home laptop and again with my working PC once I updated VSCode on the PC to 1.75.0.
Tried the 2nd fix with extensions.verifySignature. It only works after I killed the current Code server with Remote-SSH: Kill Current VS Code Server

Facing the same problem here on the remote server. I found it first with my home laptop and again with my working PC once I updated VSCode on the PC to 1.75.0. Tried the 2nd fix with extensions.verifySignature. It only works after I killed the current Code server with Remote-SSH: Kill Current VS Code Server

Proofed, and works will. thanks for the information.
If Already Upgrade to 1.75

Update the remote settings to use extensions.verifySignature and set it to false
Killed the current Code server with Remote-SSH: Kill Current VS Code Server
(Disconnected from Remote)
Restart host VS Code
Try to install extensions and make sure it works
Done

@shaoqx Facing the same problem here on the remote server. I found it first with my home laptop and again with my working PC once I updated VSCode on the PC to 1.75.0. Tried the 2nd fix with extensions.verifySignature. It only works after I killed the current Code server with Remote-SSH: Kill Current VS Code Server

Proofed, and works well. thanks for the information.
If Already Upgrade to 1.75

Update the remote settings to use extensions.verifySignature and set it to false
Killed the current Code server with Remote-SSH: Kill Current VS Code Server
(Disconnected from Remote)
Restart host VS Code
Try to install extensions and make sure it works
Done
work for me!

@dtivel @sandy081 and me discussed this and we decided on the following: for Linux distributions (like Red Hat and CentOS) that do have this established system (root-owned) code signing trust store, we will still give priority to the trust store that is shipped with VS Code. This way we can be 100% sure that the trust store we use is valid for code signing.
This fix will be included in the next Stable release that we plan to do on Wednesday or Thursday.
In our February milestone we plan to introduce a setting, for example "extensions.signatureTrustStore" "product" | "system" (default is "product") that will allow users to control what trust store should VS Code use. In the future when VS Code introduces more settings to be admin controlled, this can be the mechanism for system admins to control what trust store is to be used.
After you get this stable update I would kindly ask all of you to remove the extensions.verifySignature: false from your settings, because we want signature verification to not be disabled and to hear if there are any other issues that we might have not fixed. Thank you very much!

Closing this issue as I have verified that our fix indeed fixes the problem on CentOS.
However it would be great if someone from the community also tries out and confirms to us that the issue is indeed fixed (make sure to remove extensions.verifySignature: false from your settings).
Here's the link to the Linux x64 build https://az764295.vo.msecnd.net/stable/dd1dbfeecbd06802a4a357767fedeb5a6268cf71/code-stable-x64-1675778107.tar.gz
Thank you

@isidorn I am using vscode on macOS and connecting to remote centOS, and I also suffered from this issue. Will there be a new macOS vscode release to fix the issue?

@ByronHsu  Yes, it fixes your scenario too.

I am connecting from MacOS to Linux host but none of the above fixes worked for me. I tried everything in xiaoshude's comment which summarizes all the fixes in this thread so far but I still get an "Untrusted" error (I used the Docker extension as the example in the blow screenshot)

@grandmasteri Can you please share following logs while the issue happens?

F1 > Open View... > Remote Server
F1 > Open View... > Window

@grandmasteri
for mac2centos, in additional to the workaround, following may help.

restart remote server.
directly connect to remote server, instead of the project,

FWIW this also happens in the Dev-Containers extension workflow. I can't install any extensions in the container and if I update the settings file, since it doesnt get picked up I have to rebuild the container, which ultimately wipes out the settings.json all over again

I now see the same on Windows... disabled verify signature, updated everything, including VSCode (apparently had tons of not installed updates for extensions). But as soon as I enable it back, extension installation are no longer works with exact same error

@Rhahkeem @gusarov does the issue have similar symptoms to https://github.com/microsoft/vscode-remote-release/issues/8169 ?

authors: ByronHsu LsYueh Rhahkeem bluebandit21 cuzox darionesi dtivel eleanorjboyd grandmasteri gusarov isidorn ismail jlynchMicron maciejmatczak sandy081 shaoqx tomba4 xcmz xiaoshude zulrang


text:
Raw search gives me a search result I want while rich search does not

Testing #174724
Possibly related to #174966
Raw search has results from the output of a cell:

Rich search does not (I expected two "hello 2"s):

Find widget doesn't have this result:

Rich doesn't support outputs yet, it'll be added in the second part of https://github.com/microsoft/vscode/issues/164926

authors: TylerLeonhardt andreamah


text:
Improve network requests logging

Currently we are logging network requests with basic information. Given that shared process is being made utility process, we will loose the ability to see network requests by opening the shared process window in network tab or console tab. To compensate this, we shall improve our network requests logging to make it as similar to dev tools.

/duplicate

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


text:
Appearence - centered

Type: Bug
With latest update:
View > Appearence > Centered Layout
No code is visible. Turn off centered layout, code reappears.
VS Code version: Code 1.76.0 (Universal) (92da9481c0904c6adfe372c12da3b7748d74bdcb, 2023-03-01T10:23:45.993Z)
OS version: Darwin x64 22.3.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)

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

Load (avg)
3, 5, 4

Memory (System)
16.00GB (0.03GB free)

Process Argv
--crash-reporter-id 7f212924-c5e8-4f60-b633-c93bd7f0ac28

Screen Reader
yes

VM
0%

Extensions (82)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

codesnap
adp
1.3.4

TabOut
alb
0.2.2

Bookmarks
ale
13.3.1

swagger-viewer
Arj
3.1.2

vscode-icontheme-nomo-dark
be5
1.3.6

markdown-preview-github-styles
bie
1.0.1

blackbox
Bla
0.10.34

npm-intellisense
chr
1.4.4

path-intellisense
chr
2.8.4

regex
chr
0.4.0

codesandbox-projects
Cod
0.2.71

vscode-eslint
dba
2.4.0

denigma
den
0.0.15

gitlens
eam
13.3.1

vscode-html-css
ecm
1.13.1

vsc-material-theme
Equ
33.6.0

vsc-material-theme-icons
equ
2.6.1

prettier-vscode
esb
9.10.4

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

remotehub
Git
0.52.0

todo-tree
Gru
0.0.224

terraform
has
2.25.4

vscode-drawio
hed
1.6.6

vscode-auto-open-markdown-preview
hnw
0.0.4

vscode-codemetrics
kis
1.26.1

auto-insert-comma
Leo
0.0.4

json-to-ts
Mar
1.7.5

markdown-shortcuts
mdi
0.12.0

template-string-converter
meg
0.6.0

git-graph
mhu
1.30.0

dotenv
mik
1.0.1

document
min
2.2.1

vscode-scss
mrm
0.10.0

vscode-edge-devtools
ms-
2.1.1

isort
ms-
2022.8.0

python
ms-
2023.4.0

vscode-pylance
ms-
2023.2.40

jupyter
ms-
2023.2.1000592019

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-ssh
ms-
0.96.0

remote-ssh-edit
ms-
0.84.0

azure-repos
ms-
0.28.0

remote-explorer
ms-
0.2.0

remote-repositories
ms-
0.30.0

vscode-react-native
msj
1.10.0

color-highlight
nau
2.5.0

indent-rainbow
ode
8.3.1

material-icon-theme
PKi
4.24.0

material-product-icons
PKi
1.5.0

vscode-react-refactor
pla
1.1.3

vscode-css-peek
pra
4.2.0

vscode-yaml
red
1.11.0

LiveServer
rit
5.7.9

synthwave-vscode
Rob
0.1.15

color-manager
roy
0.7.5

svg-preview
Sim
2.8.3

music-time
sof
2.2.43

autoimport
ste
1.5.4

code-spell-checker
str
2.18.0

tabnine-vscode
Tab
3.6.41

sapling
tea
1.2.0

open-in-browser
tec
2.0.0

dotenv-intellisense
tem
0.0.4

pdf
tom
1.2.2

highlight-matching-tag
vin
0.10.1

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

codetour
vsl
0.0.58

quokka-vscode
Wal
1.0.527

footsteps
Wat
0.2.0

fig
wit
0.0.7

vscode-import-cost
wix
3.3.0

codesandbox
yes
0.0.8

markdown-all-in-one
yzh
3.5.0

json
Zai
2.0.2

material-theme
zhu
3.15.6

html-css-class-completion
Zig
1.20.0

(17 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
vsccc:30610678
pyindex848:30662994
nodejswelcome1:30587005
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
a9j8j154:30646983
pythonb192:30669360

duplicate #175795

authors: sbatten superchrisho