jiebi/CodeConvo huggingface dataset:
Change:
Issue Type: <bBug</bthe integrated console viewlets to a vertical layout the viewlet narrow When wide enough: ! Once narrowed: ! Expected result: Debug Console search bar shrinks/hides itself in order to show other tabs first (like in the first screenshot). The 3 dots "works", but is, at least in my opinion, more annoying than not being able to search in the Debug Console when the viewlet is narrow. 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 </details<!-- generated by issue reporter --
The min width is 300, I think that can be narrower. The problems view filter input goes into the body when the view is too narrow, which is sorta cool <img width="571" alt="image" src="https://user-"but I won't implement that right now
Actually it was easy to opt into that. I tweaked the min widths and also when the pane is narrow, the filter box will move down into the body
Holy, I forgot about this issue! Love the idea of copying the behaviour of the Problems tab! Excited to try it on Insiders :) Thanks !

Discussion:
.monaco-action-bar .action-item .monaco-select-box { cursor: pointer; <del> min-width: 110px; </del> <ins> min-width: 70px; </ins> min-height: 18px; padding: 2px 23px 2px 8px; }

.panel > .title .monaco-action-bar .action-item.viewpane-filter-container { max-width: 400px; <del> min-width: 300px; </del> <ins> min-width: 150px; </ins> margin-right: 10px; }

this.updateActions(); if (!shouldShowFilterInHeader) { append(this.filterContainer!, this.filterWidget.element); <del> height = height - 44; </del> } } <ins> if (!shouldShowFilterInHeader) { height = height - 44; } </ins> this.filterWidget.layout(width); this.layoutBodyContent(height, width); }

this.replInput.layout({ width: width - 30, height: replInputHeight }); } <del> override shouldShowFilterInHeader(): boolean { return true; } </del> collapseAll(): void { this.tree.collapseAll(); }
Change:
<!-- 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: OS Version: Steps to Reproduce: to search tab. Click "Open new search editor" some text. context lines to 2. It takes effect. context lines to 0. It take effect. context lines to 2. It doesn't take effect.
I can see this too (in Insiders). It is as if decreasing the context lines value to 0 toggles off the context lines for some reason. In fact, I can see the option being automatically disabled when you hit 0, but it does not reenable upon increasing the value. Toggling the context lines option icon does temporarily fix the issue.
When the context line number decrease to zero, toggle button is unchecked. However if you increase the number again, the toggle button is not checked automatically which result in this issue.

Discussion:
this.contextLinesInput = new InputBox(searchInputContainer, this.contextViewService, { type: 'number' }); this.contextLinesInput.element.classList.add('context-lines-input'); this.contextLinesInput.value = '' + (this.configurationService.getValue<ISearchConfigurationProperties>('search').searchEditor.defaultNumberOfContextLines ?? 1); <del> this._register(this.contextLinesInput.onDidChange(() => this.onContextLinesChanged())); </del> <ins> this._register(this.contextLinesInput.onDidChange((value: string) => { if (value !== '0') { this.showContextToggle.checked = true; } this.onContextLinesChanged(); })); </ins> this._register(attachInputBoxStyler(this.contextLinesInput, this.themeService)); dom.append(searchInputContainer, this.showContextToggle.domNode); }
Change:
<!-- 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?: This is an issue related to the IntelliSense information block and terminal display area. Without any extension almost all code completion is unavailable. So I guess I should answer Yes here. <!-- 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.63.2 OS Version: Windows 10 21H1 And I guess this configuration might also help: Terminal Integrated: Gpu Acceleration: off Steps to Reproduce: the integrated terminal to the right. function IntelliSense at a line long enough so that hint block should float on the right end. should get a wrong overlay at Z direction now. The hint block is hard to see. I've tried Python and C++. Both reproduced. So this should be an issue with VS Code instead of language IntelliSense extensions. !
I can definitely reproduce. The terminal is rendering on top of other stuff !
And the behavior differs with different option. !
Oh this only affects parameter hints, not the regular hover.
<img width="226" alt="image" src="https://user-"Looks good!

