jiebi/CodeConvo huggingface dataset:
Change:
private _run(): void { let workerRequestIsValid; <del> if (!this.editor.hasWidgetFocus()) { // no focus (new nb cell, etc) </del> <ins> if (!this.editor.hasTextFocus()) { // no focus (new nb cell, etc) </ins> if (WordHighlighter.query === null) { // no previous query, nothing to highlight return;

Discussion:
Keeping this open as the main tracking issue as I keep an eye on error telemetry. Been quiet and haven't seen any entries in the errors site since early Feb with +
Closing this as fixed by the above linked PR's. Error telem has been quiet with no entries for ~4 weeks.

New cells being scrolled into view momentarily have widget focus, fire a model change event and picks up an editor selection with all values of .

There are countless entries for this kind of error !
/duplicate of
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 . See also our . Happy Coding!
Change:
} } <ins> class MergeItem implements QuickPickItem { get label(): string { return this.ref.name || ''; } get description(): string { return this.ref.name || ''; } constructor(protected ref: Ref) { } } </ins> interface Command { commandId: string; key: string;

Discussion:
It does not currently appear possible to merge local git branches in VS Code. Quite a common workflow is to have a "development" branch to develop new features on (or alternatively have feature specific branches). When the development is finished, the development branch is then merged into the "master" branch before release. This can be done via the integrated terminal, but as VS Code's git implementation is so wizzy, it would be great to be able to replicate this workflow using the GUI.
I can't believe there aren't more for this... what are the current alternatives? An extension, or have you guys set up a task for this?
+1, I think that feature might be considered priority for the git extension, it's a really nice implementation and with merging, would be perfect. No news?
It'd be lovely to be able to trigger a merge from the command palette, e.g. cmd + shift + p Select a branch to merge from via search-dropdown Any opportunity to avoid having to dip back into the command line is lovely. Thanks in advance!
Weird it is still not implemented and even weirder since we can create and change branch. It spoils the git integration in Code as if the feature was unfinished. We can still rely on built-in terminal or extension but it is not a consistent Code workflow Same for git stash
I also would like to see a Git Merge implemented eventually without going in the console. you might be interested to know that there's an open PR to which will hopefully land soon. There's actually also a PR for but changes were asked over a month ago and it wasn't done yet, so it might not land.
Fixed in
Change:
private hideTwistiesOfChildlessElements: boolean = false; private shouldRenderIndentGuides: boolean = false; <del> private renderedIndentGuides = new SetMap<ITreeNode<T, TFilterData>, HTMLDivElement>(); </del> private activeIndentNodes = new Set<ITreeNode<T, TFilterData>>(); private indentGuidesDisposable: IDisposable = Disposable.None;

Discussion:
Type: <bBug</b! VS Code version: Code - Insiders 1.72.0-insider (, 2022-09-23T05:17:37.024Z) OS version: Windows_NT x64 10.0. Modes: Sandboxed: Yes /assign <!-- generated by issue reporter --
/assign
Completely agree on this. Tree ident guide highlights are pretty awful throughout the hole app, except the editor itself because of the color lines.
Great find!
Change:
return; } <del> if (!options?.skipReveal) { this._webview.focusOutput(cell.id, this._webviewFocused); } </del> <ins> const focusElementId = options?.outputId ?? cell.id; this._webview.focusOutput(focusElementId, this._webviewFocused); </ins> cell.updateEditState(CellEditState.Preview, 'focusNotebookCell'); cell.focusMode = CellFocusMode.Output;

