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.73.1 OS Version: macOS Ventura 13.0.1 Steps to Reproduce: VoiceOver a command that uses a Quick Pick List where the items have a as well as a title or description (demoed with Azure Extension "Create Resource") list a command that uses a Quick Pick List where the items have no detail, e.g. "Select Display Language" or even command palette reader will read the title of the new item with the detail of the item in the previously displayed quick pick list https://user- Same bug with the command palette reading details for items: https://user-
This issue is caused by the item still containing the values from the previous list.
Verification steps: the issue steps are good. If you want a non-Azure extension command that shows a quick pick with details, use

Discussion:
// Meta if (element.saneDetail) { <ins> data.detail.element.style.display = ''; </ins> data.detail.setLabel(element.saneDetail, undefined, { matches: detailHighlights, title: element.saneDetail }); <del> } /* else { // TODO investigate potential detail bleeding into next quickpicks data.detail.setLabel(''); } */ </del> <ins> } else { data.detail.element.style.display = 'none'; } </ins> // Separator if (element.item && element.separator && element.separator.label) {

private static QUICK_INPUT_INPUT = `${QuickInput.QUICK_INPUT} .quick-input-box input`; private static QUICK_INPUT_ROW = `${QuickInput.QUICK_INPUT} .quick-input-list .monaco-list-row`; private static QUICK_INPUT_FOCUSED_ELEMENT = `${QuickInput.QUICK_INPUT_ROW}.focused .monaco-highlighted-label`; <del> private static QUICK_INPUT_ENTRY_LABEL = `${QuickInput.QUICK_INPUT_ROW} .label-name`; </del> <ins> // Note: this only grabs the label and not the description or detail private static QUICK_INPUT_ENTRY_LABEL = `${QuickInput.QUICK_INPUT_ROW} .quick-input-list-row > .monaco-icon-label .label-name`; </ins> private static QUICK_INPUT_ENTRY_LABEL_SPAN = `${QuickInput.QUICK_INPUT_ROW} .monaco-highlighted-label`; constructor(private code: Code) { }
Change:
I switched from a testing profile to my default profile on my Windows machine, and got a message that my macOS machine turned on remote access, even though it's not even on. !
I didn't think of that, good catch. I use settings sync as a communication channel to learn about other machines connecting to a tunnel. I guess I need to add a timestamp as well.

