text:
Typescript services

Issue Type: Bug
Go to definition and typescript not working
VS Code version: Code - Insiders 1.65.0-insider (86200d542474b26aa28034e0fd5789c45c747d8b, 2022-02-17T07:18:54.447Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.84GB (2.52GB free)

Process Argv
--crash-reporter-id 67531790-25d3-412e-ad3e-9c332f3f778f

Screen Reader
no

VM
29%

Extensions (29)

Extension
Author (truncated)
Version

to
ami
0.0.10

vscode-intelephense-client
bme
1.8.1

path-intellisense
chr
2.8.0

vscode-svgviewer
css
2.0.0

docs-yaml
doc
0.2.7

githistory
don
0.6.19

es7-react-js-snippets
dsz
4.4.0

gitlens
eam
11.7.0

vscode-great-icons
emm
2.1.82

prettier-vscode
esb
9.2.0

copilot
Git
1.7.5067

json2ts
Gre
0.0.6

todo-tree
Gru
0.0.215

selected-lines-count
gur
1.4.0

javascript-snippets
jab
4.0.1

batch-rename-extension
Jan
0.0.4

vscode-peacock
joh
4.0.0

sftp
lix
1.12.10

debugger-for-edge
msj
1.0.15

vscode-graphql
ors
0.3.18

material-icon-theme
PKi
4.13.0

vscode-react-refactor
pla
1.1.3

vscode-yaml
red
1.4.0

vscode-fileutils
sle
3.5.0

laravel-goto-controller
ste
0.0.15

code-spell-checker
str
2.1.7

quokka-vscode
Wal
1.0.448

php-debug
xde
1.24.0

vscode-surround
yat
1.2.2

(3 theme extensions excluded)

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
pythonvspyt200:30323110
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
testflightcf:30433671
pythonvs932:30404738
wslgetstarted:30421357
vsclayoutctrt:30405800
vscop841:30438915
dsvsc009:30436273
pythonvspyt640:30438691
vsbas813:30436447
vscscmwlcmt:30428973
azactmsal:30432848
vscgsvid2:30433758
dockersurvey3:30438168

/needsMoreInfo
Do you see any errors?
Is it reproducible with all extensions disabled?
You can try this with F1 and >Developer: Reload Window With Extensions Disabled
Is it reproducible in stable version? Also more info about workspace and project config will be helpful or shared repo if it's public.

Are you using built-in TS version or workspace one?
This might mean that 4.6 RC has some issue that might reach next stable.
Please follow steps described in https://github.com/microsoft/vscode/issues/143140#issuecomment-1040904820 and this will help to provide info required to resolve problem.
Please pay attention at the end of the comment about paths etc.

authors: IllusionMH rogerms


text:
Allow double click on tab to return layout to original

Issue Type: Bug
If you have a split screen you can vary the width of the split.
One behaviour was that you could double click a tab and it would occupy most of the window and then double click again to return it to its previous size and layout.
The second double click now resets the layout of all splits to some sort of middle.
It used to be very useful if you had many files but only generally wanted to be able to see a little bit of them in reference (like the bootstrap css breakpoints) but then occasionally enlarge that file to look at other parts of it.
Or just flick between file tabs and keep them large. This is very useful on screens smaller than enormous.
I have removed all extensions and it appears to be the same without extensions.
VS Code version: Code 1.64.2 (Universal) (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:00:58.347Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (8 x 2800)

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)
2, 2, 3

Memory (System)
16.00GB (0.08GB free)

Process Argv
--crash-reporter-id a910920d-1205-4d5b-bb90-06a303804f97

Screen Reader
no

VM
0%

/gifPlease

Ok thanks. Will sort that later today.
Best regards
Matt Holmes
Director
Origin London Ltd
@.***
UK: 07500847210
Int: +447500847210
Companies House Number: 7302875
VAT Registration Number: GB231798196
Registered Office: 52 Llanover Road, London. SE18 3SU

From: Benjamin Pasero @.***>
Sent: Thursday, 3 March 2022, 11:44
To: microsoft/vscode
Cc: originlondon; Author
Subject: Re: [microsoft/vscode] Double click on tab no longer returns layout to original (Issue #144311)
/gifPlease
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/144311#issuecomment-1057960727, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y25OQI25IIB4HEAARYOLU6CQY7ANCNFSM5P2AIEBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks

I was asked to explain further with a screencast.
I have uploaded an mp4 and tried to embed a gif as requested, but couldn't as the mp4 converted to a gif was too large. It seems to display inline with mp4 though anyway.
https://user-images.githubusercontent.com/33525109/157091189-ef01fec6-1e59-4e57-bf98-de38377631d7.mp4

@originlondon I see but you indicate this has changed recently? I do not think so. Can you clarify?

I believe it was working as described in October last year. I couls be mistaken, as I took a break from coding for a few months.
My larger screen broke so I had to use an older smaller one. I also remember discovering that feature when using just a left-right split. So I discovered the feature around July/August last year, perhaps.
But I am pretty sure that it used to work like that as I used to keep four or five core scss variable definition files at the bottom of my left panel, each with just a few key lines showing and then expand and contract them as necessary, if needed to see the rest of the file, rather than search through them via the dropdown, or flick along the tabs or choose them in the open tabs browser in the panel.
Apologies for any typos, I was finding this difficult to write as Microsoft Outlook on Android mobile was not doing 'cut' functionality, only copy, paste and delete - weird. Lol. (not going to report that just yet - could be an Android thing after an update last night and its indicating another one due, which could correct that).
Thanks.

Best regards
Matt Holmes
Director
Origin London Ltd
@.***
UK: 07500847210
Int: +447500847210
Companies House Number: 7302875
VAT Registration Number: GB231798196
Registered Office: 52 Llanover Road, London. SE18 3SU

From: Benjamin Pasero @.>
Sent: Tuesday, March 8, 2022 6:28:33 AM
To: microsoft/vscode @.>
Cc: originlondon @.>; Mention @.>
Subject: Re: [microsoft/vscode] Double click on tab no longer returns layout to original (Issue #144311)
@originlondonhttps://github.com/originlondon I see but you indicate this has changed recently? I do not think so. Can you clarify?
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/144311#issuecomment-1061453056, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y25IF4XMFT5SWPADNSLLU63XRDANCNFSM5P2AIEBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

I think this is working for a long time like that, but treating as feature request.
//cc @joaomoreno @sbatten since this is grid related.

Ok thank you!
Best regards
Matt Holmes
Director
Origin London Ltd
@.***
UK: 07500847210
Int: +447500847210
Companies House Number: 7302875
VAT Registration Number: GB231798196
Registered Office: 52 Llanover Road, London. SE18 3SU

From: VS Code Issue Triage Bot @.>
Sent: Tuesday, March 8, 2022 8:13:49 AM
To: microsoft/vscode @.>
Cc: originlondon @.>; Mention @.>
Subject: Re: [microsoft/vscode] Allow double click on tab to return layout to original (Issue #144311)
This feature request is now a candidate for our backlog. The community has 60 days to upvotehttps://github.com/microsoft/vscode/wiki/Issues-Triaging#up-voting-a-feature-request 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 documentationhttps://aka.ms/vscode-issue-lifecycle.
Happy Coding!
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/144311#issuecomment-1061515320, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y25O3OKQDCYCP4LNIC4DU64D33ANCNFSM5P2AIEBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

: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!

source: gharchive/issue

authors: VSCodeTriageBot bpasero originlondon

repo: microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
Allow users to override an extension's Activation Event in settings.json

Pretty much all in the title. A lot of extensions don't seem to care about choosing the most optimal Activation Event, or some extensions are simply having a hard time not to lag while running on a remote server, while they work just fine locally... It would be great if users could easily override it in settings.json if they desire, without needing to fork the whole extension and edit it on their own. Would it be possible somehow?

I'm wondering what are some extensions that currently have this issue?

Hi again, sorry i had to take a job break for health reasons.
@rzhao271 It would rather be for test purposes. Most extension are super fast on a regular network, but for some reason on a job network with picky firewall some will get really slow. Being able to test different Activation Event on our own could allow developers to suggest improvement to some extensions that would not be a problem for most users; and in the case the number of users it would benefit would be too low to be worth adressing, the user could try dealing with the issue on their own without needing to fork extensions.
I'm not on my job network right now and might not be for some time. I would have been pleased to provide you examples of Extensions giving me problems (there aren't that many anyway), but i can't right now. Also after a lot of testing trying to figure out a solution, i noticed that some slow-to-start extensions aren't problematic on their own, but starts to be when combined with other Extensions, most notably Python. Considering similar issues i've read online, it seems to be a problem with C++ extension too; i guess it might have something to do with compilers/debuggers, but that's just a guess i couldn't really tell.
It seemed to me it wouldn't necessarily be very complicated to implement, and might be a good idea in this context. I could be wrong. I'm aware users could end up shooting their own foot by tweaking such setting. I would be pleased to get more info about the feasibility of such feature, the possibility it could lead to security issues, or any problem related to it. I guess there are some since there was a downvote on my issue, but no further information was given by the disliking dev.

Could you reopen the issue?

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!

: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!


text:
Synchronous launch compounds

Launch compounds in workspaces launch asynchronously. While this saves launch time, we found a couple of issues with this:

Following quick pick menu / input box will cancel the previous one. If two launch task both have such requirements, then one of them ends up to be cancelled.
One launch may depend on another.

Although launching them one at a time is a workaround, it requires a lot of mouse clicks, and is error-prone if there are a lot of launch configs in a project.
So a synchronous launch compounds feature might be a great addition. Feel free to provide other workarounds though.

The first issue is https://github.com/microsoft/vscode/issues/141514
The second, I'm not sure we can do anything about it. How can we know when one config is "done launching" so that a dependent config can be started? Is it ready when we have attached to the debuggee and initialized the session?
Can you give an example of when you have a launch config that depends on another.

The second issue is a suspicion since our project is still in its early state. A possible usage is one project starts a service, and the second, like a test or some user space app, uses this service.
Is returning from startDebugging(), which is in vs code api but there should be something equivalent internally, not enough to decide a launch action is completed?

not enough to decide a launch action is completed

Maybe - the second project depends on "something" from the first project, and there is no way to know generically when the first project is in the right state that the second needs.
But I think if we tried to address this we would want to change the launch.json format to let us declare dependencies for a launch config. Curious whether you ever considered this @isidorn @weinand

We have our own debug adapter, so we can work around this by adding a new launch config request type, which is only allowed in workspace, and in which force launch configs to start one by one. And the only criteria we are using to decide if the previous launch finishes is returning form await startDebugging():
for (const launchConfig of config.launchConfigurations) {
    const folderIndex = launchConfig.folderIndex;
    if (!isNumber(folderIndex) || folderIndex >= vscode.workspace.workspaceFolders.length || folderIndex < 0) {
        // Print error
        return;
    }
    await vscode.debug.startDebugging(vscode.workspace.workspaceFolders[folderIndex], launchConfig.launchConfigurationName);
}

And the reason I open this feature request is because, if VS Code has this built in, then I don't need to add a different request type for this.

@roblourens we do not want to duplicate shell functionality in launch configs. If more control over process execution is needed, we recommend to use a shell script.

@roblourens we do not want to duplicate shell functionality in launch configs. If more control over process execution is needed, we recommend to use a shell script.

Is it possible to start debugging in VS Code via shell script?

You approach is a good one @xisui-MSFT, it works for you but might not work in every situation, and I would not build it into vscode.
You can also start your app in a shell script in debug mode, and write an "attach" config. Or if this is javascript, you can run a shell script in a "javascript debug terminal".

authors: roblourens weinand xisui-MSFT


text:
MODULE PROBLEM

I downloaded a module named pygame, but it said there is no module named pygame when I say 'import pygame'.

/question

authors: AreejElshrief gjsjohnmurray


text:
Node debugger not working in WSL

Node debugger in WSL is not working. Node is installed in WSL but the debugger does not stop when adding breakpoints. All I am doing is creating a simple nodejs (v14.18) application, created the launch.json file and run the debugger.
I have the following launch configuration.
{     "version": "0.2.0",     "configurations": [         {             "type": "node",             "request": "launch",             "name": "Launch Program",             "skipFiles": [                 "<node_internals>/**"             ],             "program": "${workspaceFolder}/src/app.js"         }     ] }

/jsDebugLogs

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

Sent the trace file via email.

Hmm, can you set "console":"internalTerminal" in your launch.json, and screenshot the resulting TERMINAL tab in VS Code?

Hi Connor,
I changed my node version from 14 to 16 and that solved the problem. I did
not get a chance to try your fix but I will keep that in mind. Thanks for
your help.
Best,
Genti
On Tue, Oct 4, 2022 at 12:14 AM Connor Peet @.***>
wrote:

Hmm, can you set "console":"internalTerminal" in your launch.json, and
screenshot the resulting TERMINAL tab in VS Code?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/162602#issuecomment-1266374468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWRAYRZDKWBQ5J5CXITZ7TWBOVLXANCNFSM6AAAAAAQ33DW3Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

authors: VSCodeTriageBot connor4312 gentig


text:
Extension behaves VERY slowly during initialization while debugging

In the latest insiders build, initialization timings for GitLens while debugging are VERY slow (like 10x slower than when running the exact same code in 1.72.1). I can't point to any one thing but most calls during GitLens startup are just taking WAY longer. It visibily takes many seconds for the GL icon to show up in the activity bar, but under 1.72.1 it happens very quickly.
Not sure if its related, but restarting and stopping debugging seem to take extra long as well.

Today's insiders build seems to have resolved the issue so far.

I spoke too soon, with today's insiders the running code doesn't seem too slow, but stepping is VERY slow and stopping debugging gets stuck often (where I can't even click on anything)

Can you tell me where in gitlens I could set a breakpoint to see this? I've been debugging vscode-jupyter with no issues

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 eamodio roblourens


text:
Soft link causes the same source file to be edited in two windows at the same time

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

VS Code Version: 1.72.2 (Universal)
commit: d045a5eda657f4d7b676dedbfa7aab8207f8a075
date: 2022-10-12T22:16:30.254Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 21.6.0
OS Version: macOS Monterey 12.5.1

After vscode opens the project in the soft link directory, jumps to the definition in the code file, a new file will be opened, and the path of the new file is displayed as the file in the original directory.
Modifying one of the open files and saving them will trigger another unmodified "same" file window to also save, resulting in a messy file.
Steps to Reproduce:

Create a directory O, and create a soft link directory S to O;
Create project proj under O, add project file main.cpp, and open S/proj in vscode;
Open the file main.cpp through the left resource manager of vscode, add functions foo and bar, and call foo in bar;
Hold down ctrl and click foo in the bar, the expectation is to jump to the definition of foo in the same file, but it actually opens a new tab, and the display path is O/proj/main.cpp;

This works "as designed", we do not resolve symbolic links when you open an editor for performance reasons so you can end up having 2 distinct editors opened pointing to the same file with different buffers.

authors: bpasero litaohe


text:
I can not open a new terminal or split the terminal

Type: Bug
I can not open a new terminal or split the terminal!!
VS Code version: Code 1.72.1 (Universal) (129500ee4c8ab7263461ffe327268ba56b9f210d, 2022-10-10T17:25:13.482Z)
OS version: Darwin arm64 20.6.0
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.72.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!

Fixed!

authors: VSCodeTriageBot fpichlou gjsjohnmurray


text:
Selecting github enterprise for cloning a project

Hi,
In latest releases I can sign in to my github enterprise for the pull request. But, when I want to clone a project the git clone only show "github" even if I'm signed into github enterprise.

/duplicate #98349

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 idoprz joaomoreno


text:
command-line error: invalid option: --using_directory

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

VS Code Version: 1.74.0
OS Version: Linux x64 5.8.0-63-generic

Steps to Reproduce:

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!

In a selected Directory, I type in the cmd  : "code ."
VSCode opens up but the include directories of header/cpp files are not being recognized. For instance , if I have the files
"directoryA/test.h" and "directoryB/test.cpp" , and do --> include "directoryA/test.h" in the test.cpp file, then VSCODE cannot link these two files together, meaning Defined variables of test.h are not showing up automatically. Compilation works fine.
The "command-line error: invalid option: --using_directory" line is showing in both .h and .cpp files.
It also does not matter if the .h and .cpp files are in the same directory.

I have the same problem now. How was this problem finally solved?

I have the same problem now. How was this problem finally solved?

It was not.... I will write an issue to the cpp extension experts! If you find a solution please let me know.
Thanks :)

I have the same problem now. How was this problem finally solved?

There is already a thread concerning this issue :
https://github.com/microsoft/vscode-cpptools/issues/10249

Fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/v1.13.8

authors: VSCodeTriageBot sean-mcmanus smeriano yongyouhe


text:
Install extension only for this workspace (enable it only for this workspace)

Hello. I'm using VSCode with several of my Projects. Each has a different tech stack and toolset (even languages). I need always disable many extensions when creating a new one. Can developers make an option or something like this for:
Enable new (installing) extensions only for selected workspace.
For other workspaces, it should be disabled by default.
And there can be a dialog if I want to install the extension globally.
Thank you for your attention

/duplicate
Use Profiles feature - https://github.com/microsoft/vscode/issues/116740

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!

Thanks for help


text:
Selection Replace jumps unwanted

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

VS Code Version: 1.70.3 (user setup)
Commit: a21a160d630530476218b85db95b0fd2a8cd1230
Date: 2022-08-31T08:04:00.223Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT ia32 6.1.7601

Steps to Reproduce:

If you want to replace something in a selection and then you want to change the selection you must put off the Selection Replace (which is in other editor not the case).
But for this reason now the cursor jumps pretty unwanted automatically to the next hit on the whole text, which is pretty annoying in large text.

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

OK then do whatever you want with this report.

@F1r3Pr1nc3 would you mind checking if it's still an issue with the very latest VS Code stable when time allows?

@F1r3Pr1nc3 would you mind checking if it's still an issue with the very latest VS Code stable when time allows?

Yes, it is the same in the actual version.
Version: 1.75.1 (user setup)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:32:34.589Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.19042

Hey @rebornix, this issue might need further attention.
@F1r3Pr1nc3, you can help us out by closing this issue if the problem no longer exists, or adding more information.

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: F1r3Pr1nc3 VSCodeTriageBot rebornix


text:
Bottom State bar not turning orange in debug anymore

Type: Bug
Hi there!
As title says, bottom state bar of VSCode doesn't turn orange when launching debug. Can you bring it back? Or give option to do so?
Thanks for the good work!
Reproduction Steps

Launch your app with VSCode Run and Debug (F5)
Watch bottom bar not turning orange

VS Code version: Code 1.78.0 (252e5463d60e63238250799aef7375787f68b4ee, 2023-05-03T20:09:00.748Z)
OS version: Windows_NT x64 10.0.18363
Modes:
Sandboxed: No
Remote OS version: Linux x64 4.19.128-microsoft-standard

System Info

Item
Value

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

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.81GB (3.33GB free)

Process Argv
--crash-reporter-id 3c81871e-805f-4e1a-8293-4564e7bf16ac

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 4.19.128-microsoft-standard

CPUs
Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (8 x 2592)

Memory (System)
7.77GB (4.90GB free)

VM
0%

Extensions (18)

Extension
Author (truncated)
Version

vscode-svelte-snippets
fiv
0.5.0

vscode-edge-devtools
ms-
2.1.1

jupyter-keymap
ms-
1.1.0

remote-wsl
ms-
0.78.4

gitlens
eam
13.5.0

vscode-docker
ms-
1.25.0

isort
ms-
2022.8.0

python
ms-
2023.8.0

vscode-pylance
ms-
2023.5.10

jupyter
ms-
2023.4.1011241018

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

vscode-xml
red
0.25.0

copy-relative-path-posix
rss
0.0.4

docker
vsc
1.0.0

yaml
vsc
1.0.0

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
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
a9j8j154:30646983
showlangstatbar:30730054
azdwalk:30721579
pythonms35:30701012
pythonfmttext:30731395
fixshowwlkth:30730052
showsbindicator:30730056

Have you disabled debug.enableStatusBarColor?
What theme?
Can you try starting with --disable-extensions?

got same problem today the theme changed  by itself apparently

Having the same problem, this hapenning after I accepted the change to the new "Dark Modern" theme.
The flag is enabled.

Even worse, step debuggers do not work this way.

In that theme, it should turn blue. Can other share their theme?
Does it work as expected if you change your theme back to Dark+?
Maybe someone can share a video to be sure that I understand correctly, I don't see an issue.

@roblourens Yes, it works as expected when changing the theme back to Dark+. I expected the "Dark Modern" theme to color the bar in the same way, but thanks for suggesting changing the theme back to Dark+.

Do you happen to have any workbench.colorCustomizations in your settings.json?

I have the tame problem (V1.78.2). For me, it happens only with the "Dark Modern" theme, all other themes are fine, the bar is orange. I don't have any customizations in the settings.json file.
For now I simply switched to "Dark (Visual Studio)".

Do you happen to have any workbench.colorCustomizations in your settings.json?

No, I do not have any workbench.colorCustomizations in my settings.json. If the color of the bar is not expected to be orange in the "Dark Modern" theme, then I think this issue should be closed.

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!

This is a great feature. I missed this feature after updating so I downgraded to 1.74.3

authors: EthanBarlow HighLiuk VSCodeTriageBot bantunes22 bormat p32929 peerdavid roblourens ymongo


text:
restart after update，exception in macos

Type: Bug
vscode macos version，restart after update，window lost caption title bar，can't max、min and fullscreen functions， also can't close window，and also can't quit vscode，must kill process
VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T15:00:40.428Z)
OS version: Darwin arm64 22.4.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Apple M2 (8 x 24)

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

Load (avg)
6, 3, 3

Memory (System)
16.00GB (0.08GB free)

Process Argv
--crash-reporter-id aeade9be-d3e2-4070-ab12-dfee8eaedabb

Screen Reader
no

VM
0%

Extensions (93)

Extension
Author (truncated)
Version

Bookmarks
ale
13.3.1

project-manager
ale
12.7.0

stm32-for-vscode
bmd
3.2.5

better-toml
bun
0.3.2

npm-intellisense
chr
1.4.4

path-intellisense
chr
2.8.4

doxdocgen
csc
1.4.0

vscode-office
cwe
3.1.4

arm
dan
1.7.4

dart-code
Dar
3.64.0

flutter
Dar
3.64.0

vscode-eslint
dba
2.4.0

python-environment-manager
don
1.0.4

rust-syntax
dus
0.6.1

vscode-html-css
ecm
1.13.1

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.12.0

esp-idf-extension
esp
1.6.2

auto-close-tag
for
0.5.14

godot-tools
gee
1.3.1

vscode-github-actions
git
0.25.7

go
gol
0.38.0

vscode-drawio
hed
1.6.6

vscode-htmlhint
HTM
1.0.4

rest-client
hum
0.25.1

yuml
Jai
3.5.1

plantuml
jeb
2.17.5

better-cpp-syntax
jef
1.17.2

svg
joc
1.5.2

svn-scm
joh
2.15.7

cmake-language-support-vscode
jos
0.0.9

cortex-debug
mar
1.10.0

debug-tracker-vscode
mcu
0.0.15

memory-view
mcu
0.0.20

rtos-views
mcu
0.0.6

git-graph
mhu
1.30.0

diff-merge
mos
0.7.0

csharp
ms-
1.25.7

vscode-dotnet-runtime
ms-
1.6.0

vscode-kubernetes-tools
ms-
1.3.11

isort
ms-
2022.8.0

python
ms-
2023.8.0

vscode-pylance
ms-
2023.5.20

jupyter
ms-
2023.4.1011241018

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.292.0

remote-ssh
ms-
0.102.0

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.78.4

cmake-tools
ms-
1.14.31

cpptools
ms-
1.15.4

hexeditor
ms-
1.9.11

mono-debug
ms-
0.16.3

remote-explorer
ms-
0.4.0

godot-csharp-vscode
nei
0.2.1

vscode-extension-auto-import
Nuc
1.4.3

rust-and-friends
nyx
1.0.0

vetur
oct
0.37.3

platformio-ide
pla
3.1.1

minapp-vscode
qiu
2.4.10

java
red
1.18.0

vscode-commons
red
0.0.6

vscode-xml
red
0.25.0

vscode-yaml
red
1.12.2

git-commit-plugin
red
1.1.2

LiveServer
rit
5.7.9

rust-analyzer
rus
0.3.1506

crates
ser
0.5.11

markdown-preview-enhanced
shd
0.6.8

rust-pack
Swe
0.3.3

even-better-toml
tam
0.19.0

tauri-vscode
tau
0.2.6

cmake
twx
0.0.17

vscode-lldb
vad
1.9.1

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

vscode-boot-dev-pack
vmw
0.2.1

vscode-spring-boot
vmw
1.46.0

vscode-gradle
vsc
3.12.7

vscode-java-debug
vsc
0.50.0

vscode-java-dependency
vsc
0.22.0

vscode-java-pack
vsc
0.25.11

vscode-java-test
vsc
0.38.2

vscode-lombok
vsc
1.1.0

vscode-maven
vsc
0.41.0

vscode-spring-boot-dashboard
vsc
0.13.0

vscode-spring-initializr
vsc
0.11.2

vscode-icons
vsc
12.4.0

volar
Vue
1.6.4

vscode-proto3
zxh
0.5.5

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyonecf:30548226
vscccc:30610679
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
showlangstatbar:30737416
vsccsb:30705552
azdwalk:30721579
pythonms35:30701012
pythonfmttext:30731395
pythoncmvfstrcf:30731970
fixhidewlkth:30730051
hidesbindicator:30730055
pythongtdpathcf:30731979

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


text:
Performance Improvement Suggestion: Only Rerender Sticky Scroll When State Is Different

In stickyScrollWidget.ts there is setState, which seems to be called every time the scroll event of the editor fires.
That method seems to clear the dom node and reconstruct it unconditionally.
When smooth scrolling is turned on, the scroll event fires many times per second and the setState call seems to take some time:

I think if you would only rerender the sticky scroll widget when necessary (and generally try to minimize dom API accesses), we could improve the performance here easily.
I think StickyScrollWidgetState could have an equals method and setState would just do an early return if the new state equals the old state.

Thanks for this remark. It is a very good optimization point.

authors: aiday-mar hediet


text:
code -rg cannot open file on fedora OS

Type: Bug
Steps to reproduce

Install the vscode 1.80.2 on Fedora 38 OS
Open the terminal
Type code -rg /path/to/file

Expected Results:
The file should be opened in vscode.
Actual Results:
The vscode is opened but not open that file.

I cannot reproduce this issue after reboot


text:
Intellisense Not Working in Visual Studio Code

During coding sessions in Visual Studio Code, the Intellisense feature, known for code completion and suggestions, is malfunctioning. It has become unresponsive, causing coding slowdowns and heightened error risks due to the absence of its usual assistance. This setback hampers development efficiency, undermines the coding experience, and necessitates immediate resolution to restore the tool's vital support.
Solution:
Update VS Code: Ensure you have the latest version by going to Help > Check for Updates.
Restart: Restart VS Code to resolve potential Intellisense problems.
Install Language Extension: Get the right language extension from the VS Code     Marketplace.
Check Firewall: Ensure VS Code can access the internet for Intellisense resources.
Disable Interfering Extensions: Turn off extensions that might be causing conflicts in File > Preferences > Extensions.
Reset IntelliSense Database: Clear cached data by typing "C/C++: Reset IntelliSense Database" in the Command Palette (Ctrl+Shift+P).
Reinstall VS Code: If issues persist, consider reinstalling VS Code as a last resort.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!

authors: VSCodeTriageBot dishaphatta


text:
View Data in Data Viewer does not appear when debugging

Type: Bug
Hi all,
I just encountered a really tricky issue. I cannot see "view data in data viewer" option when using run and debug. I have jupyter extension installed and i uninstalled vs code and reinstalled it from scratch. However, I still cannot see the option by right clicking the variable in the debugging mode. The version of vs code is up-to-date. Could anyone help me out? Thanks for any advice.
VS Code version: Code 1.86.0 (05047486b6df5eb8d44b2ecd70ea3bdf775fd937, 2024-01-31T10:28:19.990Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12700H (20 x 2688)

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

Load (avg)
undefined

Memory (System)
23.75GB (11.50GB free)

Process Argv
C:\Users\jerry\Desktop\题目2\pairs trading.py --crash-reporter-id e3551513-5487-436b-bf38-cd4d3781ba5d

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

copilot
Git
1.156.0

copilot-chat
Git
0.12.0

debugpy
ms-
2024.0.0

python
ms-
2024.0.0

vscode-pylance
ms-
2023.12.1

jupyter
ms-
2024.1.0

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30951796
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019bcf:30953938
d34g3935:30958340
7j2b6412:30949929

duplicate of https://github.com/microsoft/vscode-jupyter/issues/15121


text:
Tasks "dependsOn" should preserve default value

At the top of tasks.json you can write default settings shared by all tasks, these can then be overwritten per task.
This feature is great: quite useful and helps reducing the verbosity of the file, e.g. setting a common "presentation", "type"...
But not all settings preserve the specified default value (could not find documentation)?
This is the case for "dependsOn" (probably also "dependsOrder").
Arguably ALL settings should respect specified global values, but my current use case for "dependsOn":

I have many tasks are related to BUILD XXXX with alternative build types/arch/targets. Preferred over a bunch of inputs (pickString) to get terminal panels for each one with separate logs.
All depend on a task that essentially stops all debugging to prevent binaries being protected from write access.
I have to add this task manually to each because the globally set "dependsOn" is ignored. If I want to change the task, I have to search and replace everywhere instead of just the flexible global etc.

In general, there is a reason why not all settings are preserved?

Regards

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!

: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 dimateos


text:
doesn't load background image on website

Type: Bug
I used this code in css but it fails to load background image in it.
.bannner
{
height: 100%;
width: 100vh;
background-image: linear-gradient(rgba(0,0,0,0.75),rgba(0,0,0,0.75)), url("background.jpg");
background-size: cover;
background-position: center;
}
VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

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

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

Load (avg)
undefined

Memory (System)
7.73GB (2.68GB free)

Process Argv
--crash-reporter-id 4c51330c-9686-4911-8eee-998c3f91cab8

Screen Reader
no

VM
0%

Extensions (38)

Extension
Author (truncated)
Version

vscode-intelephense-client
bme
1.10.2

dart-code
Dar
3.84.0

es7-react-js-snippets
dsz
4.4.3

vscode-html-css
ecm
2.0.9

copilot
Git
1.173.0

copilot-chat
Git
0.13.1

go
gol
0.41.2

csdevkit
ms-
1.4.29

csharp
ms-
2.22.3

vscode-dotnet-runtime
ms-
2.0.2

vscodeintellicode-csharp
ms-
0.1.26

debugpy
ms-
2024.2.0

python
ms-
2024.2.1

vscode-pylance
ms-
2024.3.1

jupyter
ms-
2024.2.0

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

cmake-tools
ms-
1.17.17

cpptools
ms-
1.19.8

cpptools-extension-pack
ms-
1.3.0

powershell
ms-
2024.0.0

java
red
1.28.1

LiveServer
rit
5.7.9

rust-analyzer
rus
0.3.1877

ruby-lsp
Sho
0.5.15

bootstrap4-vscode
the
6.1.0

cmake
twx
0.0.17

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.3.1

vscode-java-debug
vsc
0.56.2

vscode-java-dependency
vsc
0.23.5

vscode-java-pack
vsc
0.25.15

vscode-java-test
vsc
0.40.1

vscode-maven
vsc
0.44.0

volar
Vue
2.0.6

JavaScriptSnippets
xab
1.8.0

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:30986170
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfcontrol:30979541
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30958157
dsvsc020:30976470

Hello @Vison-west ,
This issue is not related to vs code, but your browser, so this issue should be closed.
I have also tried the code for you, and it works fine here:

/question

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

authors: IllusionMH VSCodeTriageBot Vison-west ahmed0saber


text:
[linked rename] Linked Editing does't work well

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

VS Code Version: 1.87.2
OS Version: macOS 14.3.1 (23D60)

Steps to Reproduce:

set up the linked editing option as true
crate an HTML tag with one or two attributes, like

modify the name of the tag on the opening tag, you would find out that the closing tag is automatically deleted while not added automatically.

/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!

/needsMoreInfo

Sorry, I just misclicked the post button.

The Ayu theme extension cause this issue.

/causedByExtension

/causedByExtension

Sorry for my misunderstood, It's indeed an issue. If there are some attributes in the opening tag, you can't delete the entire name, then change it to another one, like this.

If you delete part of the name, it wokrs.

If there is no attributes in the opening tags, it works perfectly whether deleting the entire name or part of the name.

@aeschli is this your area? If not, please redirect. It also needs two tags removing.

+1 Experiencing this (annoying) issue as well.

Sometimes if I type too fast, the tag on the other side couldn't catch up, and stops updating half-way.

Facing this exact same issue as well

Still happening on VSCode 1.92.2.

same here

On 1.93.0, this is no longer a problem as far as I can tell. Can anyone else confirm?
It also works pretty well with the vim plugin.

Sometimes if I type too fast, the tag on the other side couldn't catch up, and stops updating half-way.

The same problem. It appears that at this point the only way to ensure predictable behavior is to disable this setting.

This problem has nothing to do with extensions. I just did a bisect and even without any extensions enabled this bug still occures.

https://github.com/user-attachments/assets/24507368-a003-4343-810b-a12652278f3c
21-10-2024 issue persists. I have found a woraround, you have to select the tag name and then instead of clearing the name, start writing the new one..

Duplicate of #185279

authors: DevinJohw JakubStasiak00 LucasOe VSCodeTriageBot alexvoedi angelhdzmultimedia bobslee dantgw dennmtr devinjohw gjsjohnmurray mrcaidev musjj plashenkov


text:
Support full range of function breakpoint fields in plugin addBreakpoints

At the moment, it is possible to pass a FunctionBreakpoint instance with the full range of fields configured, but when the breakpoint is eventually inserted, only the name and mode are included.
It would increase the power of the API to pass the full set of fields.

Friendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.

Why i should  do this when i dont get 1 single dollar but any cheater get
so mouch money  or when i say im how to start  this  they  laughs at me and
since yesterday I keep getting stupid messages About giving access and
taking money from whom, those whom I myself brought to this stage
On Wed, May 29, 2024, 2:52 AM VSCode Triage Bot @.***>
wrote:

Friendly ping! Looks like this issue requires some further steps to be
verified. Please provide us with the steps necessary to verify this issue.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/211894#issuecomment-2137464955,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWBOC6BKJNNI3P6GED2NYO3ZEXMTJAVCNFSM6AAAAABHEW4OCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXGQ3DIOJVGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Steps: from an extension, call debug.addBreakpoints(new FunctionBreakpoint(...)) and verify that the breakpoint shows up in the UI, and in the debug.breakpoints list, with all the correct fields that you passed in the FunctionBreakpoint constructor.

authors: AP1400 OccasionalDebugger VSCodeTriageBot roblourens


text:
Ocasionally Commit & Push fails with "Actual command not found"

Type: Bug
Ocasionally I face the following error

Have pending changes
Click  Commit & Push
See error notification
Next attempt works without issues

Developer Tools
10:54:07.622 notificationsAlerts.ts:40 Error: Actual command not found, wanted to execute git.commit /30
    at r.h (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:189812)
c @ notificationsAlerts.ts:40

GIT Output
2024-05-07 10:54:04.887 [info] > git config --get commit.template [94ms]
2024-05-07 10:54:04.956 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> refs/remotes/feature/<REDACTED> [130ms]
2024-05-07 10:54:05.090 [info] > git status -z -uall [118ms]
2024-05-07 10:54:05.236 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> [114ms]
2024-05-07 10:54:05.380 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> [119ms]
2024-05-07 10:54:05.531 [info] > git config --local branch.feature/<REDACTED>.vscode-merge-base [94ms]
2024-05-07 10:54:05.531 [warning] git config failed: Failed to execute git
2024-05-07 10:54:05.647 [info] > git reflog refs/heads/feature/<REDACTED> --grep-reflog=branch: Created from *. [95ms]

VS Code version: Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:09:22.859Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-1270P (16 x 2496)

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

Load (avg)
undefined

Memory (System)
31.67GB (11.14GB free)

Process Argv
--folder-uri file:///c%3A/sources/Repos/FLT --crash-reporter-id 0ed2dc76-86cb-4e82-89ae-a98b71ec0a3f

Screen Reader
no

VM
0%

Extensions (15)

Extension
Author (truncated)
Version

vscode-tailwindcss
bra
0.10.5

copilot
Git
1.187.0

copilot-chat
Git
0.15.0

vscode-github-actions
git
0.26.2

rainbow-csv
mec
3.11.0

vscode-docker
ms-
1.29.1

vscode-dotnet-runtime
ms-
2.0.3

vscode-edge-devtools
ms-
2.1.5

data-workspace-vscode
ms-
0.5.0

mssql
ms-
1.22.1

sql-bindings-vscode
ms-
0.4.0

sql-database-projects-vscode
ms-
1.4.1

live-server
ms-
0.4.13

powershell
ms-
2024.2.1

vscode-thunder-client
ran
2.22.1

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
showvideot:31016892
chatpanelc:31018788
dsvsc021:30996838
724cj586:31013169
pythoncenvpt:31022790
fchga941:31038042
dwnewjupytercf:31035177

I experienced this error today. I was unable to commit with VSCode, but when I opened the repository with another git manager (I used GitExternsions), I was able to commit the changes which were generating the Actual command not found error in VSCode described above, presumably the CLI or another app would have also worked. After the successful commit with GitExtensions, committing within VSCode once again worked as expected.

authors: bruno-ribeiro-mck kelleyjbrady


text:
Override less specific code action with more specific code action

Testing #217611
I set "source.fixAll": "always",. Saving the TS file in the example adds a semi-colon at the end of the second import. I added "source.fixAll.eslint": "never" and "source.fixAll.ts": "never" into that object. Saving the TS file also added a semi-colon at the end of the second import.
I think I was expecting that the more specific line would override the less specific one.
https://github.com/microsoft/vscode/assets/61460952/56b9cd37-bee8-4025-b053-28140ec4dde7

yep this is a known issue with how code actions on save work atm.
right now, we always take the larger superset, so if you have source.fixAll: ____, any other source.fixAll type codeactions will be overridden. we do support language specific overrides though, but i'm not sure if the correct choice is to allow the user with this many options.

authors: aiday-mar justschen


text:
Build failed: shell integration - integration test failure

1 failing
  1) vscode API - Terminal.shellIntegration
       executeCommand(commandLine):

      AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

  {
    confidence: 2,
    isTrusted: true,
+   value: 'e'
-   value: 'echo hello'
  }
      + expected - actual

       {
         "confidence": 2
         "isTrusted": true
      -  "value": "e"
      +  "value": "echo hello"
       }

      at Context.<anonymous> (/Users/runner/work/1/s/extensions/vscode-api-tests/src/singlefolder-tests/terminal.shellIntegration.test.ts:211:18)

Build: https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=286378
Changes: https://github.com/Microsoft/vscode/compare/331b772...b786d31

Happened again here https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=286444

Seemed to be a temporal issue as it hasn't been reported since these 2 occurrences on the same day.

authors: Tyriar meganrogge


text:
filter out the changed files listed in the git source code management panel in vscode

For some projects, making certain file modifications may result in a large number of associated changes. However, these changes are typically not ones I need to be concerned about. Therefore, I hope there is a filter to sort out the listed files for easier focus on the changes that matter to me.

When the "Source Control" view is focused you can press F3 to bring up the list find widget. You can search for the items that you are interested in, then press the "Filter" toggle on the right-hand side of the input field to only show the items that are matching the filter.

When the "Source Control" view is focused you can press F3 to bring up the list find widget. You can search for the items that you are interested in, then press the "Filter" toggle on the right-hand side of the input field to only show the items that are matching the filter.

Thank you for your reply, I tried it out, it's very good, but there is an issue, I can't use wildcards (such as *) when searching.

authors: TwoBrushes lszomoru


text:
Commands executed via menu/contextmenu do not report error as notification

The built-in "Node Debug (legacy)" extension depends on "Node Debug".

Try to disable "Node Debug" but nothing happens, presumably because it has a dependency
Try to disable "Node Debug (legacy)" and it works
Then, also disable "Node Debug" and now it works, presumably because the dependency is gone
Finally, try to enable "Node Debug (legacy)" and it works?! and also automatically enabled "Node Debug"

To be consistent, if it is possible to enable "Node Debug (legacy)" when "Node Debug" is disabled and automatically enable "Node Debug" then it should also be possible to disable "Node Debug" and have "Node Debug (legacy)" also be automatically disabled.
This is also confusing because there's no indication why nothing happened when I clicked on Disable on "Node Debug" while "Node Debug (legacy)" is enabled.

Try to disable "Node Debug" but nothing happens, presumably because it has a dependency

You see an error at the bottom right that there is an extension (Node Debug Legacy) depends on it

Try to disable "Node Debug (legacy)" and it works

👍

Then, also disable "Node Debug" and now it works, presumably because the dependency is gone

👍

Finally, try to enable "Node Debug (legacy)" and it works?! and also automatically enabled "Node Debug"

Yes, enabling/installing an extension also installs its dependency. If a user is trying to enable/install an extension, it is implied dependencies too.

To be consistent, if it is possible to enable "Node Debug (legacy)" when "Node Debug" is disabled and automatically enable "Node Debug" then it should also be possible to disable "Node Debug" and have "Node Debug (legacy)" also be automatically disabled.

Other way around is not good. Uninstalling / Disabling dependencies of an extension together might not be expected and users would have installed them independently. It was this behaviour (with prompt) but I should say it was not the best. Hence made disablement and uninstalling independent.

This is also confusing because there's no indication why nothing happened when I clicked on Disable on "Node Debug" while "Node Debug (legacy)" is enabled.

There is. As I said you see error prompt at the bottom right

I don't get the error prompt at all :(

Strange I see it. May be try with all extensions disabled?

I disabled all extensions then restarted VS Code. Still nothing ☹ What other info can I collect for you?

Node Debug and Node Debug (legacy) don't appear to be installed when I run from dev (e0e2738819c0f) I'm looking for another pair to try with. Let me know if you know of one or if there's a good way to check extension dependency.

Tried with the GitHub Pull Requests extension and the built-in Git extension. Same results: when I try to disable the Git extension it does not disable (👍) but there is no notification(👎).

@alexr00 Can you please breakpoint at the following line and see if it is getting hit?
https://github.com/Microsoft/vscode/blob/a144e2fa9fc2fb91a8add05833943a00f3b86371/src/vs/workbench/parts/extensions/node/extensionsWorkbenchService.ts#L775
If it is, can you please check why the error is not being notified?

@sandy081, the error tries to fire, but in event.ts on line 132 this._listeners is undefined. this._deliveryQueue is also undefined at the start of the fire function.

@bpasero
For @alexr00 When an action is executed and returns an error, it is not notified.
https://github.com/Microsoft/vscode/blob/4b427941dc20b303e35c7687924a4a92f73c4c20/src/vs/workbench/parts/extensions/electron-browser/extensionsActions.ts#L729
Any insights?

Any insights?

Any steps?

Try to disable an extension which is a dependent of some other extension. You can try disabling Node Debug or install Pull Request Extension and disable Git. You should see an error notification.

@sbatten I can reproduce and it looks like neither our custom context menu nor our native context menu delegate failing actions to a notification service to show the error. I think we should probably hook that in. I think this is not a recent regression, this probably never worked properly (or at least for a while).

Maybe we should open a separate issue for the menu issue, up to you @sandy081

I think its fine to use this issue and update the summary or description if needed.

I don't know when or how this was fixed, but I can not reproduce any longer. @bpasero @alexr00 to verify?

I can still reproduce by trying to disable Node Debug.

Correct. I don't see that prompt. It looks as though nothing happens when I try to disable Node Debug.

@alexr00 do you see the error in the devtools console?

No, I don't see the error in the devtools console. I just get this when I right click:
dom.ts:213 [Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

@alexr00 oh im stupid, I was using the gear menu, not the context menu to disable. I can repro

@alexr00 this seems to be resolved for the context menu now, tested disabling git Hopefully I did not misread again, but please try it out.


text:
Add link in "How-To-Contribute" to GitHub Fork Help Page

In the "How-To-Contribute" wiki page under the "Getting the sources" subsection, recommending a hyperlink to the "Fork A Repo" GitHub article for users/developers that might be new to the term "Fork", albeit familiar with the concept. Also maybe a link to "Clone" as well.

Hi @jamesralstin Thank you for your suggestion. I'm reluctant to add links, that we would have to maintain if they move. Forking and cloning are part of the basic vocabulary of open-source development and I'd rather users searched and found their own guidance, which matches their level (beginner, advanced, refresher).

authors: gregvanl jamesralstin


text:
Forcing setBreakpoints request on sources change

I now work on JavaScript debugger plugin based on code instrumentation, this should allow time traveling and hot reloading during a debugging session.
I reload modules using Hot Module Replacement keeping all the state from the former version. This works except if I add a new line into a source all breakpoints become unverified, which is obviously right since their position is changed. Toggling one them sends setBreakpoints for the whole module and they are back verified and functioning.
I can workaround this using 'breakpoint' event, however, the back-end doesn't know its new correct position, resetting it to the former line looks pretty random.
Is there is some way to force resending setBreakpoints for a changed module?  Or can the client send it on, say, loadedSource event?

Currently we send the setBreakpoints request when the user has manually changed breakpoints in some way (by adding them, disabling/enabling them...).
When the initiazlied event arrives. When the file with breakpoints got deleted.
Currently the client does not send them for the loadedSource event and there is no way to force the cliend to send the setBreakpoints request programatically.
Thus leaving this open as a feature request.

@isidorn would you accept a PR if I do this?

@awto not at the moment. Since this feature is not requested and we did not plan to have it yet.
Maybe in the future we might reconsider. Thanks

@isidorn do you mean the code hot swapping feature isn't requested? Many debuggers has it and it is actually great. In fact this issue looks more like a bug to me not a feature, why do you need loadedSources event after all.
But ok, for now I'm going to hack this by toggling some breakpoint twice via debugger service, my adapter runs in the same process. If there is some other better way to convey the new breakpoint positions, I would be happy to know.
Thanks.

@awto there is currenly no feature reqeust for code how swapping as far as I know. Though feel free to open a new feature request.
Thanks

@isidorn I work now on a JS debugger which supports hot swapping among a few other nice things, and the hot swapping does already work there. Except all the breakpoints are deactivated, untill I toggle one of them (so "setBreakpoints" is sent again).
I'm not sure if such feature request really belongs here, as this is a feature of an adapter (and debuggee). From the vscode side every feature needed is already there, except this small issue - no way to update breakpoints position. Which I would guess should be a part of loadedSources response, so I wouldn't call this issue a feature at all.
I can workaround this (if my adapter runs in the same process), but the purposes of loadedSources event isn't clear though.

Why dont you just send a breakpoint event and update all the breakpoints that you want?
How do the breakpoint get deactivated? Do they say Unverified breakpoint. File is modified, please restart debug session on hover or something else?

Why dont you just send a breakpoint event and update all the breakpoints that you want?

I can, and I tried this, but since on adapter and debuggee sides I don't know the new breakpoint positions, if someone, say, adds a line into text. So I tried to resend the same positions I know from the last setBreakpoints, this sets their possition on a quite random looking line.

Do they say Unverified breakpoint. File is modified, please restart debug session on hover or something else?

yes, this message, and when I toggle one of them everything is back to normal, since the setBreakpoints request is resent.

@isidorn I've just checked the recent version and IDE does send now setBreakpoints on source file changed. This is not on loadedSource event though, but it is pretty enough for me. I don't know, maybe this didn't work the same on May, or it is just me. Thanks a lot!

Welcome. I have been doing some refactoring in that area and seems like I fixed it hooray.

authors: awto isidorn


text:
Integrated terminal seems to clear at startup

Environment

VSCode Version: 1.34.0
OS Version: Windows 10

Problem description
The integrated terminal seems to truncate output. At VSCode startup or Reload Windows, the terminal does not show anything. I got a big blank space. If I pressed "Enter", it outputs something.

The problem seems to be the same with tasks, I got a big blank space but I do not have the output of the task.

Instead of :

The result is same with powershell.exe and cmd.exe. I do not have the problem with wsl.exe, exception for the task that did not found cargo...different problem I suppose...
Steps to reproduce

Set your shell to powershell.exe

"terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"

Restart VSCode/Reload VSCode windows and display the terminal

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

This is a bug in Windows 10 1809, unfortunately we have no way to work around the issue so you will need to wait until you get the next version of Windows 10 (1903).
/duplicate https://github.com/Microsoft/vscode/issues/57803

authors: FuriouZz Tyriar


text:
html failed to save due to unknown file system error. it has been consistent with every html file I created and edited with VSCode.

VSCode Version:1.34
OS Version:Windows 10 Pro

Steps to Reproduce:
1.write anything on index.html
2.save it then sometime soon eventually it cannot be saved.

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

@Pavelbure34 same happens when you start VS Code from the command line with code --disable-extensions?

/needsMoreInfo


text:
User data: migrate Backups, Workspaces, user state into %APPDATA%/User

Today we have a bit of a mix in our %APPDATA% folder: a lot of stuff is going into the %APPDATA%/User folder but a few things outside are not:

Backups
Workspaces
storage.json

I think we should do a migration step for a while to consolidate this data under the User folder.
@Tyriar also happy for your input given you are the author of https://github.com/Microsoft/vscode/issues/3884

I removed part of the description. Specifically we can leave the backup format as it is today where we have a folder per scheme, even though that is not really needed if we take the hash of the full resource.

Is this just cleanup or is there a bigger problem with the folders being there?

@Tyriar I think it would bring us closer to a model where all of our data goes into one folder "User" and the rest is a) chrome stuff and b) some caches that can be ignored.
E.g. we could then start to think about nuking anything which is not in "User" to ensure a cleaner startup (e.g. no traces of previous chrome stuff around).

:+1: sounds good

What about extensions? Why is the extensions directory located in ~/.vscode/ rather than %APPDATA%/User?

I think very much in the beginning we were worried that Windows would automatically roam the stuff that is inside %APPDATA% so we decided to not put extensions in there. I also find it a bit unfortunate that we require 2 folders on disk to store stuff.

As mentioned in #3884, the optimum location for extensions is %LOCALAPPDATA% rather than %APPDATA%.
I expect to see the transition during my lifetime. 😁

authors: Tyriar bpasero byyxx128 gudvinr


text:
Smoke test failure in CSS for 1.36.1

Smoke test failure under Windows testing 1.36.1
** Timeout!
Error: Active element not found. Current active element is 'HTML > BODY.vs-dark.vscode-theme-defaults-themes-dark_plus-json.file-icons-enabled.windows'. Looking for  .monaco-editor[data-uri$="settings.json"] textarea
    at m.<anonymous> (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:2208:775)
    at Generator.next (<anonymous>)
    at file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:35:460
    at new Promise (<anonymous>)
    at n (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:35:237)
    at m.isActiveElement (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:2208:467)
    at call (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:1386:581)
    at C.onPromise (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:316:346)
    at C.onRawMessage (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:315:994)
    at C.protocolListener.protocol.onMessage.e (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:315:531)
    at d.fire (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:79:760)
    at EventEmitter.n (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:77:206)
    at EventEmitter.emit (events.js:182:13)
      1) verifies that warning becomes an error once setting changed