Discussion:
follow up after a notebook cell that displays multiple images down and select 'copy output to clipboard' on the last image :bug: the first image is selected and the notebook scrolls to reveal it
Change:
<!-- seperator    [ ]{0,3}([-*_][ ]{0,2}2){2,}[ t]*$n? --> <!-- list         [ ]{0,3}[*+-]([ ]{1,3}|t) --> <!-- both are folded together in the expression below --> <del> <string>(^|G)(?!s*$|#|[ ]{0,3}((([-*_][ ]{0,2}2){2,}[ t]*$n?)|([*+-]([ ]{1,3}|t)))|s*[.+?]:|&gt;)</string> </del> <ins> <string>(^|G)(?!s*$|#|[ ]{0,3}((([*_][ ]{0,2}2){2,}[ t]*$n?)|([*+-]([ ]{1,3}|t)))|s*[.+?]:|&gt;)</string> </ins> </dict> <key>raw_block</key> <dict>

Discussion:
! H1 and H2 are not highlighted. The preview is fine. Tested on VS Code 1.3.1 on OS X 10.11.6
I wanna give this one a try. Here is what I have achieved so far. !
Couple of updates on this: to highlight both lines at the same time, the way I was trying above doesn't look practical. It automatically highlights the current line assuming a match of the begin, until it finds a non matching end/while (Basically the line highlights, and if the next line isn't a '-{3,}' then the syntax goes back to normal mode. alt heading 2 syntax (just the -{3,} part) is conflicting with the rule meta.separator.markdown, which takes precedence and hence the issue. Would it be a better option to fix this conflict instead?
It doesn't work with 1.9.0 !
I believe this is as designed. Getting the TM grammar to highlight both the lines is tricky. If you refer to my previous comment, the first point: This would be confusing for the user. In simple terms, it means that as soon as a user starts typing, the line highlights, and goes back to normal syntax if the next line is neither of the alternate H1/H2 (---/===) text. What do you think?
Is it possible to let the line white and if a line starts with --- oder ===, then this one and the previous one switch to blue? That is the same behavior like in other editors.
Change:
], "configurationDefaults": { "[markdown]": { <del> "editor.unicodeHighlight.ambiguousCharacters": false, "editor.unicodeHighlight.invisibleCharacters": false </del> <ins> "editor.unicodeHighlight.ambiguousCharacters": false, "editor.unicodeHighlight.invisibleCharacters": false </ins> } } },

Discussion:
This problem still occurs even if you disable all extensions and occurs in both stable and insider. Create the following Fenced code blocks for LaTeX in Markdown file. latex documentclass{article} begin{document} Hello, LaTeX{}!! end{document} Then run (&lt;kbdCtrl+/&lt;/kbd) on the line with . You will get the following results: latex documentclass{article} begin{document} &lt;!-- Hello, LaTeX{}!! --end{document} The correct result is: latex documentclass{article} begin{document} % Hello, LaTeX{}!! end{document} ` Execute repeatedly !
Hi Did you save the file? I disabled all my extensions for vscode insider and can't reproduce this issue. Is this still happening for you?
Yes. And all extensions are disabled. Yes. The insider was updated to the following versions because has been available for updating. However, the problem continues to be reproduced.
Sorry I was saving file as latex extension so it worked. I tried with markdown and it doesn't work for me too. This is a verified bug now.
Hi, I'm having the same issue. I'm new to the codebase. Can I try to solve this issue?
I had previously submitted similar issue. It may help to solve this issue. See
thanks for this, It will help me solve this issue. I am working on this.
Hey I made the PR. Could you please check it?
Change:
{ "name": "code-oss-dev", "version": "1.86.0", <del> "distro": "2124c72ef2dcad044b30293f7548a7cc63f113fe", </del> <ins> "distro": "bfe80ecb51ea0f99e6c250ba625938dcc55461c1", </ins> "author": { "name": "Microsoft Corporation" },

Discussion:
A possible regression from
Addressed by , Electron 27-x-y PR has not merged in I will backport it for endgame.
Backport created
Change:
namespace CommandConfiguration { export namespace PresentationOptions { <del> const properties: MetaData<Tasks.PresentationOptions, void>[] = [{ property: 'echo' }, { property: 'reveal' }, { property: 'focus' }, { property: 'panel' }, { property: 'showReuseMessage' }]; </del> <ins> const properties: MetaData<Tasks.PresentationOptions, void>[] = [{ property: 'echo' }, { property: 'reveal' }, { property: 'focus' }, { property: 'panel' }, { property: 'showReuseMessage' }, { property: 'clear' }]; </ins> interface PresentationOptionsShape extends LegacyCommandProperties { presentation?: PresentationOptions;

Discussion:
To reproduce: Observe: terminal is not cleared. To make this work we need to add the clear here: Sorry for not catching this when reviewing.
Reopening until this is merged into release.
Following the steps above, I'm still seeing the task output left in the terminal with the final message "Terminal will be reused by tasks, press any key to close it.". I assume this is what should be cleared. VSCode version: Version: 1.29.0-insider Commit: Date: 2018-11-09T14:55:36.370Z
Change:
let ctrlPressed = false; let altPressed = false; let hasLoadedImage = false; <del> let consumeClick = false; </del> <ins> let consumeClick = true; let isActive = false; </ins> // Elements const container = document.body;

Discussion:
Repo an image to the side of a text editor with the text editor focused click into the image editor to focus it Bug The first click ends up zooming the image. Clicking should only zoom when the editor is already focused
Here's the relevant code about click handling in the image preview:
If focus is required for zoom, then the cursor when hovering over the image preview should be the default arrow cursor when unfocused, currently it is the zoom-in cursor. Also zooming with the mouse wheel should not be allowed when unfocused. Thoughts?
Fixed by
I'm still seeing the first click zoom. Steps: a typescript file. a gif gif to the right so that both typescript and gif are visible and side by side in typescript. in gif Expected: no zoom Actual: it zooms on the click in the gif in (5).
I'm not able to reproduce. Have tried on both insiders 1.40.0 and OSS. Does this only occur with gifs for you?
I can repo this. You may need to click back and forth multiple times trigger the error
I'm still not able to. Will try more tomorrow. A possible cause might be that the event is fired before the event on the first click. This could be tested by checking the order of execution for the corresponding event handlers in . I'll do it if I manage to reproduce the bug.
Change:
id: 'topLevelRemoteOpen', title: localize('gettingStarted.topLevelRemoteOpen.title', "Connect to..."), description: localize('gettingStarted.topLevelRemoteOpen.description', "Connect to remote development workspaces."), <del> when: '!isWeb && showRemoteStartEntry', </del> <ins> when: '!isWeb', </ins> icon: Codicon.remote, content: { type: 'startEntry',

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.80.1 (system setup) OS Version: WindowsNT x64 10.0. Commit: Date: 2023-07-12T17:22:07.651Z Electron: 22.3.14 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 vscode a couple of seconds the new "Connect to..." link button on the welcome page is delayed resulting in a really annoying change of the height for the "Start" section and, during the working, a missclick on the wrong recent project. a. remove the button b. fix the height of the "Start" section c. make the button link disable at first, in case something has to load before d. improve the a/b testing expirience, if i am in one of them!!

vsliv368: vsreu685: python383: vspor879: vspor708: vspor363: vswsl492cf: vslsvsres303: vserr242cf: pythontb: vsjup518: pythonptprofiler: vshan820: vstes263: vscod805: binariesv615: bridge0708: bridge0723: vsaa593cf: pythonvs932: py29gd2263cf: vscaat: vsclangdc: c4g48928: dsvsc012cf: pynewext54: azure-devsurveyone: 3biah626: pyind779: : pythonsymbol12: showlangstatbar: vsctsb: pythonms35: : pythonfmttext: pythoncmv: fixshowwlkth: showindicator: pythongtdpath: i26e3531: pythonnosm12tcf: pythonidxpt: pythonnoceb: : dsvsc013:
Change:
for (let required of typeDeclaration.required) { let value = result.configures[required]; if (value) { <del> label = label + ' ' + value; </del> <ins> label = label + ': ' + value; </ins> break; } }

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: 1.67.1 OS Version: macOS 12.3.1 Steps to Reproduce: a new TypeScript extension using and open it in VS Code. Ctrl/Cmd+P and and type "task " that the task for watch is labeled "npm watch" (The task has no in ), while if you were to add it by choosing to configure it, it would have been generated with a label of "npm: watch".
A few years ago we improved the performance of the task quick pick by delaying going to extensions for tasks until a task actually needs to be run. This means that properties that aren't required to be in , like , are made up by the task system instead of fetched from the extension. Here's how we make up a task label: Here's where the npm extension provides the task name (label becomes for extension provided tasks: After the task has been run, then we'll save the actual task label and it will be shown in the quick pick next time. happy to discuss with you if you want!
do we intend to change this so that the extension task name is used on first run?
there isn't a perfect solution here. It was too expensive to fetch the actual task label from the extension which is why we're in this state. I think we could either: Change how we make up the task label in the hopes that we can get closer to what most tasks end up doing. Do nothing, the discrepancy resolves after first run and was the price we had to pay for better performance.

I'm leaning slightly toward the first option since this this is one of the first things a new user of tasks might see. There's always the risk then that users might notice the change and be unhappy with it. Given that the change is just to add a in an existing string it's probably worth doing.
Change:
try { const existing = this.profiles.find(p => p.name === name || p.id === id); if (existing) { <del> return existing; </del> <ins> throw new Error(`Profile with ${name} name already exists`); </ins> } const profile = toUserDataProfile(id, name, joinPath(this.profilesHome, id), this.profilesCacheHome, options, this.defaultProfile);

Discussion:
Steps to Reproduce: Machine A - Create a profile named Empty and sync Machine B - Turn on Sync and wait until Empty profile is synced on to this machine. Machine B - Quit VS Code - to make sure it is not syncing actively. Machine A - Delete Empty Profile and wait a minute. Create Empty named profile again and sync Machine B - Open VS Code and wait for sync to run. Machine B - Deletes Empty profile and syncs which causes Empty profile to be deleted on Machine A. This scenario keeps happening to me and appears to happen when I revisit a different machine environment. It just reproduced this morning. On my primary machine, I set up a new profile called "Notes". I did all sorts of customization things were working fine until I opened my mac (secondary machine) for the first time in a few weeks. Looking at the sync longs, it the mac sync overrode my profiles on the remote which then was synced down and removed my profile on my primary machine.
Not sure the cause, are we syncing profiles differently to other resources? Also if we are not yet tracking the history of an entire deleted profile we should probably be doing that, and maybe requiring a confirmation when a local profile is deleted via a sync since it's so destructive. Marked important as it's a data loss issue.
The same thing happened to me. I have two devices, and on each one of them I have a couple of profiles and I'm using "default" on both. Now I did following: PC, enable Settings Sync macOS, enable Settings Sync Came back to PC. The profiles from macOS showed up in VS Code. In an hour, all of a sudden all my settings/keybindings werechanged in the default profile Here are the logs From what I read they got deleted. Not it's default profile.
So this might be a bug? I thought it was a design choice to discourage me from reaching around the API into unexposed configuration files? I was initially attempting to share/bundle/distribute vscode Profile configs/keybindings/etc along with my repo/code - but when I clone down the repo to a fresh location, and open vscode (mounted onto the respective and from my repo) it immediately deletes all my Profiles and configs that I committed to said dirs from my repo . I assume it's unhappy because the configs are not it's own?

I'm aware that what I'm trying to do here is probably way out of scope & unsafe - I'm just ‍experimenting - which is why I then opted to just write an extension (still in progress / not published) to get around all the (probably more security conscious) API limitations
Change:
{ "command": "git.stashPopLatest", "when": "config.git.enabled && gitOpenRepositoryCount != 0" <ins> }, { "command": "git.stashApply", "when": "config.git.enabled && gitOpenRepositoryCount != 0" }, { "command": "git.stashApplyLatest", "when": "config.git.enabled && gitOpenRepositoryCount != 0" </ins> } ], "scm/title": [

Discussion:
I've attempted to find any other requests for this but didn't seem to see any. At the moment the CVS context menu shows: ! Only "Pop latest stash" and "Pop stash..." are visible. Is it possible to change the default stash behaviour to "apply" rather than "pop"? Additionally, is it possible to add two lines under "Pop stash..." for the same actions, just using apply: Apply latest stash Apply stash... I just lost a few hours and considerable amount of hair when a popped stash was deleted. I then had to sift through doing on each . Having "Apply stash..." easily accessible might be nicer.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.676 --<!-- potentialduplicatescomment --
I suggest to simply add and commands.
is anyone working on this, if not, I'll like to pick it up as a
looks like it might already be done in
yeah, just confirmed, Thanks. If I may ask, is there any rule around tagging an issue that is being worked on as it would be multiple efforts if I happen to have started it without anyone's knowledge. I've been scouting for an issue with no assignee to work on :-( Thanks for the catch tho!
Change:
collector.setAsIncomplete(); } <del> queryUrl = `https://api.npms.io/v2/search/suggestions?size=${LIMIT}&q=${encodeURIComponent(currentWord)}`; </del> <ins> queryUrl = `https://registry.npmjs.org/-/v1/search?size=${LIMIT}&text=${encodeURIComponent(currentWord)}`; </ins> return this.xhr({ url: queryUrl, agent: USER_AGENT

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. --Hi So I noticed that the autocomplete is slow to update or can sometimes return wrong/outdated information. For example: if a package releases a patch / new version, it can take hours, maybe days until the autocompletion also suggests that version. My second concern about this is that it's actually using which is not run by npm and they have a separate which users are not aware of when using this VS Code extension. Source code From a privacy policy perspective / GDPR and also reliability issues it seems appropriate to remove all usage of this third-party API and only use npm's. Relevant past issues about npms from this repository (I found many more in other repositories):
To verify, check that code completion in dependencies of work as expected. run VSCode in a environment where is not on the path, and use hovers over dependencies of . as dependency and verify that the hover shows the actual latest version (currently 15)
Change:
override run(accessor: ServicesAccessor, query?: string): void { const quickChatService = accessor.get(IQuickChatService); <del> quickChatService.toggle(id, query ? { query } : undefined); </del> <ins> quickChatService.toggle(id, query ? { query, selection: new Selection(1, query.length + 1, 1, query.length + 1) } : undefined); </ins> } }; }

Discussion:
Originally posted by in
Marking this as debt since we'll likely be removing that command after terminal moves onto a different one in I'll change to bug if we're keeping it.
Repro: Set Hit ctrl+i in terminal, type something ctrl+` to focus terminal (don't close quick chat) ctrl+i type something is deleted
Change:
return new Uint8Array(0); } <del> if (this.experimentalSave && !this.isBrowser) { return this.serializeViaWorker(data); } </del> const serialized = serializeNotebookToString(data); return new TextEncoder().encode(serialized); } <del> private async startWorker() { if (this.disposed) { throw new Error('Serializer disposed'); } if (this.worker) { return this.worker; } const { Worker } = await import('node:worker_threads'); const outputDir = getOutputDir(this.context); this.worker = new Worker(vscode.Uri.joinPath(this.context.extensionUri, outputDir, 'notebookSerializerWorker.js').fsPath, {}); this.worker.on('exit', (exitCode) => { if (!this.disposed) { console.error(`IPynb Notebook Serializer Worker exited unexpectedly`, exitCode); } this.worker = undefined; }); this.worker.on('message', (result: { data: Uint8Array; id: string }) => { const task = this.tasks.get(result.id); if (task) { task.complete(result.data); this.tasks.delete(result.id); } }); this.worker.on('error', (err) => { if (!this.disposed) { console.error(`IPynb Notebook Serializer Worker errored unexpectedly`, err); } }); return this.worker; } private async serializeViaWorker(data: vscode.NotebookData): Promise<Uint8Array> { const worker = await this.startWorker(); const id = generateUuid(); const deferred = new DeferredPromise<Uint8Array>(); this.tasks.set(id, deferred); worker.postMessage({ data, id }); return deferred.p; } </del> } <del> function getOutputDir(context: vscode.ExtensionContext): string { const main = context.extension.packageJSON.main as string; return main.indexOf('/dist/') !== -1 ? 'dist' : 'out'; } </del>

Discussion:
This seems to be caused by following change which brought module and Webpack failed compiling this. Therefore I am reverting this commit.
The associated PR is