jiebi/CodeConvo huggingface dataset:
Change:
Type: <bBug</ba md file: a url inside the block (this is an alternative way to create a fenced code block) bug The url is incorrectly pasted as a markdown link VS Code version: Code - Insiders 1.81.0-insider (Universal) (, 2023-07-25T08:15:40.243Z) OS version: Darwin x64 22.5.0 Modes: <details<summarySystem Info</summary </details<!-- generated by issue reporter --

Discussion:
{ regex: /[.*](.*)/g, isMarkdownLink: true, isInline: true }, // Is a Markdown Link { regex: /![.*](.*)/g, isMarkdownLink: true, isInline: true }, // Is a Markdown Image Link { regex: /[([^]]*)](([^)]*))/g, isMarkdownLink: false, isInline: true }, // In a Markdown link <del> { regex: /^```[sS]*?```$/gm, isMarkdownLink: false, isInline: false }, // In a fenced code block </del> <ins> { regex: /^```[sS]*?```$/gm, isMarkdownLink: false, isInline: false }, // In a backtick fenced code block { regex: /^~~~[sS]*?~~~$/gm, isMarkdownLink: false, isInline: false }, // In a tildefenced code block </ins> { regex: /^$$[sS]*?$$$/gm, isMarkdownLink: false, isInline: false }, // In a fenced math block { regex: /`[^`]*`/g, isMarkdownLink: false, isInline: true }, // In inline code { regex: /$[^$]*$/g, isMarkdownLink: false, isInline: true }, // In inline math

assert.strictEqual(smartPaste.pasteAsMarkdownLink, true); }); <del> test('Should evaluate pasteAsMarkdownLink as false for pasting within a code block', () => { </del> <ins> test('Should evaluate pasteAsMarkdownLink as false for pasting within a backtick code block', () => { </ins> skinnyDocument.getText = function () { return '```rnrn```'; }; const range = new vscode.Range(0, 5, 0, 5); const smartPaste = checkSmartPaste(skinnyDocument, range); assert.strictEqual(smartPaste.pasteAsMarkdownLink, false); }); <ins> test('Should evaluate pasteAsMarkdownLink as false for pasting within a tilde code block', () => { skinnyDocument.getText = function () { return '~~~rnrn~~~'; }; const range = new vscode.Range(0, 5, 0, 5); const smartPaste = checkSmartPaste(skinnyDocument, range); assert.strictEqual(smartPaste.pasteAsMarkdownLink, false); }); </ins> test('Should evaluate pasteAsMarkdownLink as false for pasting within a math block', () => { skinnyDocument.getText = function () { return '$$$rnrn$$$'; }; const range = new vscode.Range(0, 5, 0, 5);
Change:
Type: <bBug</ba md file: a url inside the fence code blocks the paste as widget that shows up bug <img width="745" alt="Screenshot 2023-07-25 at 3 31 41 PM" src=""The paste as widget says that the url was pasted as a markdown link but really from the user's point of view it was just pasted the link as plain text Some ideas on how to fix this if smart paste detects that we aren't actually going to insert a markdown link: Don't return any result from . This will prevent the paste as widget from showing upshould always return an edit that inserts a markdown link. However if smart paste detects that we are not in a valid link location (such as inside a code block) the markdown link pasting should be deprioritized so that the default paste happens first. Take a look at for this VS Code version: Code - Insiders 1.81.0-insider (Universal) (, 2023-07-25T08:15:40.243Z) OS version: Darwin x64 22.5.0 Modes: <details<summarySystem Info</summary </details<!-- generated by issue reporter --
I still see this: !
So the new functionality is supposed to have the 'Smartly Insert Link' label which was previously the 'Insert as Markdown Link' label. This is a fix so that neither paste function is deprioritized and the labels still make sense to the user!

Discussion:
return; } <del> uriEdit.label = pasteEdit.label; </del> <ins> uriEdit.label = pasteUrlSetting === PasteUrlAsFormattedLink.Smart ? vscode.l10n.t('Smartly Insert Link') : pasteEdit.label; </ins> uriEdit.additionalEdit = pasteEdit.additionalEdits; return uriEdit; }
Change:
only seen in OSS so far outline view shows 'No symbols found in document '*.ipynb' or a very limited amount of the outline logs show an exception:

Discussion:
this._onDidChange.dispose(); this._dispoables.dispose(); this._entriesDisposables.dispose(); <ins> this._outlineProvider?.dispose(); </ins> } }

