jiebi/CodeConvo huggingface dataset:
Change:
{ "view": "scm", "contents": "%view.workbench.scm.folder%", <del> "when": "config.git.enabled && !git.missing && git.state == initialized && workbenchState == folder && scmRepositoryCount == 0 && git.parentRepositoryCount == 0 && git.unsafeRepositoryCount == 0 && git.closedRepositoryCount == 0 && remoteName != 'codespaces'", </del> <ins> "when": "config.git.enabled && !git.missing && git.state == initialized && workbenchState == folder && scm.providerCount == 0 && git.parentRepositoryCount == 0 && git.unsafeRepositoryCount == 0 && git.closedRepositoryCount == 0 && remoteName != 'codespaces'", </ins> "group": "5_scm@1" }, { "view": "scm", "contents": "%view.workbench.scm.workspace%", <del> "when": "config.git.enabled && !git.missing && git.state == initialized && workbenchState == workspace && workspaceFolderCount != 0 && scmRepositoryCount == 0 && git.parentRepositoryCount == 0 && git.unsafeRepositoryCount == 0 && git.closedRepositoryCount == 0 && remoteName != 'codespaces'", </del> <ins> "when": "config.git.enabled && !git.missing && git.state == initialized && workbenchState == workspace && workspaceFolderCount != 0 && scm.providerCount == 0 && git.parentRepositoryCount == 0 && git.unsafeRepositoryCount == 0 && git.closedRepositoryCount == 0 && remoteName != 'codespaces'", </ins> "group": "5_scm@1" }, {

Discussion:
Type: <bFeature Request</bNo Clone Git repository option available VS Code version: Code 1.80.1 (, 2023-07-12T17:22:07.651Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --
Have you followed the instructions at yet?
! The button for the same doesn't show up
At a Windows command prompt please run to confirm what version you installed.
[image: ] It is the latest version
What do you see after you choose the third option on Activity Bar (Source Control view) instead of Explorer view? See the screenshot at
The git extension does indeed contribute welcome views to the "Explorer" view and it uses the context key. The problem is that this particular context key is only set when the "Source Control" view is rendered. So if you switch to the "Source Control" view and then back to the "Explorer" view then the option to clone a repository will appear.
Change:
this.focus({ force: true }); this._win.webContents.openDevTools(); } }, 10000)).schedule(); }

Discussion:
Issue Type: <bBug</brun in the terminal where is the path to an existing directory see VSCode open the workspace as expected run in the terminal where is the path to an existing directory focus changes back to VSCode, but showing the window for project instead of project Here is a movie of the experience: ! In previous versions of VSCode, when opening a new project with , the new window would show up above any existing windows. This is what I expected to happen. VS Code version: Code 1.67.1 (, 2022-05-06T12:37:14.619Z) OS version: Darwin arm64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (17)</summaryExtensionVersion ------ vscode-tailwindcss0.8.3 vscode-eslint2.2.2 copilot1.19.5865 go0.33.0 terraform2.22.0 vscode-env0.1.0 jsonnet-language1.0.0 vscode-docker1.22.0 python2022.6.2 vscode-pylance2022.5.1 remote-containers0.234.0 remote-ssh0.80.0 remote-ssh-edit0.80.0 excalidraw-editor2.0.16 code-spell-checker2.1.11 svelte-vscode105.16.0 cython0.1.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Looks similar to and .
Same issue. On Mac OS, VsCode 1.67 How to reproduce: shortcut to open new window <kbdCMD</kbd+ <kbdSHIFT</kbd+ <kbdN</kbdshortcut to open new file/folder <kbdCMD</kbd+ <kbdO</kbdThe selected file/folder is now opened in the previously focused vscode window instead of the newly opened one. To solve the problem, you have to think to click in the newly opened window.

When you do so, you see the focus takes effect, proving the window was not actually focused (EDIT: What is confusing is that you can see the cursor blinking inside of the editor of the new window, even though it is not focused) I can tell this is a relatively new issue (1 or 2 months max), because I'm doing the procedure above almost every day and it has been pissing me off since then (sorry, but truly annoying).
Sounds a bit like or
Do you have configured?
This is a regression from
Thanks for the fix!
Change:
editor.executeEdits( 'inlineSuggestion.accept', [ <del> EditOperation.replaceMove(completion.range, ''), </del> <ins> EditOperation.replace(completion.range, ''), </ins> ...completion.additionalTextEdits ] );

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Not relevant <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.87.2 OS Version: MacOS Sonoma 14.3 (23D56) Steps to Reproduce: Use word-by-word/line-by-line accepts for an . I re-serve the same completion from cache after word-by-word accepts (with already accepted text filtered out). The completion suggestion flashes even though the ghost text did not change. This did not use to happen on VSCode 1.86 (downgraded and tested with the same VSIX). Example of text flashing on VSCode 1.87 gif: ! mov:
Can you give me reproduction steps? Cannot reproduce with copilot. Would be awesome if it reproduces .
Yeah let me try to figure this out and see if I can reproduce it with this! Unfortunately I wasn't able to reproduce it for CoPilot too, but with my organization's extension the behaviour changed after 1.87. The expected implementation for word-by-word/line-by-line completion is to re-serve the text from the old completion (with matching prefix removed) as a new right? Thanks for your help!
Yes
I created a mock example where I can still reproduce this on 1.87, and confirm that the text does not flash on 1.86. Still trying to investigate further if there's any link with other extensions or anything that could conflict, but a bit perplexed since it's very much reproducible with 1.87
On another interesting note, if I replace the full line (i.e including the prefix in the suggestion), it does not flash.

Maybe it's not reproducible with CoPilot if that's the approach they're taking?
Can you translate this example into a ? That way, if it is really a bug, it will significantly reduce the time I need to fix this (and for other team members to verify a bug-fix).
here's a repro on . If you type and then select code word-by-word, the text flashes. On this doesn't occur. I can repro the bug on 0.47.0 too. Hope this helps! Edit: Looks like it broke between v0.46.0-dev- and v0.46.0-dev-
Change:
if (!emptySelectionClipboard && editor.getSelection().isEmpty()) { return; } <ins> // Prevent copying an empty line by accident if (editor.getSelections().length === 1 && editor.getSelection().isEmpty()) { if (editor.getModel().getLineFirstNonWhitespaceColumn(editor.getSelection().positionLineNumber) === 0) { return; } } </ins> super.run(accessor, editor); }

Discussion:
Hello, I've initially asked about this on Twitter: Current default behaviour: (A) Ctrl + C on a line with code (no text selection): copies the whole line (B) Ctrl + C on a blank line (no text selection): copies the empty line I would love to be able to do (A), but disable (B). The closest setting for this is . Setting it to disables (B), but prevents me from using (A) forcing me to select the whole line to copy it.
I am curious.. Why would you Ctrl+C on a blank line in the first place?
Hello I don't do it intentionally. Since the and the keys are next to each other (in QWERTY keyboards at least), every now and then when I attempt to paste something on a blank line I accidentally click instead of so whatever I initially have in my clipboard gets overwritten by a blank line.
Got it, thanks.
An extension: , can you unlock that issue: , so I can put a link to the extension, since not everybody happy there and they basically want the same thing as described in this issue.
I don't believe the extension is the right solution for this problem for 2 reasons: It can easily be solved in the product itself. The extension introduces a new command which users will have to learn I believe we can add this fix as a default. Would you like to send a PR? The fix would be in the file If there is no selection and the line is empty, then we shouldn't copy to clipboard Please correct me if I am wrong above
thanks for the investigation and proposal, sounds good to me. Things to take care of carefully is lines with only leading whitespaces and multi cursors.
IDK, similar issue got 5 days ago: If you will accept PR, then I can try.
I would like to fix this issue, how to i assigne this issue to me?
There is already an open Pull Request addressing this issue, I would suggest to look for another issue to fix.
thanks but then, the status shouldn't be OPEN.
The PR hasnt been merged yet, so the issue is open. Perhaps, we can remove the help-wanted label, since the PR is already open.
Change:
display: inline; line-height: 1em; cursor: pointer; <del> } </del> <ins> } </ins>  No newline at end of file

