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 <!-- 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.64.0-insider (user setup) Commit: Date: 2022-01-30T20:09:01.122Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: to install version 1.8.0 (pre-release) or 1.8.1 (pre-release) of the C/C++ extension using VS Code (possible) versus VS Code Insiders (not possible). FYI, we have 1.8.2 (non-pre release) and 1.8.3 (pre-release) released.
Before I was getting this dialog After the fix I can nicely install -verified !
Closing as it appears to have been merged into release branch and verified

Discussion:
if (seenVersions.has(version.version)) { return; } <del> seenVersions.add(version.version); </del> if (await this.isValidVersion(version, preRelease ? 'prerelease' : 'release', true, allTargetPlatforms, targetPlatform)) { result.push({ version: version.version, date: version.lastUpdated, isPreReleaseVersion: isPreReleaseVersion(version) }); <ins> seenVersions.add(version.version); </ins> } } catch (error) { /* Ignore error and skip version */ } }));
Change:
Old behavior: ! New behavior: ! This new behavior doesn't happen all the time, this appears to happen because both suggest and parameter hints use z-index 40 right now. cc Caused by
To verify: Find a method with large parameter docs like Scroll that line to near the top Re-type to trigger hints, the parameter hint should show below Press ctrl+space (or mac equivalent) to show intellisense Also: Reload window Find a method with large parameter docs like Scroll that line to near the top Press ctrl+space (or mac equivalent) to show intellisense Press escape Re-type to trigger hints, the parameter hint should show below Press ctrl+space (or mac equivalent) to show intellisense, intellisense should be on top of parameter hints
I'm seeing this - I expected to see the definition !
when I scroll down a bit: !
that's actually the correct behavior; intellisense should cover the parameter hints popup
oh I was confused because usually old behavior is bad new is good (expected)
so this was a regression?
Yep it was a regression

