jiebi/CodeConvo huggingface dataset:
Change:
smartCase: boolean; globalFindClipboard: boolean; location: 'sidebar' | 'panel'; <ins> useReplacePreview: boolean; </ins> } export interface ISearchConfiguration extends IFilesConfiguration {

Discussion:
I think it should be possible to disable "Replace Preview" in the settings. Currently, whenever I want to replace a word, the "Replace Preview" opens for every file, because I have file preview disabled.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.546 --- <!-- score: 0.535 --- <!-- score: 0.489 --- <!-- score: 0.473 --- <!-- score: 0.46 --<!-- potentialduplicatescomment --
Are you talking about the diff editor that opens when you click a result? What do you expect to see in that case?
Yes that's what I'm talking about. I would like to see just the file without a diff, maybe with the matches highlighted as I navigate through them in the search sidebar. Then when I click on replacing the text it would just replace it directly.
This seems reasonable and I would take a PR that adds a setting to disable the replace preview. FYI Starting point: and
I'd like to take a look at this.
Change:
const positionPercentage = isMainWindow ? Number(this.storageService.get(DEBUG_TOOLBAR_POSITION_KEY, StorageScope.PROFILE)) : this.auxWindowCoordinates.get(currentWindow)?.x; <del> x = positionPercentage !== undefined </del> <ins> x = positionPercentage !== undefined && !isNaN(positionPercentage) </ins> ? positionPercentage * currentWindow.innerWidth : (0.5 * currentWindow.innerWidth - 0.5 * widgetWidth); }

