jiebi/CodeConvo huggingface dataset:
Change:
static readonly DebugCallStackContext = new MenuId('DebugCallStackContext'); static readonly DebugConsoleContext = new MenuId('DebugConsoleContext'); static readonly DebugVariablesContext = new MenuId('DebugVariablesContext'); <ins> static readonly DebugHoverContext = new MenuId('DebugHoverContext'); </ins> static readonly DebugWatchContext = new MenuId('DebugWatchContext'); static readonly DebugToolBar = new MenuId('DebugToolBar'); static readonly DebugToolBarStop = new MenuId('DebugToolBarStop');

Discussion:
This is the debug hover: ! I think it would be great if each value has a context menu (or inline buttons) to trigger (contributable) actions. Built-in actions could be: copy value copy expression watch Actions contributed by extensions could be: visualize This is already supported in the sidebar: !
good overall idea and I like it. I think we could implement it fairly easily by adding a new menu type to the hover tree. We can even open it for extensions as you suggested. However I would be interested in what other apps do you know that have a context menu on the hover? Might this be a sort of an anti pattern? I know that the debug hover is a bit heavy and a context menu might fit well there, but I would be interested in how other products do it. Maybe try out Visual Studio, Chrome Dev Tools and others... fyi
I do believe that's using the tree widget, which supports inline actions: <img width="334" alt="CleanShot 2021-06-08 at 10 46 42 src="https://user-"I'd assume either a (though there is quite a bit already in these views) or: <img width="652" alt="CleanShot 2021-06-08 at 10 48 01 src="https://user-"<img width="659" alt="CleanShot 2021-06-08 at 10 48 46 src="https://user-"
VS has quite a few nested context menus :D 
I think that would be possible since it's a toolbar, we do show more inline actions in peek/diff views: <img width="157" alt="CleanShot 2021-06-08 at 10 57 38 src="https://user-"
Cool ideas. Maybe just a right click context menu might work best. But an additional gear on the end to make it discoverable will help. Ellipsis look good in the example you provided but in practice we have a lost of overflowing text and it is all shown with ellipsis, so I think it would be very confusing, as some ellipsis would be clickable and some not... is right, it can be made possible if we make it a toolbar, however I would be worried about opening inline actions to extensions since horizontal space is already limited. I would first only open secondary actions - the one behind a context menu. Though I am flexible.
can you verify this one?
Change:
@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();

