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?: No, because feature isn't available without TS extension. I don't know which language has this feature with extensions disabled. <!-- 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.65.2 OS Version: WIN Steps to Reproduce: some TS code call hierarchy (outgoing calls) an item the place of the call (source) is revealed call hierarchy for the originally peeked word an item the definition of the call (target) is revealed It is easy to get lost when using both, and not clear in the API documentation which one to provide in an extension.
When there are cross-document links, preferences view shows clicked items' document correctly either if I provide source or target uri. However peek view tries to show the provided range in the parent document of the selected item if I provide the source uri. Double-clicking an item opens the correct document. Based on this it might be a bug that peek shows the range in parent document. Is there any restriction whether a provider should provide source or target Uris?
Hi should be already fixed? Has it been released yet? Thanks :)

Discussion:
item.tooltip = item.label ? `${item.label} - ${element.item.detail}` : element.item.detail; item.contextValue = 'call-item'; item.iconPath = getThemeIcon(element.item.kind); <ins> type OpenArgs = [vscode.Uri, vscode.TextDocumentShowOptions]; let openArgs: OpenArgs; if (element.model.direction === CallsDirection.Outgoing) { openArgs = [element.item.uri, { selection: element.item.selectionRange.with({ end: element.item.selectionRange.start }) }]; } else { // incoming call -> reveal first call instead of caller let firstLoctionStart: vscode.Position | undefined; if (element.locations) { for (const loc of element.locations) { if (loc.uri.toString() === element.item.uri.toString()) { firstLoctionStart = firstLoctionStart?.isBefore(loc.range.start) ? firstLoctionStart : loc.range.start; } } } if (!firstLoctionStart) { firstLoctionStart = element.item.selectionRange.start; } openArgs = [element.item.uri, { selection: new vscode.Range(firstLoctionStart, firstLoctionStart) }]; } </ins> item.command = { command: 'vscode.open', title: vscode.l10n.t('Open Call'), <del> arguments: [ element.item.uri, <vscode.TextDocumentShowOptions>{ selection: element.item.selectionRange.with({ end: element.item.selectionRange.start }) } ] </del> <ins> arguments: openArgs </ins> }; item.collapsibleState = vscode.TreeItemCollapsibleState.Collapsed; return item;
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.65.2 OS Version: Darwin x64 20.6.0 Steps to Reproduce: fullwidth right parenthesis the right parenthesis <img width="688" alt="image" src="https://user-"
should be escaped: ,
Thanks a lot for reporting & investigating! Up for a PR?

Discussion:
import { RunOnceScheduler } from 'vs/base/common/async'; import { CharCode } from 'vs/base/common/charCode'; import { Codicon } from 'vs/base/common/codicons'; <del> import { IMarkdownString } from 'vs/base/common/htmlContent'; </del> <ins> import { MarkdownString } from 'vs/base/common/htmlContent'; </ins> import { Disposable, IDisposable } from 'vs/base/common/lifecycle'; import * as platform from 'vs/base/common/platform'; import { InvisibleCharacters } from 'vs/base/common/strings';

}; const adjustSettings = nls.localize('unicodeHighlight.adjustSettings', 'Adjust settings'); <del> const contents: Array<IMarkdownString> = [{ value: `${reason} [${adjustSettings}](command:${ShowExcludeOptions.ID}?${encodeURIComponent(JSON.stringify(adjustSettingsArgs))})`, isTrusted: true, }]; result.push(new MarkdownHover(this, d.range, contents, index++)); </del> <ins> const uri = `command:${ShowExcludeOptions.ID}?${encodeURIComponent(JSON.stringify(adjustSettingsArgs))}`; const markdown = new MarkdownString('', true) .appendMarkdown(reason) .appendText(' ') .appendLink(uri, adjustSettings); result.push(new MarkdownHover(this, d.range, [markdown], index++)); </ins> } return result; }
Change:
This looks like a bug in VS Code, I'm seeing a lot of weird behaviors Basically sometimes the 2nd progress is not visible (but when i scroll or add a new cell it magically appears) The output is not displayed at the end (but when i scroll or add a new cell it magically appears) Originally posted by in
Verifying the corresponding bug on jupyter and I found there's still a problem. VS code shows this: ! Jupyter shows this: !
The difference being there seems to be extra lines in the VS code output.
See

