jiebi/CodeConvo huggingface dataset:
Change:
<meta charset="UTF-8"> <meta http-equiv="Content-Security-Policy" <del> content="default-src 'none'; script-src 'sha256-N4YFn5ze5crjPqMK/opogKs7bSGWtf3lmjV/3LfbSOs=' 'self'; frame-src 'self'; style-src 'unsafe-inline';"> </del> <ins> content="default-src 'none'; script-src 'sha256-7Y08cqii1UgeZbSST9r8UPSownOSMa3/PiKe77avh7I=' 'self'; frame-src 'self'; style-src 'unsafe-inline';"> </ins> <!-- Disable pinch zooming --> <meta name="viewport"

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: N/a <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: Version: 1.77.3 Commit: Date: 2023-04-12T09:16:02.548Z Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.77.3 Chrome/102.0.5005.196 Electron/19.1.11 Safari/537.36 OS Version: Steps to Reproduce: click a file in the Explorer. The background color of the row changes from blue to grey. Esc to close the context menu. The background color changes back. is not possible to emulate with an extension using a webview context menu. Fixed by my PR
<!-- 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'll verify this.
<img width="320" alt="image" src=""<img width="334" alt="image" src=""I can confirm that on that there is a style change when right-clicking a file in the Explorer. But it's not the one described, the text colour changes slightly (this may be a theme difference). What's an extension that uses a file list in a web view that I can verify?

I think any webview context menu should work for this, not necessarily a file list.
They would need to add a CSS rule with the new class name to make an actual change in visual appearance. You can verify the class is applied on the body element using the Webview Developer Tools.
this could probably be edited
Here's a snippet from my project, the selector doesn't work while the context menu is up, so I repeat the same rules with
Oh, and the original issue was reported with the previous default theme.
Thanks
Change:
const HOVER_DELAY = 300; const LAUNCH_JSON_REGEX = /launch.json$/; <del> const REMOVE_INLINE_VALUES_DELAY = 100; </del> <ins> const UPDATE_INLINE_VALUE_DECORATIONS_DELAY = 200; const REMOVE_INLINE_VALUE_DECORATIONS_DELAY = 100; </ins> const INLINE_VALUE_DECORATION_KEY = 'inlinevaluedecoration'; const MAX_NUM_INLINE_VALUES = 100; // JS Global scope can have 700+ entries. We want to limit ourselves for perf reasons const MAX_INLINE_DECORATOR_LENGTH = 150; // Max string length of each inline decorator when debugging. If exceeded ... is added

Discussion:
Right now we expose an API to cells, and to webviews, but we don't publish types for this. The webview API is very simple, but the renderer will be somewhat more complex. We should consider either publishing these in or in a separate package.
This would be helpful for I think a or something would be a good place for it. Aside, it'd be cool if ts s could be contributed to... Right now we'd need a whole separate NPM scope to have separate I believe.
We can just PR a package called The naming of packages is only constrained by the maintainers' policy, and there are types that don't correspond to single packages, e.g.
Poor wording, I mean the project would need a different and for the client code vs the extension host code. (Or just know not call acquireApi outside of the client context of course. )
Oh, yea. In the sample renderer/code generator I'm using project references to keep things separated -- that also lets us use only in the renderer and output es6 modules (only) for webpack.
PR submitted

