jiebi/CodeConvo huggingface dataset:
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 Does this issue occur when all extensions are disabled?: Yes/No VS Code Version: 1.77.1 OS Version: Ubuntu 22.10 Steps to Reproduce: !
The bot never kicked in, can you check that it is fixed in the latest Insiders build of VS Code?
I can confirm, it is fixed!

Discussion:
error.message = data.message; error.stack = data.stack; this._internalExtensionService._onExtensionRuntimeError(extensionId, error); <del> console.error(`[${extensionId}]${error.message}`); </del> <ins> console.error(`[${extensionId.value}]${error.message}`); </ins> console.error(error.stack); } async $onExtensionActivationError(extensionId: ExtensionIdentifier, data: SerializedError, missingExtensionDependency: MissingExtensionDependency | null): Promise<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 <!-- 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.78.0-insider (system setup) OS Version: Windows 10 This only happen to the latest version of insider (1.78), the current vscode is still working Steps to Reproduce: a keyword open in editor shown in editor but now unable to ctrl click "Follow link" to go to the file or the line of code
is this a regression in link detection? I also notice that I can't ctrl+click on imports in the newest insiders.
double clicking to go to the file also stopped working
I ran and it points to this commit range:
points to I think the no longer activates when opening the search editor because the extension doesn't contribute a language configuration. Do you have any suggestions about what to do here. When I try to add the activation event back to the , I get a squiggle that it isn't necessary and that I should remove it. <img width="346" alt="image" src="https://user-"
I do not see this in the latest insiders, do you still repro? I updated the extension linter to not emit a warning in (the same commit which changes the implicit activation behavior): <img width="403" alt="image" src="https://user-"
Is there any fix for this available? I rely heavily on being able to press to jump to definitions in Search Editor. Don't want to downgrade from insiders but seems I am forced to.