Discussion:
super(); const cellEditorOptions = this._register(new CellEditorOptions(this.notebookEditor, this.notebookEditor.notebookOptions, this.configurationService, this.viewCell.language)); <del> this._outputContainerRenderer = this.instantiationService.createInstance(CellOutputContainer, notebookEditor, viewCell, templateData, { limit: 2 }); </del> <ins> this._outputContainerRenderer = this.instantiationService.createInstance(CellOutputContainer, notebookEditor, viewCell, templateData, { limit: 500 }); </ins> this.cellParts = [...templateData.cellParts, cellEditorOptions, this._outputContainerRenderer]; const editorHeight = this.calculateInitEditorHeight();
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. --I work on an extension that has a custom tree view. Some of the items don't have meaningful extra information to show in a tooltip but setting the field in the to or results in the label being used for the tooltip which looks odd as it provides no additional information. We would like it if there was some way to disable tooltips for a tree item. It might be hard to used for that now as that would be a breaking change but perhaps there is some other approach that would be possible. I would note that if the tooltip is required for accessibility in some way then I'm happy that it stays but I think that angle is covered by the aria-label attribute and the tooltip is something else entirely. I have searched and I can't see reference to this from an extension API point of view in the current issues. I am not well versed in the VS Code code base but I believe the issue comes from these lines:
Here is an example screenshot of the issue: ! The supported features are programmatically detected and we don't have a reliable way of providing any additional useful information for the tooltip so being able to avoid it entirely would be desirable.
I think that allowing extensions to have no tooltip is a good feature request. Form an API perspective, do you think setting to empty string is an ok way to accomplish this? I don't think we should use since that would be a big disruption to the current behavior (where the is used).
Yeah, that makes sense to me.
To verify, modify an extension that provides a tree view so that the of it's tree items is an empty string. Verify that no hover is shown on those tree items. You can use the sample for this:

