jiebi/CodeConvo huggingface dataset:
Change:
["{", "}"], ["[", "]"], ["(", ")"] <ins> ], "autoClosingPairs": [ { "open": "{", "close": "}" }, { "open": "[", "close": "]" }, { "open": "(", "close": ")" }, { "open": "'", "close": "'", "notIn": ["string", "comment"] }, { "open": """, "close": """, "notIn": ["string"] }, { "open": "`", "close": "`", "notIn": ["string", "comment"] }, { "open": "/**", "close": " */", "notIn": ["string"] } </ins> ] <del> } </del>  No newline at end of file <ins> } </ins>

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. --I noticed some files like , etc. don't allow wrapping content with quotes: ! While a plain file allows that: ! Can we add the option to enable all files with this feature?
For that the quotes need to be ad autoClosingPairs in git language configurations files at (If it makes sense)
Can we do that in the or must via an extension?
This can't be done in settings. The feature request for that is:
I've submitted a PR for it:
Verification steps: the latest VS Code Insiders a folder/workspace that contains a git repository a change to a file, and press the "Commit" button (do not enter a commit messages) will open the COMMIT_EDITMSG file in a word, select it, and type Confirm that the word has been wrapped in
Verified.
Change:
} } } <ins> /** * Both cursors are selections */ else { const charBeforeAndAfterAnchorPositionsRoughlyEqual = isCharBeforeAndAfterPositionsRoughlyEqual( event.textEditor.document, event.selections[0].anchor, event.selections[1].anchor ); const charBeforeAndAfterActivePositionsRoughlyEqual = isCharBeforeAndAfterPositionsRoughlyEqual( event.textEditor.document, event.selections[0].active, event.selections[1].active ); if (!charBeforeAndAfterAnchorPositionsRoughlyEqual || !charBeforeAndAfterActivePositionsRoughlyEqual) { exitMirrorMode(); } } </ins> } }

Discussion:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.42.0-insider OS Version: macOS Steps to Reproduce: See the following gif: ! I first enter the tag which activates multicursor, then I use the key combi to select and jump to the end of the line, go one back and use "Backspace" to delete the attribute. This is a common operation, but now with mirror cursors it might break the HTML as seen in the gif above. Moreover, if the opening & closing tag are further apart, one might not even notice the HTML is broken. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Also this quite a lot as this is a very common operation. Related to this is ctrl+shift selecting out of the element tag name. I'd like to work on. The fix would be to exit mirror mode if the selection is not empty and we reach a none-matching state.
This also brings up an issue when you try to add an attribute to multiple tags that have none. ! If you click the open tag, it'll select the opening and closing, and usually when you're at the end and you press space to type in the attribute it doesn't add the attributes to the closing tag, but when you're adding more cursors to the tags in other lines, it doesn't act like that anymore and adds the attributes to both tags. I went crazy trying to find this to disable it.
Yeah looking at the current implementation, there's no support at all for multiple cursors. That's gonna take some work for the behavior to work correctly.
This feature doesn't work well with extension vim too, have to shut it down.
The fix will be available in until next month's release.
Change:
printf "033]633;G007" } <ins> right_prompt_start() { printf "033]633;H007" } right_prompt_end() { printf "033]633;I007" } </ins> command_complete() { local HISTORY_ID=$(history | tail -n1 | awk '{print $1;}') if [[ "$HISTORY_ID" == "$LAST_HISTORY_ID" ]]; then

Discussion:
Setup a right prompt in fish/zsh and make sure the command detected is accurate.
zsh uses for this, perhaps we should have a generic ignored ranges mechanism and combine this with the line continuation solution?
Change:
} else if (e.affectsConfiguration(TerminalSettingId.ShellIntegrationDecorationsEnabled)) { this._removeCapabilityDisposables(TerminalCapability.CommandDetection); this._updateDecorationVisibility(); <del> } else if (e.affectsConfiguration(TaskSettingId.ShowDecorations)) { this._updateDecorationVisibility(); </del> } })); this._register(this._themeService.onDidColorThemeChange(() => this._refreshStyles(true)));

