jiebi/CodeConvo huggingface dataset:
Change:
import { CommandsRegistry } from 'vs/platform/commands/common/commands'; import { FileIconThemeData } from 'vs/workbench/services/themes/browser/fileIconThemeData'; import { IConfigurationService } from 'vs/platform/configuration/common/configuration'; <ins> import { IDialogService } from 'vs/platform/dialogs/common/dialogs'; </ins> export const manageExtensionIcon = registerIcon('theme-selection-manage-extension', Codicon.gear, localize('manageExtensionIcon', 'Icon for the 'Manage' action in the theme selection quick pick.'));

Discussion:
Pre-req: Settings Sync on brand new empty profile a theme Settings sync asks this strange question: ! Additionally: this dialog Theme is still applied but not installed
I tried and can't repro. Are there any specific steps you followed?
were there specific steps to repro this?
I can verify that cancelling the dialog no longer leaves the theme applied, thanks I can still reproduce the main issue though. Why would I not want to synchronize the theme I just picked for my brand new profile, given the profile is being synced?
I think is using the general extension install command that will ask user to sync or not before installing. If it is in core, one can use the API directly to install.
I think we still want an install confirmation dialog, but I agree that there should be no question about syncing.
Change:
@command('git.rebaseAbort', { repository: true }) async rebaseAbort(repository: Repository): Promise<void> { <del> await repository.rebaseAbort(); </del> <ins> if (repository.rebaseCommit) { await repository.rebaseAbort(); } else { await window.showInformationMessage(localize('no rebase', "No rebase in progress.")); } </ins> } private createCommand(id: string, key: string, method: Function, options: CommandOptions): (...args: any[]) => any {

Discussion:
Testing Currently the command is always in the command palette. I would expect it to appear only when I am in the middle of a rebase. Not sure if we could introduce some context keys which would be true when we are in the middle of the rebase. And then use those context keys as part of the commands clause
Since triggering it outside of a rebase produces this expected error. Do we polish the message, since it looks a bit strange with the double !
Verification steps: Launch VS Code and close existing folder if needed Verify that command is not available in the command palette Open a Git repository Verify that command is not available in the command palette Switch to the SCM viewlet, and click on --- Verify that an information notification is displayed noting that there is no rebase in progress Use the steps from to rebase a topic branch on top of the main branch Verify that command is available in the command palette Invoke the command from the command palette Verify that command is available in the command palette
Change:
"tas-client-umd": "0.1.5", "vscode-oniguruma": "1.6.1", "vscode-textmate": "7.0.1", <del> "xterm": "4.19.0-beta.49", </del> <ins> "xterm": "4.19.0-beta.52", </ins> "xterm-addon-search": "0.9.0-beta.37", "xterm-addon-unicode11": "0.4.0-beta.3", "xterm-addon-webgl": "0.12.0-beta.36"

Discussion:
Issue Type: <bBug</bIn the regular MacOS terminal (outside Visual Studio Code), option+click will move the cursor to a given point in the text. This is nice for editing the middle of a long command line, or for moving around vim. However, when the MacOS Terminal is being run inside Visual Studio Code, when I option+click text, the cursor moves close to where I clicked, but it's off by about 3 characters. VS Code version: Code 1.63.2 (, 2021-12-15T09:38:17.605Z) OS version: Darwin arm64 21.1.0 Restricted Mode: No Remote OS version: Linux x64 5.4.0-105-generic <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ remote-ssh0.70.0 python2022.4.1 vscode-pylance2022.4.2 references-view0.0.89 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Guessing this is related to padding on
Does not reproduce in the demo
VS Code uses padding but the demo doesn't, try adding to
shouldn't the padding be on the cursor layer? nvm made the change in the wrong
I think this rule is the problem but haven't looked into it: ! We recently moved the padding from to I think which would explain the regression
Change:
}, { "name": "ms-vscode.js-debug", <del> "version": "1.71.0", </del> <ins> "version": "1.71.1", </ins> "repo": "https://github.com/microsoft/vscode-js-debug", "metadata": { "id": "25629058-ddac-4e17-abba-74678e126c5d",

Discussion:
Type: <bBug</bI tried to run the debugger and it's just did not start the server, it just freezed. VS Code version: Code 1.71.0 (Universal) (, 2022-09-01T07:25:38.437Z) OS version: Darwin arm64 21.6.0 Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (68)</summaryExtensionVersion ------ better-comments3.0.2 codesnap1.3.4 toggle-block-comments1.3.0 laravel-extra-intellisense0.6.2 laravel-blade-spacer2.1.3 vscode-intelephense-client1.8.2 npm-intellisense1.4.2 vscode-sql-beautify0.3.15 laravel-goto-view1.3.7 dart-code3.48.0 flutter3.48.0 vscode-markdownlint0.48.1 vscode-eslint2.2.6 javascript-ejs-support1.3.1 es7-react-js-snippets4.4.3 vscode-babel-coloring0.0.4 gitlens12.2.1 vscode-html-css1.13.1 tslint1.0.47 vscode-npm-script0.3.28 prettier-vscode9.8.0 comment-anchors1.9.6 auto-rename-tag0.1.10 copilot1.43.6621 laravel-create-view0.0.6 php-awesome-snippets1.1.3 helium-icon-theme1.0.0 rest-client0.25.1 laravel-blade-wrapper1.0.1 vue0.1.5 JavaScriptSnippetsStandard1.8.0 auto-comment-blocks1.0.1 vscode-phpfmt1.0.31 php-namespace-resolver1.1.9 vscode-language-babel0.0.36 dotenv1.0.1 djlint2022.7.2 vscode-docker1.22.1 remote-containers0.252.0 vscode-typescript-tslint-plugin1.3.4 laravel-goto-components1.2.0 vetur0.36.0 laravel-blade1.32.0 laravel-extension-pack1.1.0 laravel5-snippets1.15.0 docker-compose0.3.

5 live-sass3.0.0 LiveServer5.7.9 nunjucks0.3.1 laravel-artisan0.0.28 vscode-javascript-booster14.0.1 vue-vscode-snippets3.1.1 vscode-blade-formatter0.17.3 js-jsx-snippets11.0.0 comment-divider0.4.0 autoimport1.5.4 code-spell-checker2.7.0 svelte-vscode105.22.1 ayu1.0.5 volar0.40.5 phaser-snippets0.0.6 JavaScriptSnippets1.8.0 php-debug1.28.0 txt-syntax0.2.0 vscode-yseopml1.16.0 json2.0.2 material-theme3.15.2 html-css-class-completion1.20.0 (4 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
the same on me. and 2 team members on VS code version 1.70 + working fine on vs code 1.71 for intel and M1 broken (for the same project ) nodejs +typescript +nestjs
/jsDebugLogs
Please collect trace logs using the following instructions:
debug console doesn't show path to log. just show 1 line (with and without ) info similar issue here
!
Same issue here. I can't launch any of the automatic debug configurations that start my npm scripts (npm start, etc.). They just get stuck with the same terminal output in 's screenshot.
are you also on arm64/M1 macOS?
Same issue on Windows 10 Pro 21H2
Thanks, I can reproduce it. For now, you can create an entry in your that manually runs the script, like so:
Verification steps: a folder with npm scripts the debug dropdown or quick access, choose the "" option Select and verify you can debug one of the npm scripts
Change:
return timebomb() .then(setupIPC) <ins> .then(ipcServer => { setupMutex(); return ipcServer; }) </ins> .then(ipcServer => main(ipcServer, userEnv)); }) .done(null, quit);

Discussion:
This will let the Setup installer not go ahead and perform an update/install if Code is running.
We already have a native app mutex node module which we could use for this.
Change:
export interface IGitHubServer { login(scopes: string): Promise<string>; getUserInfo(token: string): Promise<{ id: string; accountName: string }>; <del> sendAdditionalTelemetryInfo(token: string): Promise<void>; </del> <ins> sendAdditionalTelemetryInfo(session: vscode.AuthenticationSession): Promise<void>; </ins> friendlyName: string; }

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:
} // Title <del> const shortTitle = this.computeLabel(this.original.getTitle(Verbosity.SHORT) ?? this.original.getName(), this.modified.getTitle(Verbosity.SHORT) ?? this.modified.getName(), ' ↔ '); const mediumTitle = this.computeLabel(this.original.getTitle(Verbosity.MEDIUM) ?? this.original.getName(), this.modified.getTitle(Verbosity.MEDIUM) ?? this.modified.getName(), ' ↔ '); const longTitle = this.computeLabel(this.original.getTitle(Verbosity.LONG) ?? this.original.getName(), this.modified.getTitle(Verbosity.LONG) ?? this.modified.getName(), ' ↔ '); </del> <ins> let shortTitle = this.computeLabel(this.original.getTitle(Verbosity.SHORT) ?? this.original.getName(), this.modified.getTitle(Verbosity.SHORT) ?? this.modified.getName(), ' ↔ '); let mediumTitle = this.computeLabel(this.original.getTitle(Verbosity.MEDIUM) ?? this.original.getName(), this.modified.getTitle(Verbosity.MEDIUM) ?? this.modified.getName(), ' ↔ '); let longTitle = this.computeLabel(this.original.getTitle(Verbosity.LONG) ?? this.original.getName(), this.modified.getTitle(Verbosity.LONG) ?? this.modified.getName(), ' ↔ '); const preferredTitle = this.getPreferredTitle(); if (preferredTitle) { shortTitle = `${preferredTitle} (${shortTitle})`; mediumTitle = `${preferredTitle} (${mediumTitle})`; longTitle = `${preferredTitle} (${longTitle})`; } </ins> return { name, shortDescription, mediumDescription, longDescription, forceDescription, shortTitle, mediumTitle, longTitle }; }