Discussion:
! !
Good catch
Same for breakpoints. Looks like Visual Studio also doesn't grow the breakpoint and folding icons with the font size. Users can always use the Zoom feature, which zooms everything.
I removed the code that grows the folding icon gutter by font size to avoid the clipping that can bee seen in the second screenshot. We can add that again if we decide to grow the icons along with the font size
I can fix this by converting the icon sizing to ems, but it could possibly affect the pixel-perfect lines of the icon; I wouldn't be able to test it before the freeze (because my Retina screen lies to me about how other screens will alias it. I would need my desktop). Let's hold off until March on this one just to be safe and not compromise the icon.
Makes sense. As the breakpoints also don't grow/shrink I think we are consistent.
This is fixed now I guess. !
this actually happens when you change , which is different from
Change:
}); <ins> const CONTEXT_TOOLBAR_COMMAND_CENTER = ContextKeyExpr.equals('config.debug.toolBarLocation', 'commandCenter'); </ins> MenuRegistry.appendMenuItem(MenuId.CommandCenterCenter, { submenu: MenuId.DebugToolBar, title: 'Debug', icon: Codicon.debug, order: 1, <del> when: ContextKeyExpr.and(CONTEXT_IN_DEBUG_MODE, ContextKeyExpr.equals('config.debug.toolBarLocation', 'commandCenter')) </del> <ins> when: ContextKeyExpr.and(CONTEXT_IN_DEBUG_MODE, CONTEXT_TOOLBAR_COMMAND_CENTER) </ins> }); registerDebugToolBarItem(CONTINUE_ID, CONTINUE_LABEL, 10, icons.debugContinue, CONTEXT_DEBUG_STATE.isEqualTo('stopped'));

Discussion:
When there are multiple debug sessions, the dropdown action item shows in the debug toolbar here as a button that doesn't do anything. You can see it in the gif in We could just hide that item when this setting is set
I believe it focuses the Call Stack view but only when paused and when having the view active. Tho, I do agree that we shouldn't have it there to begin with.

