jiebi/CodeConvo huggingface dataset:
Change:
abstract renderChanges(response: ReplyResponse): Promise<Position | undefined>; <ins> move?(next: boolean): void; </ins> abstract hasFocus(): boolean; getWholeRangeDecoration(): IModelDeltaDecoration[] {

Discussion:
open inline chat have it make multiple hunks (hint: ask it to use a util that needs to be imported) there is no gesture to visit all hunks except for accepting/discarding them... This can also help with accessibility when using the move
To verify let inline chat make multiple changes, e.g ask it to import a util or let is change the label of two actions make sure the inline chat status says "N changes" (n=2) select and to navigate between the changes
Change:
export const BetterMergeId = new ExtensionIdentifier('pprice.better-merge'); <del> export function getMaliciousExtensionsSet(manifest: IExtensionsControlManifest): Set<string> { const result = new Set<string>(); if (manifest.malicious) { for (const extension of manifest.malicious) { result.add(extension.id); } } return result; } </del> export function getExtensionDependencies(installedExtensions: ReadonlyArray<IExtension>, extension: IExtension): IExtension[] { const dependencies: IExtension[] = []; const extensions = extension.manifest.extensionDependencies?.slice(0) ?? [];

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. --When installing an extensions with , users can freely install extensions which are malicious, which is not possible from the UI. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- 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.69.0 OS Version: macOS 13 Steps to Reproduce: your 's to . a terminal inside of VS Code The CLI either refuses to install these extensions or warns the user.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.69.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Sorry, mistyped the version by one patch release, all fixed now.
Can you please let me know which extension you are trying to install that is malicious and VS Code allows it from CLI?
that would be any extension list that I tried and exists in the Marketplace, for example installs just fine although not allowing me to install via the UI <img width="725" alt="image" src="https://user-"
Change:
private readonly _providers: ISemanticSimilarityProvider[] = []; <ins> constructor(@ILogService private readonly logService: ILogService) { } </ins> isEnabled(): boolean { return this._providers.length > 0; }

Discussion:
I see the second entry being selected shortly after the recent results appear: ! My settings:
I did extension bisect and the issue is caused by copilot chat extension. Here is the profile you can use to repro this bug -
Change:
export const mediaFileExtensions = new Map<string, MediaKind>([ // Images <ins> ['avif', MediaKind.Image], </ins> ['bmp', MediaKind.Image], ['gif', MediaKind.Image], ['ico', MediaKind.Image],

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 <!-- 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/Linux Steps to Reproduce: Drag AVIF image from MacOS Finder / KDE Dolphin to VS code markdown image copied to workspace, and to be to markdown result: AVIF file not copied, and is to markdown
<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to 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 . Happy Coding!
Hi I am working in this feature. Please let me know if any concerns.
Hi again Thia happened to be faster than I thought! Please have a look at my proposal on and please don't hesitate to tell me if you have any concern. Best, /Bruno
<!-- -a7ce-58b9-b1f9- --This feature request has not yet received the 20 community it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our . Happy Coding!
<!-- -b8df-69ca-c20a- --:slightlyfrowningface: 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 . Happy Coding!
Change:
import { CancellationToken } from 'vs/base/common/cancellation'; import { URI } from 'vs/base/common/uri'; import { ITelemetryService } from 'vs/platform/telemetry/common/telemetry'; <del> import { IWorkspaceContextService, WorkbenchState } from 'vs/platform/workspace/common/workspace'; </del> <ins> import { IWorkspaceContextService } from 'vs/platform/workspace/common/workspace'; </ins> import { IWorkspaceTagsService } from 'vs/workbench/contrib/tags/common/workspaceTags'; import { getErrorMessage } from 'vs/base/common/errors'; <ins> const SelectProfileSubMenu = new MenuId('SelectProfile'); </ins> export class UserDataProfilesWorkbenchContribution extends Disposable implements IWorkbenchContribution { private readonly currentProfileContext: IContextKey<string>;

Discussion:
We have noticed in the user study that users interact with profiles in different ways and they do not find the indication of active profile super useful. We should also be aware of all the Menus that profiles are present in right now in addition to the Profile activity bar item are confusing. Main menu Account activity bar item Gear activity bar item
After discussing in today's stand up we agreed upon having its own space for profiles and therefore we wanted to show profile indicator and drop the actions in accounts and gear menus. We shall investigate on how to make this profile indicator appealing to users -
Looks great -verified
Change:
} if (filepath.startsWith(this.inMemoryResourcePrefix)) { <del> const parts = filepath.match(/^^/([^/]+)/(.+)$/); </del> <ins> const parts = filepath.match(/^^/([^/]+)/([^/]*)/(.+)$/); </ins> if (parts) { <del> const resource = vscode.Uri.parse(parts[1] + '://' + parts[2]); </del> <ins> const resource = vscode.Uri.parse(parts[1] + '://' + (parts[2] === this.emptyAuthority ? '' : parts[2]) + '/' + parts[3]); </ins> return this.bufferSyncSupport.toVsCodeResource(resource); } }

Discussion:
Request refactorings, and extract to a function at the top-level. Expected: no crash Actual: I'm not sure on the specific version, but in the last 9 days or so we started seeing the following crash:
Actually I found this while trying to repro a different bug. The one I was looking to repro had the following stack trace: <details<summaryOriginal Stack Trace </summary</details I think this actually only repros when working in an anonymous buffer in VS Code. When you ask for a refactoring on an anonymous buffer, we come back with the same buffer name However, VS Code pops up a notification that "You cannot rename this element" and creates a new buffer with the contents. This confuses TSServer a lot, and makes it fail over and over again.
I initially read the last part of the issue title as “thanks, language service” and thought the sarcasm was appropriate.
I may steal that in the future :D
can you transfer this issue to VSCode if appropriate?
Did this just start happening with the latest insiders?
Possible introduced with
Yeah, I believe it didn't repro on a 2 week old nightly, but I can't 100% confirm.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
Change:
resolve(button); } })); <del> quickPick.onDidTriggerItemButton(async (e) => { </del> <ins> disposables.add(quickPick.onDidTriggerItemButton(async (e) => { </ins> if (isKernelSourceQuickPickItem(e.item) && e.item.documentation !== undefined) { const uri = URI.isUri(e.item.documentation) ? URI.parse(e.item.documentation) : await this._commandService.executeCommand(e.item.documentation); void this._openerService.open(uri, { openExternal: true }); } <del> }); </del> <ins> })); </ins> disposables.add(quickPick.onDidAccept(async () => { resolve(quickPick.selectedItems[0]); }));