Discussion:
*--------------------------------------------------------------------------------------------*/ .monaco-editor .parameter-hints-widget { <del> /* Must be higher than sash's z-index and terminal canvases */ z-index: 40; </del> <ins> /* Must be higher than the sash's z-index and terminal canvases but lower than the suggest widget */ z-index: 39; </ins> display: flex; flex-direction: column; line-height: 1.5em;
Change:
Comments cannot be updated using the comment API. Specifically, anything that causes the comment body to change will throw an error:

Discussion:
private updateCommentBody(body: string | IMarkdownString) { this._body.innerText = ''; <del> if (this._md) { this._body.removeChild(this._md); this._md = undefined; } </del> <ins> this._md = undefined; </ins> if (typeof body === 'string') { this._body.innerText = body; } else {
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.63.2 OS Version:MacOS Big Sur Steps to Reproduce: the in repo and Run on any step that shows a PNG image, like ! the image is vertically aligned on Top on the step ! the image is vertically aligned on Center I know SVGs are better alternatives, and its support were to allow themes (), but even PNG images should be properly aligned. Thank you

Discussion:
.monaco-workbench .part.editor>.content .gettingStartedContainer .gettingStartedSlideDetails .gettingStartedDetailsContent.image>.getting-started-media { grid-area: title-start / media-start / steps-end / media-end; align-self: unset; <ins> display: flex; justify-content: center; </ins> } .monaco-workbench .part.editor>.content .gettingStartedContainer.width-semi-constrained .gettingStartedSlideDetails .gettingStartedDetailsContent.image>.getting-started-media {

<del> <svg width="520" height="238" viewBox="0 0 520 238" fill="none" xmlns="http://www.w3.org/2000/svg"> </del> <ins> <svg viewBox="0 0 520 238" fill="none" xmlns="http://www.w3.org/2000/svg"> </ins> <g> <rect width="520" height="238" fill="var(--vscode-breadcrumb-background, #1E1E1E)" /> <g clip-path="url(#clip0_1_138)">

<rect width="115.654" height="39.2998" fill="var(--vscode-activityBar-activeBorder, #FFFFFF)" /> </clipPath> </defs> <del> </svg> </del>  No newline at end of file <ins> </svg> </ins>
Change:
! In the video, I am tabbing from the input, to the first item, then to the first button, and then the next tab, leaves the quickpick completely (which caused the quickpick to close since it lost focus). It seems to only happen on the 2nd tab from a button to the next. /cc
I talked to about this and he mentioned that this is by-design in that we leave navigating around a widget (Actionbar in this case) to the arrow keys. please let me know if I have this wrong. in other words: Tab -navigation between widgets Arrow -navigation within widgets
Yeah this is by design. I agree that this situation here is not the best... check out this aria toolbar example which we are following.
I do get not being able to tab between the individual buttons (and having to use the arrows), but this issue isn't about that. If you open a quick pick without any buttons on items -- you can keep tabbing to cycle around all the parts of the quick pick and not have the quick pick disappear -- it will just cycle. But once an item has buttons, the "tab" after the buttons have focus, causes the whole quick pick to lose focus and if you don't have the "ignoreFocusOut" setting set, the quick pick will close. That IMO can't be by-design.
Yea I guess after that tab is should go back to the input box instead of the editor... do you know if there's a common way to loop around?
I see, thanks for clarifying. I agree with you. the only way I know is to listen to focus changes and programatically set and remove on HTML elements. Which is a pain.
hmm ok. I wonder why it's working without buttons but not with buttons... I'll investigate as soon as I get the time.
Verification: Install GitLens if you don't already have it hover over an inline blame to get the rich hover ! click the show more actions ! That gives you the quick pick mentions in the original issue. Hitting TAB should cycle between: input this list the first quick pick button The quick pick shouldn't be hidden at all during tabbing.
Woo! /verified

Discussion:
break; case KeyCode.Tab: if (!event.altKey && !event.ctrlKey && !event.metaKey) { <del> const selectors = ['.action-label.codicon']; </del> <ins> // detect only visible actions const selectors = [ '.quick-input-list .monaco-action-bar .always-visible', '.quick-input-list-entry:hover .monaco-action-bar', '.monaco-list-row.focused .monaco-action-bar' ]; </ins> if (container.classList.contains('show-checkboxes')) { selectors.push('input'); } else {

// screen readers to read operations in the input box. dom.EventHelper.stop(e, true); list.clearFocus(); <del> } else if (!event.shiftKey && event.target === stops[stops.length - 1]) { </del> <ins> } else if (!event.shiftKey && dom.isAncestor(event.target, stops[stops.length - 1])) { </ins> dom.EventHelper.stop(e, true); stops[0].focus(); }
Change:
VS Code Version: 1.64.0 OS Version: Windows 10 x64 21H1 (Build ) to the shell (pwsh v7.2) My existing PowerShell is setup with module It would look like the following (with listview of history) ! When is configured/enabled and restarted the shell, this is how it looks like ! The history does not show up I do have other modules installed such as and from the looks of it, it seems to be working fine since the theme is showing correctly as before Not sure if any other modules are affected as well
this function should be:
Had to revert, see
! looks fixed to me

Discussion:
# TODO: Gracefully fallback when PSReadLine is not loaded function Global:PSConsoleHostReadLine { <del> [Microsoft.PowerShell.PSConsoleReadLine]::ReadLine($Host.Runspace, $ExecutionContext) </del> <ins> $lastRunStatus = $? Microsoft.PowerShell.CoreSet-StrictMode -Off $tmp = [Microsoft.PowerShell.PSConsoleReadLine]::ReadLine($host.Runspace, $ExecutionContext, $lastRunStatus) </ins> # Write command executed sequence directly to Console to avoid the new line from Write-Host <del> [Console]::Write("`e]133;C`u{7}") </del> <ins> [Console]::Write("`e]133;C`a") return $tmp </ins> } # Set IsWindows property
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. --markdown has built-in math render, but there is no math-snippet
FYI

Discussion:
"body": "~~${1:${TM_SELECTED_TEXT}}~~", "description": "Insert strikethrough" }, <ins> "Insert inline math": { "prefix": [ "inline math" ], "body": "$${1:${TM_SELECTED_TEXT}}$", "description": "Insert inline math" }, "Insert fenced math": { "prefix": [ "fenced math" ], "body": [ "$$", "${1:${TM_SELECTED_TEXT}}", "$$" ], "description": "Insert fenced math" } </ins> }
Change:
Steps to reproduce: a large cell with height more than your screen. same word at the beginning and end of the cell. the word and use <kbdCtrl</kbd<kbdd</kbd(add selection to next find match) The new cursor is now outside viewport which contradicts with its behavior in normal editor (which centers new cursor if outside viewport). Does this issue occur when all extensions are disabled?: Yes VS Code version: Code 1.63.2 (, 2021-12-15T09:39:46.686Z) OS version: Linux x64 5.13.0-22-generic snap Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --

Discussion:
return; } <del> const primarySelection = this.templateData.editor.getSelection(); </del> <ins> const selections = this.templateData.editor.getSelections(); </ins> <del> if (primarySelection) { this.notebookEditor.revealLineInViewAsync(this.viewCell, primarySelection.positionLineNumber); </del> <ins> if (selections?.length) { const lastSelection = selections[selections.length - 1]; this.notebookEditor.revealLineInViewAsync(this.viewCell, lastSelection.positionLineNumber); </ins> } }));

