jiebi/CodeConvo huggingface dataset:
Change:
if (!profileExtension.version && preRelease) { profileExtension.preRelease = true; } <del> result.push(profileExtension); </del> <ins> result.set(profileExtension.identifier.id.toLowerCase(), profileExtension); </ins> } <del> return result; </del> <ins> return [...result.values()]; </ins> }); }

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes, actually this issue has nothing to do with extensions <!-- 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. --- Version: 1.79.1 (user setup) Commit: Date: 2023-06-12T16:14:05.102Z Electron: 22.5.7 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: Connect to WSL(Ubuntu ) Profiles =Show Contents... <img width="286" alt="image" src=""As you can see, the extensions of the profile are duplicated. The reason I found is I installed the extensions in WSL again. Maybe It's not a bug. But, the profile should distinguish between extensions installed in the host and WSL. Maybe like this: ESLint - host Disabled ESLint - WSL So that I know which place I install the extension and its enabled/disabled status. When I open the detail page of the duplicated extensions, both of them display an "Extension is enabled on 'WSL: Ubuntu-22.04'" message. What I expect is: The extension is installed and enabled on the host, the message should be "Extension is enabled". The extension is installed and enabled on the WSL, the message should be "Extension is enabled on 'WSL: Ubuntu-22.04'". Does it make sense?
Related on Stack Overflow: .