Discussion:
], "main": "./out/extension.js", "browser": "./dist/extension.js", <del> "activationEvents": [], </del> <ins> "activationEvents": [ "onLanguage:search-result" ], </ins> "scripts": { "generate-grammar": "node ./syntaxes/generateTMLanguage.js", "vscode:prepublish": "node ../../node_modules/gulp/bin/gulp.js --gulpfile ../../build/gulpfile.extensions.js compile-extension:search-result ./tsconfig.json"
Change:
Type: <bBug</bSteps to reproduce: the comment-sample demo extension adding a comment by invoking ("Add Comment on Current Selection") from Command Palette (or programmatically, it behaves the same) Expected behavior: a new comment thread is created and a new comment can be edited; Actual behavior: Error is thrown: "Cannot read properties of undefined (reading 'range')"; As far as I know, this used to work 2-3 weeks ago in the Insiders builds. ! VS Code version: Code - Insiders 1.78.0-insider (, 2023-04-07T05:20:50.322Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes Remote OS version: Linux x64 4.18.0-372.19.1.el86.x8664 Remote OS version: Linux x64 4.18.0-372.19.1.el86.x8664 Remote OS version: Linux x64 4.18.0-372.19.1.el86.x8664 Remote OS version: Linux x64 4.18.0-372.19.1.el86.x8664 <details<summarySystem Info</summary </details<details<summaryExtensions (1)</summaryExtensionVersion ------ remote-ssh0.98.0 </details<!-- generated by issue reporter --

Discussion:
const ADD_COMMENT_COMMAND = 'workbench.action.addComment'; CommandsRegistry.registerCommand({ id: ADD_COMMENT_COMMAND, <del> handler: (accessor, args: { range: IRange; fileComment: boolean }) => { </del> <ins> handler: (accessor, args?: { range: IRange; fileComment: boolean }) => { </ins> const activeEditor = getActiveEditor(accessor); if (!activeEditor) { return Promise.resolve();

return Promise.resolve(); } <del> const position = args.range ? new Range(args.range.startLineNumber, args.range.startLineNumber, args.range.endLineNumber, args.range.endColumn) : (args.fileComment ? undefined : activeEditor.getSelection()); </del> <ins> const position = args?.range ? new Range(args.range.startLineNumber, args.range.startLineNumber, args.range.endLineNumber, args.range.endColumn) : (args?.fileComment ? undefined : activeEditor.getSelection()); </ins> return controller.addOrToggleCommentAtLine(position, undefined); } });
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 <!-- 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.77.1 OS Version: Pop OS 22.04 Steps to Reproduce: : New Jupyter Notebook from command panel integrated terminal panel with keyboard shortcut or by clicking the "maximize panel size" button in the integrated terminal. This is an issue only since 1.77.0. The issue is not seen in 1.76.2 Expected: Integrated terminal covers the notebook entirely. ! Actual: The jupyter notebook top bar overlaps with the integrated terminal. !
Seeing the same bug with which is just another implementation of the Notebook APIs.
It looks like a fix didn't make it into the latest recovery release. Anything planned to fix it, please Thanks!
A PR with a fix was raised in
meybe , but the insiders version seems normal.. !
It is reproducible to me in Insiders. !
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. I am verifying.
Reproduced, it should have been caused by something else just now.
yes, I first was assuming a PR of yours was causing it as reverting the change kind of fixed the bug however further investigations have shown that was the culprit and the provided PR proposes a fix for it.
Reopening as the fix was causing
Digging into this a bit, it seems when we maximize the panel, the grid view will layout the editor with height around , thus we still render the notebook editor. Since the notebook editor is rendered out of the grid view (just like webview editor), its zindex will cause this bug.
! Wow, the notebook is on such an outer layer, and now I only found these.
Related on Stack Overflow:
Potentially fixed by
Is this still happening? I 'm not able to reproduce, but I might not have the right repo steps
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!

Discussion:
this._overlayContainer.style.position = 'absolute'; this._overlayContainer.style.overflow = 'hidden'; <del> this.layoutContainerOverShadowElement(dimension, position); </del> <ins> if (this._isVisible) { this.layoutContainerOverShadowElement(dimension, position); } </ins> if (this._webviewTransparentCover) { this._webviewTransparentCover.style.height = `${dimension.height}px`;
Change:
VS Code Shell Integration vulnerability when re-running a command Escape sequences implemented by VS Code to support shell integration allow for a previously run command line to be replaced.

Discussion:
import { ILifecycleService } from 'vs/workbench/services/lifecycle/common/lifecycle'; import { IDecoration, ITerminalAddon, Terminal } from 'xterm'; import { AudioCue, IAudioCueService } from 'vs/platform/audioCues/browser/audioCueService'; <ins> import { INotificationService, Severity } from 'vs/platform/notification/common/notification'; </ins> interface IDisposableDecoration { decoration: IDecoration; disposables: IDisposable[]; exitCode?: number; markProperties?: IMarkProperties }

@ILifecycleService lifecycleService: ILifecycleService, @ICommandService private readonly _commandService: ICommandService, @IInstantiationService instantiationService: IInstantiationService, <del> @IAudioCueService private readonly _audioCueService: IAudioCueService </del> <ins> @IAudioCueService private readonly _audioCueService: IAudioCueService, @INotificationService private readonly _notificationService: INotificationService </ins> ) { super(); this._register(toDisposable(() => this._dispose()));

const labelRun = localize("terminal.rerunCommand", 'Rerun Command'); actions.push({ class: undefined, tooltip: labelRun, id: 'terminal.rerunCommand', label: labelRun, enabled: true, <del> run: () => this._onDidRequestRunCommand.fire({ command }) </del> <ins> run: async () => { this._notificationService.prompt(Severity.Info, localize('rerun', 'Do you want to run the command: {0}', command.command), [{ label: localize('yes', 'Yes'), run: () => this._onDidRequestRunCommand.fire({ command }) }, { label: localize('no', 'No'), run: () => { } }]); } </ins> }); const labelCopy = localize("terminal.copyCommand", 'Copy Command'); actions.push({
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 <!-- 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.77.2 OS Version: macOS 13.0 Steps to Reproduce: up a Github CodeSpaces in browser. a trivial extension that uses the api and logs the event out in its callback. the extension and focus on the new tab (Extension Development Host tab). outside the browser window, but the callback is not triggered. I notice that it will only be triggered if I am switching tabs, but I think it should also react when the browser loses focus.
Here's relevant info to fix this:
Actually the vscode api already implements a focus/blur event handling for this reason.

Discussion:
this._register(addDisposableListener(element, EventType.FOCUS, onFocus, true)); this._register(addDisposableListener(element, EventType.BLUR, onBlur, true)); <del> this._register(addDisposableListener(element, EventType.FOCUS_IN, () => this._refreshStateHandler())); this._register(addDisposableListener(element, EventType.FOCUS_OUT, () => this._refreshStateHandler())); </del> <ins> if (element instanceof HTMLElement) { this._register(addDisposableListener(element, EventType.FOCUS_IN, () => this._refreshStateHandler())); this._register(addDisposableListener(element, EventType.FOCUS_OUT, () => this._refreshStateHandler())); } </ins> } refreshState() {
Change:
This works on web e.g. but does not work in desktop, either with a desktop git clone or with RemoteHub. The last time this happened it was due to a regression in the list of enabled codecs for our Electron builds.
Sorry for the breakage, the changes from has not been to Electron = 22 versions yet. It will be addressed in new builds this week.
Addressed in
Reopening because of

Discussion:
}); } exports.config = { <del> version: product.electronRepository ? '22.4.5' : util.getElectronVersion(), </del> <ins> version: product.electronRepository ? '22.4.7' : util.getElectronVersion(), </ins> productAppName: product.nameLong, companyName: 'Microsoft Corporation', copyright: 'Copyright (C) 2023 Microsoft. All rights reserved',

}; } async function main(arch = process.arch) { <del> const version = product.electronRepository ? '22.4.5' : util.getElectronVersion(); </del> <ins> const version = product.electronRepository ? '22.4.7' : util.getElectronVersion(); </ins> const electronPath = path.join(root, '.build', 'electron'); const versionFile = path.join(electronPath, 'version'); const isUpToDate = fs.existsSync(versionFile) && fs.readFileSync(versionFile, 'utf8') === `${version}`;

} export const config = { <del> version: product.electronRepository ? '22.4.5' : util.getElectronVersion(), </del> <ins> version: product.electronRepository ? '22.4.7' : util.getElectronVersion(), </ins> productAppName: product.nameLong, companyName: 'Microsoft Corporation', copyright: 'Copyright (C) 2023 Microsoft. All rights reserved',

} async function main(arch = process.arch): Promise<void> { <del> const version = product.electronRepository ? '22.4.5' : util.getElectronVersion(); </del> <ins> const version = product.electronRepository ? '22.4.7' : util.getElectronVersion(); </ins> const electronPath = path.join(root, '.build', 'electron'); const versionFile = path.join(electronPath, 'version'); const isUpToDate = fs.existsSync(versionFile) && fs.readFileSync(versionFile, 'utf8') === `${version}`;
Change:
or VS Code Desktop 1) Enable sticky scroll 1) Type 1) Errors should spawn (with delay / debounce) in console Throws aync cancel error No response It IS_ reproducible in also! But I had to check it to be able to submit this form
Hi Anders, I am still having this issue. Lots of errors are generated each time I type something with stickyScroll on. Does closing this issue mean that it has been solved?
you are right! it's still yields a lot of errors - I was too fast when I saw the new version and updated vscode ref.
, are you sure this bug shouldn't be filed at ?
I did - it was moved here by hediet the 13. of April (see "log" on this page).. it seems like it was fixed in vscode and made it to the site - and the monaco vscode ref was update after - but I spose the ref was for an "earlier" version :/
any status on this cool feature? It has been a couple of monaco releases now with out a fix and it seems to have been fixed elsewhere
this is still an issue in version 0.41.0
Hi Is it possible to publish a small fix with a try catch surrounding the ()? Debugging code in combination with this monaco feature is becoming very hard to do because it floods the debugger with a lot of duplicate errors.. If not, we will wait patiently, you will get a lot of kudos for your good work anyhow ;-) !
can you look into this? I think it should be easy to fix.
Will do so now