this._register(this.instantiationService.createInstance(NotebookEditorContextKeys, this)); <del> this._notebookOutline = this.instantiationService.createInstance(NotebookCellOutlineProvider, this, OutlineTarget.QuickPick); </del> <ins> this._notebookOutline = this._register(this.instantiationService.createInstance(NotebookCellOutlineProvider, this, OutlineTarget.QuickPick)); </ins> this._register(notebookKernelService.onDidChangeSelectedNotebooks(e => { if (isEqual(e.notebook, this.viewModel?.uri)) {

dispose(): void { // selectionListener.clear(); <ins> this._entriesDisposables.dispose(); </ins> this._dispoables.dispose(); }

}; if (this._configurationService.getValue(OutlineConfigKeys.problemsEnabled)) { markerServiceListener.value = this._markerService.onMarkerChanged(e => { <ins> if (notebookEditorWidget.isDisposed) { console.error('notebook editor is disposed'); return; } </ins> if (e.some(uri => notebookEditorWidget.getCellsInRange().some(cell => isEqual(cell.uri, uri)))) { doUpdateMarker(false); this._onDidChange.fire({});
Change:
Testing seems to fail on zsh shell: !
Moving this to August same as the other issue:
Let me know if we're unable to fix this in time, in which case I'll stop prepending for zsh in Python extension.
Looking into it now

Discussion:
IFS=':' read -rA ADDR <<< "$VSCODE_ENV_PREPEND" for ITEM in "${ADDR[@]}"; do VARNAME="$(echo ${ITEM%%=*})" <del> export $VARNAME="$(echo -e {ITEM#*=})${(P)VARNAME}" </del> <ins> export $VARNAME="$(echo -e ${ITEM#*=})${(P)VARNAME}" </ins> done unset VSCODE_ENV_PREPEND fi

IFS=':' read -rA ADDR <<< "$VSCODE_ENV_APPEND" for ITEM in "${ADDR[@]}"; do VARNAME="$(echo ${ITEM%%=*})" <del> export $VARNAME="${(P)VARNAME}$(echo -e {ITEM#*=})" </del> <ins> export $VARNAME="${(P)VARNAME}$(echo -e ${ITEM#*=})" </ins> done unset VSCODE_ENV_APPEND fi
Change:
a cell that updates the same line of output continuously :bug: extra character appended at the end and the last update doesn't seem to occur !

Discussion:
} } <del> const didCompression = compressStreamBuffer(buffers); const data = formatStreamText(VSBuffer.concat(buffers.map(buffer => VSBuffer.wrap(buffer)))); </del> <ins> let didCompression = compressStreamBuffer(buffers); const concatenated = VSBuffer.concat(buffers.map(buffer => VSBuffer.wrap(buffer))); const data = formatStreamText(concatenated); didCompression = didCompression || data.byteLength !== concatenated.byteLength; </ins> return { data, didCompression }; }
Change:
Still investigating two issues: It will be safest to revert to the old certificate loading for now until we get more time for investigating and testing fixes for these issues.
Closing for verification.
To verify: Set log level to trace. Reload window. Check that the Extension Host output channel does not contain any entries. (To cross-check you can re-enable the reverted behavior with the user setting: )

Discussion:
import { IExtensionDescription } from 'vs/platform/extensions/common/extensions'; import { LogLevel, createHttpPatch, createProxyResolver, createTlsPatch, ProxySupportSetting, ProxyAgentParams, createNetPatch } from '@vscode/proxy-agent'; <del> const systemCertificatesV2Default = true; </del> <ins> const systemCertificatesV2Default = false; </ins> export function connectProxyResolver( extHostWorkspace: IExtHostWorkspaceProvider,
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. --

Discussion:
} } <del> private _runRestartTaskCommand(arg?: any): void { const runQuickPick = (promise?: Promise<Task[]>) => { this._showQuickPick(promise || this.getActiveTasks(), </del> <ins> private async _runRestartTaskCommand(arg?: any): Promise<void> { const activeTasks = await this.getActiveTasks(); if (activeTasks.length === 1) { this._restart(activeTasks[0]); return; } if (this.inTerminal()) { // try dispatching using task identifier const identifier = this._getTaskIdentifier(arg); if (identifier !== undefined) { for (const task of activeTasks) { if (task.matches(identifier)) { this._restart(task); return; } } } // show quick pick with active tasks const entry = await this._showQuickPick( activeTasks, </ins> nls.localize('TaskService.taskToRestart', 'Select the task to restart'), { label: nls.localize('TaskService.noTaskToRestart', 'No task to restart'), task: null }, <del> false, true ).then(entry => { const task: Task | undefined | null = entry ? entry.task : undefined; if (task === undefined || task === null) { return; } this._restart(task); }); }; if (this.inTerminal()) { const identifier = this._getTaskIdentifier(arg); let promise: Promise<Task[]>; if (identifier !== undefined) { promise = this.getActiveTasks(); promise.then((tasks) => { for (const task of tasks) { if (task.matches(identifier)) { this._restart(task); return; } } runQuickPick(promise); }); } else { runQuickPick(); </del> <ins> false, true ); if (entry && entry.task) { this._restart(entry.task); </ins> } } else { <del> this.getActiveTasks().then((activeTasks) => { if (activeTasks.length === 0) { return; } const task = activeTasks[0]; this._restart(task); }); </del> <ins> if (activeTasks.length > 0) { this._restart(activeTasks[0]); } </ins> } }
Change:
The main menu entries have a scrollbar when needed: ! The custom context menu has none, even when needed: ! Looking at the sources, I see that the menu sets it to visible though:
Oh wow, looks like they do appear in other places though, outside the editor: !
This is 100% related to the use of shadow DOM, commenting out this resolves it:
Thanks!!

Discussion:
padding: 0 1.8em; } <del> .linux .monaco-menu .monaco-action-bar.vertical .submenu-indicator { </del> <ins> .linux .monaco-menu .monaco-action-bar.vertical .submenu-indicator, </ins> :host-context(.linux) .monaco-menu .monaco-action-bar.vertical .submenu-indicator { height: 100%; mask-size: 10px 10px;
Change:
Type: <bBug</bSteps: VS Code text in the terminal. Ctrl+F to search. You won't see results. a different word and Ctrl+F. You will see matches for the previous word searched. steps 2-4. Same issue. a word in search box. It will work. the word in search and repeat steps 2-4. Issue still persists. VS Code version: Code 1.80.2 (, 2023-07-27T20:40:28.909Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (50)</summaryExtensionVersion ------ pascal9.6.0 pascal-formatter2.8.1 vscode-intelephense-client1.9.5 doxdocgen1.4.0 githistory0.6.20 go0.39.1 minifier0.0.4 better-cpp-syntax1.17.2 tws1.0.1 restructuredtext189.3.0 add-to-gitignore1.0.0 Lisp0.1.12 pretty-formatter0.2.2 vscode-docker1.26.0 csharp1.26.0 vscode-edge-devtools2.1.3 black-formatter2023.4.1 isort2023.10.1 python2023.12.0 vscode-pylance2023.7.40 jupyter2023.6. jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.299.0 remote-ssh0.102.0 remote-ssh-edit0.86.0 remote-wsl0.80.2 cmake-tools1.14.34 cpptools1.16.3 cpptools-extension-pack1.3.0 hexeditor1.9.12 live-server0.4.9 powershell2023.6.0 vscode-serial-monitor0.10.0 debugger-for-edge1.0.15 vscode-groovy-lint2.0.0 java1.21.0 code-spell-checker2.20.5 simple-rst1.5.3 cmake0.0.17 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 vscode-arduino0.6.0 vscode-java-debug0.52.0 vscode-java-dependency0.23.0 vscode-java-pack0.25.12 vscode-java-test0.39.0 vscode-maven0.41.0 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
does this repro in insider's?
Yes.

Discussion:
override reveal(): void { const initialInput = this._instance.hasSelection() && !this._instance.selection!.includes('n') ? this._instance.selection : undefined; <ins> const inputValue = initialInput ?? this.inputValue; </ins> const xterm = this._instance.xterm; <del> if (xterm && this.inputValue && this.inputValue !== '') { </del> <ins> if (xterm && inputValue && inputValue !== '') { </ins> // trigger highlight all matches <del> this._findPreviousWithEvent(xterm, this.inputValue, { incremental: true, regex: this._getRegexValue(), wholeWord: this._getWholeWordValue(), caseSensitive: this._getCaseSensitiveValue() }).then(foundMatch => { </del> <ins> this._findPreviousWithEvent(xterm, inputValue, { incremental: true, regex: this._getRegexValue(), wholeWord: this._getWholeWordValue(), caseSensitive: this._getCaseSensitiveValue() }).then(foundMatch => { </ins> this.updateButtons(foundMatch); this._register(Event.once(xterm.onDidChangeSelection)(() => xterm.clearActiveSearchDecoration())); }); } this.updateButtons(false); <del> super.reveal(initialInput); </del> <ins> super.reveal(inputValue); </ins> this._findWidgetVisible.set(true); }
Change:
Describe the bug There's a typo in an error message within the file. To Reproduce Steps to reproduce the behavior: Go to src/vs/platform/encryption/electron- Notice the typo "valu" which should be "value" Expected behavior The error message should read "Invalid encrypted value" instead of "Invalid encrypted valu".

Discussion:
{ "name": "code-oss-dev", "version": "1.82.0", <del> "distro": "2a9b1552a828c44e6454db2848ba954f2497a6b3", </del> <ins> "distro": "bc3b9188018c76ecdd69d813c95c5101e5f3da5e", </ins> "author": { "name": "Microsoft Corporation" },

try { parsedValue = JSON.parse(value); if (!parsedValue.data) { <del> throw new Error(`[EncryptionMainService] Invalid encrypted valu: ${value}`); </del> <ins> throw new Error(`[EncryptionMainService] Invalid encrypted value: ${value}`); </ins> } const bufferToDecrypt = Buffer.from(parsedValue.data);
Change:
VS Code Version: OS Version: Steps to Reproduce: a Markdown file without pending changes and check the More Actions menu in the upper right of the editor. The Open Accessible Diff Viewer command is visible. Selecting the command has no effect. ! the Markdown preview for the file and check the More Actions menu. The Open Accessible Diff Viewer command is visible. !
Thanks for finding this! I don't know how I missed this.
Fixed by and

Discussion:
}, order: 10, group: '2_diff', <del> when: EditorContextKeys.accessibleDiffViewerVisible.negate(), </del> <ins> when: ContextKeyExpr.and( EditorContextKeys.accessibleDiffViewerVisible.negate(), ContextKeyExpr.has('isInDiffEditor'), ), </ins> }); export class AccessibleDiffViewerPrev extends Action2 {
Change:
Code-OSS dev tools this message
From , cc do you want to look at this?
I'm in the middle of moving otherwise I would. If it can wait until next weekend I don't mind
From
sorry about the late response. I just returned from moving and a wedding and can sort this out tomorrow if you are not already working on it?
Sure, I haven't looked closely, thanks
After reviewing I can say this is not from our changes. This is prehistoric to us and . For my changes I just did the same thing for continuity. Additionally using vscode I can not see these warnings in dev console or any of the output channels. So this may be specific to code-oss, could be wrong though. Either way, perhaps the solution is to correctly escape the prefixes in all instances where needed Since I don't use code-oss and can't reproduce in vscode I can't verify if that change sufficiently satisfies the code-oss warning
That's a different pattern, in those the second fixes it

Discussion:
}, "$a <=> $b": { "prefix": "spaceship", <del> "body": "(${1:$$a} <=> ${2:$$b} === ${3|0,1,-1|})", </del> <ins> "body": "(${1:$a} <=> ${2:$b} === ${3|0,1,-1|})", </ins> "description": "Spaceship equality check" }, "attribute": {
Change:
Look after is merged in Dark Modern: !
I see that it's currently using via Changing it to works, but I'm wondering what exactly broke this and why it was using in the first place?
It might have just always been out of sync which is common between the editor and simple find widget
! left : version 81 right : insiders Maybe it's related to background-color ?
! test, --vscode-panelInput-border color effect
hi , I don't know if it's some new issues.
is the find bg color meant to look like that?
Yes—changes made in to make editor widget and quick input backgrounds lighter to more easily distinguish against the editor background.
Yes, it's normal.Terminal simple find widget just not synchronized with the editor.

Discussion:
background-color: var(--vscode-editorWidget-background) !important; color: var(--vscode-editorWidget-foreground); box-shadow: 0 0 8px 2px var(--vscode-widget-shadow); <del> border: 1px solid var(--vscode-contrastBorder); </del> <ins> border: 1px solid var(--vscode-widget-border); </ins> border-bottom-left-radius: 4px; border-bottom-right-radius: 4px; font-size: 12px;
Change:
Hi. i am creating a theme pack for VSCode. I have discovered that there is a to customize the background color of a status bar hovered item but there is no option to customize the color of the hovered item foreground color. Something like !
<!-- -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!
Yeah there seems to be colors like but not the relevant foreground colors. //cc
Added with values defaulting to in . You'll be able to set that manually in your or in the theme itself.
nice, but we do have more hover backgrounds: <img width="725" alt="image" src=""I am not sure about the compact one but maybe prominent one needs it too?
Added via

Discussion:
"--vscode-statusBarItem-errorForeground", "--vscode-statusBarItem-focusBorder", "--vscode-statusBarItem-hoverBackground", <ins> "--vscode-statusBarItem-hoverForeground", </ins> "--vscode-statusBarItem-prominentBackground", "--vscode-statusBarItem-prominentForeground", "--vscode-statusBarItem-prominentHoverBackground",

.monaco-workbench .part.statusbar > .items-container > .statusbar-item > a:hover:not(.disabled) { text-decoration: none; <ins> color: var(--vscode-statusBarItem-hoverForeground); </ins> } .monaco-workbench .part.statusbar > .items-container > .statusbar-item > a.disabled {

hcLight: Color.black.transparent(0.12) }, localize('statusBarItemHoverBackground', "Status bar item background color when hovering. The status bar is shown in the bottom of the window.")); <ins> export const STATUS_BAR_ITEM_HOVER_FOREGROUND = registerColor('statusBarItem.hoverForeground', { dark: STATUS_BAR_FOREGROUND, light: STATUS_BAR_FOREGROUND, hcDark: STATUS_BAR_FOREGROUND, hcLight: STATUS_BAR_FOREGROUND }, localize('statusBarItemHoverForeground', "Status bar item foreground color when hovering. The status bar is shown in the bottom of the window.")); </ins> export const STATUS_BAR_ITEM_COMPACT_HOVER_BACKGROUND = registerColor('statusBarItem.compactHoverBackground', { dark: Color.white.transparent(0.20), light: Color.white.transparent(0.20),
Change:
Depending oh how many editors windows are open and the size of them, sometimes the standalone color picker is partially hidden behind other editor panel. vscode version:1.81.0 x64 !

Discussion:
static readonly ID = 'editor.contrib.standaloneColorPickerWidget'; readonly allowEditorOverflow = true; <del> private body: HTMLElement = document.createElement('div'); </del> private readonly _position: Position | undefined = undefined; private readonly _standaloneColorPickerParticipant: StandaloneColorPickerParticipant; <ins> private _body: HTMLElement = document.createElement('div'); </ins> private _colorHover: StandaloneColorPickerHover | null = null; private _selectionSetInEditor: boolean = false;

endLineNumber: editorSelection.endLineNumber, endColumn: editorSelection.endColumn } : { startLineNumber: 0, endLineNumber: 0, endColumn: 0, startColumn: 0 }; <del> const focusTracker = this._register(dom.trackFocus(this.body)); </del> <ins> const focusTracker = this._register(dom.trackFocus(this._body)); </ins> this._register(focusTracker.onDidBlur(_ => { this.hide(); }));

this._render(result.value, result.foundInEditor); })); this._start(selection); <ins> this._body.style.zIndex = '50'; </ins> this._editor.addContentWidget(this); }

} public getDomNode(): HTMLElement { <del> return this.body; </del> <ins> return this._body; </ins> } public getPosition(): IContentWidgetPosition | null {

public focus(): void { this._standaloneColorPickerFocused.set(true); <del> this.body.focus(); </del> <ins> this._body.focus(); </ins> } private async _start(selection: IRange) {

if (colorPickerWidget === undefined) { return; } <del> this.body.classList.add('standalone-colorpicker-body'); this.body.style.maxHeight = Math.max(this._editor.getLayoutInfo().height / 4, 250) + 'px'; this.body.style.maxWidth = Math.max(this._editor.getLayoutInfo().width * 0.66, 500) + 'px'; this.body.tabIndex = 0; this.body.appendChild(fragment); </del> <ins> this._body.classList.add('standalone-colorpicker-body'); this._body.style.maxHeight = Math.max(this._editor.getLayoutInfo().height / 4, 250) + 'px'; this._body.style.maxWidth = Math.max(this._editor.getLayoutInfo().width * 0.66, 500) + 'px'; this._body.tabIndex = 0; this._body.appendChild(fragment); </ins> colorPickerWidget.layout(); const colorPickerBody = colorPickerWidget.body;
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. --When the user has a high debounce delay and changes the files to include/exclude text fields it can take a couple of seconds for the search results to update. This could be fixed by giving the user the option to skip this delay by pressing enter. This already happens with the search text field. It seams like calling triggerQueryChange(); after the user presses enter in one of the fields would fix this problem. Maybe somewhere in setSearchParameters (line 1,329) at
I'll try to fix this

Discussion:
if (options.triggeredOnType && !this.searchConfig.searchOnType) { return; } if (!this.pauseSearching) { <ins> const delay = options.triggeredOnType ? options.delay : 0; </ins> this.triggerQueryDelayer.trigger(() => { this._onQueryChanged(options.preserveFocus, options.triggeredOnType); <del> }, options.delay); </del> <ins> }, delay); </ins> } }