I can successfully run the smoketest on 1.38on Windows

authors: aeschli dbaeumer


text:
Statusbar or top row cut off with Mac native tabs

Issue Type: Bug
The first Mac native tab has its top row cut off:

The second one has the statusbar below the visible window:

Resizing the window is a workaround.
VS Code version: Code - Insiders 1.38.0-insider (44a48f75d64333b8e33a1fe4f57f6a60553b1e6b, 2019-08-15T05:23:00.986Z)
OS version: Darwin x64 18.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

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

Load (avg)
4, 11, 10

Memory (System)
16.00GB (3.89GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (27)

Extension
Author (truncated)
Version

unique-lines
bib
1.0.0

ssh
chr
0.0.4

ghlink
dt
1.1.0

remotehub
eam
0.5.0

EditorConfig
Edi
0.13.0

tslint
eg2
1.0.44

git-project-manager
fel
1.7.1

rest-client
hum
0.22.0

solidity
Jua
0.0.58

theme-karyfoundation-themes
kar
18.2.1

graphql-for-vscode
kum
1.15.1

vscode-docker
ms-
0.7.0

remote-containers
ms-
0.67.4

remote-ssh-edit-nightly
ms-
2019.8.19620

remote-ssh-explorer-nightly
ms-
2019.8.19622

remote-ssh-nightly
ms-
2019.8.19620

azure-account
ms-
0.8.4

azurecli
ms-
0.4.6

github-issues-prs
ms-
0.9.1

debugger-for-chrome
msj
4.11.7

vetur
oct
0.22.1

vscode-versionlens
pfl
0.24.0

vscode-yaml
red
0.4.1

vscode-workspacecontains-canary
rob
0.0.2

vscode-open-in-github
sys
1.12.0

ayu
tea
0.18.0

vscodeintellicode
Vis
1.1.9

@chrmarti does this reproduce when you disable grid layout?

Yes, it's the same with grid layout disabled.

@chrmarti I cannot reproduce, attach your settings.

I cannot reproduce using Electron 4.2.7

Fix is up at https://github.com/electron/electron/pull/19878 , should be available with next electron release.

we will take the new build and @bpasero will push it via a PR.

authors: alexandrudima bpasero chrmarti deepak1556


text:
Vertical Select with middle click is not working

Issue Type: Bug
In older versions of VSCode, I did vertical selection by clicking the middle button on the mouse and dragging.
It seems like this doesn't work anymore.
VS Code version: Code 1.40.1 (8795a9889db74563ddd43eb0a897a2384129a619, 2019-11-13T16:49:30.162Z)
OS version: Linux x64 5.0.0-36-generic snap

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 x 1960)

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