Discussion:
Type: <bBug</bHi, After the recent update on vscode on macOS, I am seeing the debug toolbar stuck to the top left corner of the window when I debug a .java file. And I cannot move it. The options overlap the window maximize, minimize and cancel buttons at the top left corner and are preventing me from clicking the options on the debug toolbar. Please fix this. Thank you. VS Code version: Code 1.86.0 (Universal) (, 2024-01-31T10:29:15.765Z) OS version: Darwin x64 23.2.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (11)</summaryExtensionVersion ------ live-sass6.1.2 intellij-idea-keybindings1.5.13 java1.27.0 LiveServer5.7.9 intellicode-api-usage-examples0.2.8 vscodeintellicode1.2.30 vscode-java-debug0.56.0 vscode-java-dependency0.23.4 vscode-java-pack0.25.15 vscode-java-test0.40.1 vscode-maven0.44.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Could you share a screenshot? Maybe related to but I wouldn't expect this on mac
It was working correctly (toolbar at the centre of the screen) just before the latest update. Here is what it looks like now: <img width="434" alt="vscode1" src=""
Same problem after the latest update.
same
Same here. Using 1.86. This is incredible annoying to work with.
I've run into the same thing on 1.86 although I was able to grab/move the debug toolbar to the center of my screen (ever so gingerly trying to grab the dots without touching the close window button, it felt like playing the game Operation). It has stayed there since (my is ), but it may not work for you and clearly was something that changed with the update for me as well
Change:
const enum ReuseOrder { PreviouslySelected = 1 << 8, SameExtensionAsNotebook = 2 << 8, <del> BuiltIn = 3 << 8, OtherRenderer = 4 << 8 </del> <ins> OtherRenderer = 3 << 8, BuiltIn = 4 << 8, </ins> } const preferred = notebookProviderInfo && this.preferredMimetype.getValue()[notebookProviderInfo.id]?.[mimeType];

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: Ubuntu Steps to Reproduce: New machine Install VS Code insiders Open an existing notebook text/latext output is rendered by built-in renderer Install jupyter based on VSCodes recommendation Re-load VSCode text/latext output is still rendered by built-in renderer Note: This workflow is not going to work as we know of a lot of text/latext that doesnt' work with the built-in renderer, & novice users won't know that they need to change the renderer to Jupyter Notebook renderer. I've submitted a PR to remove the text/latex renderer from VS Code
I believe this is where we select the renderer (we currently always take the first one): I agree that automatically deprioitizing built-in renderers makes sense
Starting from a clean user-data-dir, I follow the steps, and it picks the built-in one by default. ! If I pick the extension renderer, it seems to remember that selection.
How do I get the latex mime types to show in that picker? I only see one: !
To verify: sure you have the jupyter extension installed and are in an ipynb notebook a normal python cell, run: the output is rendered nicely <img width="515" alt="Screen Shot 2021-11-01 at 9 20 35 AM" src="https://user-"
Change:
import { TerminalLocation } from 'vs/platform/terminal/common/terminal'; import { IThemeService } from 'vs/platform/theme/common/themeService'; import { IConfigurationService } from 'vs/platform/configuration/common/configuration'; <ins> import { IKeybindingService } from 'vs/platform/keybinding/common/keybinding'; </ins> export class TerminalFindWidget extends SimpleFindWidget { protected _findInputFocused: IContextKey<boolean>;

Discussion:
And instead pass in (or don't) a new option for the type
so the complexity here is that we can't reference the keybinding service within the super call to the constructor and need to do that to provide the options to the find input object that's read only.
the alternative would be to pass in the options from both the terminal view and terminal editor (redundant)
going to pass in an options object and handle the keybinding in simple find widget
Spent awhile on this, don't think we will get to it
Change:
const response = await fetch(url, init); if (!response.ok) { <ins> console.error('Invalid GitHub URL provided.'); </ins> return false; } const result = await response.json();

Discussion:
Testing I had the arg For and clicking "Create on GitHub" did nothing. I would expect an error to log in the console for this so that devs know what has happened.
Did this log anything in the console? (ie, or something like that)
I didn't see anything in the debug console.
Technically, it's a valid URI, but it doesn't resolve to a valid endpoint.

Testing <img alt="image" src=""For this, I put an invalid , and as expected, the field in the issue reporter is not set to a specific extension. However, I'd appreciate a warning log in the debug console that warns devs that they have an invalid
Change:
await this.storeForwarded(); return deprecatedValue; } <del> const storageKey = await this.getStorageKey(); </del> <ins> const storageKey = await this.getTunnelRestoreStorageKey(); </ins> if (!storageKey) { return undefined; }

Discussion:
I had to clear settings sync for an unrelated issue and start fresh, but enabling the "UI State" option causes the error below to be continually thrown. If I disable the "UI State" option in settings sync, it starts working again. Type: <bBug</bsettings sync, check all boxes except "UI State" settings sync log, see that it succeeds settings sync config to include UI State VS Code version: Code 1.85.1 (Universal) (, 2023-12-13T09:48:06.308Z) OS version: Darwin arm64 23.2.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (12)</summaryExtensionVersion ------ erb0.0.1 vscode-eslint2.4.2 prettier-vscode10.1.0 codespaces1.16.6 copilot1.148.0 copilot-chat0.11.1 vscode-graphql-syntax1.2.3 endwise1.5.1 remote-containers0.327.0 proto0.0.4 rewrap1.16.3 gitblame10.6.0 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Can you please share the UI state using following steps F1 Export Profile... Select only UI state Export the profile and share it
The exported file is 2.3 MB, and it has some things inside that might be considered sensitive, I'm not sure. Is there a way I can share it privately?
You can share it to me by email - 2.3 MB is way under the limits right?
Just emailed the file, thank you!
I just checked the size limits on the server and it is indeed 2MB caps
Thanks for sharing. I figured out that port forwarding state is taking majority of the size. Hence assigning to
Discussed with and there are 3 easy things I can do to quickly reduce the size: Don't save empty values Add an expiry time to values so they don't live forever Save fewer fields per port in . For example, only tunnels should be stored + restored, so should be removed. So should , , , and .
the limit per resource version is 2mb atm
Are there steps to verify this?

To verify: to a Codespace and forward a port the remote connection the steps in to collect a profile the file created in step 3. Check that the port that you just forwarded in step 1 is listed there under a key and that it doesn't have a value.
For the step, does this mean to stop the codespace?
This is verified. The new port forwarded doesn't have , but I did notice some old ports of mine from old codespaces still having . Not sure if that was expected to be covered.
The behavior you see is expected. I didn't add any cleanup of the old state.
Change:
override dispose(immediate?: boolean): void { <del> if (this._isDisposed) { return; } this._isDisposed = true; </del> this._logService.trace(`terminalInstance#dispose (instanceId: ${this.instanceId})`); dispose(this._linkManager); this._linkManager = undefined;

Discussion:
I have been testing the task shell integration (running some tasks, resizing the terminal to see if the decoration stayed in the right place) and now one of my task terminals is unkillable: ! I had just killed 2 other task terminals without issue.
This seems like something that might be un-reproducible so I tried to debug a bit. The has set to , which is probably not very helpful information since I don't know how that happened. Error in Log (Window):
Maybe caused by
Is that issue about terminal editors? I never moved the terminal into an editor.
It is, but the change is related to dispose/isDisposed in the command TerminalInstance class
Change:
ALL_WINDOWS } <ins> export const MAX_ZOOM_LEVEL = 8; export const MIN_ZOOM_LEVEL = -8; </ins> /** * Apply a zoom level to the window. Also sets it in our in-memory * browser helper so that it can be accessed in non-electron layers. */ export function applyZoom(zoomLevel: number, target: ApplyZoomTarget | Window): void { <ins> zoomLevel = Math.min(Math.max(zoomLevel, MIN_ZOOM_LEVEL), MAX_ZOOM_LEVEL); // cap zoom levels between -8 and 8 </ins> const targetWindows: Window[] = []; if (target === ApplyZoomTarget.ACTIVE_WINDOW) { targetWindows.push(getActiveWindow());

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 Version: 1.68.0 (user setup) Commit: Date: 2022-06-08T11:44:16.822Z Electron: 17.4.7 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: is not in F11 fullscreen mode. the Settings GUI, set window.zoomLevel to a negative value (e.g. -3) add an extra 0 (e.g. -30) setting is automatically applied, which leads to a state where the entire UI disappears. Clicking anywhere in the window minimizes the window. F11 fullscreen mode appears to fix this situation and the UI becomes visible again(albeit very tiny at the -30 zoom level). My initial take is this could be fixed with a sane lower bounds on window.zoomLevel. However, it appears that part of the issue is also that as window.zoomLevel becomes more negative(zooms out), the Menu Bar becomes larger. At high magnitude negative values, the Menu Bar increases in size to the point where it takes up the entire window and prevents user input. Ex.) window.zoomLevel: -20 . ! Ex.) window.zoomLevel: -30. At this level, the Menu Bar minimize "-" icon takes up the whole window.