Discussion:
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.
Change:
} } <del> (needsToSubstitute ? this.substituteVariables(launch, unresolved) : TPromise.as(session.configuration)).then(resolved => { </del> <ins> let configPromise = TPromise.as(session.configuration); if (needsToSubstitute) { configPromise = this.configurationManager.resolveConfigurationByProviders(launch.workspace && launch.workspace.uri, unresolved.type, unresolved) .then(resolved => this.substituteVariables(launch, resolved)); } configPromise.then(resolved => { </ins> session.setConfiguration({ resolved, unresolved }); session.configuration.__restart = restartData;

Discussion:
Version: 1.27.2 (user setup) Commit: Date: 2018-09-12T16:17:45.060Z Electron: 2.0.7 Chrome: 61.0.3163.100 8.9.3 V8: 6.1.534.41 Architecture: x64 OS: Window 10 Steps to Reproduce: Install Latest VS Live Share extension on Insiders Host: Share a Node JS App, set a breakpoint and start debugging : Join collaboration session (guest automatically joins debug session) Guest: Restart debug session ! This issue appears to be due to recent debug restart refactoring: The issue occurs in debugService's restartSession. When the VS Live Share Guest clicks restart the correct resolved and unresolved debug configurations are found on the session. The unresolved configuration does not equal the session.unresolvedConfiguration. needsToSubstitute is set to true and the sessions resolved configuration ends up getting replaced with an unresolved configuration that doesn't contain the required information for VSLS to properly initialize the debug session (ex: localPath, joinUniqueId, etc is missing) Resolved configuration is set correctly if substituteVariables isn't called: ! When subsituteVariables is called required debug configuration information is lost: !
Thanks a lot for filling this issue with great steps and detail. I have explained the reson what caused this regression in This pr is merged, so this should be fixed in the next stable and from Insiders tomorrow. I have verified this worked for me when doing a live share session with myself on my mac. Though it would be great if you can also verify
Thanks Verified this resolves the associated issues.
great, adding verified label!
Change:
import { Emitter, Event } from 'vs/base/common/event'; import { IHoverDelegate } from 'vs/base/browser/ui/hover/hoverDelegate'; import { IListVirtualDelegate } from 'vs/base/browser/ui/list/list'; <del> import { IObjectTreeElement, ITreeNode, ITreeRenderer } from 'vs/base/browser/ui/tree/tree'; </del> <ins> import { IObjectTreeElement, ITreeEvent, ITreeNode, ITreeRenderer } from 'vs/base/browser/ui/tree/tree'; </ins> import { localize } from 'vs/nls'; import { IInstantiationService } from 'vs/platform/instantiation/common/instantiation'; import { WorkbenchObjectTree } from 'vs/platform/list/browser/listService';

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.88.0-insider OS Version: MacOs Steps to Reproduce: In the python and python debugger extension we use the QuickPick, we add an option to accept the value in the input. It was working in stable, but in insiders it doesn't work. Steps: a picker some text in the input box, make sure that it match with one option at first. enter, to select the text in the input box. last value that appeared in the list is the one that is selected. You can check the implementation . I was debugging the code a little bit, and found that in stable when you press enter, the function is called. But in insider when you press enter instead of call that function, the function is called.
Verification: Install Python extension Open a python workspace with no Open the debug pane and click the "create a file" Choose Python Debugger Choose Django Type ONLY 'b' and notice that "Browse Files" becomes the active item Type then, 'z' and notice that the list is empty hit ENTER and notice that the gets created with "bz" in the
The fix fully resolves as well!
Resolves my issue as well.
Change:
}; Registry.as<IConfigurationRegistry>(ConfigurationExtensions.Configuration).registerConfiguration({ <ins> scope: ConfigurationScope.RESOURCE, </ins> 'properties': { 'audioCues.enabled': { markdownDeprecationMessage: 'Deprecated. Use the specific setting for each audio cue instead (`audioCues.*`).',

Discussion:
VS Code Version: Version : 1.87.1 Validation : Date : 2024-03-06T00:22:39.156Z Electron : 27.3.2 ElectronBuildId : Chromium : 118.0.5993.159 : 18.17.1 V8 : 11.8.172.18-electron.0 Système d’exploitation : Darwin arm64 23.3.0 Steps to Reproduce: Just launch VS Code and get an error message like in picture joined. I don't know how to not get them <img width="582" alt="Capture d’écran 2024-03-07 à 19 40 25" src=""
any ideas here ? rough translation: "Unable to be described in folder settings because does not support the scope of folder resources"
Repro steps a multi-root workspace. the setting to the files of one of those workspaces. the window. :bug: The dialogs show up.
and what should I do to remove this error message ???
A workaround would be: which root folder in the multi-root workspace has defined in . the multi-root workspace, and open that root folder in a separate VS Code window. The editor should automatically migrate over the outdated setting. the multi-root workspace again.
Hi, i am sorry i don't think that i understood precisely what you meant by: Check which root folder in the multi-root workspace has defined in Close the multi-root workspace, and open that root folder in a separate VS Code window. The editor should automatically migrate over the outdated setting. Open the multi-root workspace again. Can you be clearer please ? I am relatively new to VsCode Thanks
how can I do to get rid off the error message ? Thx
English repro looks like this: <img width="402" alt="Screenshot 2024-04-04 at 6 50 20 AM" src=""
Change:
this._colorHoverParticipant = participants.find(p => p instanceof ColorHoverParticipant); } <ins> public focusHoverPartWithIndex(index: number): void { if (index < 0 || index >= this._renderedParts.length) { return; } this._renderedParts[index].hoverElement.focus(); } </ins> public getAccessibleContent(): string { const content: string[] = []; for (let i = 0; i < this._renderedParts.length; i++) {

Discussion:
Testing on Linux Open a hover with multiple parts Tab to focus one of the hover parts Open accessible view/help Esc to close it Now the whole hover is focused, instead of the individual part I'd focused
Verified with GitLens's editor hover
Change:
if (this.configurationService.getValue(NotebookSetting.notebookVariablesView) && this.editorService.activeEditorPane?.getId() === 'workbench.editor.notebook') { <del> if (this.hasVariableProvider()) { </del> <ins> if (this.hasVariableProvider() && !this.initialized && this.initializeView()) { </ins> this.viewEnabled.set(true); <del> } if (!this.initialized && this.initializeView()) { </del> this.initialized = true; this.listeners.forEach(listener => listener.dispose()); }

Discussion:
Steps to Reproduce: a notebook and put in a cell and run it to establish a kernel for that notebook vscode and run the cell before the kernel is auto-selected :bug: notebook variable view will not initialize
HI is this a candidate? This issue is assigned to the recovery 2 milestone, but it does not have a candidate label and there appears to only be one PR to main. We will discuss this issue in standup and decide if this should be merged to the release branch.
As mentioned in a private discussion, if we accept this candidate recovery release will be held on Monday which is when the next endgame starts. To avoid overlap of the two endgames, this fix should be included instead in the next release.
Change:
private readonly _headerHeight = /*this._elements.header.clientHeight*/ 48; <ins> private _lastScrollTop = -1; private _isSettingScrollTop = false; </ins> public render(verticalRange: OffsetRange, width: number, editorScroll: number, viewPort: OffsetRange): void { this._elements.root.style.visibility = 'visible'; this._elements.root.style.top = `${verticalRange.start}px`;

Discussion:
Multi diff editor issue while expanding the hidden lines VS Code Version: 1.86 insider OS Version: Windows 11 //cc Steps to Reproduce: the multi diff editor on the hidden lines at the bottom ( the blue line) now it will expand the 10 lines now scrolling top doesn't show me the '5 hidden lines' text until I scroll down and then scroll up again
Change:
colorTheme: IColorTheme, model: IViewModel, userInputEvents: ViewUserInputEvents, <del> overflowWidgetsDomNode: HTMLElement | undefined </del> <ins> overflowWidgetsDomNode: HTMLElement | undefined, @IInstantiationService private readonly _instantiationService: IInstantiationService </ins> ) { super(); this._selections = [new Selection(1, 1, 1, 1)];

Discussion:
Type: <bBug</bWhen accessibility mode is off and focus is in the editor, pressing Alt +F1 produces the following announcement to screen reader users: "The editor is not accessible at this time. Press Alt+F1 for options.". If one is a new user of the product and screen reader mode doesn't turn on automatically, pressing the command which is supposed to help one get started just repeats the same announcement inviting the user to use Alt +F1 to obtain help. VS Code version: Code - OSS Dev 1.81.0 (Commit unknown, Date unknown) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</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.80.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
I filed the bug while running VS Code from source. That's why version information doesn't reflect that I'm using the latest. Correct version information: Version: 1.81.0-insider (user setup) Commit: Date: 2023-07-18T05:36:41.526Z Electron: 22.3.14 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.
Since the help menu is not accessible with that off, instead of we should say to enable screen reader mode.
Change:
} private _updateEverything(): void { <del> this._visibleCells.forEach(cell => cell.dispose()); this._visibleCells.clear(); this._updateVisibleCells({ added: this._observer.visibleCells, removed: [] }); </del> <ins> const newCells = this._observer.visibleCells.filter(cell => !this._visibleCells.has(cell.handle)); const visibleCellHandles = new Set(this._observer.visibleCells.map(item => item.handle)); const currentCellHandles = Array.from(this._visibleCells.keys()); const removedCells = currentCellHandles.filter(handle => !visibleCellHandles.has(handle)); const itemsToUpdate = currentCellHandles.filter(handle => visibleCellHandles.has(handle)); this._updateVisibleCells({ added: newCells, removed: removedCells.map(handle => ({ handle })) }); itemsToUpdate.forEach(handle => this._visibleCells.get(handle)?.update()); </ins> } <del> private _updateVisibleCells(e: ICellVisibilityChangeEvent): void { </del> <ins> private _updateVisibleCells(e: { added: CellViewModel[]; removed: { handle: number }[]; }): void { </ins> const vm = this._notebookEditor.viewModel; if (!vm) { return;

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: Insiders OS Version: Mac Basically when i have a statusbar item (extension that contributes statusbar items), VS Code re-creates all of the statusbar items for all cells. This causes ALL statubar items in all cells to flicker (as its destroyed and re-created) & we also end up with duplicates. /cc Flickering UI Duplicate statusbar items See below (from latest VS Code Insiders, can also replicate in latest main branch) Note how we end up with two language pickers in statusbar. ! After the fix (re-use instead of re-creating & only create what we need): !
Thought I had squashed all of these. Thanks for the PR!
The power tools don't seem to provide line numbers anymore so I tried switching the language mode around to repro and couldn't so I'm not sure if that's good enough for verification
I think it's sufficient to mess around with it and not see any dupes. And there were random reports of dupes earlier and I haven't heard that in awhile.
Change:
export const EDIT_SESSIONS_SIGNED_IN = new RawContextKey<boolean>(EDIT_SESSIONS_SIGNED_IN_KEY, false); export const EDIT_SESSIONS_CONTAINER_ID = 'workbench.view.editSessions'; <ins> export const EDIT_SESSIONS_DATA_VIEW_ID = 'workbench.views.editSessions.data'; </ins> export const EDIT_SESSIONS_TITLE = localize('edit sessions', 'Edit Sessions'); export const EDIT_SESSIONS_VIEW_ICON = registerIcon('edit-sessions-view-icon', Codicon.cloudDownload, localize('editSessionViewIcon', 'View icon of the edit sessions view.'));

Discussion:
Testing Store an edit session in for a GH repo Open desktop Insiders Use GH Repositories extension to open same remote GH repo Edit Sessions view is empty - since I'm logged into GH in both web and desktop, I anticipated seeing my 3 edit sessions from here: !
Duplicate of If you run the 'Focus on All Sessions View' command, do your edit sessions show up? In tomorrow's insiders that view container should only appear in the sidebar after you explicitly run the command to Show Edit Sessions.
These are the only edit session commands I see in desktop today: ! I see more options in than desktop - should I be seeing more of these options in desktop? ! Maybe this is a dupe of Edit: Yes, this seems to be When I stored an edit session in desktop, I was prompted to log into GH Repositories, and now I see more options: ! Except now I still don't see anything in the Edit Sessions view in desktop, although I'm working on the same GH repo through GH Repositories that I was working on in the web: !
Ah, I had to select the menu in the Edit Session view, and choose to "Show all sessions." Now I can see the session from I would've expected to see all my edit sessions by default.
that shouldn't happen, the 'Edit sessions' view container should be hidden unless the 'All sessions' view is also showing. Do you recall how you got the edit sessions container to show up without the sessions ?
I believe these were my steps: Make an edit and store a session in Open same repo via GH Repositories in desktop VS Code Make an edit and store a session in desktop Storing in desktop prompts me to log into GH Once logged in and the session is stored, run command to Confused because Edit Session view is empty I manually select menu in Edit Session view to and then I can see my sessions (I guess the web ones were hidden by default in desktop)
:+1: tracking as
I couldn't repro this yesterda on desktop, but just repro-ed this with a clean user data dir, this is a bug with the Show Edit Sessions action. It should focus the view, not the container.
<!-- 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!
I'm trying to test this again, but I don't see any edit session commands: ! Am I missing something?
/verified
Change:
ExtensionIdentifier.toKey(entry.description.identifier), candidate.name ?? entry.description.displayName ?? entry.description.name, candidate.text, <del> undefined, undefined, undefined, undefined, </del> <ins> undefined, candidate.command ? { id: candidate.command, title: candidate.name } : undefined, undefined, undefined, </ins> candidate.alignment === 'left', candidate.priority, undefined

Discussion:
Testing I might be doing something wrong, my contribution: I see no status entry that I can click on. I also tried with an existing command such as . ! Extension code is a hello world: Full :
not implemented
Change:
const enableDeveloperTools = (process.env['VSCODE_DEV'] || !!configuration.extensionDevelopmentPath) && !configuration.extensionTestsPath; let developerToolsUnbind; if (enableDeveloperTools || (options && options.forceEnableDeveloperKeybindings)) { <del> developerToolsUnbind = registerDeveloperKeybindings(); </del> <ins> developerToolsUnbind = registerDeveloperKeybindings(options && options.disallowReloadKeybinding); </ins> } // Correctly inherit the parent's environment

Discussion:
Issue Type: <bBug</bHitting Ctrl+R refresh Issue Report window content and the filled information are lost after refreshing. VS Code version: Code 1.35.1 (, 2019-06-12T14:27:31.086Z) OS version: Linux x64 4.15.0-54-generic <details<summaryExtensions (15)</summaryExtensionVersion ------ githistory0.4.6 es7-react-js-snippets2.3.0 json-tools1.0.2 prettier-vscode1.9.0 composer-support-client0.19.12 golang-tdd0.0.9 solidity0.0.56 vscode-docker0.7.0 python2019.6. cpptools0.24.0 Go0.11.4 sqltools0.19.6 material-icon-theme3.8.0 sass-indented1.5.1 gitblame2.8.1 </details<!-- generated by issue reporter --