Discussion:
<!-- 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 set to fixed, the title of diff editor which is opened by clicking item in timeline view will only show the title of the editor, and I also need to see all of the editor name: !
<!-- 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!
Change:
cell.updateEditState(CellEditState.Editing, 'focusNotebookCell'); cell.focusMode = CellFocusMode.Editor; if (!options?.skipReveal) { <del> this.revealInCenterIfOutsideViewport(cell); </del> <ins> const selectionsStartPosition = cell.getSelectionsStartPosition(); if (selectionsStartPosition?.length) { const firstSelectionPosition = selectionsStartPosition[0]; this.revealRangeInCenterIfOutsideViewportAsync(cell, Range.fromPositions(firstSelectionPosition, firstSelectionPosition)); } else { this.revealInCenterIfOutsideViewport(cell); } </ins> } } else if (focusItem === 'output') { this.focusElement(cell);

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?: N/A <!-- 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.63.2 Commit: Date: 2021-12-15T09:39:46.686Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.11.0-46-generic OS Version: Ubuntu Linux 21.04 (running under VMware) Steps to Reproduce: a notebook (ipynb) in VS Code a lot of code into a cell -- too much code to fit onto the screen at once other cells to scroll back and forth between cells using the keyboard Expected: The arrow keys should be able to scroll to the cell immediately before the current cell Actual: The arrow keys are ignored; eventually, it sometimes scrolls, but then to the top of the entire notebook. Scroll doesn't work; it locks on the cell. Sometimes, when it releases, it goes to the top of the entire notebook.
Change:
} function scrollableArrayOfString(id: string, buffer: string[], container: HTMLElement, trustHtml: boolean) { <del> container.classList.add('scrollable'); </del> <ins> const scrollableDiv = document.createElement('div'); scrollableDiv.classList.add('scrollable'); </ins> if (buffer.length > 5000) { container.appendChild(generateViewMoreElement(id, false)); } <del> const div = document.createElement('div'); container.appendChild(div); div.appendChild(handleANSIOutput(buffer.slice(0, 5000).join('n'), trustHtml)); </del> <ins> container.appendChild(scrollableDiv); scrollableDiv.appendChild(handleANSIOutput(buffer.slice(0, 5000).join('n'), trustHtml)); </ins> } export function insertOutput(id: string, outputs: string[], linesLimit: number, scrollable: boolean, container: HTMLElement, trustHtml: boolean) {

Discussion:
It should be outside of the output region <img width="962" alt="image" src="https://user-"
Change:
} } <ins> public hasPendingScrollAnimation(): boolean { return this._scrollable.hasPendingScrollAnimation(); } </ins> public deltaScrollNow(deltaScrollLeft: number, deltaScrollTop: number): void { const currentScrollPosition = this._scrollable.getCurrentScrollPosition(); this._scrollable.setScrollPositionNow({

Discussion:
Type: <bBug</bI found this problem in Vim extension when using half page scroll with centered view and smoothScrolling, and reproduce this bug in test clean extension. Without smoothScrolling it works fine. When executing command two times with ~150ms delay second action dont trigger (view stay in position by first ). U can see it on this video, when view in some cases not returned to 31 line from 39. https://user- Reproduce: reproducing i set interval with two timeouts to create delay between two executions and set smoothScrolling. ! VS Code version: Code 1.76.2 (, 2023-03-14T17:55:54.936Z) OS version: WindowsNT x64 10.0.

Modes: Unsupported Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (35)</summaryExtensionVersion ------ better-comments3.0.2 astro-vscode0.28.2 vscode-tailwindcss0.9.11 path-intellisense2.8.4 vscode-css-modules0.4.2 vscode-database-client26.3.4 vscode-eslint2.4.0 es7-react-js-snippets4.4.3 vsc-material-theme-icons2.7.4 prettier-vscode9.10.4 auto-close-tag0.5.14 auto-rename-tag0.1.10 code-runner0.12.0 geril-vim1.25.2 go0.38.0 vscode-graphql0.8.7 vscode-graphql-syntax1.1.0 code-background2.5.4 vscode-docker1.24.0 remote-wsl0.76.1 remote-explorer0.4.0 remote-server1.0.0 material-icon-theme4.25.0 prisma4.12.0 LiveServer5.7.9 rust-analyzer0.3.1463 vscode-styled-components1.7.8 svelte-vscode107.3.0 errorlens3.8.0 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 vscode-icons12.2.0 JavaScriptSnippets1.8.0 material-theme3.15.8 vscode-proto30.5.5 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.77.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
After update to 1.77.1 bug still exists
Thank you for the repro! The root cause is this particular call - introduced via cc That code runs even when the inlayHintsController doesn't do anything and it ends up interrupting the current editor scroll animation.
Change:
*--------------------------------------------------------------------------------------------*/ import { KeyCode, KeyMod } from 'vs/base/common/keyCodes'; <del> import { DisposableStore } from 'vs/base/common/lifecycle'; </del> <ins> import { Disposable, DisposableStore, IDisposable } from 'vs/base/common/lifecycle'; </ins> import { assertType } from 'vs/base/common/types'; import { ICodeEditor } from 'vs/editor/browser/editorBrowser'; import { EditorCommand, EditorContributionInstantiation, registerEditorCommand, registerEditorContribution } from 'vs/editor/browser/editorExtensions';

Discussion:
This problem still occurs even if you disable all extensions. This problem was confirmed in Markdown file. below the snippet (it contains a snippet choice) below the code in Markdown file snippet in Markdown file I expected to see link label suggestion, but it does not display link label suggestion... Included by snippet choice reproduces the issue. It is not displayed even if is pressed. Gif demo: ! VS Code Windows 11
Sorry but I am unaware of link label suggestions. What are those and where do they usually come from?
I'm sorry, I had my own way of saying it. I don't know the correct terminology, but I'll show you an example in action. the following markdown your cursor inside the second ! I haven't been able to find any release notes for this feature, but it's a feature in VS Code and not coming from an Installed extension. This feature doesn't work within certain snippets.
I can reproduce. Looks like the choice suggest provider is staying active despite its placeholder not being active anymore
Using a snippet seems to break label suggestions until the editor is reloaded. Even reopening the file doesn't fix it:
repro steps please
the snippet from the original issue in your global snippets a new markdown file with the contents as in the video, you can get completions until the moment you use the snippet
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Change:
import { IOpenerService } from 'vs/platform/opener/common/opener'; import { IHostService } from 'vs/workbench/services/host/browser/host'; <del> import { INotificationService, IPromptChoice } from 'vs/platform/notification/common/notification'; </del> <ins> import { INotificationService } from 'vs/platform/notification/common/notification'; </ins> import { IDialogService, IConfirmationResult } from 'vs/platform/dialogs/common/dialogs'; import { IModelService } from 'vs/editor/common/services/modelService';

Discussion:
We have a temporary fix for the release for but we need to do something better long term.
while working on quick access for tasks I noticed that we seem to be having 2 pickers for the same thing (?): Task quick open: ! "Run Task" picker: ! Is that intentional? Should the one be merged into the other?
Yes, they do not share much code :( as part of improving the quick pick I will converge them.
sounds good, please only change  and leave the other one because I plan to delete those old ones soon.
Change:
if (command && inputValue.startsWith(`/${command.command} `)) { if (!this._slashCommandContentWidget) { <del> this._slashCommandContentWidget = new SlashCommandContentWidget(this.widget.inputEditor); </del> <ins> this._slashCommandContentWidget = new SlashCommandContentWidget(this.widget.inputEditor, this.accessibilityService); </ins> this._store.add(this._slashCommandContentWidget); } this._slashCommandContentWidget.setCommandText(command.command);

Discussion:
on a screen reader on Windows (JAWS/NVDA) in the chat view backspace hear "space' said this is typical of a screen reader. We discussed using an audio cue to indicate deletion. We have concluded it would be better and simpler to just disable this feature for screen reader users. !
-- After this meeting, something came to mind. What if I love the current command deletion behavior and would like to keep it? would you like to add a user setting to toggle this behavior for some advanced users?
We try to add settings sparingly because we want the default experience to be very nice. I will leave this with to decide. We could keep this behavior and mention it in the chat's accessibility help menu so a screen reader user is aware of what's happening.
do you personally anticipate that you would use this setting to preserve the command deletion behavior? Do you know why the screenreader reads 'space' on a deletion? If we can avoid that, would it be more reasonable that hitting backspace results in the screenreader announcing 'exiting mode'?
JooYoung and I discussed that approach and agreed it would be too verbose. We should either use an audio cue, disable the feature, or provide a setting.
Or mention it in the chat's accessibility help?
After thinking about this issue for a day, I think we can add an alert "input cleared" when the command is entirely deleted. I found that character-by-character deletion works after when you move your cursor to the left.
This is great
Change:
import { assertIsDefined } from 'vs/base/common/types'; import { ISplashStorageService } from 'vs/workbench/contrib/splash/browser/splash'; import { mainWindow } from 'vs/base/browser/window'; <ins> import { ILifecycleService, LifecyclePhase } from 'vs/workbench/services/lifecycle/common/lifecycle'; </ins> export class PartsSplash {

Discussion:
I noticed that saving parts splash occurs during startup, even though delayed: ! I am not sure we need that, maybe we can put that on the phase. The following profile: was taken on Windows with a non-minified / non-mangled build to aid reading has the event at
Moved it out a bit further but the overall timing is a lottery because it depends on the current state (destruction) of the dom and how long measuring will take