Discussion:
import { joinPath } from 'vs/base/common/resources'; import { join } from 'vs/base/common/path'; import { ITunnelApplicationConfig } from 'vs/base/common/product'; <ins> import { isNumber, isObject, isString } from 'vs/base/common/types'; </ins> export const REMOTE_TUNNEL_CATEGORY: ILocalizedString = { original: 'Remote Tunnels',

const REMOTE_TUNNEL_USED_STORAGE_KEY = 'remoteTunnelServiceUsed'; const REMOTE_TUNNEL_PROMPTED_PREVIEW_STORAGE_KEY = 'remoteTunnelServicePromptedPreview'; const REMOTE_TUNNEL_EXTENSION_RECOMMENDED_KEY = 'remoteTunnelExtensionRecommended'; <ins> const REMOTE_TUNNEL_EXTENSION_TIMEOUT = 4 * 60 * 1000; // show the recommendation that a machine started using tunnels if it joined less than 4 minutes ago interface UsedOnHostMessage { hostName: string; timeStamp: number } </ins> type ExistingSessionItem = { session: AuthenticationSession; providerId: string; label: string; description: string }; type IAuthenticationProvider = { id: string; scopes: string[] };

if (await this.extensionService.getExtension(remoteExtension.extensionId)) { return false; } <del> const usedOnHost = this.storageService.get(REMOTE_TUNNEL_USED_STORAGE_KEY, StorageScope.APPLICATION); if (!usedOnHost) { </del> <ins> const usedOnHostMessage = this.storageService.get(REMOTE_TUNNEL_USED_STORAGE_KEY, StorageScope.APPLICATION); if (!usedOnHostMessage) { return false; } let usedOnHost: string | undefined; try { const message = JSON.parse(usedOnHostMessage); if (!isObject(message)) { return false; } const { hostName, timeStamp } = message as UsedOnHostMessage; if (!isString(hostName)! || !isNumber(timeStamp) || new Date().getTime() > timeStamp + REMOTE_TUNNEL_EXTENSION_TIMEOUT) { return false; } usedOnHost = hostName; } catch (_) { // problems parsing the message, likly the old message format </ins> return false; } const currentHostName = await this.remoteTunnelService.getHostName();

] } }); <del> storageService.store(REMOTE_TUNNEL_USED_STORAGE_KEY, connectionInfo.hostName, StorageScope.APPLICATION, StorageTarget.USER); </del> <ins> const usedOnHostMessage: UsedOnHostMessage = { hostName: connectionInfo.hostName, timeStamp: new Date().getTime() }; storageService.store(REMOTE_TUNNEL_USED_STORAGE_KEY, JSON.stringify(usedOnHostMessage), StorageScope.APPLICATION, StorageTarget.USER); </ins> } else { await notificationService.notify({ severity: Severity.Info,
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.75 Insiders OS Version: macOS https://user-
It seems we have a transparent background when using the v2 dark theme. Though there should always be a bg color fallback.
The relevant color here is . There are two problems: this should be defined opaque if this isn't opaque, maybe we should force it to be opaque in code
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!
this is
I'm still seeing this with Peek View. The problems listed by is not being fixed it seems. <img width="1330" alt="image" src="https://user-"
Not for me. Please provide repro info like the theme you are using and/or customisations you are doing <img width="1103" alt="Screenshot 2022-12-13 at 08 34 25" src="https://user-"
I'm using Dark+ V2 (experimental) theme.
Likely just a theme bug then. I'll take a look.

Discussion:
"panelTitle.activeBorder": "#2488d8", "panelTitle.activeForeground": "#ffffffc5", "panelTitle.inactiveForeground": "#8b949e", <del> "peekViewEditor.background": "#6e76811a", </del> <ins> "peekViewEditor.background": "#1f1f1f", </ins> "peekViewEditor.matchHighlightBackground": "#bb800966", "peekViewResult.background": "#1f1f1f", "peekViewResult.matchHighlightBackground": "#bb800966",

"panelTitle.activeBorder": "#005FB8", "panelTitle.activeForeground": "#000000e4", "panelTitle.inactiveForeground": "#000000e4", <del> "peekViewEditor.background": "#6e76811a", </del> "peekViewEditor.matchHighlightBackground": "#bb800966", "peekViewResult.background": "#ffffff", "peekViewResult.matchHighlightBackground": "#bb800966",
Change:
I think this started for me with the new insiders version today, when I press to open symbol, often focus remains in the editor and is not put into the input box. See video: ! Steps for me are to switch to another editor and then immediately try //cc for a related fix in this area
I can still reproduce in todays insider, but with command palette. !
This seems to happen when the input box is not shown so: ctrl+tab cmd+shift+p
points me to this
thanks a lot for bisecting this and the revert

Discussion:
const focusChanged = !this.ui?.container.contains(document.activeElement); this.controller = null; this.onHideEmitter.fire(); <del> const ui = this.getUI(); ui.container.style.display = 'none'; ui.list.setElements([]); </del> <ins> this.getUI().container.style.display = 'none'; </ins> if (!focusChanged) { let currentElement = this.previousFocusElement; while (currentElement && !currentElement.offsetParent) {
Change:
I think this started for me with the new insiders version today, when I press to open symbol, often focus remains in the editor and is not put into the input box. See video: ! Steps for me are to switch to another editor and then immediately try //cc for a related fix in this area
I can still reproduce in todays insider, but with command palette. !
This seems to happen when the input box is not shown so: ctrl+tab cmd+shift+p
points me to this
thanks a lot for bisecting this and the revert

Discussion:
} public select(range: IRange | null = null): void { <ins> this.input.select(); </ins> if (range) { this.input.setSelectionRange(range.start, range.end); if (range.end === this.input.value.length) { this.input.scrollLeft = this.input.scrollWidth; } <del> } else { this.input.select(); </del> } }
Change:
I think it used to be a lighter gray: <img width="797" alt="image" src="https://user-"
This looks normal to me. Do you mean the tooltip?
No this: <img width="683" alt="image" src="https://user-"Compared with stable: <img width="555" alt="image" src="https://user-"

Discussion:
} .monaco-editor .parameter-hints-widget .signature .parameter.active { <del> color: var(--vscode-editor-hoverHighlightForeground); </del> <ins> color: var(--vscode-editorHoverWidget-highlightForeground); </ins> font-weight: bold; }
Change:
From: Crash dump: I tried to use but the result seems weird, maybe you can help me explain how you do it? Attaching the output here:
will use symbols from which does not contain symbols for our custom Electron builds, so you will have to manually replace the symbols under with corresponding ones extracted from
should address this crash.
but then our instructions are not correct right? can we please update them to explain how to do this step by step? thanks!

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

"git": { "name": "chromium", "repositoryUrl": "https://chromium.googlesource.com/chromium/src", <del> "commitHash": "16e28102fdf876ce6d136674ba66343ede07441f" </del> <ins> "commitHash": "a8a8309404d39efa9c624d7aee0e27562721e522" </ins> } }, "licenseDetail": [

"SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE." ], "isOnlyProductionDependency": true, <del> "version": "102.0.5005.167" </del> <ins> "version": "102.0.5005.194" </ins> }, { "component": {

}, "isOnlyProductionDependency": true, "license": "MIT", <del> "version": "19.1.8" </del> <ins> "version": "19.1.9" </ins> }, { "component": {

"cssnano": "^4.1.11", "debounce": "^1.0.0", "deemon": "^1.8.0", <del> "electron": "19.1.8", </del> <ins> "electron": "19.1.9", </ins> "eslint": "8.7.0", "eslint-plugin-header": "3.1.1", "eslint-plugin-jsdoc": "^39.3.2",

resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.4.207.tgz#9c3310ebace2952903d05dcaba8abe3a4ed44c01" integrity sha512-piH7MJDJp4rJCduWbVvmUd59AUne1AFBJ8JaRQvk0KzNTSUnZrVXHCZc+eg+CGE4OujkcLJznhGKD6tuAshj5Q== <del> electron@19.1.8: version "19.1.8" resolved "https://registry.yarnpkg.com/electron/-/electron-19.1.8.tgz#3ce19c270ca86d05bbf0df5ceeaea2d23edc7083" integrity sha512-UfPQdFjgKI0xCm1V5sV3iAVOs0kCwAE91xWzV5tI7ij14yOkxTdXp9BqTzFaSbQYLYxn6q1BUUe1nlzjJjzAnw== </del> <ins> electron@19.1.9: version "19.1.9" resolved "https://registry.yarnpkg.com/electron/-/electron-19.1.9.tgz#01995eea4014f7cdb2f616f5f3492d4ed6f5e4f0" integrity sha512-XT5LkTzIHB+ZtD3dTmNnKjVBWrDWReCKt9G1uAFLz6uJMEVcIUiYO+fph5pLXETiBw/QZBx8egduMEfIccLx+g== </ins> dependencies: "@electron/get" "^1.14.1" "@types/node" "^16.11.26"
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.74.0 OS Version: Windows 11 Steps to Reproduce: dragging the minimap slider from the left edge. the mouse to the right of the minimap while scrolling. how the slider on the minimap stops scrolling the editor. https://user-
Do you see any errors in developer tools? (Help Toggle Developer Tools)
No, I don't see any errors in the developer tools. I think it's caused by a really annoying feature of windows that is standard across all scrollbars. This explains the feature: It seams strange that in VSCode the minimap slider snaps back even when the mouse is still on the minimap slider. I think you should either increase the buffer zone referred to in the link, to make sure that the minimap slider never snaps back when the mouse is still on the slider while dragging, or completely remove the snap back feature which is how it is on macOS:

Discussion:
this._slider.toggleClassName('active', true); const handlePointerMove = (posy: number, posx: number) => { <del> const pointerOrthogonalDelta = Math.abs(posx - initialPosX); </del> <ins> const minimapPosition = dom.getDomNodePagePosition(this._domNode.domNode); const pointerOrthogonalDelta = Math.min( Math.abs(posx - initialPosX), Math.abs(posx - minimapPosition.left), Math.abs(posx - minimapPosition.left - minimapPosition.width) ); </ins> if (platform.isWindows && pointerOrthogonalDelta > POINTER_DRAG_RESET_DISTANCE) { // The pointer has wondered away from the scrollbar => reset dragging
Change:
Steps to Reproduce: Open theme picker Select any theme Nothing happens
After , I new also get a with empty active
Maybe related?
Yes this appears to have happened yesterday. This change is suspicious:

Discussion:
const focusChanged = !this.ui?.container.contains(document.activeElement); this.controller = null; this.onHideEmitter.fire(); <del> const ui = this.getUI(); ui.container.style.display = 'none'; ui.list.setElements([]); </del> <ins> this.getUI().container.style.display = 'none'; </ins> if (!focusChanged) { let currentElement = this.previousFocusElement; while (currentElement && !currentElement.offsetParent) {
Change:
open two editor side by side drag the sidebar sash and the sash between the editors there will be screen cheese, looks like a redraw is missing at time <img width="1025" alt="Screenshot 2022-12-08 at 11 53 29" src="https://user-"

Discussion:
} .monaco-editor .sticky-line-root { <ins> background-color : inherit; </ins> overflow : hidden; white-space : nowrap; width : 100%;
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.74.0 OS Version: Ubuntu 20.04.1 When an extension assigns a value to an input box's property, the box slightly moves to the right or left (See the screen capture below). Note that it's not because of text length changes or other text rendering details. Even re-assigning the property with a constant value makes the shaking happen. I've made a repo to help verify this on your side. As of my observations, the problem was not present in VS Code v1.72. It's now happening in v1.74 (I'm not sure about v1.73 since I've skipped that update). this repo (it's a sample extension): the cloned directory in VS Code. debugging by pressing F5. the opened window, open the command palette, find the "Hello World" command and invoke it. should now see a shaking input box, like this: ! The extension just creates an input box, and repeatedly updates the title of the input box with a constant value:
I've pushed a fix for that.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
/verified

Discussion:
ui.message.style.display = visibilities.message ? '' : 'none'; ui.progressBar.getContainer().style.display = visibilities.progressBar ? '' : 'none'; ui.list.display(!!visibilities.list); <del> ui.container.classList.toggle('show-checkboxes', visibilities.checkBox); </del> <ins> ui.container.classList.toggle('show-checkboxes', !!visibilities.checkBox); </ins> this.updateLayout(); // TODO }
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.74.0 OS Version: macOS 13.0 Error when launching terminal with fish integration set up: Steps to Reproduce: terminal. is there.

Discussion:
# Sent whenever a new fish prompt is about to be displayed. # Updates the current working directory. function __vsc_update_cwd --on-event fish_prompt <del> __vsc_esc P "Cwd=$(__vsc_escape_value "$PWD")" </del> <ins> __vsc_esc P Cwd=(__vsc_escape_value "$PWD") </ins> # If a command marker exists, remove it. # Otherwise, the commandline is empty and no command was run.
Change:
Based on the user studies I noticed that users always get confused when they have to choose which profile to rename. I suggest to just keep the one that is renaming the active profile. The action to rename an non active profile is not needed imho. If you want we can keep it in the command palette.

Discussion:
category: PROFILES_CATEGORY, f1: true, precondition: ContextKeyExpr.and(PROFILES_ENABLEMENT_CONTEXT, HAS_PROFILES_CONTEXT), <del> menu: [ { id: ManageProfilesSubMenu, group: '3_manage_profiles', when: PROFILES_ENABLEMENT_CONTEXT, order: 1 } ] </del> }); }
Change:
Type: <bBug</bSteps to reproduce: a fresh, vanilla VS Code Insiders installation without any extensions. and open a new folder. , open it, and save it with the following contents: Actual results: A warning is reported in Problems tab and via yellow squiggles at line 10, column 25 (= character of the line specifying the ): Expected results: No warning is reported. Additional information: The problem matcher has been copied directly from the (). VS Code should not display warnings for unmodified examples from the docs. This also occurs in the current non-insiders release 1.74.0. VS Code version: Code - Insiders 1.75.0-insider (, 2022-12-08T05:20:51.149Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I can repro this. probably caused by your changes to the schema - could you pls take a look?
Of course. I'll submit the fix.
The PR is ready for review.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
/verified Thanks for the quick fix!

Discussion:
}, { type: 'array', <del> items: { type: 'string' }, </del> <ins> prefixItems: [ { type: 'string', enum: ['absolute', 'relative', 'autoDetect', 'search'] }, ], minItems: 1, maxItems: 1, additionalItems: false }, { type: 'array', prefixItems: [ { type: 'string', enum: ['relative', 'autoDetect'] }, { type: 'string' }, ], minItems: 2, maxItems: 2, additionalItems: false, </ins> examples: [ ['relative', '${workspaceFolder}'], ['autoDetect', '${workspaceFolder}'],

}, { type: 'array', <del> items: [ </del> <ins> prefixItems: [ </ins> { type: 'string', enum: ['search'] }, { type: 'object',

required: ['include'] } ], <ins> minItems: 2, maxItems: 2, </ins> additionalItems: false, examples: [ ['search', { 'include': ['${workspaceFolder}'] }],