Load (avg)
4, 2, 1

Memory (System)
7.76GB (0.16GB free)

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

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

plantuml
jeb
2.13.5

intellij-idea-keybindings
k--
0.2.37

python
ms-
2019.11.50794

vscode-yaml
red
0.6.1

@yanniszark In some Linux distributions, middle clicking is reserved for moving windows. Did you perhaps change window compositors, or have upgraded your distribution since it last worked? Does middle clicking work for you in other applications?

@alexandrudima thanks for the response!
I'm working on Ubuntu 18.04.
This is the output of lsb_release -a:
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic

In Jetbrains Goland, vertical selection with middle click works as expected.

Thanks for your quick reply.
VS Code is built with Electron, which is built with Chromium. Can you please try opening https://vscode-web-test-playground.azurewebsites.net (it might take a long time to load) in Chromium on the same machine? Does using the middle mouse button work there?

@alexandrudima I loaded the web page and the middle click vertical select still doesn't work.
When I try to select vertically, it just selects normally.
Also, middle click for paste works.

Also, middle click for paste works.

Aha! Thanks for the last extra detail to jog my memory. Indeed, the middle mouse button by default will paste the selection clipboard on Linux. You can disable that via "editor.selectionClipboard": false. Once the selection clipboard is disabled, the middle mouse button can be used for column selection.