Discussion:
Note that quick pick instances and their events are disposables. Noticed a few cases of missing:
Change:
import { Position } from 'vs/editor/common/core/position'; import { Selection } from 'vs/editor/common/core/selection'; import { deserializePipePositions, serializePipePositions, testRepeatedActionAndExtractPositions } from 'vs/editor/contrib/wordOperations/test/wordTestUtils'; <del> import { CursorWordEndLeft, CursorWordEndLeftSelect, CursorWordEndRight, CursorWordEndRightSelect, CursorWordLeft, CursorWordLeftSelect, CursorWordRight, CursorWordRightSelect, CursorWordStartLeft, CursorWordStartLeftSelect, CursorWordStartRight, CursorWordStartRightSelect, DeleteWordEndLeft, DeleteWordEndRight, DeleteWordLeft, DeleteWordRight, DeleteWordStartLeft, DeleteWordStartRight, CursorWordAccessibilityLeft, CursorWordAccessibilityLeftSelect, CursorWordAccessibilityRight, CursorWordAccessibilityRightSelect } from 'vs/editor/contrib/wordOperations/wordOperations'; </del> <ins> import { CursorWordEndLeft, CursorWordEndLeftSelect, CursorWordEndRight, CursorWordEndRightSelect, CursorWordLeft, CursorWordLeftSelect, CursorWordRight, CursorWordRightSelect, CursorWordStartLeft, CursorWordStartLeftSelect, CursorWordStartRight, CursorWordStartRightSelect, DeleteWordEndLeft, DeleteWordEndRight, DeleteWordLeft, DeleteWordRight, DeleteWordStartLeft, DeleteWordStartRight, CursorWordAccessibilityLeft, CursorWordAccessibilityLeftSelect, CursorWordAccessibilityRight, CursorWordAccessibilityRightSelect, DeleteInsideWord } from 'vs/editor/contrib/wordOperations/wordOperations'; </ins> import { withTestCodeEditor } from 'vs/editor/test/browser/testCodeEditor'; import { CoreEditingCommands } from 'vs/editor/browser/controller/coreCommands'; import { ViewModel } from 'vs/editor/common/viewModel/viewModelImpl';

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --The 'deleteWordLeft' command cannot delete letters on right side of the cursor. We want new function which can delete the whole word. (We submit this issue formally. Sorry.)
To verify, please look for a "Delete Word" action that you can bind to a keybinding if you wish to. The action will delete the current word under the cursor (both to the left and to the right of the cursor) and will delete any trailing whitespace.
I've checked. I could find the "Delete Word" action and bind a keybinding to it. The function works properly. Thank you!
Change:
if (options.env) { shellLaunchConfig.env = options.env; } <ins> // Conpty doesn't do linefeeds in an expected way. Force winpty unless the user has requested otherwise. shellLaunchConfig.forceWinpty = !this.configurationService.getValue('tasks.terminal.windowsAllowConpty'); </ins> return shellLaunchConfig; }

Discussion:
Steps to reproduce: clone open a terminal Debug viewlet Launch client Observe that building never finishes Now switch the terminal to the npm: watch task Observe: building finished. Looks like the terminal is not delivering any output as long as the view is not visible.
are there any differences on when onLineData occurs in the terminal with conpty?
discovered a new issue
Change:
export const KEYBINDINGS_EDITOR_COMMAND_COPY_COMMAND = 'keybindings.editor.copyCommandKeybindingEntry'; export const KEYBINDINGS_EDITOR_COMMAND_SHOW_SIMILAR = 'keybindings.editor.showConflicts'; export const KEYBINDINGS_EDITOR_COMMAND_FOCUS_KEYBINDINGS = 'keybindings.editor.focusKeybindings'; <ins> export const KEYBINDINGS_EDITOR_SHOW_DEFAULT_KEYBINDINGS = 'keybindings.editor.showDefaultKeybindings'; export const KEYBINDINGS_EDITOR_SHOW_USER_KEYBINDINGS = 'keybindings.editor.showUserKeybindings'; </ins> export const FOLDER_SETTINGS_PATH = join('.vscode', 'settings.json'); export const DEFAULT_SETTINGS_EDITOR_SETTING = 'workbench.settings.openDefaultSettings';

Discussion:
<!-- Do you have a question? Please ask it on --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.20.0-ins OS Version: win7x64 In we have a column called "Source". How about to create a filter called "source:user", so as "source:default", etc... ? !
any code-pointer to start on this?
Here it is -
hey! are you working on this? If not, I can take this.
I'm already started on this. Thanks for asking though.
sumitted a PR here. Care to comment / review.
Change:
resolve(); } } <ins> private onTypesInstallerInitializationFailed() { vscode.window.showWarningMessage(localize('typesInstallerInitializationFailed', "Could not install typings files for JS/TS language features. Please ensure that NPM is installed")); } </ins> }

