jiebi/CodeConvo huggingface dataset:
Change:
<!-- 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.0 Stable OS Version: Windows 11 Steps to Reproduce: a .md file, add a header ⌘T, type 1.66.2: works fine ! 1.67.0: No matching workspaces symbols !
I confirmed that markdown returns the workspace symbols in this case. They then seem to be filtered out on the VS Code side
https://user-
Did the filtering for quick pick change?
This is a regression from I have changed how is configured and made the wrong adoption here...

Discussion:
return { data: FuzzyScore.Default, visibility: true }; } <del> const score = fuzzyScore(this._pattern, this._lowercasePattern, 0, labelStr, labelStr.toLowerCase(), 0); </del> <ins> const score = fuzzyScore(this._pattern, this._lowercasePattern, 0, labelStr, labelStr.toLowerCase(), 0, { firstMatchCanBeWeak: true, boostFullMatch: true }); </ins> if (score) { this._matchCount++; return labels.length === 1 ?

} function doScoreFuzzy2Single(target: string, query: IPreparedQueryPiece, patternStart: number, wordStart: number): FuzzyScore2 { <del> const score = fuzzyScore(query.original, query.originalLowercase, patternStart, target, target.toLowerCase(), wordStart); </del> <ins> const score = fuzzyScore(query.original, query.originalLowercase, patternStart, target, target.toLowerCase(), wordStart, { firstMatchCanBeWeak: true, boostFullMatch: true }); </ins> if (!score) { return NO_SCORE2; }
Change:
A11yMAS; #A11ySev1; #A11yTCS; #DesktopApp; #BM-PowerShellCore-MAC-Jan21; #PowerShell Core; #MAS1.3.1; #MAC; #AINotInScope; #Info and Relationships; #Voiceover; #Element: Button; #ScreenReader; #Benchmark. Application Name: Visual Studio Code Version: 1.66.2(user setup) PowerShell Verion: v2022.5.0 MAC Version: macOS Monterey 12.2.1 Voiceover with using shortcut key Command+F5. VS Code Space Insiders VS Code Space insiders till Extension in the left navigation and press enter till Search Extensions in Marketplace and type PowerShell and press enter till Rating information check whether Voiceover is reading the rating information such as 4 stars rated for PowerShell or not Voiceover is not announcing about "rating" information about the PowerShell. Voiceover should be announcing about "Rating" information about the PowerShell for the users to understand how much PowerShell is rated !
The rating element should have an aria-label which has the rating in it, so the user can hear the rating. should be pretty straight forward, feel free to assign back to me if you would like me to push this.
Issue is fixed. Adding #Closed; tag.

Discussion:
render(): void { this.container.innerText = ''; <ins> this.container.title = ''; </ins> if (!this.extension) { return;

} const rating = Math.round(this.extension.rating * 2) / 2; <ins> this.container.title = localize('ratedLabel', "Average rating: {0} out of 5", rating); </ins> if (this.small) { append(this.container, $('span' + ThemeIcon.asCSSSelector(starFullIcon)));
Change:
VS Code: 1.67.0 (, 2022-05-04T12:06:02.889Z) Since this update (also tested on clean Insiders), if a variable is selected using the "" shortcut ( in my case), the occurrence indicators of it don't clean up when selection is canceled by cursor navigating away from it. Here is how it works with a mouse (correct): ! And with a shortcut (stay forever): ! They won't clean up even if I select a different variable, the indicators are just to the previous ones. They only disappear if I switch editor to a different file and come back.
fyi this is also caused by recursing i.e.
Would you like to release a patch? This bug is so annoying!!!

Discussion:
* It is not globally unique in order to limit it to one character. */ private readonly _instanceId: string; <ins> private _deltaDecorationCallCnt: number = 0; </ins> private _lastDecorationId: number; private _decorations: { [decorationId: string]: IntervalNode }; private _decorationsTree: DecorationsTrees;

} try { <ins> this._deltaDecorationCallCnt++; if (this._deltaDecorationCallCnt > 1) { console.warn(`Invoking deltaDecorations recursively could lead to leaking decorations.`); onUnexpectedError(new Error(`Invoking deltaDecorations recursively could lead to leaking decorations.`)); } </ins> this._onDidChangeDecorations.beginDeferredEmit(); return this._deltaDecorationsImpl(ownerId, oldDecorations, newDecorations); } finally { this._onDidChangeDecorations.endDeferredEmit(); <ins> this._deltaDecorationCallCnt--; </ins> } }
Change:
<!-- 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.67.0 OS Version: Windows 11 Steps to Reproduce: an extension which has published pre-releases before pre-release of that extension a new stable with a higher number than all the pre-releases Install another version :bug: existing pre-releases are not listed, as though the user never opted into pre-releases for that extension in the first place. There is also no indication that pre-releases exist for this extension anymore. You have to wait for the extension to publish the next pre-release before you can install pre-releases (I verified that this fixes things with the Azure Repos extension) Currently reproducible with the Python extension: !

Discussion:
return; } const targetPlatform = await this.extension!.server!.extensionManagementService.getTargetPlatform(); <del> const allVersions = await this.extensionGalleryService.getAllCompatibleVersions(this.extension!.gallery!, this.extension!.local!.isPreReleaseVersion, targetPlatform); </del> <ins> const allVersions = await this.extensionGalleryService.getAllCompatibleVersions(this.extension!.gallery!, this.extension!.local!.preRelease, targetPlatform); </ins> if (!allVersions.length) { await this.dialogService.show(Severity.Info, localize('no versions', "This extension has no other versions.")); return;
Change:
<!-- 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. --This will be useful to my extension. Thanks.
Please describe your use case.
I have an extension with 2 output channels, and I need to switch between them for different situations. But if the user navigates away, I don't want to bother him. So I need code like:
Not sure if I understand your use case, what do you mean by navigates away? Can you be more clear in explaining your use case?
I have an extension with 2 output channels, one for info and one for errors. If the user looks at the info channel and there are errors, I want to switch to the errors channel for him. If there are no more errors and he's looking at the errors channel, I want to switch to the info channel. But if the user looks at other channel, or doesn't look at any channel at all, I don't want to bring up my channel to him. I hope this is clearer.
Did you try using api? Output channel is an editor internally and opened output channel can be accessed from the above api
I didn't try. How can I know a TextEditor is the output channel? How can I get the currently open output channel from the TextEditor object?
From its URI
So I tried and I see this object: I wish there was the output name instead of , then it could help. As it is now, the number doesn't allow to differentiate between the two, since I can't know which was created first (and I'd rather not track it). Maybe it can be improved to include the output name? Maybe something like .
I think is a good reasonable workaround for this. So I would close this as won't fix
Here is my case use: I create multiple output channels for each launched script. There is also "common" output channel which displays output from all launched scripts. When script finished it's task and exits, it's output channel is removed with , at which point VSCode automatically opens the first available output channel in the list (in my case it's ). I need to detect if any of output channels created by my extension were opened prior , if so, switch to "common" output channel otherwise do nothing. [EDIT] Ok, so as suggested we could check using document url: replace and with your extension and from

Discussion:
public async $register(label: string, log: boolean, file: UriComponents, languageId: string, extensionId: string): Promise<string> { const idCounter = (MainThreadOutputService._extensionIdPool.get(extensionId) || 0) + 1; MainThreadOutputService._extensionIdPool.set(extensionId, idCounter); <del> const id = `extension-output-${extensionId}-#${idCounter}`; </del> <ins> const id = `extension-output-${extensionId}-#${idCounter}-${label}`; </ins> Registry.as<IOutputChannelRegistry>(Extensions.OutputChannels).registerChannel({ id, label, file: URI.revive(file), log, languageId }); this._register(toDisposable(() => this.$dispose(id)));
Change:
<!-- 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.0 OS Version: Windows 10 Steps to Reproduce: Please add some margin there, I've Provided img below and pointed out that place with red clr It's Just Sticking each other !
Sorry can you clarify what you mean?
As, You can see in the img I've pointed out a terminal place with red clr circle where Source Control is there and ahead of it 1 Badge is there. So, Then it's below line and the Badge does not have any space/margin they both are sticking.
I see space between the badge and the active indicator,
I think it's too small.
I think these changes when the panel padding got updated with the secondary side bar. Not sure what else we can do besides add the padding back. It is quite tight right now.
Should be fixed now thanks to <img width="127" src="https://user-"

Discussion:
} .monaco-workbench .part.basepanel > .composite.title > .panel-switcher-container > .monaco-action-bar .action-item .active-item-indicator { <del> top: -6px; </del> <ins> top: -4px; </ins> left: 10px; width: calc(100% - 20px); } .monaco-workbench .part.basepanel > .composite.title > .panel-switcher-container > .monaco-action-bar .action-item.icon .active-item-indicator { <del> top: -1px; </del> <ins> top: 1px; </ins> left: 2px; width: calc(100% - 4px); }
Change:
Refs
Not sure what's going on - this process is pretty straightforward and hasn't changed in years. I am launching the full vscode window on this build machine, nothing has changed in electron that would interact with that right?
and are on same electron versions, the step worked fine in the latest build last Friday , first timeout failure started since insiders were turned back on last Saturday and since then all insiders build seem to consistently hit the timeout Todays' nightly run: Testing if I can repro the issue locally.
Testing the callsite locally seems to work fine.
I wonder if the timeout is insufficient, testing a build with increased timeout here
Previous build did not enable the upload step, new build
Kicked off another, removing the branch check
Might not be fixed ( - run on 11th of May, one day after this fix has been merged to main)
the fix only landed in , failing build was on , how do you feel about backporting the fix to ?
I can do that

Discussion:
const timer = setTimeout(() => { codeProc.kill(); reject(new Error('export-default-configuration process timed out')); <del> }, 12 * 1000); </del> <ins> }, 30 * 1000); </ins> codeProc.on('error', err => { clearTimeout(timer); reject(err);

const timer = setTimeout(() => { codeProc.kill(); reject(new Error('export-default-configuration process timed out')); <del> }, 12 * 1000); </del> <ins> }, 30 * 1000); </ins> codeProc.on('error', err => { clearTimeout(timer);
Change:
<!-- 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 <!-- 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.0 OS Version: Windows 11 Steps to Reproduce: a q file, e.g. test.q and press enter freezes I detected this before when I try to use the Bracket Pair Colorization plugin, but this feature is enabled by default, so I have to raise this issue. Also, this happens even if I disable it Look at this weird color. ! works, freezes. Related issue
Thanks for reporting this! Please also report bugs for non-default configuration, as this helps us to improve the quality of the product. I will look into this very soon.
I'm quite sure this is caused by invalid (here: unsorted) semantic tokens reported by the extension. These are the line tokens that bracket pair colorization is working on: ! The value in the array at position 12 is wrong, as it is smaller than the previous one. This causes the endless-loop. However, I only have been able to reproduce this on the latest stable. did you fix something for semantic tokens already this milestone?
I think this got fixed with
Thank you very much. I will take a look semantic highlight on my side as well.
If you investigate, please post here the semantic tokens that you were returning for this line. I would like to double check that does indeed fix this case too.
Sure, I will let you know.
I was also curious so I a breakpoint to investigate. When the document is empty, there are no semantic tokens (), and then after pasting we get back a document semantic tokens edit with the following data:
My extension returns 3 semantic tokens for in following order 0 10 1 1 0 -2nd x 0 14 1 1 0 -3rd x 0 8 1 1 0 -1st x And the final result is actually (15) [0, 10, 1, 1, 0, 0, 4, 1, 1, 0, 0, -6, 1, 1, 0] I need to sort the semantic tokens and push.
I have fixed semantic tokens on my side, and vscode doesn't freeze anymore. Thank you very much for your help!!

Discussion:
const endOffset = lineTokens.getEndOffset(this.lineTokenOffset); // Is there a bracket token next? Only consume text. <del> if (containsBracketType && isOther && endOffset !== this.lineCharOffset) { </del> <ins> if (containsBracketType && isOther && this.lineCharOffset < endOffset) { </ins> const languageId = lineTokens.getLanguageId(this.lineTokenOffset); const text = this.line.substring(this.lineCharOffset, endOffset);
Change:
<!-- 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)

Discussion:
disturl "https://electronjs.org/headers" <del> target "17.4.1" </del> <ins> target "17.4.3" </ins> runtime "electron" build_from_source "true"

"git": { "name": "electron", "repositoryUrl": "https://github.com/electron/electron", <del> "commitHash": "73c87bcfc6e18428c21676d68f829364e6a7b15d" </del> <ins> "commitHash": "322f1c3f8907f2592eef5b5e03a97045e30df9e3" </ins> } }, "isOnlyProductionDependency": true, "license": "MIT", <del> "version": "17.4.1" </del> <ins> "version": "17.4.3" </ins> }, { "component": {

"cssnano": "^4.1.11", "debounce": "^1.0.0", "deemon": "^1.4.0", <del> "electron": "17.4.1", </del> <ins> "electron": "17.4.3", </ins> "eslint": "8.7.0", "eslint-plugin-header": "3.1.1", "eslint-plugin-jsdoc": "^19.1.0",

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"
Change:
<!-- 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: Version: 1.68.0-insider (user setup) Commit: Date: 2022-05-11T05:17:12.474Z Electron: 17.4.1 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: here are my settings: The new titleMenu shows up, but it is not clickable !

Discussion:
} /* Window Title Menu */ <ins> .monaco-workbench .part.titlebar>.titlebar-container>.window-title.title-menu { z-index: 3000; -webkit-app-region: no-drag; } </ins> .monaco-workbench .part.titlebar>.titlebar-container>.window-title.title-menu .action-item.quickopen { color: var(--vscode-input-foreground); border: 1px solid var(--vscode-dropdown-border);
Change:
use web (windows?) use with open quick pick, all is good change to open quick pick, the top position is wrong <img width="1394" alt="Screenshot 2022-05-12 at 16 53 01" src="https://user-"This is because is only ready after a layout change event and that event isn't triggered by the title bar change. Once you resize the window (or force another layout) things will recover
fyi
I will push a fix as part as a title menu effort (the title menu being overlayed by QP)
Sorry, I was wrong about that... I could figure out on the spot what event is missing. Sorry, passing it on

Discussion:
this.setEditorHidden(!visible, true); } this._onDidChangePartVisibility.fire(); <ins> this._onDidLayout.fire(this._dimension); </ins> })); }
Change:
<img width="1440" alt="image" src="https://user-"version:
cc not sure why this would be
Let me investigate
There seems to be a older version of this extension in the extensions installation folder. Deleting it will fix it. It seems to be a bug in VS Code for showing reload in this case.
Would be helpful to provide a command to remove all old extensions cache
This is a bug in VS Code that it is not removing the obsolete extensions. So you do not need a command. Manually deleting is just a workaround for now.
To verify: Download and install with version from Version History tab. Reload window and go to extensions view and search for extension and make sure you do not see Reload Required button

Discussion:
import { ExtensionIdentifier, IExtensionDescription, IRelaxedExtensionDescription } from 'vs/platform/extensions/common/extensions'; import { localize } from 'vs/nls'; import { ILogService } from 'vs/platform/log/common/log'; <ins> import * as semver from 'vs/base/common/semver/semver'; // TODO: @sandy081 merge this with deduping in extensionsScannerService.ts </ins> export function dedupExtensions(system: IExtensionDescription[], user: IExtensionDescription[], development: IExtensionDescription[], logService: ILogService): IExtensionDescription[] { let result = new Map<string, IExtensionDescription>(); system.forEach((systemExtension) => {

const extension = result.get(extensionKey); if (extension) { if (extension.isBuiltin) { <ins> if (semver.gt(extension.version, userExtension.version)) { logService.warn(`Skipping extension ${userExtension.extensionLocation.path} with lower version ${userExtension.version}.`); return; } </ins> // Overwriting a builtin extension inherits the `isBuiltin` property and it doesn't show a warning (<IRelaxedExtensionDescription>userExtension).isBuiltin = true; } else {