@alexandrudima yes that was it!
Thanks a lot for the help!
I can now go back to my favorite editor :smile:

authors: alexandrudima yanniszark


text:
cannot reference $returnValue in logpoint

testing https://github.com/microsoft/vscode/issues/93807
Not sure if this should work or not, but what the heck I'll give it a try!

In the debug console, I get this:
this is the ReferenceError: $returnValue is not defined
    at eval (logpoint-bce3f6f.cdp:3:5)
    at eval (logpoint-bce3f6f.cdp:7:3)
    at helloWorld (/Users/chris/src/test93807/index.js:6:16)
    at Object.<anonymous> (/Users/chris/src/test93807/index.js:10:11)
    at Module._compile (internal/modules/cjs/loader.js:956:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
    at Module.load (internal/modules/cjs/loader.js:812:32)
    at Function.Module._load (internal/modules/cjs/loader.js:724:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
    at internal/main/run_main_module.js:17:11

Living loco @chrisdias
Though forwarding to @connor4312 since he is the author of that test plan item

Thanks for the issue! Unfortunately this won't work because the $returnValue is only available after stepping over the return statement, but breakpoints can't be set there.

@connor4312 In  the following code
function foo() {
    const val = [];
    for (let i = 0; i < 20; i++) {
        val.push(bar(i));
    }
    return val;
}

function bar(i) {
    return {
        code: i,
        message: `msg ${i}`
    };
}

foo();

I can set a breakpoint on line 13. When this one is hit $returnValue is defined. However logpoints  referencing $returnValue fail and conditional breakpoints  referencing $returnValue are never hit. When are those conditions being evaluated? In this case I'd guess after the return value was evaluated.

Ah, okay. I'll check on this.

Fixed in the linked commit. Note that, as mentioned, you need to make sure the logpoint is set after the return statement, since before it's evaluated the call frame's return value is not set. If compiling to js, the sourcemaps might already be set up like this.

authors: chrisdias connor4312 isidorn kieferrm


text:
Build initial renderer starter code sample/repo

Refs: #95908
Create a sample renderer repo with all the good defaults. To be converted to a yeoman generator later.

Created in https://github.com/microsoft/vscode-notebook-renderer-starter


text:
Can't view images when doing ssh-remote, port other than 22 is used.

VSCode Version: 1.46.0-insider
OS Version: Catalina 10.15.4; Darwin x64 19.4.0

Why I can't view an image through ssh-remote mode?
My situation is port22 is disabled, and I login by ssh -p NUMBER name@ip -A, where the host listens to that port.
Steps to Reproduce:

Login to ssh-remote with -p specified. Simply can't view images in any window/tab.

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

/needsMoreInfo
Please provide more detailed steps for how to reproduce the problem.
Are you using a VS Code Remote extension? What other extensions are you using?

Hi, @egamma

I disabled all extensions except for remote-ssh.
This happens only for insider-version. Since I also have a 1.45.1 code-stable-version, I tested on that, and all things went on well.
I can't say how to reproduce the problem. Since I just can't open an image or load a jupyter notebook(the kernel is started but the view doesn't appear) .

Could you give me some suggestions where to look for? like logfiles, check some port settings ?

authors: egamma zehongs


text:
Fixes 113603: Change reason for moveWordCommand to CursorChangeReason.Explicit

This PR fixes https://github.com/microsoft/vscode/issues/113603
https://user-images.githubusercontent.com/17052177/104156845-456d8900-542d-11eb-957b-8a8e01d50dee.mp4

Thank you!

Thank you!

source: gharchive/pull-request

authors: alexdima shskwmt


text:
[sql] grammar update, added window functions

This PR fixes #118500 Syntax support for SQL WINDOW functions.
Apologies as I am unsure how to test the changes.

Note:
https://github.com/microsoft/vscode/blob/120a9f6476553edf3275bfa23df5e3245cfa0146/extensions/sql/syntaxes/sql.tmLanguage.json#L2-L5

authors: life-droid yume-chan


text:
Add single level of categorization #126089

This PR affects #126089

Here's how the toc currently looks

Testing GHPRI

Testing extension


text:
Fix #146166: Snippet transform preserves existing camel/Pascal case

This PR fixes #146166 so that existing camel/Pascal case within a snake_case or kebab-case name is preserved. For example, transforming stub_PathServiceToken to camel case now produces stubPathServiceToken, rather than stubPathservicetoken. Corresponding tests have been added to demonstrate this new behavior.
However, this adjusted implementation introduces some ambiguity I'd like to discuss. In the previous camel case implementation, the name portland-OR-temp would be transformed into portlandOrTemp. Now, it would become portlandORTemp, preserving the upper-case OR. Is this behavior desirable? I assumed this approach would best preserve user intent, but I understand preferences for the consistency of the former approach.

Thanks @amanasifkhalid

authors: amanasifkhalid jrieken


text:
merge editor - add setting for layout

This PR is for:

https://github.com/microsoft/vscode/issues/150813
https://github.com/microsoft/vscode/issues/150812

This also puts "Merge Editor" quite prominently under the "Text Editor"

The setting is currently not resource scoped, not sure, that is maybe overkill, though could be added later.

No worries, we can discuss (in the end it's just a swap of services mainly).
I think I tried to model this after some existing settings we have that are similar:

But I do not have arguments for or against. The only thing to note is that resource scoped setting (if we ever wanted to allow the user to control layout per file) would require us to use a setting.

No and I'll tell u this if it's mine tell them to release it
On Thu, Jun 23, 2022, 6:25 AM Benjamin Pasero @.***>
wrote:

No worries, we can discuss (in the end it's just a swap of services
mainly).
I think I tried to model this after some existing settings we have that
are similar:
[image: image]
https://user-images.githubusercontent.com/900690/175287376-550408f2-90bf-4b09-b336-421b5b80b9e8.png
[image: image]
https://user-images.githubusercontent.com/900690/175287428-b3253c9a-9dec-48ef-82b5-4433bfe639b0.png
But I do not have arguments for or against. The only thing to note is that
resource scoped setting (if we ever wanted to allow the user to control
layout per file) would require us to use a setting.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/pull/152953#issuecomment-1164288446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYYXGWSYOMFL44V7BLHADZDVQRCRLANCNFSM5ZTN4QZA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

closing in favour of https://github.com/microsoft/vscode/pull/153108

authors: Athayde3586 bpasero jrieken


text:
Added more documentation for better readability

Addresses Issue #234442. Added more JSDoc style comments on the src/server-main file to enhance code readability. Implemented documentation on the following parts: the shouldSpawnCli conditional, parseRange function, and prompt function. This is so that there is consistent documentation throughout the file to help future contributors to understand seemingly complex code.

@microsoft-github-policy-service agree

Thanks you for the PR, but we rather leave the code as is, I think it's clear, what it does without comments

authors: aeschli alyssacabading


text:
Key to request for administrator privileges

Description of the new feature/enhancement
It would be good having a feature which requests for administrator privileges without opening a new window of the terminal.

Proposed technical implementation details (optional)
With a button and also a keyboard shortcut.

@albertopasqualetto I'm not sure how this would work. There is no "native" Windows "sudo" equivalent. What you are asking for might be better requested from https://github.com/Microsoft/Terminal.

As a quick fix, scoop has a sudo you can download that works reasonably well, but yeah I agree Terminal is probably the better idea, if anything because it would be shell-wide rather than a specific program

Sorry, completely mistaken the git project! Thanks

authors: Masamune3210 albertopasqualetto denelon

repo: microsoft/winget-cli


text:
I hope that I can change the default installation location

Description of the new feature / enhancement
I hope to configure the json file to install the software to the specified drive through winget, and I don't want to install it to C by default
Proposed technical implementation details
I hope to configure the json file to install the software to the specified drive through winget, and I don't want to install it to C by default

Duplicate of #3608


text:
New version: Amazon.WorkspacesClient version 5.9.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[x] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@JamieSabbatella Just an fyi: The PR has been manually validated and is waiting on you to resolve the comments before merge.

@JamieSabbatella Just an fyi: The PR has been manually validated and is waiting on you to resolve the comments before merge.

Yes - sorry about these Internal-Error-Dynamic-Scan errors. They're caused by Automated Validation pipeline interference, and the package did pass our alternate Manual Validation pipeline.

repo: microsoft/winget-pkgs


text:
TimBrogden.Keysticks version 2.1.3.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109156&drop=dogfoodAlpha

This package seems to install the installer. Is it a nested installer?

authors: stephengillie superusercode


text:
New version: Ndd version 2.7.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116399&drop=dogfoodAlpha

/AzurePipelines run

@wingetbot


text:
SmartSoft.SmartFTP version 10.0.3185.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @matbech,
Apps and Features Entries were omitted on this version. Should they be included?

Thank you for pointing this out. It seems the latest version of wingetcreate removed the UpgradeCode field if it wasn't under AppsAndFeaturesEntries node.

authors: matbech stephengillie


text:
New package: sigoden.Dufs version 0.38.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Executable-Error

authors: SpecterShell stephengillie


text:
New version: Cockos.REAPER version 7.09

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

authors: LeonarddeR mdanish-kh


text:
New package: Nbc66.VTFEditReloaded version 2.0.4.00

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[x] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Hi is there anything else i need to do to be abel to get this package inside of winget?

Automatic Validation ended with:

No errors to post.

(Automated response - build 791.)

Automatic Validation ended with:

No errors to post.

(Automated response - build 791.)

So whats the issue then?

Manual Validation ended with:

@wingetbot waivers Add Validation-Executable-Error

@stephengillie I updated the manifest with the requested changes


text:
OpenRCT2.OpenRCT2 version 0.4.10

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-04-02T23:31:38.9813405Z ##[error]Manifest Validation Failed
2024-04-02T23:31:44.0645527Z ##[section]Finishing: Validate Manifest

(Automated response - build 876.)


text:
New version: Hugo.Hugo version 0.125.0

Created by 🥟 Dumplings in workflow run #4445.
Logs
Updated: 0.124.1 → 0.125.0
Submitting WinGet manifests

Microsoft Reviewers: Open in CodeFlow

Spaces detected in version number.
(Automated response - build 876)


text:
New version: Tencent.TencentDocs version 3.5.1

Created by 🥟 Dumplings in workflow run #4995.
Logs
Updated: 3.5.0 → 3.5.1
Submitting WinGet manifests

Microsoft Reviewers: Open in CodeFlow

I'm having trouble finding a link to this version - has it been released yet?

I'm having trouble finding a link to this version - has it been released yet?

It is released in their update channel.


text:
chore: add vcredist dep to gptscript installer

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[x] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

authors: drpebcak hackean-msft


text:
New package: Mozilla.Thunderbird.de version 128.2.0

Microsoft Reviewers: Open in CodeFlow

Possible duplicate package entry.
Similar installer SHA256 hash found in manifest:

InstallerSha256: 895d194cbd42e3e2dfd6b22d395bfd986beed988ee1f294bbc9e013b3e0b01d4

manifests\m\Mozilla\Thunderbird\128.2.0

InstallerSha256: ae83bc03129e3f5e166f304b31e32781fe124178fec2c9bae47179538080a856

manifests\m\Mozilla\Thunderbird\128.2.0

Verify by hash.


text:
Update manifests/e/Eugeny/Tabby/1.0.141/Eugeny.Tabby.locale.en-US.yaml

Fixes an issue where this package has multiple different monikers
Microsoft Reviewers: Open in CodeFlow

[Policy] Reset Labels


text:
Remove version: NumeRe.NumeRe version 1.1.4.2209

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


text:
Remove version: REALiX.HWiNFO version 8.04

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


text:
Remove version: WinSCP.WinSCP version 5.19.4

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/winscp/files/WinSCP/5.19.4/WinSCP-5.19.4-Setup.exe/download
OK
(Automated message - build 923)


text:
ARP: Amazon.Chime version 4.39.10232.1

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow


text:
New version: Couchbase.ServerEnterprise version 7.0.7031

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?
[X] Have you validated your manifest locally with winget validate --manifest <path>?
[X] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

Should probably add a ShortDescription too.

@wingetbot waivers Add Policy-Test-2.7

authors: ImJoakim OfficialEsco zachcarp


text:
JanDeDobbeleer.OhMyPosh version 7.87.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

authors: ItzLevvie JanDeDobbeleer


text:
ARP Entries: Azul.Zulu.13.JDK version 13.35.51

Pull request has been automatically created using Add-ARPEntries

Removed DisplayVersion because it matches https://github.com/microsoft/winget-pkgs/pull/74965


text:
[Zip][WiX] New package: Uzero.ScanScan version 0.2.7

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?
[X] Have you validated your manifest locally with winget validate --manifest <path>?
[x] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow

@msftbot .zip

authors: SpecterShell mdanish-kh


text:
up whatsapp.whatsapp description

null
Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree