jiebi/CodeConvo huggingface dataset:
Change:
} } export class ManagedResolvedAuthority { <ins> public static isManagedResolvedAuthority(resolvedAuthority: any): resolvedAuthority is ManagedResolvedAuthority { return resolvedAuthority && typeof resolvedAuthority === 'object' && typeof resolvedAuthority.makeConnection === 'function' && (resolvedAuthority.connectionToken === undefined || typeof resolvedAuthority.connectionToken === 'string'); } </ins> constructor(public readonly makeConnection: () => Thenable<vscode.ManagedMessagePassing>, public readonly connectionToken?: string) { if (typeof connectionToken !== 'undefined') { validateConnectionToken(connectionToken);

Discussion:
Version: 1.79.0-insider Commit: Date: 2023-05-16T05:23:57.470Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Linux x64 5.14.0-1048-oem open a wsl or a dev containers window fails with a notification: Could not fetch remote environment. this.c.makeConnection is not a function
I see the same error, yesterdays version worked fine.
and it is fixed: it seems they rolled back to yesterdays version Version: 1.79.0-insider (user setup) Commit: Date: 2023-05-15T05:20:50.327Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.

ERR this.factory.makeConnection is not a function: TypeError: this.factory.makeConnection is not a function at ExtHostManagedSockets.$openRemoteSocket (c:Usersmartinaeworkspacesvscodeoutvsworkbenchapicommon) at RPCProtocol.doInvokeHandler (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at RPCProtocol.invokeHandler (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at RPCProtocol.receiveRequest (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at RPCProtocol.receiveOneMessage (c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon) at c:Usersmartinaeworkspacesvscodeoutvsworkbenchservicesextensionscommon at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at PrivateEventDeliveryQueue.deliver (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasepartsipccommon) at c:Usersmartinaeworkspacesvscodeoutvsworkbenchapinode at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at PrivateEventDeliveryQueue.deliver (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasecommon) at (c:Usersmartinaeworkspacesvscodeoutvsbasepartsipccommon) at MessagePortMain.<anonymous(c:Usersmartinaeworkspacesvscodeoutvsworkbenchapinode) at (node:events:513:28) at (node:electron/js2c/utilityinit:2:367)
for me now the forwarded ports on remote hosts are broken:
Change:
// Python style error: File "<path>", line <line> { urlFormat: 'File "{0}"', linkCellStartOffset: 5 }, { urlFormat: 'File "{0}", line {1}', line: '5', linkCellStartOffset: 5 }, <ins> // Unknown tool #200166: FILE  <path>:<line>:<col> { urlFormat: ' FILE  {0}', linkCellStartOffset: 7 }, { urlFormat: ' FILE  {0}:{1}', line: '5', linkCellStartOffset: 7 }, { urlFormat: ' FILE  {0}:{1}:{2}', line: '5', column: '3', linkCellStartOffset: 7 }, </ins> // Some C++ compile error formats { urlFormat: '{0}({1}) :', line: '5', linkCellEndOffset: -2 }, { urlFormat: '{0}({1},{2}) :', line: '5', column: '3', linkCellEndOffset: -2 },

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.84.2 (user setup) OS Version: WindowsNT x64 10.0. Copied from VSCode: Version: 1.84.2 (user setup) Commit: Date: 2023-11-09T10:51:52.184Z Electron: 25.9.2 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: WindowsNT x64 10.0. Steps to Reproduce: at least one space in the FILE path, in my case, in the username I created... Click doesn't function due to the space. If I remove the space in terminal.integrated.wordSeparators, the beginning of the line, the "FILE " gets copied as well, ruining the entire Ctrl + Click functionality. I've been searching online to change the Windows username, but all the required steps are extremely frustrating (me hincha mucho las pelotas). In the end, the only solution seems to be creating a new user or formatting, which is even more frustrating because I need to work! I can't believe this, all because they didn't implement a Regex in terminal.integrated.wordSeparators instead of "1 character in that configuration string = 1 space". Goodness!
This is a pretty clear violation of the , consider this a warning.
I think you're saying removing space from word separators would fix this but that would not work because then would be part of the .
To verify make sure links in the format above () work correctly
Change:
import { URI } from 'vs/base/common/uri'; import { FileKind } from 'vs/platform/files/common/files'; import { compareFileNames } from 'vs/base/common/comparers'; <del> import { FuzzyScore, createMatches } from 'vs/base/common/filters'; </del> <ins> import { FuzzyScore, createMatches, IMatch } from 'vs/base/common/filters'; </ins> import { IViewDescriptor, IViewDescriptorService } from 'vs/workbench/common/views'; import { localize } from 'vs/nls'; import { flatten, find } from 'vs/base/common/arrays';

Discussion:
I often make a lot of changes at once, and then need to commit them. Some changes don't belong together in the same commit, and some aren't ready to be committed at all. The current UI allows me to select some files to be staged for commit and exclude others, but it requires me to carefully select my changes from a potentially very long list. It would be incredibly useful if I could search or filter files by path pattern and stage/unstage all search results. Even better would be if I could search for lines of code and either stage files containing those lines or just the matched lines. This would streamline my git workflow by a lot.
I guess my ideal UI would allow me to: search files by path, and stage/unstage all matched files stage/unstage individually selected files search code in files, and stage/unstage all matched lines stage/unstage individually selected lines stage/unstage all matched files stage/unstage individually selected files
Since last month, SCM supports fancy keyboard navigation and filtering. Simply start typing when focused on the view. A widget will appear which you can use to toggle between simple highlighting and filtering. Currently filtering is done only on file names though, not paths or even code, so I can leave this open for additional filtering fields.
<!-- -96bd-47a8-a0e8- --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 . Happy Coding!
Change:
resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.4.45.tgz#cf1144091d6683cbd45a231954a745f02fb24598" integrity sha512-czF9eYVuOmlY/vxyMQz2rGlNSjZpxNQYBe1gmQv7al171qOIhgyO9k7D5AKlgeTCSPKk+LHhj5ZyIdmEub9oNg== <del> electron@17.4.1: version "17.4.1" resolved "https://registry.yarnpkg.com/electron/-/electron-17.4.1.tgz#203961ca7551553d6497a1ec61d5f85d64d7e2ef" integrity sha512-0qX+DbiNXlVSUxXq4lWVTis8QYqC4Q7R/Xkk3YZQbHMXZ90bWilypC3gBZAcN4MQD4AYUIebphBOpRPxlXY3nQ== </del> <ins> electron@17.4.3: version "17.4.3" resolved "https://registry.yarnpkg.com/electron/-/electron-17.4.3.tgz#5f3c26cb211f9267d2becee717f34e3ce564a6bf" integrity sha512-WQggyCgNUOzoOn+wJKe+xFhYy56gyrn/jIa/l7dyD3TxPb8lddSc86OAqPnP5EugcNXQ0yIu8b+SIE8duKozSw== </ins> dependencies: "@electron/get" "^1.13.0" "@types/node" "^14.6.2"

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: Win 7 x64 Steps to Reproduce: update Electron to 17.4.3
Does this fix the high CPU usage on OSX? (introduced in 1.67.0)
Change:
this.view.setScrollTop(positionTop - 30); } else if (positionTop > wrapperBottom) { this.view.setScrollTop(scrollTop + positionTop - wrapperBottom + 30); <del> } else if (newlyCreated) { // newly scrolled into view if (alignToBottom) { // align to the bottom this.view.setScrollTop(scrollTop + positionTop - wrapperBottom + 30); } else { // align to to top this.view.setScrollTop(positionTop - 30); } </del> <ins> } else if (alignHint === 'bottom') { // Scrolled into view from below this.view.setScrollTop(scrollTop + positionTop - wrapperBottom + 30); } else if (alignHint === 'top') { // Scrolled into view from above this.view.setScrollTop(positionTop - 30); </ins> } element.revealRangeInCenter(range); } //#endregion

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: OS Version: Steps to Reproduce: a new notebook a code cell a markdown cell with a few lines such as follows Go into preview mode in markdown Edit first cell to get into notebook mode Arrow down to select markdown cell and hit enter Watch how the mardown cell scrolls up in the notebook view Go back to preview mode Scroll the notebook to view the first cell again and edit it Now select the markdown cell using the mouse Double click the mardown cell to edit it and wathc how it does not scroll!! I.e. using keyboard vs mouse results in different behaviour with scrolliing of the notebook. Ideally I would expect there to be no automatic scrolling when editing using keyboard, just as with mouse given the md cell is already in view we should not scroll this cell !
When pressing enter, we try to reveal the cursor selection in the cell editor into view by calling which uses the reveal type My expectation is it only scrolls the cell if it's out of the viewport but currently it always reveals the cell to the top of the viewport. Changing the reveal type to does fix the problem (as it should behave, here I'm not necessarily suggesting we change the reveal type in ).
Assigning to Feb milestone as the experience is quite bad. What surprised me is we didn't get user reports for this, which made me wonder how many users edit markdown cells after they are initially created.
Change:
}, "brackets": [ ["<!--", "-->"], <del> ["<", ">"], </del> ["{", "}"], ["(", ")"] ],

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.76.0 OS Version: Windows 10 The most recent VS Code update broke bracket colorization for PHP files, when you close a PHP tag then open it again before using a closing bracket. Steps to Reproduce: a PHP file a PHP open tag , open a bracket with , use an end tag , step 2, but with a closed bracket show as red, and the coloured line that joins the brackets doesn't show. Note: The red brackets are normally only used for errors, so it makes it look like there's errors in the file Screenshot: !
Same problem here on Unbutu! Could you fix it please?
Same error on ubuntu Ubuntu 22.04.2 LTS
Also happens if you just have the opening tag but no closing tag at the end: !
Hello, thank you to open this topic. I have the same issue while writing PHP code on VSC. It would be great if could be fixed. Have a nice day !!
Same issue here on Mac OS 13.2.1
Same here
For anyone who needs this fix before the next update: Add this to your settings JSON (fix via PR )
I have a similar issue using math equations in markdown, the image on the left is version 1.76 and the one on the right is 1.75.1, both of them with the same settings (by sharing them). The fix suggested by did not resolve my problem. Should I open a new issue since it is a different language and context? !

Possibly related on Stack Overflow:
Related: :
Same issue with me
You should scope it to language, otherwise the bracket setting applys to all languages
The update and modified settings as suggested by didn't solve the issue I mentioned in . Might be related to . Below is the today's insiders version w/o any extensions with the same issue despite even scoping the brackets as suggested by above. !
omh same here lol..
Change:
hc: null }, localize('editorDragAndDropBackground', "Background color when dragging editors around. The color should have transparency so that the editor contents can still shine through.")); <del> export const SIDE_BY_SIDE_EDITOR_BORDER = registerColor('sideBySideEditor.border', { </del> <ins> export const SIDE_BY_SIDE_EDITOR_HORIZONTAL_BORDER = registerColor('sideBySideEditor.horizontalBorder', { </ins> dark: EDITOR_GROUP_BORDER, light: EDITOR_GROUP_BORDER, hc: EDITOR_GROUP_BORDER <del> }, localize('sideBySideEditor.border', "Color to separate two editors from each other when shown side by side in an editor group.")); </del> <ins> }, localize('sideBySideEditor.horizontalBorder', "Color to separate two editors from each other when shown side by side in an editor group from top to bottom.")); export const SIDE_BY_SIDE_EDITOR_VERTICAL_BORDER = registerColor('sideBySideEditor.verticalBorder', { dark: EDITOR_GROUP_BORDER, light: EDITOR_GROUP_BORDER, hc: EDITOR_GROUP_BORDER }, localize('sideBySideEditor.verticalBorder', "Color to separate two editors from each other when shown side by side in an editor group from left to right.")); </ins> // < --- Panels --- >

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. --There is a new color which can be used when we split an editor in group. The layout can be horizontal or vertical. Please support different border color settings for vertical and horizontal layouts. For example in the following vertical layout I don't need/want any border. It is easy to distinguish each editor. ! But it is hard to distinguish editors in horizontal layout without a border. !
Sounds reasonable, open for help for a meaningful small PR.
Verification: configure colors for the new theme colors and and verify they apply properly as advertised depending on the split in group layout
Change:
private async initialize(): Promise<void> { await this.extensionsScannerService.initializeDefaultProfileExtensions(); <del> await this.onDidChangeProfiles(this.userDataProfilesService.profiles, []); </del> <ins> await this.onDidChangeProfiles(this.userDataProfilesService.profiles); </ins> this.registerListeners(); await this.uninstallExtensionsNotInProfiles(); } private registerListeners(): void { <del> this._register(this.userDataProfilesService.onDidChangeProfiles(e => this.onDidChangeProfiles(e.added, e.removed))); </del> <ins> this._register(this.userDataProfilesService.onDidChangeProfiles(e => this.onDidChangeProfiles(e.added))); </ins> this._register(this.extensionsProfileScannerService.onAddExtensions(e => this.onAddExtensions(e))); this._register(this.extensionsProfileScannerService.onDidAddExtensions(e => this.onDidAddExtensions(e))); this._register(this.extensionsProfileScannerService.onRemoveExtensions(e => this.onRemoveExtensions(e)));

Discussion:
I had a "Testing" profile with various remote extensions installed. I deleted it (while being in it) and then recreated it empty. I still found all remote menu contributions even though the profile should have been empty. Maybe switching profiles should ask to reload the window when extensions require so? Steps to Reproduce: fresh user data dir, fresh extensions dir create an empty profile install SSH extension notice how the remote explorer view appears delete the profile notice how the remote explorer view is still there, same as the status bar entry for remote
Another case from is interesting: I do not think using a profile is a good idea for when extensions require a window reload to be disabled. So you need to then probably ask the user to reload the window or do it automatically.
AFAIK every extension requires a window reload after being disabled (except for package-json only extensions). We cannot unload code from extensions and cannot enforce them not doing anything anymore. There we always reload the window or at least the extension host
While switching profiles we restart extension host. You say this is not enough to unload extensions? Also while trusting/untrusting a workspace.
No, only those that are activate with code loaded. Here are steps: fresh user data dir, fresh extensions dir create an empty profile install SSH extension notice how the remote explorer view appears delete the profile notice how the remote explorer view is still there, same as the status bar entry for remote
I see this can be reproduced with above steps. But Remote Explorer view disappears with switching profile. So I think this is a bug (either in views or profiles) when profile is deleted. But status bar entries always appear.
Change:
constructor( @IInstantiationService private instantiationService: IInstantiationService, <del> @IExtensionManagementService private extensionManagementService: IExtensionManagementService </del> <ins> @IExtensionManagementService private extensionManagementService: IExtensionManagementService, @IExtensionGalleryService private galleryService: IExtensionGalleryService </ins> ) { super(); this.modelPromise = null;

Discussion:
from If you select "Show Installed Extensions" you won't see the update button but if you select "Install Extension" and search for an already installed extension that has a newer version available, the update button is visible. Is this part of this bug or is this something else? Install Extension: ! Show Installed Extensions: !
Change:
import { timeout } from 'vs/base/common/async'; import { CancellationToken } from 'vs/base/common/cancellation'; import { Disposable } from 'vs/base/common/lifecycle'; <del> import { CoreEditingCommands } from 'vs/editor/browser/controller/coreCommands'; </del> <ins> import { CoreEditingCommands, CoreNavigationCommands } from 'vs/editor/browser/controller/coreCommands'; </ins> import { Position } from 'vs/editor/common/core/position'; import { ITextModel } from 'vs/editor/common/model'; import { InlineCompletionsProvider, InlineCompletion, InlineCompletionContext } from 'vs/editor/common/modes';

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?: No (Needs InlineSuggestions from some extension) <!-- 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.60.0 OS Version: MacOS Catalina 10.15.7 Steps to Reproduce: GitHub Copilot. The exact version shouldn't be important, but this was verified using 1.4.2586. a blank Python document and enter the following text: There are a single space after each sign. Put the cursor on the end of the first line and trigger Copilot inline-suggestion by pressing Backspace then Space. Don't accept it, but press Down-arrow, Backspace, Space. After pressing Down-arrow the suggestion on the first line disappears (as it should), but after the Backspace+space, you may see the suggestion briefly appear again, before the new inline-suggestion appearing on the second line. This is a bit flaky, and it may not appear every time the cursor is moved. It may also depend on latency to the Copilot server, and so be less pronounced in e.g. North America than in Europe or Asia. Edit by This is the buggy behavior: !
Please let me know soon if we should release this with our Recovery Release tomorrow!
Thanks for your lightning fast fix, Releasing this quickly would be awesome - it's a quite distracting glitch!
can you verify that the issue is fixed in todays insider build?
As he's out today, I've had a play with today's insiders build and can't reproduce it, whereas I can with the insiders build from 6th September. So looks good to me!
Change:
joiners.push(promise); } }); <del> await Promises.settled(joiners); </del> <ins> try { await Promise.allSettled(joiners); } catch (error) { this.logService.error(error); } </ins> if (profile.id === this.profilesObject.emptyWindow?.id) { this.profilesObject.emptyWindow = undefined;

Discussion:
I'll be honest, I made this profile a while ago so maybe I'm just in a bad state... but I get this: ! ! Testing
Hmm, I think this operation would still remove the profile instead of throwing an error.
Unfortunately, it doesn't delete it so I appear stuck with having this extra profile I made a while ago.
It seems I am not catching the error for tasks I do before removing the profile. They should not stop the remove operation. Fixing it. Please verify in tomorrows insiders if you can remove it.
Worked today!