Testing Followed the steps to turn on the debug toolbar with commandCenter options. However, when the debugging started, clicking the area around the directory name did not trigger 'search files'. (the blank space at the right side of 'vscode-python' in terms of the attached screenshot. I was able to trigger 'search files' only when pressing specifically on the directory name, in this case, 'vscode-python. ++ Nice feature by the way! <img width="983" alt="Screenshot 2023-09-26 at 10 42 11 AM" src=""<img width="512" alt="Screenshot 2023-09-26 at 11 02 46 AM" src=""
Change:
}, 'terminal.integrated.rightClickBehavior': { type: 'string', <del> enum: ['default', 'copyPaste', 'selectWord'], </del> <ins> enum: ['default', 'copyPaste', 'paste', 'selectWord'], </ins> enumDescriptions: [ nls.localize('terminal.integrated.rightClickBehavior.default', "Show the context menu."), nls.localize('terminal.integrated.rightClickBehavior.copyPaste', "Copy when there is a selection, otherwise paste."), <ins> nls.localize('terminal.integrated.rightClickBehavior.paste', "Paste on right click."), </ins> nls.localize('terminal.integrated.rightClickBehavior.selectWord', "Select the word under the cursor and show the context menu.") ], default: platform.isMacintosh ? 'selectWord' : platform.isWindows ? 'copyPaste' : 'default',

Discussion:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --With being merged, I'd now like to be able to directly paste after selection. The current behaviour with copyOnSelection = true and rightClickBehavior = copyPaste: text (text is then copied into clipboard) or left click, this clears the selection click again to paste With the proposed mode, copyOnSelection = true and rightClickBehavior = paste: text (text is then copied into clipboard) click, and text is pasted Why do I want this? Simple: it removes an extra click when pasting. This mirrors how PuTTY's pastes. The new Windows Terminal recently got support for this feature, too -
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.5 --- <!-- score: 0.483 --- <!-- score: 0.457 --<!-- potentialduplicatescomment --
To verify test on Windows and make sure that acts correct (as opposed to the default )
Change:
resolved "https://registry.yarnpkg.com/xterm-addon-unicode11/-/xterm-addon-unicode11-0.4.0-beta.3.tgz#f350184155fafd5ad0d6fbf31d13e6ca7dea1efa" integrity sha512-FryZAVwbUjKTmwXnm1trch/2XO60F5JsDvOkZhzobV1hm10sFLVuZpFyHXiUx7TFeeFsvNP+S77LAtWoeT5z+Q== <del> xterm-addon-webgl@0.13.0-beta.2: version "0.13.0-beta.2" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.13.0-beta.2.tgz#f58a7a3641ad7c8ac82dd24cfb0165656ed9ac1c" integrity sha512-98tX0BkpD402RoCO6SyikUXpzCn9/OQhlXsRmM/kRFCxMWWofStWTXzCPhN0MjIx2IdGueDjCmnShhidwihErg== xterm@4.20.0-beta.5: version "4.20.0-beta.5" resolved "https://registry.yarnpkg.com/xterm/-/xterm-4.20.0-beta.5.tgz#d707b0dcb477a554135fb767b24003fced079866" integrity sha512-KBWfk9UPBKRy662DVGGTZEcW1becEjYvlyWbn2hLj9h2gy6Q4EEEEbggJh8I7SGwdFizl+apHQGhEOZmFCA70w== </del> <ins> xterm-addon-webgl@0.13.0-beta.3: version "0.13.0-beta.3" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.13.0-beta.3.tgz#2b456c3105238e64b40a30787d6335f5f6f85abb" integrity sha512-DFGcXAolA0VTsOLIKcORxUOp/FTJdD/YiRzKVLARjgOycwVRKvW2L5Tge8Z7ysZ16sKfnV2vCXyonXYfUWozXw== xterm@4.20.0-beta.6: version "4.20.0-beta.6" resolved "https://registry.yarnpkg.com/xterm/-/xterm-4.20.0-beta.6.tgz#3ed87ba383a5cf44284098278f714df7113e3e3c" integrity sha512-xJd6vyOuYo4Ht/hTY3DyXGIj0U6kHjr2vWQ1lRmearo3t7QKf7uqOAAfTLeWt/g1P8qe/r0DnsNTeag6vI9RVw== </ins>

Discussion:
fixed in Need to update xterm to pull it in: !
What's a way to verify this issue on Windows?
With Powershell on Windows in the integrated terminal without a powerline font enabled: You should get something like this: <img width="62" alt="image" src="https://user-"
They seem a bit clipped to me: !
tracked in
Change:
}); } <del> protected override revealLine(lineNumber: number) { this.editor.revealLineInCenterIfOutsideViewport(lineNumber, ScrollType.Smooth); </del> <ins> protected override revealRange(range: Range) { this.editor.revealLineInCenterIfOutsideViewport(range.endLineNumber, ScrollType.Smooth); </ins> } hasFocus(): boolean {

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes (depends on language) <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.68.0 OS Version: Windows/Linux (does not matter for this bug) The problem is, if you set the to higher value like 10, vscode will starts to scroll the editor if i open a peek editor with the or similar commands (even if the editor would easily fit in the remaining area under the active line). I use 100 as a value for the surrounding lines to keep the cursor vertically in the middle, so i dont need to scroll when i move between lines, but this way when i open any peek editor, vscode will scrolls the active line to the top. If the peek editor can fit under the active line, it should not scroll the editor. I tested this with python, c++, and javascript, so this scrolling issue is not caused by extensions. It works exactly the same way with all of these languages. With javascript it occures even if vscode was started with . Steps to Reproduce: Place this in your (or use the settings editor) a file that has functions in it. the command. active line will be scrolled to the top, no matter what. !
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.68.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
The peek widget reveal the line it and that causes the shift. Tho, when we would reveal the line above it would cut off the button of the peek widget. We might need a way to reveal a line without honouring the surrounding lines setting
Change:
assertVariableResolve3(resolver, 'CURRENT_HOUR'); assertVariableResolve3(resolver, 'CURRENT_MINUTE'); assertVariableResolve3(resolver, 'CURRENT_SECOND'); <ins> assertVariableResolve3(resolver, 'CURRENT_DAY_NAME'); assertVariableResolve3(resolver, 'CURRENT_DAY_NAME_SHORT'); assertVariableResolve3(resolver, 'CURRENT_MONTH_NAME'); assertVariableResolve3(resolver, 'CURRENT_MONTH_NAME_SHORT'); </ins> }); });