Bug Set "debug.inlineValues": true. Set breakpoint somewhere. After paused on the step, goto the end of the line and hit enter. Before After VS Code version: Code 1.20.0 (, 2018-02-07T17:02:34.244Z) OS version: Darwin x64 16.7.0 <details<summarySystem Info</summary </details<details<summaryExtensions (9)</summaryExtensionVersion ------ EditorConfig0.12.0 vscode-eslint1.4.5 vscode-great-icons2.1.24 auto-rename-tag0.0.15 code-beautifier1.7.2 vscode-scss0.6.2 mssql1.3.0 cpptools0.14.6 licenser1.1.1 (1 theme extensions excluded) </detailsReproduces only with extensions
I acknowledge the bug. This is just how decoartions are behaving, unfortunetly the inline decorations do not seem to have an option to not grow beyond the line. maybe you have an idea how to solve this? fyi in case you are interested into looking for a fix
debugger.inlineValues uses the editor's decorator api. A fix we can do is that if the editor is edited , then we re-sync the inlineValue decorators I'm not sure how this works but would love it if the bug was assigned to me so I can see it in my issues list
that's a good idea. can you please add to our project so we can assign some issues to him?
Change:
body = body.join('n'); } <ins> if (Array.isArray(description)) { description = description.join('n'); } </ins> if ((typeof prefix !== 'string' && !Array.isArray(prefix)) || typeof body !== 'string') { return; }