return; } <del> const primarySelection = editor.getSelection(); </del> <ins> const selections = editor.getSelections(); </ins> <del> if (primarySelection) { this.notebookEditor.revealRangeInViewAsync(this.viewCell, primarySelection); </del> <ins> if (selections?.length) { const lastSelection = selections[selections.length - 1]; this.notebookEditor.revealRangeInViewAsync(this.viewCell, lastSelection); </ins> } }));
Change:
Tracks including TS 4.6 in VS Code See and the TS repo for details on upcoming features

Discussion:
"license": "MIT", "description": "Dependencies shared by all extensions", "dependencies": { <del> "typescript": "^4.6.1-rc" </del> <ins> "typescript": "4.6.2" </ins> }, "scripts": { "postinstall": "node ./postinstall"

resolved "https://registry.yarnpkg.com/fast-plist/-/fast-plist-0.1.2.tgz#a45aff345196006d406ca6cdcd05f69051ef35b8" integrity sha1-pFr/NFGWAG1AbKbNzQX2kFHvNbg= <del> typescript@^4.6.1-rc: version "4.6.1-rc" resolved "https://registry.yarnpkg.com/typescript/-/typescript-4.6.1-rc.tgz#75baa823a6fca592f358b486acc2039f103ca2af" integrity sha512-tLPT3GelVfTN9wXPOuPKfY83PkMvgdF3V3gHK/ElNrpQPdLKQ/HMU5cS6+7epYSIF2gne190jzydAW0FLLwU7A== </del> <ins> typescript@4.6.2: version "4.6.2" resolved "https://registry.yarnpkg.com/typescript/-/typescript-4.6.2.tgz#fe12d2727b708f4eef40f51598b3398baa9611d4" integrity sha512-HM/hFigTBHZhLXshn9sN37H085+hQGeJHJ/X7LpBWLID/fbc2acUMfU+lGD98X81sKP+pFa9f0DZmCwB9GnbAg== </ins> vscode-grammar-updater@^1.0.3: version "1.0.3"
Change:
Issue Type: <bBug</bDear VS code team, Searching unicode-korean in bash terminal is little bit buggy. For example, when I type ''(means word), searching box shows ''. Thanks :) VS Code version: Code 1.63.2 (, 2021-12-15T09:40:02.816Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Can you provide a gif? It seems to work for me !
Thanks for your quick response. I'm working on Windows11, VS code 1.63.1 (system setup). [image: Untitled-1 - Visual Studio Code 2022-02-11 11-53-] 2022 2 11 () 8:28, Megan Rogge : !
Can you pls try in insider's? maybe something was fixed since 1.63 or perhaps this is a windows issue only ?
This is indeed broken: ! It should read
Hoping we can fix for December, this makes it unusable for Korean.

Discussion:
@IThemeService private readonly _themeService: IThemeService, @IConfigurationService private readonly _configurationService: IConfigurationService ) { <del> super(findState, { showCommonFindToggles: true, showResultCount: true, type: 'Terminal' }, _contextViewService, _contextKeyService, keybindingService); </del> <ins> super(findState, { showCommonFindToggles: true, checkImeCompletionState: true, showResultCount: true, type: 'Terminal' }, _contextViewService, _contextKeyService, keybindingService); </ins> this._register(findState.onFindReplaceStateChange(() => { this.show();
Change:
! VS Code Version: Version: 1.64.1 Commit: Date: 2022-02-07T17:17:47.733Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.13.0-28-generic OS Version: Ubuntu 20.04 Steps to Reproduce: a Jupyter notebook, just do Ctrl+H and put some strings in find and replace boxes.
Hi - Apology to bother. Is there any update on this issue or any work-around that I can do. Because without the replace-all functionality, it's becoming very hard to manage long notebooks in VSCode.
Just realized this is a regression from previously stable.
NOT Resolved in the latest stable version of code.
Not working on the latest Insiders Version: 1.66.0-insider (user setup) Commit: Date: 2022-03-29T07:31:54.286Z Electron: 17.2.0 Chromium: 98.0.4758.109 16.13.0 V8: 9.8.177.11-electron.0 OS: Windows_NT x64 10.0.
After updating to version 1.66.0 - I get the "Replace All" button activated (as in not grayed-out any more) - But it does NOT work. i.e. after clicking on the button naothing happens.
Hi, this is still not resolved after today's release to Version: 1.67.1 Below my current version details.
can you try again on VS Code Insiders? Otherwise, you'll have to wait for version 1.68.
Great its working in the Insider version. Thanks.

Discussion:
matches.forEach(match => { match.matches.forEach((singleMatch, index) => { <del> if ((singleMatch as OutputFindMatch).index !== undefined) { </del> <ins> if ((singleMatch as OutputFindMatch).index === undefined) { </ins> textEdits.push({ edit: { range: (singleMatch as FindMatch).range, text: texts[index] }, resource: match.cell.uri
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.64.1 (Universal) OS Version: MacOS 11.5.2 Steps to Reproduce: any text in an open text document the search panel using (cmd+shift+f) search field is now erroneously updated. This is a recent regression, though not sure exactly when.
Please, fix this since it is really annoying behavior
closing in favor of
This is not the same as Steps to repro this: : a search near a word in the editor. editor will use the selection to seed the search :bug:
What's the best way to verify this? I tried to repro with VS Code stable, and I couldn't. The setting seems to be about the find widget not the search view, which I'm also confused about. My steps: the setting a text document and select a word +shift+f to open the search view view is never populated with the currently selected word from step 2, no matter what the value of the setting is.
This version should include the fix in I can reproduce the issue with: to a text file and selecting a text (shift+left/right arrow key in my case) Next Selection ( key) the cursor to any other different word in the text without selecting it Next Selection ( key) At this point the other different word is searched instead of the one that was searched in step 3 Reproducible also if is set to in step 1
I believe that this is a different bug. Can you file a new issue for this? This issue seems to concern workspace search (++)
The verification steps shoud be as follows: a workspace search with an arbitrary string in settings. some text in your editor that is different from the string that you searched. for workspace search. that the text in the search input does not update using the selection.

Discussion:
private updateTextFromSelection({ allowUnselectedWord = true, allowSearchOnType = true }, editor?: IEditor): boolean { const seedSearchStringFromSelection = this.configurationService.getValue<IEditorOptions>('editor').find!.seedSearchStringFromSelection; <del> if (!seedSearchStringFromSelection) { </del> <ins> if (!seedSearchStringFromSelection || seedSearchStringFromSelection === 'never') { </ins> return false; }
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. --Hello Guys, Add a new Feature in the theme to Change the Color of the Scroll to Top while reading any Extension's Readme. Because Default Blue Color Does not match some Theme's. <br<brExample:- "extensionButton.scrolltotop": "#"; !<br<br
We don't need a new theme key specifically for this. Instead it should use one of the existing ones, likely the ones for buttons
hello! Can I work on this issue? Maybe we can using existing one , or create new color setting for these buttons.

Discussion:
height: 40px; right: 25px; bottom: 25px; <del> background-color:#444444; </del> <ins> background-color:var(--vscode-button-background); </ins> border-radius: 50%; cursor: pointer; box-shadow: 1px 1px 1px rgba(0,0,0,.25);

} #scroll-to-top:hover { <del> background-color:#007acc; </del> <ins> background-color:var(--vscode-button-hoverBackground); </ins> box-shadow: 2px 2px 2px rgba(0,0,0,.25); }
Change:
This problem still occurs even if you disable all extensions. in Fenced code blocks for JSONC doesn't work well in Markdown. On the other hand, in Fenced code blocks for JSON and JSON5 does work well. Create the following Fenced code blocks for JSONC. jsonc { "settings": true } Then run on the line with . You will get the following results: jsonc { &lt;!-- "settings": true --} The correct result is: jsonc { // "settings": true } ` Execute repeatedly !
I'd like to work on this. Could you please give me some leads?
I made the PR. Could you please check it?

Discussion:
"meta.embedded.block.pug": "jade", "meta.embedded.block.javascript": "javascript", "meta.embedded.block.json": "json", <ins> "meta.embedded.block.jsonc": "jsonc", </ins> "meta.embedded.block.less": "less", "meta.embedded.block.objc": "objc", "meta.embedded.block.scss": "scss",
Change:
shell integration some commands and drop the terminal in the editor area a decoration context menu
the inverse is also broken - drag from editor area to panel click a decoration no context menu
The context menu is working for me now, but the alignment is not correct !
original issue was a duplicate of Renaming to address the alignment issue

Discussion:
padding-right: 20px; } <del> .monaco-workbench .editor-instance .terminal-group .monaco-split-view2.horizontal .split-view-view:first-child .xterm .terminal-command-decoration, </del> .monaco-workbench .pane-body.integrated-terminal .terminal-group .monaco-split-view2.horizontal .split-view-view:first-child .xterm .terminal-command-decoration { margin-left: -17px; } <del> .monaco-workbench .editor-instance .terminal-group .monaco-split-view2.horizontal .split-view-view .xterm .terminal-command-decoration, </del> <ins> .monaco-workbench .editor-instance .xterm .terminal-command-decoration, .monaco-split-view2.vertical .split-view-view .xterm .terminal-command-decoration, </ins> .monaco-workbench .pane-body.integrated-terminal .terminal-group .monaco-split-view2.horizontal .split-view-view .xterm .terminal-command-decoration { margin-left: -12px; }
Change:
Issue Type: <bFeature Request</b The Test Explorer filter should be preserved if a window reload occurs, rather than resetting to default. This behavior could be gated by a setting. ! VS Code version: Code - Insiders 1.65.0-insider (, 2022-02-16T05:16:18.653Z) OS version: WindowsNT x64 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (32)</summaryExtensionVersion ------ vscode-color0.4.5 vscode-opennewinstance0.0.12 gitlens11.7.0 filter-lines1.0.0 EditorConfig0.16.4 prettier-vscode9.2.0 copilot-nightly1.7.5030 remotehub0.24.0 gc-excelviewer4.0.50 todo-tree0.0.215 vscode-drawio1.6.4 change-case1.0.2 vscode-peacock4.0.0 git-graph1.30.0 vscode-azurefunctions1.6.0 vscode-azureresourcegroups0.4.0 vscode-docker1.19.0 remote-containers0.222.0 azure-account0.10.0 powershell-preview2022.2.1 indent-rainbow8.2.2 docthis0.8.2 pester-test2021.10.2 vscode-commons0.0.6 vscode-yaml1.4.0 vscode-inline-values-powershell0.0.5 errorlens3.4.1 vscode-icons11.10.0 codetour0.0.58 gistfs0.3.0 gitmoji-vscode1.0.9 better-align1.1.6 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
That makes sense.
I'm still able to reproduce this with the latest mainline build. May I pick this up since it's still open?
Sure!

Discussion:
const wrapper = this.wrapper = dom.$('.testing-filter-wrapper'); container.appendChild(wrapper); <ins> const history = this.history.get([]); if (history.length) { this.state.setText(history[history.length - 1]); } </ins> const input = this.input = this._register(this.instantiationService.createInstance(ContextScopedSuggestEnabledInputWithHistory, { id: 'testing.explorer.filter', ariaLabel: localize('testExplorerFilterLabel', "Filter text for tests in the explorer"),

value: this.state.text.value, placeholderText: localize('testExplorerFilter', "Filter (e.g. text, !exclude, @tag)"), }, <del> history: this.history.get([]) </del> <ins> history </ins> })); this._register(attachSuggestEnabledInputBoxStyler(input, this.themeService));