Discussion:
I noticed this: We always want to add the sequences as it enabled command navigation, the decorations showing is purely a visual thing that hides the decoration button. So I suggest we remove the ShowDecorations check there and instead call into the terminal addon to disable the decoration.
To verify: repo (or any repo with a task that exits) the default build task to some file the test task it the test task it /ctrl+up should take you to the start of the task in step 6, not the very top of the terminal
I actually think we should remove the setting outright as we already have which essentially does the same thing. This would save us from exposing outside of the terminal part the ability to configure decoration visibility. Timeline: The terminal setting was as a boolean in Feb The task setting was in June The terminal setting was made more granular in July The interaction between the 2 settings confused someone in I'll leave the decision up to you whether we remove it, it feels like too much granularity to me as the user must like the terminal ones but not the task ones.
Let's remove it
Change:
import { IssueWebReporter } from 'vs/workbench/contrib/issue/browser/issueReporterService'; import { AuxiliaryWindowMode, IAuxiliaryWindowService } from 'vs/workbench/services/auxiliaryWindow/browser/auxiliaryWindowService'; <ins> export interface IssuePassData { issueTitle: string; issueBody: string; } </ins> export class IssueFormService implements IIssueMainService { readonly _serviceBrand: undefined;

Discussion:
Testing to open the issue reporter for an extension issue reporter open, return to the main window step 1 for another extension =issue reporter opens but doesn't update the issue reporter input fields.
Change:
"name": "HTML: Tag Names", "scope": "entity.name.tag", "settings": { <del> "foreground": "#4B83CD" </del> <ins> "foreground": "#4B69C6" </ins> } }, {

Discussion:
Environment Details: VSCode Version : 1.25.0 OS Version : Win10 Additional Details: HighContrast,MAS1.4.3 Repro Steps: Visual Studio code desktop application. to "Plain Text" of "Status Bar"-Enter "PowerShell" in "Select Language Mode" combo box-Write the PowerShell Code in plain editor-Save the editor. to Setting button of Activity Bar and select "Color Theme" option. Themes shows number of different colors list apply all that theme on the editor. color contrast analyser and check the color contrast ratio. shows color contrast ratio less than expected color contrast ratio. Actual: After applying color themes to editor it shows color contrast ratio as 3.5:1 eg. Select "QuietLight" theme from color theme list and check for the color contrast ratio. Expected: The expected colorcontrast ratio should be greater than or equals to 7:1 ratio. Recommendations: Refer below link which is repository of bug fixes code  User Impact: User will not able to see the content of the editor. MAS Reference: MAS1.4.3- Attachment For Reference: ! Does this issue occur when all extensions are disabled?: Yes
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.701 --- <!-- score: 0.617 --- <!-- score: 0.552 --- <!-- score: 0.508 --<!-- potentialduplicatescomment --
I believe you are using the wrong color contrast ratio. From the link you provided: We've only been targeting the minimum contrast ratio, which is Level AA at 4.5:1
Change:
return await this.run(Operation.Stash, () => this.repository.applyStash(index)); } <del> async showStash(index: number): Promise<string[] | undefined> { </del> <ins> async showStash(index: number): Promise<Change[] | undefined> { </ins> return await this.run(Operation.Stash, () => this.repository.showStash(index)); }

Discussion:
Testing Create a git stash that includes a new file, or a renamed file "View stash" The editor only shows modified files, and there is no indication that some content is missing <img width="442" alt="image" src=""<img width="305" alt="image" src=""<img width="887" alt="image" src=""
Maybe the pattern is that it only shows files that currently exist in the workspace. If I delete , then "View stash", I don't see that file either.
could you please take a look at this. I have checked and the git extensions is passing all files but it does look like the multi-file diff editor does not display all of them. Let me know if I need to change anything in the git extension. Thanks!
still seeing this, <img width="1725" alt="Screenshot 2024-01-25 at 8 31 59 AM" src=""<img width="1728" alt="Screenshot 2024-01-25 at 8 31 44 AM" src=""<img width="650" alt="Screenshot 2024-01-25 at 8 32 13 AM" src=""
when you have untracked filed you have to use the "Git: Stash (Include Untracked)" command otherwise the untracked files are not being included in the stash.
Change:
return allDependenciesAndPacks.filter(e => !installed.some(i => areSameExtensions(i.identifier, e.gallery.identifier))); } <del> private async checkAndGetCompatibleVersion(extension: IGalleryExtension, fetchCompatibleVersion: boolean, installPreRelease: boolean): Promise<{ extension: IGalleryExtension; manifest: IExtensionManifest }> { </del> <ins> private async checkAndGetCompatibleVersion(extension: IGalleryExtension, sameVersion: boolean, installPreRelease: boolean): Promise<{ extension: IGalleryExtension; manifest: IExtensionManifest }> { </ins> const report = await this.getExtensionsControlManifest(); if (getMaliciousExtensionsSet(report).has(extension.identifier.id)) { throw new ExtensionManagementError(nls.localize('malicious extension', "Can't install '{0}' extension since it was reported to be problematic.", extension.identifier.id), ExtensionManagementErrorCode.Malicious);

Discussion:
Version: 1.65.0-insider (user setup) Commit: Date: 2022-02-11T05:19:13.554Z Electron: 16.0.8 Chromium: 96.0.4664.110 16.9.1 V8: 9.6.180.21-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: an extension (such as the C/C++ extension) that uses platform-specific VSIX's in the marketplace. a Remote WSL workspace. Install that extension into the remote. the extension UI for the instance installed remotely, try to select "Install Another Version..." or "Install Another Prerelease Version..." This results in an error: ! (There is a similar error in latest non-insider version, 1.64.2)
Can you please enable the log level to trace and provide following logs while performing this action? Log (Shared) Log (Window) Log (Remote)
When this repro's, I see the following in (with and is set to . I do not see any such setting as ) : is similar: was not logged to for this repro.
You can use following command to set log level to trace
Log (Shared): Log (Windows): Log (Remote Server): Log (Remote Extension Host): Please re-open. Please don't block waiting for me to provide information. This bug is extremely easy to reproduce.
Please re-open.
To verify: Open a remote window (make sure local and remote are on different Operating Systems) Install C++ extension Install another version of C++ extension (right click on the extension and you will see this action) Make sure another version is installed.
Change:
for (const widget of Object.values(this._widgets)) { const range = widget.preference.range; <del> if (range.endLineNumber < visibleStartLineNumber || range.startLineNumber > visibleEndLineNumber) { </del> <ins> const { startLineNumber, endLineNumber } = this._context.viewModel.coordinatesConverter.convertModelRangeToViewRange(Range.lift(range)); if (!startLineNumber || !endLineNumber || endLineNumber < visibleStartLineNumber || startLineNumber > visibleEndLineNumber) { </ins> // The widget is not in the viewport continue; } // The widget is in the viewport, find a good line for it <del> const widgetLineNumber = Math.max(range.startLineNumber, visibleStartLineNumber); </del> <ins> const widgetLineNumber = Math.max(startLineNumber, visibleStartLineNumber); </ins> const lane = Math.min(widget.preference.lane, this._glyphMarginDecorationLaneCount); requests.push(new WidgetBasedGlyphRenderRequest(widgetLineNumber, lane, widget.preference.zIndex, widget)); }

Discussion:
As you can see, the positioning does not folding into account: ! This breaks the revert arrows in the diff editor, as I adopted glyph widgets for them.
We're deciding whether to render widgets based on and here but these are the viewport and not the model line numbers
Change:
.scm-view .scm-editor-container.synthetic-focus, .monaco-workbench .part.panel .scm-view .scm-editor-container.synthetic-focus { outline: 1px solid var(--vscode-focusBorder); <ins> outline-offset: -1px; </ins> } .scm-view .scm-editor-container.validation-info { outline: 1px solid var(--vscode-inputValidation-infoBorder) !important; <ins> outline-offset: -1px; </ins> } .scm-view .scm-editor-container.validation-warning { outline: 1px solid var(--vscode-inputValidation-warningBorder) !important; <ins> outline-offset: -1px; </ins> } .scm-view .scm-editor-container.validation-error { outline: 1px solid var(--vscode-inputValidation-errorBorder) !important; <ins> outline-offset: -1px; </ins> } .scm-editor-validation-container {

Discussion:
Source control warning not aligned on the right hand side with the input field: <img width="473" alt="image" src="https://user-"
Draft PR here but I feel that there is a better way. For whatever reason the editor within SCM input is not as wide as the input it is rendered in—or something like that. Open to ideas!
Here is the updated layout: <img width="567" alt="image" src="https://user-"
Change:
case 'terminated': this._onDidTerminateDebugee.fire(<DebugProtocol.TerminatedEvent>event); break; <del> case 'exit': </del> <ins> case 'exited': </ins> this._onDidExitDebugee.fire(<DebugProtocol.ExitedEvent>event); break; case 'progressStart':

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.81.1 OS Version: any Steps to Reproduce: The code in does not handle DAP event This looks like a typo error.
Change:
} setState(_state: StickyScrollWidgetState | undefined, foldingModel: FoldingModel | null, _rebuildFromLine?: number): void { <del> if ((!this._previousState && !_state) || (this._previousState && this._previousState.equals(_state))) { </del> <ins> if (_rebuildFromLine === undefined && ((!this._previousState && !_state) || (this._previousState && this._previousState.equals(_state))) ) { </ins> return; } const isWidgetHeightZero = this._isWidgetHeightZero(_state);

Discussion:
Repro: some typescript file with = 1 levels of sticky scroll visible in the editor window -:bug: Version: 1.86.0-insider Commit: Date: 2023-12-20T05:47:39.317Z Electron: 27.1.3 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 23.2.0 cc since you mentioned sticky scroll during planning call
you should listen on the tokenization changed/finished event.
Change:
disposables.add(quickPick.onDidAccept(async () => { resolve(quickPick.selectedItems[0]); })); <ins> disposables.add(quickPick.onDidHide(() => { resolve(undefined); })); </ins> this._calculdateKernelSources(editor).then(quickPickItems => { quickPick.items = quickPickItems;

Discussion:
Testing a notebook in a new workspace run on a cell, this should pop-up the kernel selection the kernel selection quickpick without selecting anything :bug: cell appears to be running, and cannot be stopped or run again
works correctly when cancelling on the initial quickpick, but not when cancelling in a later stage: !
the cell never ends up running in that gif
Change:
} async toggleApplyExtensionToAllProfiles(extension: IExtension): Promise<void> { <del> if (!extension.local || isApplicationScopedExtension(extension.local.manifest)) { </del> <ins> if (!extension.local || isApplicationScopedExtension(extension.local.manifest) || extension.isBuiltin) { </ins> return; } await this.extensionManagementService.toggleAppliationScope(extension.local, this.userDataProfileService.currentProfile.extensionsResource);

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. --I have multiple profiles in VS Code and I disable everything I don't need in each of them, including built-in extensions that I will never use with a particular profile. After the successful installation of the latest version I wanted to try the new option; while it works for user-installed extensions, it fails for built-in extensions, read more below. 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: OS Version: , 22H2 (.2070) Steps to Reproduce: the extensions view built-in extensions only the cog icon on any (enabled) extension on error will occur (see attached screenshot) <div align="center"<img src="" alt="Error in VS Code"</div<brNote: all extensions are present at the provided folder shown in the error message.
Same for me but on MacOS Ventura 13.5 (22G74)
Can you see if the extension is maybe uninstalled when you follow your steps? That could hint to
/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 . See also our . Happy Coding!
Unfortunately the latest patch release: and the mentioned didn't fix it, here's the error screenshot again, in the latest version. Also, I've opened the folder itself where the extension is located, while VS Code complains it doesn't exist. <div align="center"<img src="" alt="Error in VS Code"</div
This action should not be shown on builtin extensions because they are available for all profiles by default.
Change:
"category": "Git" }, { <ins> "command": "git.merge", "title": "%command.merge%", "category": "Git" }, { </ins> "command": "git.pull", "title": "%command.pull%", "category": "Git"

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:
function computeColors(model: IDocumentColorComputerTarget): IColorInformation[] { const result: IColorInformation[] = []; // Early validation for RGB and HSL <del> const initialValidationRegex = /b(rgb|rgba|hsl|hsla)(([0-9s,.%]*))|(#)([A-Fa-f0-9]{6})b|(#)([A-Fa-f0-9]{8})b/gm; </del> <ins> const initialValidationRegex = /b(rgb|rgba|hsl|hsla)(([0-9s,.%]*))|(#)([A-Fa-f0-9]{3})b|(#)([A-Fa-f0-9]{4})b|(#)([A-Fa-f0-9]{6})b|(#)([A-Fa-f0-9]{8})b/gm; </ins> const initialValidationMatches = _findMatches(model, initialValidationRegex); // Potential colors have been found, validate the parameters

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. --is great! It seems to currently only support the six- and eight-value syntaxes, and . It'd be useful to support the three- and four-value syntaxes, and . (Spec: MDN: ) For example this code in a JS file renders for me as !
<!-- -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!
To test this issue: on the setting . any file and write a hex value in the editor of length three or four. Verify that a color decorator is rendered next to the hex value.
Thank you! For anyone who finds this issue and thinks it still isn't supported, make sure you've also disabled any plugins which contribute decorators <img width="132" alt="image" src=""