Discussion:
} } return null; <ins> }).catch((error) => { onUnexpectedError(error); return null; </ins> }); } }
Change:
Code-OSS dev tools :bug: see (note that I see this even if I do not have the start entry enabled in settings) IMHO this contribution does not need to appear in , because it appears in the Welcome page, which only kicks in on . I would suggest to also instantiate RemoteStartEntry in .
Like the idea
This is a good find , can we get this out for April? We should put startup perf improvements always in as soon as possible.
ping
Thanks!

Discussion:
workbenchContributionsRegistry.registerWorkbenchContribution(PortRestore, LifecyclePhase.Eventually); workbenchContributionsRegistry.registerWorkbenchContribution(AutomaticPortForwarding, LifecyclePhase.Eventually); workbenchContributionsRegistry.registerWorkbenchContribution(RemoteMarkers, LifecyclePhase.Eventually); <del> workbenchContributionsRegistry.registerWorkbenchContribution(RemoteStartEntry, LifecyclePhase.Starting); </del> <ins> workbenchContributionsRegistry.registerWorkbenchContribution(RemoteStartEntry, LifecyclePhase.Restored); </ins>
Change:
Type: <bBug</bnew file file to some location, say, breadcrumb for the same file that you just saved, still open in the editor. The location you saved the file to won't appear, instead, the file appears in VS Code version: Code 1.77.3 (, 2023-04-12T09:16:52.732Z) OS version: Linux x64 5.14.0-1059-oem snap Modes: Sandboxed: No <details<summarySystem Info</summary </detailsExtensions disabled<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
may be related.
<!-- 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 can't reproduce the original issue in 1.77, so can you tell us whether it's fixed for you in Insiders?
you would need to use Ubuntu <= 21.04 VM for repro'ing the bug on v1.77
I was using Ubuntu 18.04 but also xfce, if it matters
/verified
Reported on StackOverflow:

