jiebi/CodeConvo huggingface dataset:
Change:
"@vscode/vscode-languagedetection": "1.0.21", "@vscode/windows-process-tree": "^0.6.0", "@vscode/windows-registry": "^1.1.0", <del> "@xterm/addon-clipboard": "0.2.0-beta.34", "@xterm/addon-image": "0.9.0-beta.51", "@xterm/addon-search": "0.16.0-beta.51", "@xterm/addon-serialize": "0.14.0-beta.51", "@xterm/addon-unicode11": "0.9.0-beta.51", "@xterm/addon-webgl": "0.19.0-beta.51", "@xterm/headless": "5.6.0-beta.51", "@xterm/xterm": "5.6.0-beta.51", </del> <ins> "@xterm/addon-clipboard": "0.2.0-beta.35", "@xterm/addon-image": "0.9.0-beta.52", "@xterm/addon-search": "0.16.0-beta.52", "@xterm/addon-serialize": "0.14.0-beta.52", "@xterm/addon-unicode11": "0.9.0-beta.52", "@xterm/addon-webgl": "0.19.0-beta.52", "@xterm/headless": "5.6.0-beta.52", "@xterm/xterm": "5.6.0-beta.52", </ins> "cookie": "^0.4.0", "http-proxy-agent": "^7.0.0", "https-proxy-agent": "^7.0.2",

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 <!-- 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.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.
Change:
.join(''); } <ins> private _toCamelCase(value: string): string { const match = value.match(/[a-z0-9]+/gi); if (!match) { return value; } return match.map((word, index) => { if (index === 0) { return word.toLowerCase(); } else { return word.charAt(0).toUpperCase() + word.substr(1).toLowerCase(); } }) .join(''); } </ins> toTextmateString(): string { let value = '${'; value += this.index;

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. --I see the grammar at only supports , , and for format options. can there be a option that would transform the match text into camelCase? Thanks for the awesome work!
Just FYI, I believe pascalcase is also supported but undocumented.
The docs were updated to include in
To verify: insert a snippet like below type 'Hello_World' press the second line should become
Change:
readonly extensions?: string; } <ins> function isUserDataProfileTemplate(thing: unknown): thing is IUserDataProfileTemplate { const candidate = thing as IUserDataProfileTemplate | undefined; return !!(candidate && typeof candidate === 'object' && (candidate.name && typeof candidate.name === 'string') && (isUndefined(candidate.shortName) || typeof candidate.shortName === 'string') && (isUndefined(candidate.settings) || typeof candidate.settings === 'string') && (isUndefined(candidate.globalState) || typeof candidate.globalState === 'string') && (isUndefined(candidate.extensions) || typeof candidate.extensions === 'string')); } </ins> export class UserDataProfileImportExportService extends Disposable implements IUserDataProfileImportExportService, IURLHandler { private static readonly PROFILE_URL_AUTHORITY_PREFIX = 'profile-';

Discussion:
Testing Try to import this profile file: Restart VS Code. Observe that VS Code does not load anymore.
Change:
color: ${tokenNumberColor}; } `); <ins> const debugConsoleInputBorderColor = theme.getColor(inputBorder) || Color.fromHex('#80808060'); const debugConsoleInfoForegroundColor = theme.getColor(debugConsoleInfoForeground)!; const debugConsoleWarningForegroundColor = theme.getColor(debugConsoleWarningForeground)!; const debugConsoleErrorForegroundColor = theme.getColor(debugConsoleErrorForeground)!; const debugConsoleSourceForegroundColor = theme.getColor(debugConsoleSourceForeground)!; const debugConsoleInputIconForegroundColor = theme.getColor(debugConsoleInputIconForeground)!; collector.addRule(` .repl .repl-input-wrapper { border-top: 1px solid ${debugConsoleInputBorderColor}; } .monaco-workbench .repl .repl-tree .output .expression .value.info { color: ${debugConsoleInfoForegroundColor}; } .monaco-workbench .repl .repl-tree .output .expression .value.warn { color: ${debugConsoleWarningForegroundColor}; } .monaco-workbench .repl .repl-tree .output .expression .value.error { color: ${debugConsoleErrorForegroundColor}; } .monaco-workbench .repl .repl-tree .output .expression .source { color: ${debugConsoleSourceForegroundColor}; } .monaco-workbench .repl .repl-tree .monaco-tl-contents .arrow { color: ${debugConsoleInputIconForegroundColor}; } `); if (!theme.defines(debugConsoleInputIconForeground)) { collector.addRule(` .monaco-workbench.vs .repl .repl-tree .monaco-tl-contents .arrow { opacity: 0.25; } .monaco-workbench.vs-dark .repl .repl-tree .monaco-tl-contents .arrow { opacity: 0.4; } .monaco-workbench.hc-black .repl .repl-tree .monaco-tl-contents .arrow { opacity: 1; } `); } </ins> });

Discussion:
I stumbled over and saw that there are still many colors hard-coded. Also while at the .css file, it's good practice to qualify all rules with (or ) now that the workbench can be embedded in the web.
Thanks for great feedback. There was some unused CSS, like the .annotation in the repl, so I removed that. I have also now qualifed all with . There is still one hard coded color for in repl, but I believe tackled this with his great PR. Though I might be mistaken?
I did, indeed, add colour contribution points to the REPL as part of but eventually you asked me to defer those until later, I do not remember the reason precisely... So the REPL is still not theme-able, unfortunately.
thanks for refreshing my memory. In case you would like to contribute that part of your PR we are open to accept it now :D From the I only see a need for color, not sure if there is more.
I am working on this now. I am taking it a step further, though, and adding theming to most of the REPL elements (errors, warnings, infos, source filenames etc.). Basically I want the whole REPL view to be fully customisable.
To verify, make sure you can customise the following colors in the debug console. You can use the setting :
Change:
export function registerCompletionItemProvider(selector: DocumentSelector, provider: CompletionItemProvider, ...triggerCharacters: string[]): Disposable; /** <ins> * Registers an inline completion provider. * * Multiple providers can be registered for a language. In that case providers are asked in * parallel and the results are merged. A failing provider (rejected promise or exception) will * not cause a failure of the whole operation. * * @param selector A selector that defines the documents this provider is applicable to. * @param provider An inline completion provider. * @return A {@link Disposable} that unregisters this provider when being disposed. */ export function registerInlineCompletionItemProvider(selector: DocumentSelector, provider: InlineCompletionItemProvider): Disposable; /** </ins> * Register a code action provider. * * Multiple providers can be registered for a language. In that case providers are asked in

Discussion:
(edited by We use this issue to track the progress of the Inline Completions API. The currently proposed API can be found in . There is a sample extension . Before this API can be finalized, we need to figure out these items at least: [x] How can inline completions interact with completions? (Currently, inline completions are hidden when autocomplete shows up and if there is an inline completion, autocomplete does not show up automatically)
why is this proposal not still open? Normally for proposals, we keep them open until the api is finalized and shipped. So that users/extension authors can track the proposal more easily.
Trying to copy and get 404. Is this link dead? This makes the sample in vscode: useless as well. Can you please help?
They have an updated way to get the file. First you have to change the to in the file. Then run to download the latest version of and then run . See more (if the link doesn't scroll down to the "updated api proposal structure" you have to control f it).
Hi folks! Is the API still likely to be released in April as mentioned in ?
it is currently assigned to April and that is our plan. It might slip to May depending on how testing and feedback from Extensions that use this proposed API goes. I suggest to follow this issue for more details. Thanks!
Hello! While trying out the sample package (). I receive the following errors. I also attempted the method you specified and the methods mentioned in the readme. In addition, I also tried the following npm commands: Npm install Npm run postinstall Is this sample still up to date?
good catch. I have tackled the outdated extension via this PR Once we get it approved I will merge it in and then the sample should be up to date. Thanks
Looks like this is on mainline? Any idea when it will be released beyond insiders?
this is assigned to the May milestone. Which means it is part of our May release which usually gets shipped first 10 days of the following month. So this one should be available on Thursday.
amazing! Thanks so much for getting back to me, I'll be deving accordingly :)
I have opened this discussion for any follow up questions since we have done the finalization
Change:
export interface ISettingsEditorViewState { settingsTarget: SettingsTarget; <ins> query?: string; // used to keep track of loading from setInput vs loading from cache </ins> tagFilters?: Set<string>; extensionFilters?: Set<string>; featureFilters?: Set<string>;

Discussion:
Issue Type: <bBug</bthe settings UI. for a setting (e.g. "inlay"). the settings tab to a new editor group. Note that the search you entered previously has been cleared. https://user- VS Code version: Code 1.60.0 (, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 vscode-nginx-conf0.1.3 reorder-lines-by-length1.0.2 docs-view0.0.9 pgformatter1.17.0 vscode-eslint2.1.25 gitlens11.6.0 vscode-diff1.4.2 shell-format7.1.0 go0.27.2 postgresql0.0.2 rainbow-csv1.9.1 render-crlf1.5.21 template-string-converter0.5.3 python2021.9. vscode-pylance2021.9.2 jupyter2021.8. jupyter-keymap1.0.0 debugger-for-chrome4.13.0 nbsp-vscode0.0.1 vscode-commons0.0.6 vscode-yaml0.22.0 final-newline0.3.2 vscode-hexdump1.8.1 change-case1.0.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
A function called in is being called after the drop, which is correct. But, the function in the same file name isn't being called when the user does step 3 above. Another repro is to use the "move editor to X group" commands. Therefore, the fix doesn't have to do directly with dnd.
Change:
this.onScreenReaderModeChange(); } })); <del> CommandsRegistry.registerCommand({ id: 'showEditorScreenReaderNotification', handler: () => this.showScreenReaderNotification() }); </del> this.updateScreenReaderModeElement(this._accessibilityService.isScreenReaderOptimized()); } <del> private showScreenReaderNotification(): void { this.screenReaderNotification = this.notificationService.prompt( Severity.Info, localize('screenReaderDetectedExplanation.question', "Are you using a screen reader to operate VS Code?"), [{ label: localize('screenReaderDetectedExplanation.answerYes', "Yes"), run: () => { this.configurationService.updateValue('editor.accessibilitySupport', 'on', ConfigurationTarget.USER); } }, { label: localize('screenReaderDetectedExplanation.answerNo', "No"), run: () => { this.configurationService.updateValue('editor.accessibilitySupport', 'off', ConfigurationTarget.USER); } }], { sticky: true, priority: NotificationPriority.URGENT } ); Event.once(this.screenReaderNotification.onDidClose)(() => this.screenReaderNotification = null); } </del> private updateScreenReaderModeElement(visible: boolean): void { if (visible) { if (!this.screenReaderModeElement.value) {

Discussion:
We should not prompt IMO anymore since we detect the screen reader.
let's discuss this on Monday
I like the idea, but I suggest that we leave the prompt for at least one more milestone. After that, we can compare the number of accessibility users we have after changes and see how precise the detection is. We might also see that the detection is more precise on some platforms, in which case we can leave the prompt only for some platforms. Does that make sense? What do you think? fyi who introduced the prompt initially
Safe to remove now?
I suggest to leave it on for at least one more milestone since our accessibility detection got off. I will assign it to March for now. Hope that is ok.
Thanks for fixing this. I just assigned to October and verification-needed. I think the verify steps are the following: On Windows turn on NVDA VS Code insiders (have no settings set). an editor, type some text sure NVDA reads this text as you navigate through it character by character Same on macOS with VoiceOver.
I haven't heard user complaints, so let's just keep this
Change:
} if (beforeCommandExecution && !this._placeholderDecoration) { this._placeholderDecoration = decoration; <del> this._placeholderDecoration.onDispose(() => this._placeholderDecoration = undefined); </del> } else if (!this._decorations.get(decoration.marker.id)) { decoration.onDispose(() => this._decorations.delete(decoration.marker.id)); this._decorations.set(decoration.marker.id,

Discussion:
!
Think I saw this today
that was when I here, which causes other issues so i'm removing
working on it
repro is to create some decorations via commands and then delete the terminal
Change:
this.handleFocusChange(false); })); <del> this._register(this.on('did-keydown', (data: KeyboardEvent) => { // Electron: workaround for https://github.com/electron/electron/issues/14258 // We have to detect keyboard events in the <webview> and dispatch them to our // keybinding service because these events do not bubble to the parent window anymore. this.handleKeyDown(data); })); </del> <ins> if (!isLinux) { // Fixes #82670 webview responding shortcuts twice on linux. this._register(this.on('did-keydown', (data: KeyboardEvent) => { // Electron: workaround for https://github.com/electron/electron/issues/14258 // We have to detect keyboard events in the <webview> and dispatch them to our // keybinding service because these events do not bubble to the parent window anymore. this.handleKeyDown(data); })); } </ins> this.style(); this._register(webviewThemeDataProvider.onThemeDataChanged(this.style, this));

Discussion:
Issue Type: <bBug</bOpen a new window, close the Untitled tab, open Release notes and press Ctrl+W (or Cmd+W) on macOS. Expected: Release notes tab is closed. Actual: Release notes tab is closed as well as the current window. You can also open a file, open Release notes and press Ctrl+W. Release notes and the last file will close. VS Code version: Code 1.39.2 (, 2019-10-15T15:33:40.634Z) OS version: Linux x64 4.15.0-65-generic
I tried reproducing the issue, seems everything is working fine.
The same happened when closing opened images. Using "Ctrl+W" to close an image would 1)close another file if there is, 2) otherwise close current VSCODE window OS version: Linux Mint 19.2 Tina (Cinnamon)/ XM Linux live(XFCE) image on VM VS Code version: 1.40.0 and the insider version Also I tried to reproduce it on a Windows 7 VM, and it was not there. Is it caused by Electron by any chance? I'd love to try to fix it. However, yet have no clue on where the related lines of codes are located. Any hints or suggestions? Thanks
Reopening since the fix caused regressions and had to be reverted
I confirm this is still happening with vscode v1.44.0 and Ubuntu 18.04. Many similar issues are opened already: ,
Should be fixed by
Change:
precondition: ContextKeyExpr.and( _ctxHasTypeHierarchyProvider, PeekContext.notInPeekEditor <del> ) </del> <ins> ), f1: true </ins> }); }

Discussion:
Testing <img width="497" alt="image" src=""<img width="667" alt="image" src=""
same is true for "Peek Type Hierarchy"
Hi Rob and Johannes, Would you mind if I took a crack at this issue? I am just starting open source, and I think this would be a great learning experience to do!
I stand in line
Hey have you started working on this issue?
Yes I have! I have already wrote code for this issue, just haven't made a pr yet :)
Hey can you take a little time and help me if you have resolved this issue how you did it? just a brief, also where is your pr I want to take a look at it!
It's been quite a while that no updates about the fix is coming out, so I've committed mine in .
To verify: open a TS file, wait the language service to be ready select F1 and type Peek Call Hierarchy
Change:
protected override _fillHead(container: HTMLElement): void { super._fillHead(container, true); <del> const previous = this.instantiationService.createInstance(UIEditorAction, this.editor, new ShowPreviousChangeAction(), ThemeIcon.asClassName(gotoPreviousLocation)); const next = this.instantiationService.createInstance(UIEditorAction, this.editor, new ShowNextChangeAction(), ThemeIcon.asClassName(gotoNextLocation)); </del> <ins> const previous = this.instantiationService.createInstance(UIEditorAction, this.editor, new ShowPreviousChangeAction(this.editor), ThemeIcon.asClassName(gotoPreviousLocation)); const next = this.instantiationService.createInstance(UIEditorAction, this.editor, new ShowNextChangeAction(this.editor), ThemeIcon.asClassName(gotoNextLocation)); </ins> this._disposables.add(previous); this._disposables.add(next);

Discussion:
Found while working on a file tracked by git and make two distinct changes in separate lines the same file on the other side the dirty diff gutter marker on each of the editors to open the dirty diff views the outer editor on the right-hand side the action on the left-hand side dirty diff editor The right-hand side dirty diff editor jumps to the next change !
Change:
} const existing = this._diagnostics.get(kind); <del> if (arrays.equals(existing || arrays.empty, diagnostics, diagnosticsEquals)) { </del> <ins> if (existing?.length === 0 && diagnostics.length === 0) { </ins> // No need to update return false; }

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. --Version: 1.75.0-insider Commit: Date: 2022-12-16T05:22:34.551Z Electron: 19.1.8 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin x64 22.2.0 Sandboxed: Yes Steps to reproduce: a TypeScript file and insert , insert or enough to get a GitHub Copilot inline suggestion of , and press <kbdtab</kbdto accept. (I assume other inline suggestion providers can trigger the same behavior.) that the rendered error span has moved to the curly brace. that TS Server logs show the text insertion and subsequent results with proper spans: https://user-
Full ts server log:
<!-- 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:
private listening: boolean = false; private readonly synchronizer: BufferSynchronizer; <ins> private readonly _tabResources: TabResourceTracker; </ins> constructor( client: ITypeScriptServiceClient, modeIds: readonly string[],

Discussion:
Issue Type: <bBug</bMoved off Steps to reproduce: code that generates a linting warning (in this case, should should generate an unused variable warning) the file, and then close it before the diagnostics appear Expected behavior: Diagnostics are not shown when the file is closed. Actual behavior: Diagnostics are sometimes shown when the file is closed, and will not disappear until I reload the window. Please note that I couldn't reproduce this behaviour reliably. Action gif: ! VS Code version: Code 1.46.1 (, 2020-06-17T21:17:14.222Z) OS version: Darwin x64 19.5.0 <details<summarySystem Info</summary </details<details<summaryExtensions (15)</summaryExtensionVersion ------ bracket-pair-colorizer-20.2.0 gitlens10.2.2 prettier-vscode5.1.3 vscode-pull-request-github0.17.0 vscode-docker1.3.1 python2020.6. vscode-pylance2020.6.1 remote-containers0.122.1 remote-ssh0.51.0 remote-ssh-edit0.51.0 remote-wsl0.44.4 vscode-remote-extensionpack0.20.0 azure-account0.8.11 vscode-typescript-tslint-plugin1.2.3 vscode-icons10.1.1 (3 theme extensions excluded) </details<!-- generated by issue reporter --