Discussion:
While creating a user snippet, the rule must be like this: If I want to show a lot of description, I must write a huge string which includes many escape characters like this: It maybe a good idea that option receive a list value, like the :
The Version infomations: Code Version: 1.30.1 (user setup) Commit: Date: 2018-12-18T18:12:07.165Z Electron: 2.0.12 Chrome: 61.0.3163.100 8.9.3 V8: 6.1.534.41 OS: Windows_NT x64 10.0.
Can you guide me on resolving this issue?
sure, checkout , and
Change:
items.splice(0, 0, item); } <ins> if (showUncommitted) { const working = repo.workingTreeGroup.resourceStates.find(r => r.resourceUri.fsPath === uri.fsPath); if (working) { const date = new Date(); const item = new GitTimelineItem('', index ? '~' : 'HEAD', localize('git.timeline.uncommitedChanges', 'Uncommitted Changes'), date.getTime(), 'working', 'git:file:working'); // TODO@eamodio: Replace with a better icon -- reflecting its status maybe? item.iconPath = new ThemeIcon('git-commit'); item.description = ''; item.setItemDetails(you, undefined, dateFormatter.format(date), Resource.getStatusText(working.type)); const cmd = this.commands.resolveTimelineOpenDiffCommand(item, uri); if (cmd) { item.command = { title: openComparison, command: cmd.command, arguments: cmd.arguments, }; } items.splice(0, 0, item); } } </ins> } return {

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. --A feature called Local History has been to show entries such as "File Saved" and "Undo/Redo" in the timeline of a file. Simultaneously, an item called "Uncommitted changes" has been removed apparently in I found the "Uncommitted changes" item very useful to quickly see the changes of a file since the last version. Current implementation with the local history feels unconvenient and does not reveal the same information as the previous Uncommited changes item did. It also compares the file with the current version on the disk and not the changes between the two versions (version in previous commit vs. saved version). So I would like to have a possibility to configure the timeline so that the previous behaviour showing the Uncommitted changes is restored.
cc I think it is reasonable to bring back the uncommitted changes when local history is disabled.
I second this!
Opened PR to have a setting for this. I do not think making this conditional on which timeline provider is showing is clever.
A new setting allows to enable this starting in tomorrows insider build.
Wow! That's great, thanks
/verified
Change:
if (this._isVisible) { const notificationsList = assertIsDefined(this.notificationsList); <del> // Make visible and focus first notificationsList.show(true /* focus */); </del> <ins> // Make visible notificationsList.show(); // Focus first </ins> notificationsList.focusFirst(); return; // already visible

Discussion:
Testing Repro: screen reader mode the editor the show notification command, :bug: the editor is still focused the show notification command, the notification center is now focused?
My notification was read once fully, then the screen reader started reading it a second time. Part way through that second time, the notification no longer seemed selected (didn't have a blue box around it), and the screen reader just stopped reading it.
the looks correct here, but I can repro the focus getting stuck in the editor any thoughts would be appreciated
Change:
# Sanitize the command line to ensure it can get transferred to the terminal and can be parsed # correctly. This isn't entirely safe but good for most cases, it's important for the Pt parameter # to only be composed of _printable_ characters as per the spec. <del> $CommandLine = $LastHistoryEntry.CommandLine ?? "" </del> <ins> if ($LastHistoryEntry.CommandLine) { $CommandLine = $LastHistoryEntry.CommandLine } else { $CommandLine = "" } </ins> $Result += $CommandLine.Replace("`n", "<LF>").Replace(";", "<CL>") $Result += "`a" # Command finished exit code

Discussion:
Type: <bBug</bJust tried to install the shell integration, however when i add: to my PowerShell Profile it spits out an error everytime i open vscode. My shell profile is completely standard apart from the vscode shell integration snippet. Error looks like this: VS Code version: Code 1.70.0 (, 2022-08-04T04:38:16.462Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (31)</summaryExtensionVersion ------ better-comments3.0.2 cypress-snippets1.2.0 vscode-tailwindcss0.8.6 path-intellisense2.8.1 gitlens12.1.2 vscode-html-css1.13.1 prettier-vscode9.5.0 auto-rename-tag0.1.10 copilot1.38.6394 copilot-labs0.2.221 discord-vscode5.8.0 fix-relative-imports-to-baseurl1.1.9 dotenv1.0.1 inline-fold0.1.6 vscode-docker1.22.1 vscode-kubernetes-tools1.3.10 remote-containers0.241.3 remote-ssh0.84.0 remote-ssh-edit0.80.0 remote-wsl0.66.3 vscode-remote-extensionpack0.21.0 material-icon-theme4.19.0 vscode-thunder-client1.17.1 vscode-rapidapi-client1.3.0 vscode-yaml1.9.1 LiveServer5.7.5 gitmoji-vscode1.1.2 php-formatter0.2.4 vscode-status-bar-format-toggle3.1.1 sort-lines1.9.1 errorlens3.6.0 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Looks like the null coalescing operator is pwsh 7+ only, I'd recommend upgrading pwsh if possible which should fix the issue in the meantime.
Change:
const appendFileQueue = new Queue(); <del> const decoder = iconv.getDecoder(encoding); </del> <ins> const decoder = iconv.default.getDecoder(encoding); </ins> process.stdin.on('data', chunk => { const chunkStr = decoder.write(chunk);

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: OS Version: and Steps to Reproduce: reports the following error and fails to read from stdin. I have located the root cause:
Great catch!
The fix should be in, could you verify after having pulled in the latest insiders update?
Yes, it works on the latest insiders with commit . Thank you :heart:.
Change:
import { IdleValue } from 'vs/base/common/async'; import { IConfigurationService } from 'vs/platform/configuration/common/configuration'; import { IConfigurationRegistry, Extensions as ConfigurationExtensions } from 'vs/platform/configuration/common/configurationRegistry'; <del> import { marked } from 'vs/base/common/marked/marked'; </del> import { renderMarkdownAsPlaintext } from 'vs/base/browser/markdownRenderer'; import { INotebookExecutionStateService } from 'vs/workbench/contrib/notebook/common/notebookExecutionStateService'; import { executingStateIcon } from 'vs/workbench/contrib/notebook/browser/notebookIcons'; import { URI } from 'vs/base/common/uri'; <ins> import { getMarkdownHeadersInCell } from 'vs/workbench/contrib/notebook/browser/viewModel/foldingModel'; </ins> export interface IOutlineMarkerInfo { readonly count: number;

Discussion:
[X] Notebooks (.ipynb files) [ ] Interactive Window and/or Cell Scripts (.py files with #%% markers) I expected that folding cells per a markdown header level would collapse all of the markdown and code cells under that header, per the VS Code Outline view of the notebook. In practice though, if there is a markdown cell with a python code block, then the comments in that python code block are considered the next top-level markdown section which interrupts the code folding. a new file and set the interpreter markdown cell with content: markdown cell: code cell: markdown cell: python print('hello world') the cell that cells 2 and 3 are collapsed and hidden, but cell 4 is not Add additional 's to the embedded python comment so that its not at the same level of the makrdown section it is under; e.g., python print('hello world') 70.0 v2022.7. Python 3.8.13 v2022.12.0 conda 4.13.0 Local
still seeing this issue- lmk if my setup is wrong. thanks! <img width="1322" alt="Screenshot 2023-01-25 at 1 11 16 PM" src="https://user-"<img width="1314" alt="Screenshot 2023-01-25 at 1 11 11 PM" src="https://user-"
Can you try finishing editing the cells to put them into render mode: ! I don't think we update the folding until the cell is no longer being edited
was verifying another issue and this works now!
Change:
// Only Desktop has the concept of installing language packs so we only do this for Desktop // and only if the language pack is not installed if (!installedLanguages.some(installedLanguage => installedLanguage.id === languagePackItem.id)) { <del> // Show the view so the user can see the language pack to be installed let viewlet = await this.paneCompositePartService.openPaneComposite(EXTENSIONS_VIEWLET_ID, ViewContainerLocation.Sidebar); (viewlet?.getViewPaneContainer() as IExtensionsViewPaneContainer).search(`@id:${languagePackItem.extensionId}`); </del> // Only actually install a language pack from Microsoft if (languagePackItem.galleryExtension?.publisher.toLowerCase() !== 'ms-ceintl') { <ins> // Show the view so the user can see the language pack that they should install // as of now, there are no 3rd party language packs available on the Marketplace. let viewlet = await this.paneCompositePartService.openPaneComposite(EXTENSIONS_VIEWLET_ID, ViewContainerLocation.Sidebar); (viewlet?.getViewPaneContainer() as IExtensionsViewPaneContainer).search(`@id:${languagePackItem.extensionId}`); </ins> return false; } <del> await this.extensionManagementService.installFromGallery(languagePackItem.galleryExtension); </del> <ins> await this.progressService.withProgress( { location: ProgressLocation.Notification, title: localize('installing', "Installing {0} language support...", languagePackItem.label), }, progress => this.extensionManagementService.installFromGallery(languagePackItem.galleryExtension!, { // Setting this to false is how you get the extension to be synced with Settings Sync (if enabled). isMachineScoped: false, }) ); </ins> } await this.writeLocaleValue(locale);

Discussion:
Testing Things I would change: make it clear in the picker that selecting a language from the lower list will install it have a button in the picker that installs and syncs it. don't reveal the extension viewlet don't show that dialog <img width="444" alt="capture" src="https://user-"
is there a way to not show this dialog when installing an extension using the Extension management service? Here's the specific line:
How would you make this clearer? I figured since we had a section called that will always be there on Desktop it's implied that must not be installed. What will the default behavior be then when you accept a quick pick item? That it will install but not sync? That's not what the default is for the button in the extension pane so that seems a bit odd to me. This was to give a progress indication. We do the same thing for the Theme picker. I would like to hide this dialog. I didn't see it locally because Settings Sync isn't available in but I asked Sandeep above.
Yes, you can pass machine scoped flag to avoid this. Passing for this flag will not sync the extension and will sync it.
I thought the main reason for the dialog was to inform the user that something is installed. I can easily live with only the picker Since the dialog offered the option, I thought it is important. I can live with the default without a choice. I found it disturbing. I could live without progress or some window progress.
Change:
title: { value: LOCALIZED_START_INLINE_CHAT_STRING, original: 'Start Inline Chat' }, category: AbstractInlineChatAction.category, f1: true, <del> precondition: CTX_INLINE_CHAT_HAS_PROVIDER, </del> <ins> precondition: ContextKeyExpr.and(CTX_INLINE_CHAT_HAS_PROVIDER, EditorContextKeys.writable), </ins> keybinding: { when: EditorContextKeys.focus, weight: KeybindingWeight.WorkbenchContrib,

Discussion:
open the log in the output view press Ctrl + I. :bug: Inline chat opens in the output view. It's not possible to enter a question. Should not open in the output view.
Tried this and it now does nothing when I press ctrl + I. This is the expected behavior now right?
Change:
import { KeyCode, KeyMod } from 'vs/base/common/keyCodes'; import { Disposable, DisposableStore } from 'vs/base/common/lifecycle'; import { localize } from 'vs/nls'; <del> import { CONTEXT_ACCESSIBILITY_MODE_ENABLED, IAccessibilityService } from 'vs/platform/accessibility/common/accessibility'; </del> <ins> import { CONTEXT_ACCESSIBILITY_MODE_ENABLED } from 'vs/platform/accessibility/common/accessibility'; </ins> import { IConfigurationService } from 'vs/platform/configuration/common/configuration'; import { ContextKeyExpr } from 'vs/platform/contextkey/common/contextkey'; import { IInstantiationService } from 'vs/platform/instantiation/common/instantiation';

Discussion:
Changing this behavior could be jarring, so instead, we will set it to by default and include a hint about this in the terminal accessibility help dialog.
To verify, enable screen reader mode, run the command . The terminal shouldn't be focused and the accessible buffer shouldn't be opened. Change the setting and repeat and verify that it works per the setting descriptions.
So that is u - who spoiled the terminal focus in user-input scenarios. Would be awesome if auto-focus worked only on pending user input to the terminal, so everybody would be happy. But I have no clue if such a functionality is even possible.
not sure what you mean, but you can set it to to have the terminal focused automatically !
Yes, thank you, I know. I mean next cases at the same time: only prints to the console - no focus to the waits for user input - terminal receives auto-focus
Change:
} } <ins> public async focusTabsView(): Promise<void> { await this.showPanel(true); const pane = this._viewsService.getActiveViewWithId<TerminalViewPane>(TERMINAL_VIEW_ID); pane?.terminalTabbedView?.focusTabsView(); } </ins> private _getIndexFromId(terminalId: number): number { let terminalIndex = -1; this.terminalInstances.forEach((terminalInstance, i) => {

Discussion:
This would be useful since we can now navigate the tabs via the keyboard, so you could hit <keybinding, up n times, enter to focus that terminal.
Also it's a little tough to tell which split pane is actually focused right now, perhaps some extra visual hint?
Opening to double check what the ideal keybinding would be on each platform
Let's go with ctrl/cmd+shift+ for this, to align with 's navigate tabs keybinding.
Change:
return out; } <ins> function extractDocumentLink( document: vscode.TextDocument, base: string, pre: number, link: string, matchIndex: number | undefined ): vscode.DocumentLink | undefined { const offset = (matchIndex || 0) + pre; const linkStart = document.positionAt(offset); const linkEnd = document.positionAt(offset + link.length); try { return new vscode.DocumentLink( new vscode.Range(linkStart, linkEnd), normalizeLink(document, link, base)); } catch (e) { return undefined; } } </ins> export default class LinkProvider implements vscode.DocumentLinkProvider { <del> private readonly linkPattern = /([[^]]*](s*)((([^s()]|(S*?))+))s*(".*?")?)/g; </del> <ins> private readonly linkPattern = /([((![[^]]*?](s*)([^s()]+?)s*)]|[^]]*])(s*)(([^s()]|(S*?))+)s*(".*?")?)/g; </ins> private readonly referenceLinkPattern = /([([^]]+)][s*?)([^s]]*?)]/g; private readonly definitionPattern = /^([t ]*[([^]]+)]:s*)(S+)/gm;

Discussion:
Steps to Reproduce: the markdown: Bug Only is detected as a clickable link.
Hey can I try working on this one?
Sure, here's the relevant regular expression that matches links: And the related tests: You can run the tests by opening VS Code and selecting the from the debug target menu. The regexp is rather complex so let me know if you have any questions
Could you please tell me what is the expected behaviour?
In the example, it should underline and as clickable links that open files and