Discussion:
@@NAME@@: command: electron-launch $SNAP/usr/share/@@NAME@@/bin/@@NAME@@ --no-sandbox common-id: @@NAME@@.desktop <del> environment: GTK_USE_PORTAL: 1 </del> url-handler: command: electron-launch $SNAP/usr/share/@@NAME@@/bin/@@NAME@@ --open-url --no-sandbox <del> environment: GTK_USE_PORTAL: 1 </del>
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 <!-- 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.77.3 arm64 OS Version: macOS 13.3.1 Steps to Reproduce: user preference, set an empty workbench (or a new window), or a folder without readme. Expected: it should fallback to "welcomePage" and open the welcome page. Actual: no startup editor opened.
Either the description of the option is wrong or the above code needs an block to run when no readmes were found.

Discussion:
}), this.editorService.openEditors(readmes.filter(readme => !isMarkDown(readme)).map(readme => ({ resource: readme }))), ]); <ins> } else { // If no readme is found, default to showing the welcome page. await this.openGettingStarted(); </ins> } } }
Change:
Does this issue occur when all extensions are disabled?: Yes Search rearranges the items according to how well they match, so items are no longer in the original groups. Because of that we remove the separators. (See, e.g., the theme picker.) Initial state: <img width="622" alt="image" src="https://user-"When typing: <img width="651" alt="image" src="https://user-"Steps to Reproduce: items and separators in the quickPick (grouping). to search VS Code Version: Version: 1.77.3 (Universal) Commit: Date: 2023-04-12T09:19:37.325Z Electron: 19.1.11 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin arm64 22.4.0 Sandboxed: Yes
Hi which extension is providing this quickpick?
Hello ! This is my debugger for .NET apps QuickPick implementation:
Any updates?
I can repro this. I'll get this fixed ASAP but as a workaround you could listen to the event that fires when the user updates the filter value and then clear out the separators from
Thank you,
I have a fix for this. It won't make it for this release on Wednesday, but it'll be in the following release (late May/early June)
<!-- 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!
Verified in the task list. !
/verified

Discussion:
element.hidden = element.item ? !element.item.alwaysShow : true; } <ins> // Ensure separators are filtered out first before deciding if we need to bring them back if (element.item) { element.separator = undefined; } else if (element.separator) { element.hidden = true; } </ins> // we can show the separator unless the list gets sorted by match if (!this.sortByLabel) { const previous = element.index && this.inputElements[element.index - 1];
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. --<!-- 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. --On (), folding icon is invisible in the gutter, but clicking it works: https://user- Version: 1.78.0-insider Commit: Date: 2023-04-17T05:16:14.521Z Browser: Chrome/112.0.0.0 Safari/537.36
I am also seeing this in desktop Insiders today: Version: 1.78.0-insider Commit: Date: 2023-04-17T05:26:43.771Z Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.78.0-insider Chrome/108.0.5359.215 Electron/22.4.5 Safari/537.36 Maybe related to
Caused by

Discussion:
const classNames = toRender[lineIndex]; let lineOutput = ''; for (let i = 0, len = classNames.length; i < len; i++) { <del> lineOutput += '<div class="cldr ' + classNames[i] + common; </del> <ins> lineOutput += '<div class="cldr ' + classNames[i][0] + common; </ins> } output[lineIndex] = lineOutput; }

const classNames = toRender[lineIndex]; let lineOutput = ''; for (let i = 0, len = classNames.length; i < len; i++) { <del> lineOutput += '<div class="cmdr ' + classNames[i] + '" style=""></div>'; </del> <ins> lineOutput += '<div class="cmdr ' + classNames[i][0] + '" style=""></div>'; </ins> } output[lineIndex] = lineOutput; }