Let me know if there's any debugging steps or details you'd like be to solicit from people in my answer there.
/duplicate
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for . See also our . Happy Coding!
what's it a duplicate of?
I am sorry, I remembered this bug and thought there is an issue already, but there is not. Reopened it.
I guess duplicate only shows for extensions installed in both local VS Code and remote hosts. !
Fixed: Contents show only one instance of the extension
Change:
async logFile(uri: Uri, options?: LogFileOptions): Promise<Commit[]> { const maxEntries = options?.maxEntries ?? 32; <del> const args = ['log', `-${maxEntries}`, `--format=${COMMIT_FORMAT}`, '-z', '--', uri.fsPath]; </del> <ins> const args = ['log', `-n${maxEntries}`, `--format=${COMMIT_FORMAT}`, '-z', '--', uri.fsPath]; </ins> const result = await this.run(args); if (result.exitCode) {

Discussion:
VSCode Version: 1.42.0 OS Version: Darwin x64 19.2.0 Git version: 2.24.1 Steps to Reproduce: and Debug extension git api commands, specifically Results in This format option was introduced here, and seems to be the change causing the issues I'm experiencing:
Reopening as it is not merged yet.
Change:
for (( i = 0; i < ${#str}; ++i )); do byte="${str:$i:1}" <del> # Backslashes must be doubled. </del> <ins> # Escape backslashes and semi-colons </ins> if [ "$byte" = "" ]; then token="" <del> # Conservatively pass alphanumerics through. elif [[ "$byte" == [0-9A-Za-z] ]]; then token="$byte" # Hex-encode anything else. # (Importantly including: semicolon, newline, and control chars). </del> <ins> elif [ "$byte" = ";" ]; then token="x3b" </ins> else <del> token="x${(l:2::0:)$(( [##16] #byte ))}" #            | |  |       |/|/ |_____| #            | |  |       | |     | # left-pad --+ |  |       | |     +- the byte value of the character # two digits --+  |       | +------- in hexadecimal # with '0' -------+       +--------- with no prefix </del> <ins> token="$byte" </ins> fi out+="$token"

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No Splitting terminal in folder with ë character or any subdirectories errors and doesn't split. The terminal process failed to launch: Starting directory (cwd) "/Users/liam-nt/Documents/vscodebugtest/eÃ«e" does not exist. <!-- 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 (Universal) OS Version: macOS Monterey 12.5 (21G72) Steps to Reproduce: a folder containing 'ë' in name integrated VSCode terminal and split terminal by keyboard shortcut or interface.
related
!
Regression from is encoding all multibyte utf8 characters
Change:
return _sanitizeCwd(cwd); } <ins> function _resolveCwd(cwd: string, lastActiveWorkspace: IWorkspaceFolder | undefined, configurationResolverService: IConfigurationResolverService | undefined, logService?: ILogService): string | undefined { if (configurationResolverService) { try { return configurationResolverService.resolve(lastActiveWorkspace, cwd); } catch (e) { logService?.error('Could not resolve terminal cwd', e); return undefined; } } return cwd; } </ins> function _sanitizeCwd(cwd: string): string { // Make the drive letter uppercase on Windows (see #9448) if (platform.platform === platform.Platform.Windows && cwd && cwd[1] === ':') {

Discussion:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.39.2 OS Version: macOS 10.14.3 Steps to Reproduce: the new terminal.newWithCwd command as a new keybinding: to use the new keybinding with an open editor while using VS Code Remote - SSH. Expected Result: New terminal created with the cwd set at ${fileDirname} Actual Result: Error: '${fileDirname}' can not be resolved. Please open an editor. Notes: The keybinding works correctly when working with local directories. The issue only appears over SSH. The Terminal Here extension does work over SSH and accomplishes the same thing, but I would rather use the native feature if possible. The "echo ${fileDirname}" command (run through a task) prints the correct directory over SSH.
is the resolver service being used incorrectly here? seems to resolve fine but not or .
Configuration resolver is owned by hence assigning to him.
that usage seems good. Just make sure you always pass a workspace in. Also note that might be working as expacted ${workspaceFolder} can only be resolved if a folder is opened in VSCode, not in the pruple vscode. ${fileDirname} should always be resolved if there is an open file fyi
Change:
const snippets = contributes?.snippets || []; snippets.forEach(snippet => { <ins> if (!isString(snippet.language)) { // ignore invalid snippets return; } </ins> let language = byId[snippet.language]; if (language) {

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 89.1 x64 OS Version: Edition Windows 11 Pro Version 23H2 Installed on ‎2023-‎11-‎28 OS build .3593 Experience Windows Feature Experience Pack 1000..1003.0 Steps to Reproduce: the VS Code the introduction page of buildin plugin the FEATURES page 's Empty
I am seeing following !
Yes, I see the same. There should be details about supported languages like other built-in plugins.
Can you point me to the place I need to fix this?
Here it is
Change:
import { DiffEditorWidget } from 'vs/editor/browser/widget/diffEditor/diffEditorWidget'; import { LineRange, LineRangeSet } from 'vs/editor/common/core/lineRange'; import { Range } from 'vs/editor/common/core/range'; <del> import { RangeMapping } from 'vs/editor/common/diff/rangeMapping'; </del> <ins> import { LineRangeMapping, RangeMapping } from 'vs/editor/common/diff/rangeMapping'; </ins> import { GlyphMarginLane } from 'vs/editor/common/model'; import { localize } from 'vs/nls';

Discussion:
a change it using the gutter arrow :bug: indentation is lost
Can you share a screenshot/screenrecording and provide context on the document you have? Thanks!
Cannot reproduce: ! Please always try to include as much context as you can.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Hi Henning I think I can also reproduce this in 1.84.0-insider (MacOS). I believe the preconditions to reproduce is to set (which is also the default) and revert a deleted code chunk. See attached gif. !
Hey this issue might need further attention. you can help us out by closing this issue if the problem no longer exists, or adding more information.
Change:
// We only want to fire a telemetry if we haven't seen this account yet in this session. if (!this._accountsSeen.has(session.account.id)) { this._accountsSeen.add(session.account.id); <del> this._githubServer.sendAdditionalTelemetryInfo(session.accessToken); </del> <ins> this._githubServer.sendAdditionalTelemetryInfo(session); </ins> } }

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: NA OS Version: NA Steps to Reproduce: The github education team sees about calls from Visual-studio-code in an hour for api/user. This is quite unusual and since we are rate limiting anyway, it is not an immediate issue. From initial discussions with I understand that the call is made only for telemetry and has no impact on the user. So, raising this bug, if we can find a better way to do telemetry without having to rate limit. This here shows some more details.
, can you please help me understand what is the likelihood of this work getting prioritised and by when can we expect to resolve this issue.
I wasn't able to get to it this week during our allocated debt time so I will try again to make time early April. I'll let you know if anything changes.
Change:
multipleDefinitions: input.multipleDefinitions ?? EditorStringEnumOption.stringSet<GoToLocationValues>(input.multipleDefinitions, 'peek', ['peek', 'gotoAndPeek', 'goto']), multipleTypeDefinitions: input.multipleTypeDefinitions ?? EditorStringEnumOption.stringSet<GoToLocationValues>(input.multipleTypeDefinitions, 'peek', ['peek', 'gotoAndPeek', 'goto']), multipleDeclarations: input.multipleDeclarations ?? EditorStringEnumOption.stringSet<GoToLocationValues>(input.multipleDeclarations, 'peek', ['peek', 'gotoAndPeek', 'goto']), <del> multipleImplemenations: input.multipleImplemenations ?? EditorStringEnumOption.stringSet<GoToLocationValues>(input.multipleImplemenations, 'peek', ['peek', 'gotoAndPeek', 'goto']), </del> <ins> multipleImplementations: input.multipleImplementations ?? EditorStringEnumOption.stringSet<GoToLocationValues>(input.multipleImplementations, 'peek', ['peek', 'gotoAndPeek', 'goto']), </ins> multipleReferences: input.multipleReferences ?? EditorStringEnumOption.stringSet<GoToLocationValues>(input.multipleReferences, 'peek', ['peek', 'gotoAndPeek', 'goto']), }; }

Discussion:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.41.0-insider OS Version: Windows_NT x64 10.0. Steps to Reproduce: to settings for "Implemenations" "Editor Goto Location: Multiple Implemenations" appears instead of "Editor Goto Location: Multiple Implementations" This also shows up as "editor.gotoLocation.multipleImplemenations" in "" instead of as "editor.gotoLocation.multipleImplementations" <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Change:
text = editor.getModel().getValueInRange(selection, endOfLinePreference); } instance.sendText(text, true, true); <del> await focusActiveTerminal(instance, terminalEditorService, terminalGroupService); </del> <ins> await revealActiveTerminal(instance, terminalEditorService, terminalGroupService); </ins> } }); registerAction2(class extends Action2 {

Discussion:
Type: <bBug</bThis was working in the previous version, now when running lines of code from the editor with "key": "ctrl+enter", "command": "" The cursor automatically snaps to the terminal which is extremely annoying. Please fix this ASAP. VS Code version: Code 1.75.0 (, 2023-02-01T15:23:45.584Z) OS version: Windows_NT x64 10.0. Modes: Sandboxed: No Remote OS version: Linux x64 5.15.0-1031-azure <details<summaryExtensions (25)</summaryExtensionVersion ------ better-cpp-syntax1.17.2 jupyter-keymap1.0.0 vscode-ai-remote0.22.0 remote-containers0.275.0 remote-ssh0.96.0 remote-ssh-edit0.84.0 remote-wsl0.75.1 vscode-remote-extensionpack0.23.0 remote-explorer0.2.0 material-icon-theme4.23.1 vscode-kdb-q-forked1.2.2 unique-lines1.0.0 gitlens13.2.0 json-tools1.0.2 isort2022.8.0 python2023.2.0 vscode-pylance2023.2.10 jupyter2023.1. jupyter-keymap1.0.0 jupyter-renderers1.0.14 vscode-ai0.24.0 vscode-jupyter-cell-tags0.1.6 vscode-jupyter-slideshow0.1.5 azure-account0.11.3 code-spell-checker2.16.0 (2 theme extensions excluded) </details<!-- generated by issue reporter --
Temporary work around is to use to refocus on editor 1, however that's not really effective for long periods of time.
in order to run text in the terminal, we need to focus it. this is working as designed
this wasn't the case on the previous version. You could execute lines of code from the editor with e.g. ctrl+enter without shifting focus to the terminal.

Here is a very simple example from the previous version I have on another machine: <img width="467" alt="image" src="https://user-"<img width="838" alt="image" src="https://user-"All 3 lines are executed with ctrl+enter, and focus does not shift to the terminal so I can e.g. move up/down and execute lines, type lines to execute on the fly. Please advise further as this was definately the behaviour in 1.74.3 and now broken in 1.75.0
ran into the same issue as you. Suspect you've already done this, but a quick fix is to add a new keybinding in with the multi-command extension installed:
Thank you so much for this workaround! If anyone else needs this, the extension is
This was caused by where it changed from just revealing to focusing
Thanks !
Hi, pls do we know when will be new release with this fix publicly available?
it will come in 1.76 which should get releases in about 3 weeks time.
Change:
import { assertIsDefined } from 'vs/base/common/types'; import 'vs/css!./parameterHints'; import { ContentWidgetPositionPreference, ICodeEditor, IContentWidget, IContentWidgetPosition } from 'vs/editor/browser/editorBrowser'; <del> import { EditorOption } from 'vs/editor/common/config/editorOptions'; </del> <ins> import { EDITOR_FONT_DEFAULTS, EditorOption } from 'vs/editor/common/config/editorOptions'; </ins> import * as languages from 'vs/editor/common/languages'; import { ILanguageService } from 'vs/editor/common/languages/language'; import { IMarkdownRenderResult, MarkdownRenderer } from 'vs/editor/browser/widget/markdownRenderer/browser/markdownRenderer';

Discussion:
I got the default font rendered in the parameter hint widget. It looks alien compared to the rest of the hover widget UI. Steps: chat sample line 21 type the following: will see the parameter hints with a weird font (default system?) ! fyi
I haven't been able to reproduce this Are you still seeing this issue? Does it only show up with specific functions?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Yes, I still see this. I see this for all parameter hovers. I have nailed this down to be due to this setting I got a new mac, so most likely I do not have Fira Code installed. So the Editor seems to fall back nicely to a good default font, and Parameter Hints falls back to a non coding font. Which looks like the gist of this bug. I will reopen this so you can chime in. Thanks
Change:
background-color: var(--vscode-editor-findMatchBackground); } </style> <del> <style id="vscode-tokenization-styles" nonce="${this.nonce}">${getTokenizationCss()}</style> </del> </head> <body style="overflow: hidden;"> <div id='findStart' tabIndex=-1></div>

Discussion:
<!-- Please search existing issues to avoid creating duplicates. --- VS Code version: 1.79.1 Jupyter Extension version: 2023.5. Python Extension version: 2023.10.1 OS and version: Windows 11 Home Version 22H2, build .1778 If I change the theme after entering code in a Markdown cell, the code highlighting should change accordingly. Light theme: <img width="51" alt="image" src=""Dark theme: <img width="52" alt="image" src=""The code highlighting in Markdown cells does not change according to the theme. Light theme: <img width="44" alt="image" src=""Dark theme: <img width="48" alt="image" src=""an .ipynb file. a Markdown cell. some text formatted as code, e.g. python a = 5 ` Shift + Enter to render cell. theme (for example, if code was entered when using Light Modern, switch to Dark Modern). The code highlighting in the Markdown cell does not change and is now difficult to read.
Change:
*  Licensed under the MIT License. See License.txt in the project root for license information. *--------------------------------------------------------------------------------------------*/ <ins> import { mainWindow } from 'vs/base/browser/window'; </ins> import { isRemoteDiagnosticError, SystemInfo } from 'vs/platform/diagnostics/common/diagnostics'; import { ISettingSearchResult, IssueReporterExtensionData, IssueType } from 'vs/platform/issue/common/issue'; export interface IssueReporterData { issueType: IssueType; issueDescription?: string; <ins> issueTitle?: string; </ins> extensionData?: string; versionInfo?: any;

Discussion:
Testing to open the issue reporter for an extension issue reporter open, return to the main window step 1 for another extension =issue reporter opens but doesn't update the issue reporter input fields.
Change:
this.notificationService.info(message); }); <ins> ipc.on('vscode:displayChanged', (event: IpcEvent) => { clearAllFontInfos(); }); </ins> // Fullscreen Events ipc.on('vscode:enterFullScreen', async () => { await this.lifecycleService.when(LifecyclePhase.Ready);

Discussion:
VSCode Version: 1.27.2 OS Version: Windows 10 Enterprise 1803 Build .345 Steps to Reproduce: Pre Condition: Dual monitor setup. Screen 1 on top of Screen 2. Screen 1 Scale set to 150% Screen 2 Scale set to 125% Visual studio code open with a python script on Screen 1. down some p-thon the cursor back a few char positions and make note. the vs code app from Screen 1 to Screen 2 where it resizes. the relocation of the cursor. your code and note that the cursor does not match the output text. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Unsure. Note: I am unsure if this is a Windows 10 bug or Visual Studio code bug but I have not noticed this on other software at the time of this bug report. In the meantime I have aligned my screen scaling as a work around for this issue.
This is caused by scaling difference. The bigger the scaling difference, the more evident. I have my surface book 2's main monitor set to 150% scaling, and my external monitor set to 100% scaling. Leaving VSCode open after the monitor switch will result in bad the cursor alignment. The workaround is to restart VSCode.

Version 1.19.3 Commit Date 2018-01-25T10:36:34.867Z Shell 1.7.9 Renderer 58.0.3029.110 Node 7.9.0 Architecture x64 Steps to Reproduce: VSCode using 4K monitors (150x magnify) the session remotely via RDP using 1080p monitors From now on, even if taking back the session locally, the caret position is corrupt. The picture shows the result of highlighting the "location" word. The caret has an offset of 4 characters to the right. ! Does this issue occur when all extensions are disabled?: Yes

Following the discussion in Repro steps on Windows: use a monospace font, make sure ligatures are not used, etc. (i.e. default editor related settings) change the scale setting of the display the editor decorations / selection should render correctly (on top of the correct text) (the problem was that the font measurements done with a certain display scale were used across all display scales).
Change:
if (this._state.isReplaceRevealed) { if (!this._codeEditor.getConfiguration().readOnly && !this._isReplaceVisible) { this._isReplaceVisible = true; <ins> this._replaceInputBox.width = this._findInput.inputBox.width; </ins> this._updateButtons(); } } else {

Discussion:
VSCode Version: Code 1.17.2 (, 2017-10-16T13:47:41.889Z) OS Version: Darwin x64 17.0.0 Extensions: Extensions are disabled Steps to Reproduce: Find widget (choose Edit -Find). the Find widget. the Find widget. Find widget with replace feature (choose Edit -Replace). of the Replace textbox is not same as the Find textbox, while expecting them to be same. <!-- Launch with to check. --Reproduces without extensions: Yes
It does not reproduce for me (Windows 10 x64, VSCode 1.17.2, extensions disabled).
Strange...I can reproduce this problem on all platforms that I have access (macOS, Linux, Windows 10 x64 in a VM) with version 1.17.2.
I don't have access to other platforms now, but this is how it works for me: ! Maybe this bug appears only in VM or something.
Your recording actually shows exactly how this bug is reproduced. Please note difference of green bounding boxes of two text boxes in the Find widget. When opened, bounding box of the Replace textbox is much wider than it of the Find textbox (where they should be same as each other). Also, please try to resize the Find widget and see how bounding box of the Replace textbox changes.
I guess that's what meant: ! Input box of find and replace should be the same length, however they are not if you do Find -Resize Find Box -Replace.
Ok, sorry for misleading, I thought it was about whole widget box, not just text field inside it, I see it now!