At this level, the setting input box also de-focuses, preventing the user from pressing backspace to remove the extra 0. !
<!-- 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:
const caseIgnoreFlag = serializedValue[end + 1] === 'i' ? 'i' : ''; try { return new RegExp(value, caseIgnoreFlag); <del> } catch (e) { console.warn(`bad regexp-value '${serializedValue}', parse error: ${e}`); </del> <ins> } catch (_e) { </ins> return null; } }

Discussion:
Looks like has some statements. This is fair for local development but shouldn't be shipping in the product.
Change:
} .monaco-editor .suggest-widget .details > .header > .title { <del> flex: 2; </del> <ins> overflow: hidden; text-overflow: ellipsis; </ins> } .monaco-editor .suggest-widget .details > .header > .go-back {

Discussion:
In a suggestions view, navigate to a suggestion with a long label and enter the details view on this suggestions. Bug <img width="593" alt="screen shot 2017-02-15 at 4 14 18 pm" src=""The label for the completion item goes outside of the suggestion box
Change:
ToggleAutoRun = 'testing.toggleautoRun', ToggleInlineTestOutput = 'testing.toggleInlineTestOutput', UnhideTestAction = 'testing.unhideTest', <ins> UnhideAllTestsAction = 'testing.unhideAllTests', </ins> }

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 would like to run all the tests from the task. However, if there is a hidden test (e.g. by mistake), that test will not be executed. Is it possible to make work from task? Or if there is a command that ignores the hidden ones and runs all tests, that would be fine.
It looks like expects some arguments but you're looking for a command that unhides all instead.
Code pointer for the existing action:
Should there be a new command to unhide all tests say testing.hideAll or a task to run all tasks including hidden tests - testing.runAllIncludingHidden?
Yes! please.
Verified it unhides all hidden tests.
Change:
const electronOpts = _.extend({}, exports.config, { platform: process.platform, arch: arch === 'armhf' ? 'arm' : arch, <del> ffmpegChromium: true, </del> <ins> ffmpegChromium: false, </ins> keepDefaultApp: true }); return vfs.src('package.json')

Discussion:
The Angular language service extension spawns a child process using and listens for the and events. The current version works as expected. Without any changes to the project, simply updating to results in the forked child process acting differently (never erroring and never closing). I'm using Mac 13.3.1 but we also had a report that the forked process isn't working in WindowsNT x64 10.0. either. There was a similar issue (though not entirely the same) a while back: Apologies for the rather involved reproduction... Here's how I'm able to reproduce and compare the behavior between the versions: our the repository with vscode insider version 1.78.0-insiders out the branch (we're actually removing this in the next version so it doesn't exist on ) dependencies with debugging, put a debugger statement before and one in the . The project is built with bazel so breakpoints would have to be put in the compiled JS files. the build script with the extension development host (Dev Client + Server run configuration) In the extension host, open the and then open the template file -- debugger should stop on the fork and if you continue, you will see that the debugger stops in the stderr data listener but never in the or . The output of the stderr also indicates that it is listening for a debugger and that it gets attached. The fork used which should have prevented this. The process also never produces any results or completes. You can have the fork retry by running the Angular: Restart Angular Language server command in the extension host. I've also verified that the spawn args are the same between versions and both include "--ms-enable-electron-run-as-node".
Issue was caused by the allocator changes to processes which now schedule delayed tasks to purge memory cache ;l=1183 and that revealed a bug in the causing the process to hang.
<!-- 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:
} } <del> registerWorkbenchContribution2(InteractiveDocumentContribution.ID, InteractiveDocumentContribution, WorkbenchPhase.AfterRestored); </del> <ins> registerWorkbenchContribution2(InteractiveDocumentContribution.ID, InteractiveDocumentContribution, WorkbenchPhase.BlockRestore); </ins> registerWorkbenchContribution2(InteractiveInputContentProvider.ID, InteractiveInputContentProvider, { editorTypeId: INTERACTIVE_WINDOW_EDITOR_ID });