Discussion:
if (!(node instanceof ResolvableTreeItem) || !node.hasResolve) { if (resource && !node.tooltip) { return undefined; <del> } else if (!node.tooltip) { </del> <ins> } else if (node.tooltip === undefined) { </ins> return label; } else if (!isString(node.tooltip)) { return { markdown: node.tooltip, markdownNotSupportedFallback: resource ? undefined : renderMarkdownAsPlaintext(node.tooltip) }; // Passing undefined as the fallback for a resource falls back to the old native hover <del> } else { </del> <ins> } else if (node.tooltip !== '') { </ins> return node.tooltip; <ins> } else { return undefined; </ins> } }

templateData.actionBar.clear(); templateData.icon.style.color = ''; if (resource) { const fileDecorations = this.configurationService.getValue<{ colors: boolean; badges: boolean }>('explorer.decorations'); const labelResource = resource ? resource : URI.parse('missing:_icon_resource');
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.66.0 OS Version: MacOS 11.5.2 Steps to Reproduce: the relevant lines to to enable the prompt it works in regular OS terminal (outside VSCode or inside VSCode without experimental shell integration) <img width="302" alt="image" src="https://user-"the experimental shell integration in VSCode the integrated terminal, visit the same location and see the error <img width="298" alt="image" src="https://user-"
I wonder if instead of replacing the entire , the VSCode change could update it with concatenation so that existing commands remain as they are?
the approach we're taking is to wrap the function, also we need some code before and some code after the original prompt and bash can have it in a bunch of different formats so it's not as easy as it sounds.
/closedWith

Discussion:
IFS=' ' fi builtin read -ra ADDR <<<"$__vsc_original_prompt_command" <del> for ((i = 0; i < ${#ADDR[@]}; i++)); do builtin eval ${ADDR[i]} done </del> if [[ ${__vsc_original_ifs+set} ]]; then IFS="$__vsc_original_ifs" unset __vsc_original_ifs else unset IFS fi <ins> for ((i = 0; i < ${#ADDR[@]}; i++)); do # unset IFS builtin eval ${ADDR[i]} done </ins> __vsc_precmd }
Change:
Issue Type: <bBug</bWith the recent update 1.66, where the release note mentions that repositories are listed in alphabetical order in source control tab. But, this created another bug where if we have 2 repros with same name under a folder, one of them will miss in the list. Steps to reproduce: 1) Create root folder and project1 and project2 as sub folder under it 2) Create a git repo name with 'test' under each project1/2 3) Now add root folder to the project explorer. And you will notice only one test git repo listed under source control tab VS Code version: Code 1.66.0 (, 2022-03-30T05:50:14.623Z) OS version: Windows_NT x64 10.0. Restricted Mode: No Remote OS version: Linux x64 5.4.0-90-generic <!-- generated by issue reporter --
/assign
I've already pointed one duplicate to this. I think a fix needs to be considered for recovery.
yeah, I am currently looking at this and I will make sure that it is in the next recovery release.
The fix for this has been checked into main and it will be fixed in tomorrow's Insiders release. I am also porting this fix to to the release branch and it will be part of the next recovery release.

Discussion:
import { IStorageService, StorageScope, StorageTarget } from 'vs/platform/storage/common/storage'; import { debounce } from 'vs/base/common/decorators'; import { IWorkspaceContextService } from 'vs/platform/workspace/common/workspace'; <del> import { compareFileNames } from 'vs/base/common/comparers'; </del> <ins> import { compareFileNames, comparePaths } from 'vs/base/common/comparers'; </ins> import { basename } from 'vs/base/common/resources'; import { binarySearch } from 'vs/base/common/arrays';

const name1 = getRepositoryName(workspaceContextService, op1); const name2 = getRepositoryName(workspaceContextService, op2); <del> return compareFileNames(name1, name2); </del> <ins> const nameComparison = compareFileNames(name1, name2); if (nameComparison === 0 && op1.provider.rootUri && op2.provider.rootUri) { return comparePaths(op1.provider.rootUri.fsPath, op2.provider.rootUri.fsPath); } return nameComparison; </ins> }; scmService.onDidAddRepository(this.onDidAddRepository, this, this.disposables);

private insertRepository(repositories: ISCMRepository[], repository: ISCMRepository): void { const index = binarySearch(repositories, repository, this._compareRepositories); <del> if (index < 0) { repositories.splice(~index, 0, repository); } </del> <ins> repositories.splice(index < 0 ? ~index : index, 0, repository); </ins> } private onWillSaveState(): void {
Change:
Issue Type: <bBug</bWith the latest update, active and inactive menu in settings UI does not look any different from each other VS Code version: Code 1.66.0 (, 2022-03-30T05:50:14.623Z) OS version: WindowsNT x64 10.0. Restricted Mode: No Remote OS version: Linux x64 3.10.0-1127.10.1.el7.x8664 <details<summarySystem Info</summary </details<details<summaryExtensions (42)</summaryExtensionVersion ------ LogFileHighlighter2.15.0 remotehub0.28.0 better-cpp-syntax1.15.13 blockman1.5.7 jupyter-keymap1.0.0 remote-containers0.231.1 remote-ssh0.78.0 remote-ssh-edit0.78.0 remote-wsl0.66.0 remote-repositories0.4.0 material-icon-theme4.15.0 rewrap1.16.3 vscode-icons11.10.0 vscode-todo-highlight1.0.5 path-intellisense2.8.0 vscode-clock0.0.1 gitlens12.0.5 systemverilog0.12.1 prettier-vscode9.5.0 seito-openfile1.8.8 html-preview-vscode0.2.5 jira-plugin0.22.2 gitlab-workflow3.41.2 gc-excelviewer4.2.54 beautify1.5.0 path-autocomplete1.19.1 svg1.4.17 vscode-jira0.6.0 restructuredtext183.0.0 python2022.4.0 vscode-pylance2022.3.4 jupyter2022.3. jupyter-renderers1.0.6 cpptools1.9.7 veriloghdl1.5.3 subtle-brackets3.0.0 LiveServer5.7.5 code-spell-checker2.1.11 vscode-input-sequence0.2.0 simple-rst1.5.2 vscodeintellicode1.2.17 better-align1.1.6 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/gifPlease
! ! ! !
By "active and inactive menu" I assume you are referring to the tabs labelled "User", "Remote", "Workspace" etc. Which color theme are you using? Do you also see the issue when using the default themes (Light+ and Dark+)?
Yeah, I am referring to "User", "Remote", "Workspace" etc. I am using Night Owl Light Theme
Does this problem occur when you don't have a multi-root workspace open?
The issue is seen only with a multi-root workspace. Is it a known issue?

Discussion:
/* padding must be on action-label because it has the bottom-border, because that's where the .checked class is */ } <ins> .settings-editor > .settings-header > .settings-header-controls .settings-tabs-widget > .monaco-action-bar .action-item.focused { outline-offset: -1.5px; } </ins> .settings-editor > .settings-header > .settings-header-controls .settings-tabs-widget > .monaco-action-bar .action-item .action-label { text-transform: none; font-size: 13px; <del> padding-bottom: 7px; </del> <ins> padding-bottom: 6.5px; </ins> padding-top: 7px; padding-left: 8px; padding-right: 8px; } <ins> .settings-editor > .settings-header > .settings-header-controls .settings-tabs-widget > .monaco-action-bar .action-item .action-label .dropdown-icon { padding-top: 2px; } </ins> .settings-editor > .settings-header > .settings-header-controls .settings-tabs-widget > .monaco-action-bar .action-item .action-label:not(.checked):not(:focus) { /* Add an extra pixel due to it not getting the outline */ padding-bottom: 8px;
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.66.0 OS Version: Windows/Linux Steps to Reproduce: there is a keybinding to . a camel case word with a number immediately preceding an upper case character and leave the cursor at the end of the word, e.g. "foo1Bar|". via keybinding in (1). the cursor to end up before the upper case character (i.e. ), but cursor is observed to be at the beginning of the camel case word (i.e. ).
Will like to request for a review on the issue/MR please. /cc
Still an issue in version 1.67.1. Linked MR is ready for review.
Similar issues: ("Feature 1")

Discussion:
return 0; } <ins> export function isAsciiDigit(code: number): boolean { return code >= CharCode.Digit0 && code <= CharCode.Digit9; } </ins> export function isLowerAsciiLetter(code: number): boolean { return code >= CharCode.a && code <= CharCode.z; }

return new Position(lineNumber, column); } <del> if (strings.isLowerAsciiLetter(left) && strings.isUpperAsciiLetter(right)) { </del> <ins> if ((strings.isLowerAsciiLetter(left) || strings.isAsciiDigit(left)) && strings.isUpperAsciiLetter(right)) { </ins> // camelCaseVariables return new Position(lineNumber, column); }

// thisIsACamelCaseWithOneLetterWords if (column + 1 < maxColumn) { const rightRight = lineContent.charCodeAt(column); <del> if (strings.isLowerAsciiLetter(rightRight)) { </del> <ins> if (strings.isLowerAsciiLetter(rightRight) || strings.isAsciiDigit(rightRight)) { </ins> return new Position(lineNumber, column); } }
Change:
With support for for Electron tests, we should enable terminal tests: I eagerly had enabled them but since we don't know whether Electron smoke tests with are stable, I moved back to only running them in web. We should not enable these tests until we are sure, smoke tests are stable, so maybe this should only happen in May.
Failing macOS run for reference: !
Still not passing, deferring to a debt week

Discussion:
setupSearchTests(logger); setupNotebookTests(logger); setupLanguagesTests(logger); <del> if (opts.web) { setupTerminalTests(logger); } // Not stable on desktop/remote https://github.com/microsoft/vscode/issues/146811 </del> <ins> setupTerminalTests(logger); </ins> setupTaskTests(logger); setupStatusbarTests(logger); if (quality !== Quality.Dev && quality !== Quality.OSS) { setupExtensionTests(logger); }
Change:
All of our ~input controls~ checkboxes in the dark & light theme need to have a 3:1 contrast ratio between its background and adjacent color in the empty state. So either the border (if it has one) or the container's background. cc
I think dropdown doesn't need 3:1 border if it won't be empty. This rule only applies to controls without text or icon inside. If it has text, then the text will be required to have 4.5:1 CCR from another rule (icon will have 3:1). Either of the content inside will satisfy the overall active indicator rule.
Gửi từ điện thoại thông minh Samsung Galaxy của tôi.
Verified with Light+ and Dark+ themes in the Settings editor. The v2 versions of those themes might have an issue, though.

Discussion:
"$schema": "vscode://schemas/color-theme", "name": "Dark (Visual Studio)", "colors": { <ins> "checkbox.border": "#6B6B6B", </ins> "editor.background": "#1E1E1E", "editor.foreground": "#D4D4D4", "editor.inactiveSelectionBackground": "#3A3D41",

"$schema": "vscode://schemas/color-theme", "name": "Light (Visual Studio)", "colors": { <ins> "checkbox.border": "#919191", </ins> "editor.background": "#FFFFFF", "editor.foreground": "#000000", "editor.inactiveSelectionBackground": "#E5EBF1",
Change:
Tracks enabling the new drop into editor features () for code cells in notebooks Was disabled as we were incorrectly showing the drop into indicator while dragging cells within a notebook
Actually looks like may have the most experience in this area. I'll submit a PR shortly that may fix the issue but will need your help verifying it

Discussion:
this._register(DOM.addDisposableListener(document.body, DOM.EventType.DRAG_START, this.onGlobalDragStart.bind(this), true)); this._register(DOM.addDisposableListener(document.body, DOM.EventType.DRAG_END, this.onGlobalDragEnd.bind(this), true)); <del> const addCellDragListener = (eventType: string, handler: (e: CellDragEvent) => void) => { </del> <ins> const addCellDragListener = (eventType: string, handler: (e: CellDragEvent) => void, useCapture = false) => { </ins> this._register(DOM.addDisposableListener( notebookEditor.getDomNode(), eventType,

if (cellDragEvent) { handler(cellDragEvent); } <del> })); </del> <ins> }, useCapture)); </ins> }; addCellDragListener(DOM.EventType.DRAG_OVER, event => { <ins> if (!this.currentDraggedCell) { return; } </ins> event.browserEvent.preventDefault(); <ins> event.browserEvent.stopImmediatePropagation(); </ins> this.onCellDragover(event); <del> }); </del> <ins> }, true); </ins> addCellDragListener(DOM.EventType.DROP, event => { <ins> if (!this.currentDraggedCell) { return; } </ins> event.browserEvent.preventDefault(); this.onCellDrop(event); });

width: width, height: editorHeight }, <ins> enableDropIntoEditor: true, </ins> // overflowWidgetsDomNode: this.notebookEditor.getOverflowContainerDomNode() }, { contributions: this.notebookEditor.creationOptions.cellEditorContributions

width: 0, height: 0 }, <ins> enableDropIntoEditor: true, </ins> }, { contributions: this.notebookEditor.creationOptions.cellEditorContributions });