Discussion:
I'm happy to see the new date-based snippet variables in v1.20.0. I would love to see some additional ones since I wanted to use this for generating journal templates. Something like this: CURRENTDAYNAME: Monday, Tuesday, ... CURRENTDAYNAMESHORT: Mon, Tue, ... CURRENTMONTHNAME: January, February, ... CURRENTMONTHNAMESHORT: Jan, Feb, ... Thank you.
A little more tricky because you might want to consider localisation settings...
Change:
constructor( @ISCMService scmService: ISCMService, @IContextKeyService contextKeyService: IContextKeyService, <ins> @IExtensionService extensionService: IExtensionService, </ins> @IInstantiationService instantiationService: IInstantiationService, @IConfigurationService private readonly configurationService: IConfigurationService, @IStorageService private readonly storageService: IStorageService,

Discussion:
I end up with all my repositories selected when going into an empty profile and out again: !
we figured out together that this reproduces easily by running the command to restart the extension host while having 1 repository selected. The underlying issue is that there are events fired from the extension host being disposed. This somehow has an impact on the state of the selected repositories and should probably be ignored or handled differently.
Change:
isFeatured = await this.instantiationService.invokeFunction(a => checkGlobFileExists(a, folders, walkthrough.featuredFor!, token.token)); } <ins> const iconStr = walkthrough.icon ?? extension.icon; </ins> const walkthoughDescriptor: IWalkthrough = { description: walkthrough.description, title: walkthrough.title,

Discussion:
Is there a way to use a codicon instead of an extension PNG? It feels out of place amongst built-in walkthroughs that can use a codicon. <img width="539" alt="CleanShot 2022-10-07 at 14 27 23 src="https://user-"cc since we chatted about this before
Conversation over at
Change:
codeEditor = codeEditorService.getActiveCodeEditor()!; } accessibleViewService.show(instantiationService.createInstance(AccessibilityHelpProvider, codeEditor)); <del> })); </del> <ins> }, EditorContextKeys.focus)); </ins> } }

Discussion:
Notice the "Define Keybinding" button: !
how did you get this to happen? I cannot repro
This happens when the keybinding editor is in the background
yeah, that's what I tried. !
might have been fixed via that styling pr where I a high z-index?
Can you check the dom? z-index shouldn't be the solution to this problem
i'm not able to reproduce so don't know if checking the dom would help
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
! I'm able to reproduce it consistently. Open keyboard shortcuts (JSON) While the editor has focus, press alt+F1 Notice that the dialog has the "define keybinding" button Also, I can only use alt+f1 once. After I close the dialog I have to reload VS Code. And I suggest to add the accessibility help command to the F1 command palette. I have a different keybinding on Alt+F1 and for testing this feature, it would be very helpful if you don't have to lookup/redefine a keybinding.
Still cannot reproduce but will keep trying it's in the command palette <img width="671" alt="Screenshot 2023-08-10 at 11 13 34 AM" src=""that's a different bug, thanks.
Oh sorry, I didn't see it! I can also investigate the context key issue if it doesn't reproduce for you. ~Actually, that is very weird, now I cannot reproduce anymore. But I was able to reproduce on two different devices (though with synced settings).~ It seems like it happens when something other than the editor has focus: ! When I now open accessibility help using the command palette, I get this: !
Oh, like the panel?
Yes
Change:
/** * An object that keeps information about how this extension can use language models. * <del> * @see {@link lm.sendChatRequest} </del> <ins> * @see {@link LanguageModelChat.sendRequest} </ins> */ readonly languageModelAccessInformation: LanguageModelAccessInformation; }

Discussion:
doesn't seem to exist in any of our 'es
Are you looking at an old version of
Oops, no it's right there
guess I'm not sure whether to link or just remove it since it's not the first entrypoint to making a request
<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history. If this was closed in a separate repo you can add the label directly, or comment .
Change:
import { ITreeRenderer, ITreeNode, IAsyncDataSource } from 'vs/base/browser/ui/tree/tree'; import { WorkbenchAsyncDataTree } from 'vs/platform/list/browser/listService'; import { IKeybindingService } from 'vs/platform/keybinding/common/keybinding'; <del> import { Event } from 'vs/base/common/event'; </del> <ins> import { Event, Emitter } from 'vs/base/common/event'; </ins> import { ExtensionsRegistry, IExtensionPointUser } from 'vs/workbench/services/extensions/common/extensionsRegistry'; import { SyncDescriptor } from 'vs/platform/instantiation/common/descriptors'; import * as icons from 'vs/workbench/contrib/remote/browser/remoteIcons';

Discussion:
Steps to Reproduce: remote explorer and view help links ( etc) under the viewlet for existing remote extensions. additional remote extensions and view the help link options again. Expected: links for the newer extensions show up in the lists. Actual: does not change. and reopening updates the list.