Discussion:
!
Is this in web? Whats your setup?
Yes, this is in web. When you open and reload the page, does it open as text for you?
I can reproduce. My guess is it has something to do with the extension not being present on restore
This is strange: the first time I did this, the notebook opened as text. But now when I try to open the link, I am always getting put back to the readme as preview Did we somehow miss the ability to deep-link a file on or is it just me?
This works for me.
Whenever I click the link I get the notebook as text regardless of having the extension installed . I don't get the readme preview though.
!
Change:
private _headerVisible = true; private _minimumBodySize: number; private _maximumBodySize: number; <del> private ariaHeaderLabel: string; </del> <ins> private _ariaHeaderLabel: string; </ins> private styles: IPaneStyles = {}; private animationTimer: number | undefined = undefined;

Discussion:
GitHub Tags:#A11yMAS;#A11yTCS;#A11ySev2;#DesktopApp;#Win32;#Visual Studio Code Client;#BM-VisualStudioCodeClient-Win32-Aug2022;#WCAG1.3.1;#NVDA; #ScreenReader;#JAWS;#AILimited;#Element:Button; Application Name: Visual Studio Live Share Application version: 1.56.2 (user setup) Windows Version: Win10 VS Code a project (e.g., vsls-guestbook) in VSCode. till “sign in” button. till "Live share" under Extensions and hit enter on the NVDA and tab to drop down 'Visual Studio live share work' screen. The label of the 'Visual Studio live share work….' is being read as 'folder section button' when the screen reader focus moves to it using tab key. Similar issue is observed with JAWS. The screen reader should read it as 'Visual Studio live share work button' when screen reader focus moves to it. People who uses screen reader may face difficulty while activating an object when the accessible label is different than that of the visible labels. https://user-
logged for primary bug
I think this issue makes sense. In short - aria label of the explorer view should contain the name of the top folder. Currently it is just "Folders". So it should be dynamic. Assigning to
Actually not too sure how to fix this one. The section being read out is the static section name of the view pane We do have an aria label within that section header with the name of the folder which dynamically updates but that never gets focused. The pane registration is static and we don't know the folder name at that time
there's the  method in the . Update header should set the aria label of the header. And the explorer should call updateHeader every time the content of the header changes (which it might do already).

could you please the bug in open state the bug can be closed only by trusted tester after verification right now the fix is not present in the app Version: 1.72.0-insider (user setup) Commit: Date: 2022-09-23T05:17:37.024Z Electron: 19.0.17 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes !
please look at the label that the VS Code bot has to the issue. It says "unreleased". Once the bot adds the label "released" that means the fix is present. We can not leave the issue open for the tester to close this since this does not align with the rest of our VS Code processes. In case the bug is not fixed after it is released, just comment on the issue and we will reopen it. Thanks!
GitHubTags:#Closed;
Change:
) { super(parent, instantiationService, themeService, configurationService); this._symbolSortOrder = BreadcrumbsConfig.SymbolSortOrder.bindTo(this._configurationService); <ins> this._outlineComparator = new OutlineItemComparator(); </ins> } protected _createTree(container: HTMLElement) {

Discussion:
The setting "breadcrumbs.symbolSortOrder" cannot be enabled for a specific language, i.e. "[markdown]": { "breadcrumbs.symbolSortOrder": "position" } is not possible in the settings. It makes sense to sort by position in markdown files to see headers and subheaders as they are. However, one might want to display symbols by type when writing code. Thank you in advance!
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 existing issues . See also our guidelines. Happy Coding!
Actually not a duplicate but should be straight forward to implement as filter-options can already be defined per language
Could you point me towards how to get the current resource from the editor model inside ?
The  has a reference to the text model
to verify, have this setting and a file with this content (symbol should be sorted alphabetically) Now, paste the same content into and make sure symbols are sorted by position