Discussion:
VSCode Version: Code 1.10.0 (, 2017-03-01T17:09:34.031Z) OS Version: Linux x64 4.5.5-300.fc24.x86_64 Extensions: none Steps to Reproduce: -Does not show type-specific proposals There is a single file in the cache: with just the empty object in it. /cc
The root cause seems to be that is not installed. I'm investigating this on other platforms as well
Two issues are tracking this on the TypeScript side: No error being generated: Add error message to typings install failure:
With TS 2.2.2 insiders we just picked up, an error notification is now generated in this case. It still does not have a good user facing message about not having npm installed. That is being tracked by
We don't handle the new event from the TS Server yet.
Change:
exports.code = [ createModuleDescription('vs/code/electron-main/main'), <del> createModuleDescription('vs/code/node/cli/main'), createModuleDescription('vs/code/node/cli/cliProcessMain', ['vs/code/node/cli/main']), </del> <ins> createModuleDescription('vs/code/node/cli'), createModuleDescription('vs/code/node/cliProcessMain', ['vs/code/node/cli']), </ins> createModuleDescription('vs/code/electron-sandbox/issue/issueReporterMain'), createModuleDescription('vs/code/node/sharedProcess/sharedProcessMain'), createModuleDescription('vs/code/electron-sandbox/processExplorer/processExplorerMain')

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/No <!-- 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: Latest Insiders. OS Version: Mac Steps to Reproduce: Run the VS Code-Jupyter tests on CI and it fails. Here are the logs where we use the VS Code test cli to download VS Code and install the Python extension Basically it looks like we cannot install any extension into VS Code I have tried this locally as well and the same code falls over Here is the code used to isntall the extension here are the logs
If i try this manually in the terminal this fails Here is the same CLI with the stable version of VS Code
Thanks, I was not aware that upstream modules depend on the path to our CLI. I will revert that part of the move.
Change:
'builtin-extensions-dir': { type: 'string' }, 'list-extensions': { type: 'boolean', cat: 'e', description: localize('listExtensions', "List the installed extensions.") }, 'show-versions': { type: 'boolean', cat: 'e', description: localize('showVersions', "Show versions of installed extensions, when using --list-extensions.") }, <del> 'category': { type: 'string', cat: 'e', description: localize('category', "Filters installed extensions by provided category, when using --list-extensions."), args: 'category' }, </del> <ins> 'category': { type: 'string', allowEmptyValue: true, cat: 'e', description: localize('category', "Filters installed extensions by provided category, when using --list-extensions."), args: 'category' }, </ins> 'install-extension': { type: 'string[]', cat: 'e', args: 'ext-id | path', description: localize('installExtension', "Installs or updates an extension. The argument is either an extension id or a path to a VSIX. The identifier of an extension is '${publisher}.${name}'. Use '--force' argument to update to latest version. To install a specific version provide '@${version}'. For example: 'vscode.csharp@1.2.3'.") }, 'pre-release': { type: 'boolean', cat: 'e', description: localize('install prerelease', "Installs the pre-release version of the extension, when using --install-extension") }, 'uninstall-extension': { type: 'string[]', cat: 'e', args: 'ext-id', description: localize('uninstallExtension', "Uninstalls an extension.") },

Discussion:
Does this issue occur when all extensions are disabled?: Yes VS Code Version: 1.77.3 OS Version: Ubuntu 20.04.5 Steps to Reproduce: (incorrect category, should be themes) outputs: suggestion: Get warning:
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
Change:
pathName = '/' + pathName; } <del> return encodeURI('file://' + pathName).replace(/#/g, '%23'); </del> <ins> /** @type {string} */ let uri; if (pathName.startsWith('//')) { uri = encodeURI('file:' + pathName); } else { uri = encodeURI('file://' + pathName); } return uri.replace(/#/g, '%23'); </ins> }; //#endregion

Discussion:
VSCode Version:1.25 OS Version:Windows Server 2012r2 / Win 10 Steps to Reproduce: 1.25 to an Network share. create an .data folder to make it an portable .exe runs as background process in task manager. No Gui is shown on Fileserver from local Filesystem works as expected with gui in portable mode. Does this issue occur when all extensions are disabled?: Yes
Just found out it happens only if started from UNC path. If you map a drive it works as expected.
/duplicate
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues . See also our guidelines. Happy Coding!
isn’t a duplicate of this issue
Thanks my bad.
Can you go through this checklist, so we figure out what goes wrong? Here is a checklist to find out more about the freeze/slow/crash [ ] it reproduces with extensions disabled ( from the command line - NOT the integrated terminal of Code) if it does not reproduce with extensions disabled, you can stop testing and report this! [ ] it was not happening in the previous stable release ) [ ] there is no suspicious output when running from the command line () [ ] there is no suspicious output in the window itself (Help Console) [ ] it reproduces on Windows, Linux and Mac [ ] it reproduces after deleting and (backup first! see below for paths) [ ] it reproduces when opening empty ( from the command line) [ ] it reproduces opening any folder [ ] it reproduces opening any file [ ] it reproduces when only having a single window open [ ] it reproduces by just using Code without external tools running on the same folder [ ] it reproduces from a workspace that is not under Git version control [ ] it reproduces independently if a file is opened or not after startup [ ] it reproduces when running with GPU disabled () [ ] it reproduces when being offline [ ] it reproduces when disabling the file watching (set to ) [ ] it reproduces after uninstalling and reinstalling [ ] it reproduces after deleting the application data directory (backup first!

see below for paths) [ ] I have not played around with permissions or ran Code as administrator [ ] I am seeing a single CPU process spin high (please share the full command line arguments) [ ] I am seeing Code consuming lots of memory in a short time Application Data Directory for VS Code: Windows: Mac: Linux: Application Data Directory for VS Code Insiders: Windows: Mac: Linux:
Change:
"pickerGroup.foreground": "#75715E", "input.background": "#414339", "inputOption.activeBorder": "#75715E", <del> "focusBorder": "#75715E", </del> <ins> "focusBorder": "#99947c", </ins> "editorWidget.background": "#1e1f1c", "debugToolBar.background": "#1e1f1c", "diffEditor.insertedTextBackground": "#4b661680", // middle of #272822 and #a6e22e

Discussion:
+F to open the editor find widget. Focus should be on the find input box. case-sensitive search. to the case-sensitive search button. :bug: Keyboard focus is on that element, but it's not clear that keyboard focus is on that element. !
works fine on my machine with Light+ and Dark+ theme, what theme are you using? ! !
Thanks! I guess the problem depends on the theme. The problem seems to occur on at least Quiet Light, Solarized Light, and Monokai.
Can confirm the the issue in those themes on my windows machine. I never sent a pull request to vscode but that seems easy to solve, the question is what highlight color would fit best each theme, i might take a look later unless there are some rules about how to set some of the theme colors... the colors effecting this seem to be "focusBorder" and "inputOption.activeBorder" I would love to offer some new colors later today/tomorrow and pull request them
I propose giving a bit of contrast to the "focusBorder" I think that focus border should have a bit of contrast from background as this is marking elements the user needs to spot quickly, even in themes with less contrast light quiet light i think this is best to increase contrast in those areas, this is only showing for elements put in focus and wont change the feeling of the theme by much. Here are the new colors i propose and will commit and pull request later if those look acceptable For Quiet Light: ! For Solarized Light: ! For Monokai: !