Discussion:
*--------------------------------------------------------------------------------------------*/ .monaco-editor .parameter-hints-widget { <del> z-index: 10; </del> <ins> /* Must be higher than sash's z-index and terminal canvases */ z-index: 40; </ins> display: flex; flex-direction: column; line-height: 1.5em;
Change:
It is possible with VSCode to follow a path printed in the terminal. When that path also contains the line and column number in the format ( ≙ line number; ≙ column number), VSCode currently doesn't interpret it completely and therefore doesn't also jump to the line/column in the opened file. Example: ` This path format indicates the path to the file but also the line (49) and column (46) number. Ctrl + clicking this path currently in VSCode will open the file but not jump to the line or the column. As this format is used by many linters and compilers (e.g. SASS), it would be a very useful and time-saving feature.
Code link: I think here we'd want to require the exact (num)(colon)(num) to prevent problems with (link) (number) (text)
nice feature for many front end build tools.
I PR for this.

Discussion:
/** As xterm reads from DOM, space in that case is nonbreaking char ASCII code - 160, replacing space with nonBreakningSpace or space ASCII code - 32. */ export const lineAndColumnClause = [ <ins> '(([^:s()<>'"[]]*) ((d+))(:(d+)))', // (file path) 336:9 [see #140780] </ins> '((S*)['"], line ((d+)( column (d+))?))', // "(file path)", line 45 [see #40468] '((S*)['"],((d+)(:(d+))?))', // "(file path)",45 [see #78205] '((S*) on line ((d+)(, column (d+))?))', // (file path) on line 8, column 13

{ urlFormat: '{0} ({1}, {2})', line: '5', column: '3' }, { urlFormat: '{0}:{1}', line: '5' }, { urlFormat: '{0}:{1}:{2}', line: '5', column: '3' }, <ins> { urlFormat: '{0} {1}:{2}', line: '5', column: '3' }, </ins> { urlFormat: '{0}[{1}]', line: '5' }, { urlFormat: '{0} [{1}]', line: '5' }, { urlFormat: '{0}[{1},{2}]', line: '5', column: '3' },
Change:
Failed twice in a row today I've skipped this test
This failed a lot, I'm not sure it was flaky? Please check it one out during this milestone to verify it's not important.
I'm not able to reproduce locally, so I guess it's flaky. I more debug output and enabled it again.

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
takes much longer to render with file nesting enabled. Impact is lessened by disabling file nest auto-expansions. is not significantly slower to render with nesting, though I have not collected proper numbers yet.
closedWith
takes a comparable amount of time to render with file nesting enabled, though there is a perceptible delay for both. However, I do also notice that the window becomes intermittently unresponsive after expanding , e.g. when scrolling in the explorer. Is this known?
Yeah, same thing happens with nesting disabled. There's an open issue somewhere for ways to reduce that (like streaming the dir contents).

Discussion:
import { DisposableStore, dispose, IDisposable } from 'vs/base/common/lifecycle'; import { ScrollEvent } from 'vs/base/common/scrollable'; import { IThemable } from 'vs/base/common/styler'; <ins> import { isIterable } from 'vs/base/common/types'; </ins> interface IAsyncDataTreeNode<TInput, T> { element: TInput | T;

if (!node.hasChildren) { childrenPromise = Promise.resolve(Iterable.empty()); } else { <del> const slowTimeout = timeout(800); </del> <ins> const children = this.doGetChildren(node); if (isIterable(children)) { childrenPromise = Promise.resolve(children); } else { const slowTimeout = timeout(800); </ins> <del> slowTimeout.then(() => { node.slow = true; this._onDidChangeNodeSlowState.fire(node); }, _ => null); </del> <ins> slowTimeout.then(() => { node.slow = true; this._onDidChangeNodeSlowState.fire(node); }, _ => null); </ins> <del> childrenPromise = this.doGetChildren(node) .finally(() => slowTimeout.cancel()); </del> <ins> childrenPromise = children.finally(() => slowTimeout.cancel()); } </ins> } try {

} } <del> private doGetChildren(node: IAsyncDataTreeNode<TInput, T>): Promise<Iterable<T>> { </del> <ins> private doGetChildren(node: IAsyncDataTreeNode<TInput, T>): Promise<Iterable<T>> | Iterable<T> { </ins> let result = this.refreshPromises.get(node); if (result) { return result; } <del> result = createCancelablePromise(async () => { const children = await this.dataSource.getChildren(node.element!); </del> <ins> const children = this.dataSource.getChildren(node.element!); if (isIterable(children)) { </ins> return this.processChildren(children); <del> }); this.refreshPromises.set(node, result); return result.finally(() => { this.refreshPromises.delete(node); }); </del> <ins> } else { result = createCancelablePromise(async () => this.processChildren(await children)); this.refreshPromises.set(node, result); return result.finally(() => { this.refreshPromises.delete(node); }); } </ins> } private _onDidChangeCollapseState({ node, deep }: ICollapseStateChangeEvent<IAsyncDataTreeNode<TInput, T> | null, any>): void {
Change:
<!-- 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: OS Version: Steps to Reproduce: default keybinding F1 for Show All Commands new Keybinding for Show All Commands and try to assign F1 to it. When trying to add F1 as a new keybinding for Show All Commands it just does nothing. You can assign other shortcuts like "ctrl+F1". The only way to get F1 back is by removing all keybindings for "Show All Commands" and then reset the keybinding. ! Keybindings for other commands can be assigned with F1. I tried it with the stable VS Code and there it works just fine.
I can reproduce and confirm that this is a bug. As a workaround, you can open your file using and remove the following rule:

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
Error from telemetry. I ran into this as well sometimes when opening a second IW.
Here are some of my findings: We don't have smoke tests for IW Some how the stable version of Jupyter is in the smoke tests Stable version is some how (for some reason) launching IW, hence we see errors Could be because we're testing in stable vs code and requires insiders.
Note: These are messages on the CI server (in our tests). Seems to be in smoke tests.
I believe we get these on CI too: Here's an example from running on main:
I believe this is an issue in core. We might be changing the selected notebook to nothing and it doesn't handle it.
is used only when an issue isn't yet assigned to its rightful owner.
this repros every time an interactive window with a specific name is created for the first time - we haven't created the document for that IW yet. But then the same $acceptNotebookAssociation is fired again after creating that document anyway

Discussion:
const allKernels = kernelService.getMatchingKernel({ uri: notebookUri, viewType: 'interactive' }).all; const preferredKernel = allKernels.find(kernel => kernel.id === id); if (preferredKernel) { <del> kernelService.selectKernelForNotebook(preferredKernel, { uri: notebookUri, viewType: 'interactive' }); </del> <ins> kernelService.preselectKernelForNotebook(preferredKernel, { uri: notebookUri, viewType: 'interactive' }); </ins> } }

} } <ins> preselectKernelForNotebook(kernel: INotebookKernel, notebook: INotebookTextModelLike): void { const key = NotebookTextModelLikeId.str(notebook); const oldKernel = this._notebookBindings.get(key); if (oldKernel !== kernel?.id) { this._notebookBindings.set(key, kernel.id); this._persistMementos(); } } </ins> updateKernelNotebookAffinity(kernel: INotebookKernel, notebook: URI, preference: number | undefined): void { const info = this._kernels.get(kernel.id); if (!info) {

selectKernelForNotebook(kernel: INotebookKernel, notebook: INotebookTextModelLike): void; /** <ins> * Set the kernel that a notebook should use when it starts up */ preselectKernelForNotebook(kernel: INotebookKernel, notebook: INotebookTextModelLike): void; /** </ins> * Bind a notebook type to a kernel. * @param viewType * @param kernel
Change:
Neither the vscode repository nor the package itself provide any appdata, which is important to have gnome-software working properly. The vscode repository should generate appstream data (xml) and provide them. So the PackageKit can save it into /var/cache/app-info/xmls/. The itself also should install a into /usr/share/metainfo/. Look here:
I believe we include in the root of the package, is that not the case?
Unfortunately, it is not the case. There's no or file. Output from : The preferred place for that appdata file is Then the repository creation should also include generating AppStream repository metadata. The mechanics of doing this is documented here: (Ignore the argument, that should not be used)
Hey this issue might need further attention. you can help us out by closing this issue if the problem no longer exists, or adding more information.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
This should be reopened, because it's still broken.
Confirmed that the deb package is good but that the rpm package has this issue.
I have about 200 messages coming a day I don't know what happened how do I unsubscribe from this Microsoft thing vs code please advise
see
Verification steps: the on a Linux distribution with rpm (the link downloads an x64 .rpm file) in a terminal that shows up.

Discussion:
.pipe(replace('@@NAME_LONG@@', product.nameLong)) .pipe(replace('@@NAME@@', product.applicationName)) .pipe(replace('@@LICENSE@@', product.licenseName)) <del> .pipe(rename('usr/share/appdata/' + product.applicationName + '.appdata.xml')); </del> <ins> .pipe(rename('BUILD/usr/share/appdata/' + product.applicationName + '.appdata.xml')); </ins> const workspaceMime = gulp.src('resources/linux/code-workspace.xml', { base: '.' }) .pipe(replace('@@NAME_LONG@@', product.nameLong))

mkdir -p %{buildroot}%{_bindir} mkdir -p %{buildroot}%{_datadir}/%{name} mkdir -p %{buildroot}%{_datadir}/applications <ins> mkdir -p %{buildroot}%{_datadir}/appdata </ins> mkdir -p %{buildroot}%{_datadir}/mime/packages mkdir -p %{buildroot}%{_datadir}/pixmaps mkdir -p %{buildroot}%{_datadir}/bash-completion/completions

# Support files cp -r usr/share/applications/%{name}.desktop %{buildroot}%{_datadir}/applications cp -r usr/share/applications/%{name}-url-handler.desktop %{buildroot}%{_datadir}/applications <ins> cp -r usr/share/appdata/%{name}.appdata.xml %{buildroot}%{_datadir}/appdata </ins> cp -r usr/share/mime/packages/%{name}-workspace.xml %{buildroot}%{_datadir}/mime/packages/%{name}-workspace.xml cp -r usr/share/pixmaps/@@ICON@@.png %{buildroot}%{_datadir}/pixmaps # Shell completions

%{_datadir}/%{name}/ %{_datadir}/applications/%{name}.desktop %{_datadir}/applications/%{name}-url-handler.desktop <ins> %{_datadir}/appdata/%{name}.appdata.xml </ins> %{_datadir}/mime/packages/%{name}-workspace.xml %{_datadir}/pixmaps/@@ICON@@.png %{_datadir}/bash-completion/completions/%{name}
Change:
<!-- 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 When I hover over the command in the Unicode Highlighted character I get a very long tooltip message (most of it isn't in the demo): ! Version: 1.64.0-insider (user setup) Commit: Date: 2022-01-21T13:25:29.978Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.

Discussion:
} } <ins> const configureUnicodeHighlightOptionsStr = nls.localize('unicodeHighlight.configureUnicodeHighlightOptions', 'Configure Unicode Highlight Options'); </ins> export class UnicodeHighlighterHoverParticipant implements IEditorHoverParticipant<MarkdownHover> { public readonly hoverOrdinal: number = 5;

const markdown = new MarkdownString('', true) .appendMarkdown(reason) .appendText(' ') <del> .appendLink(uri, adjustSettings); </del> <ins> .appendLink(uri, adjustSettings, configureUnicodeHighlightOptionsStr); </ins> result.push(new MarkdownHover(this, d.range, [markdown], false, index++)); } return result;

const result = await quickPickService.pick( options, <del> { title: nls.localize('unicodeHighlight.configureUnicodeHighlightOptions', 'Configure Unicode Highlight Options') } </del> <ins> { title: configureUnicodeHighlightOptionsStr } </ins> ); if (result) {
Change:
include information about the args that are accepted/not.
An exhaustive list of what's supported or not would be better for docs and when it's stable, I included a statement about some custom profile args might not work.

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
Testing open a notebook open the find widget the height is off (too heigh in comparison) <img width="702" alt="Screen Shot 2022-01-25 at 10 42 51" src="https://user-"

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
Testing (see attached recording) open my-endgame notebook search for your user name run the "Issues filed by me" query search in output too, go through all matches replace your own username with its upper case variant the number of matches is bogous https://user- <img width="442" alt="Screen Shot 2022-01-25 at 10 51 39" src="https://user-"
Verifier: Follow the steps above. When searching in output is enabled and there are search results in outputs, the replace all button is disabled. The replace one button is enabled only when the current find match is a model match, you need to navigate to that match to test replacement.

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
Testing open run all cells default find settings, search for "opened" no matches enable search in output, there are matches :bug: the arrow buttons are still disabled <img width="464" alt="Screen Shot 2022-01-25 at 11 03 54" src="https://user-"

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
Testing <img width="415" alt="Screen Shot 2022-01-25 at 11 11 46" src="https://user-"The names seem a bit overly specific, like "Code Cell Outputs" could just be "Cell Outputs" (as in the output switcher) or "Outputs". Also "outputs" is plural while others are singular
Good suggestion, is a good candidate.
I wonder if we should also change to to align with but not sure if that would be too ambiguous.

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
Testing fresh workspace open stable code move panel left move side bar right have a 2x2 grid editor layout start with latest insiders = panel is not restored and when showing appears at bottom
+1. Repros for me too using 1.63 insiders.
However it does remember if I open in the side panel with latest, then restart.
The issue here was that I extra prefix to the layout state keys. to ... since is redundant in this context, I've opted to go back to the old key prefix. this will mess up insiders state overnight, but I think this is better than messing up a lot of stable users state.

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();
Change:
Testing open stable code on fresh workspace hide activity bar maximize panel reopen with insiders = panel is not restored as maximized
see regarding fix

Discussion:
disposables.push(server.onServerStart(path => { <del> defaultStatus.text = '$(flame) Runnning'; </del> <ins> defaultStatus.text = '$(flame) Running'; </ins> defaultStatus.command = 'o.pickProjectAndStart'; defaultStatus.color = ''; render();