jiebi/CodeConvo huggingface dataset:
Change:
Does this issue occur when all extensions are disabled?: 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: 1.74.2 OS Version: Arch with Linux v6.1.3 Steps to Reproduce: VS Code in portable mode (VSCODEPORTABLE env var set to a directory) a file in the instance by typing in the integrated terminal. Code opens a new window rather than opening the file as a tab, and the new window reads userdata from instead of "$VSCODEPORTABLE". Possible solution: I investigated and noticed that the integrated terminal in VS Code reads the env var as unset even if it is set by the OS. As a workaround, I have this to my config, and it works:
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.3. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Happens on the latest version as well: !
Oh if we just need set for this to work I can remove that from the env sanitization.
<!-- 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!

Discussion:
}, {} as Record<string, boolean>); const keysToRemove = [ /^ELECTRON_.+$/, <del> /^VSCODE_(?!SHELL_LOGIN).+$/, </del> <ins> /^VSCODE_(?!(PORTABLE|SHELL_LOGIN)).+$/, </ins> /^SNAP(|_.*)$/, /^GDK_PIXBUF_.+$/, ];

VSCODE_DEV: 'x', VSCODE_IPC_HOOK: 'x', VSCODE_NLS_CONFIG: 'x', <del> VSCODE_PORTABLE: 'x', </del> <ins> VSCODE_PORTABLE: '3', </ins> VSCODE_PID: 'x', VSCODE_SHELL_LOGIN: '1', VSCODE_CODE_CACHE_PATH: 'x',

processes.sanitizeProcessEnvironment(env); assert.strictEqual(env['FOO'], 'bar'); assert.strictEqual(env['VSCODE_SHELL_LOGIN'], '1'); <del> assert.strictEqual(Object.keys(env).length, 2); </del> <ins> assert.strictEqual(env['VSCODE_PORTABLE'], '3'); assert.strictEqual(Object.keys(env).length, 3); </ins> }); });
Change:
CC and Version: 1.75.0-insider (system setup) Commit: Date: 2023-01-16T05:21:04.032Z Electron: 19.1.9 Chromium: 102.0.5005.194 16.14.2 V8: 10.2.154.23-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes VSCode-insiders with screen reader. any PR commit in diff editor. Alt+F5 to go to the next change in diff editor: You will hear audio cues. the changed line, press F7 to open the special diff pane where you can navigate what's been deleted and denoted with +/- signs. ESC to close the special diff pane once you have figured out the differences: The cursor location has changed. The original cursor line is not preserved in the diff editor. Notes: The original cursor location is preserved only when you explicitly press enter on the changed line in F7 diff pane. The original cursor position in the diff editor must be preserved after closing the F7 diff pane via ESC. I have already found the amazing usefullness of Alt+F5 and F7 interplays. Alt+F5 is very useful for a general overview of changes (+-) whereas F7 gives the detailed information on changes. It would be even nicer if we could have a smoother interplay between them like below: diff editor, press Alt+F5 to go to any next changes. F7 to open detailed changes in the special diff pane. soon as the F7 diff pane is open, the focus is landed on the specific change denoted with +/- signs: Currently the focus moves to the top of the F7 diff pane so that users need to arrow-down several times to find the specific changes.
This makes sense to me. The F7 special diff pane feels jumpy to me as it currently is.
any historical context here I'm missing?
<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!
I do not have much historical context here. But I think we should be flexible to change things here based on user feedback and what we think is better.
I'm not sure if it was fixed or not, here's what I see. The same with or without a screenreader enabled alt+F5, the cursor is at the top of a changed block F7 Escape, the cursor is now a couple lines above the changed block
This is working - notice the blue focus border around the line in the f7 view - that's where the cursor is and should be when I escape that view https://user-
This works well when I use the arrow keys after F7, but if I just do F7 and then then I see the same as Rob.
has this been fixed in v2?
I'm not so sure this is a bug. Afaik we intentionally synchronize the cursor position from the accessible diff viewer with the normal diff viewer.
This is working for me.

Discussion:
|| e.equals(KeyMod.CtrlCmd | KeyCode.Escape) || e.equals(KeyMod.Alt | KeyCode.Escape) || e.equals(KeyMod.Shift | KeyCode.Escape) <del> ) { e.preventDefault(); this.hide(); } if ( e.equals(KeyCode.Space) </del> <ins> || e.equals(KeyCode.Space) </ins> || e.equals(KeyCode.Enter) ) { e.preventDefault();
Change:
vscode project run open find widget and search for "RawSearchService" at one point there is a match "1 of 1" :bug: arrow keys stay disabled, arrow keys work https://user-
I can't reproduce. What theme is that and does inspecting the buttons show something off?
It's unrelated to the theme - I do see them enabled at times
I cannot reproduce either
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
I have given precise steps, did you follow them the exact way? https://user-
It's not researching on Windows <img width="1578" alt="image" src="https://user-"But I think the part I was missing was doing the search before the term exists, bug is likely not re-evaluating button state after a research triggered by buffer change
I still managed to get into this state after messing around with the find widget for a little while: ! Here's what seemed to repo it for me: a large folder, run for a common character like should see a find widget that shows arrows but doesn't have a find result count on the arrows in the find widget :bug: Now the arrows are disabled but still clickable
I also have if that's relevant
I can see this too, also it shows before disappearing if you do the search before running ls -lr
<img width="289" alt="image" src="https://user-"<img width="356" alt="image" src="https://user-"
This is happening because we behave a little differently when there are more than 1000 results: We can improve this but it's a separate problem, opened To verify this just verify the steps above, with either a specific term like "RawSearchService" or with a small scrollback value.
I can verify this works, however given the fact that was unable to repro at some point, its possible that I too am running into the same situtation Probably best if and/or also tested this. Either way, marking as verified

Discussion:
this._matchesCount = document.createElement('div'); this._matchesCount.className = 'matchesCount'; this._findInput.domNode.insertAdjacentElement('afterend', this._matchesCount); <del> this._register(this._findInput.onDidChange(() => { this.updateResultCount(); this.updateButtons(this._foundMatch); </del> <ins> this._register(this._findInput.onDidChange(async () => { await this.updateResultCount(); </ins> })); this._register(this._findInput.onDidOptionChange(async () => { this._foundMatch = this._onInputChanged(); await this.updateResultCount(); <del> this.updateButtons(this._foundMatch); </del> this.focusFindBox(); this._delayedUpdateHistory(); }));

async updateResultCount(): Promise<void> { if (!this._matchesCount) { <ins> this.updateButtons(this._foundMatch); </ins> return; }

alertFn(this._announceSearchResults(label, this.inputValue)); this._matchesCount.appendChild(document.createTextNode(label)); this._foundMatch = !!count && count.resultCount > 0; <ins> this.updateButtons(this._foundMatch); </ins> } changeState(state: INewFindReplaceState) {
Change:
I noticed this starting yesterday: <img width="343" alt="image" src="https://user-"Create PR one works fine though: <img width="425" alt="image" src="https://user-"
This is happening because it exits with success <img width="379" alt="image" src="https://user-"
Was caused by the Windows pwsh strict mode change FYI

Discussion:
} function Global:Prompt() { <ins> $FakeCode = [int]!$global:? </ins> # NOTE: We disable strict mode for the scope of this function because it unhelpfully throws an # error when $LastHistoryEntry is null, and is not otherwise useful. Set-StrictMode -Off <del> $FakeCode = [int]!$global:? </del> $LastHistoryEntry = Get-History -Count 1 # Skip finishing the command if the first command has not yet started if ($Global:__LastHistoryId -ne -1) {
Change:
on macOS ventura, using Angular 12. See screenshot. ! The line of code below is what causes the above error to be logged: But the text is grey, and there doesn't seem to be a way around this, which is a problem.
Seems like the class is not applied to stderr output with variablesReferences
I think there is an issue for this, I can't find it right now. Started working on it but needs a little refactor
Going to steal this since involves fixing that todo

Discussion:
const outputQueue = new Queue<void>(); this.rawListeners.push(this.raw.onDidOutput(async event => { <ins> const outputSeverity = event.body.category === 'stderr' ? Severity.Error : event.body.category === 'console' ? Severity.Warning : Severity.Info; </ins> // When a variables event is received, execute immediately to obtain the variables value #126967 if (event.body.variablesReference) { const source = event.body.source && event.body.line ? {

// For single logged variables, try to use the output if we can so // present a better (i.e. ANSI-aware) representation of the output if (resolved.length === 1) { <del> this.appendToRepl({ output: event.body.output, expression: resolved[0], sev: Severity.Info, source }, event.body.category === 'important'); </del> <ins> this.appendToRepl({ output: event.body.output, expression: resolved[0], sev: outputSeverity, source }, event.body.category === 'important'); </ins> return; } resolved.forEach((child) => { // Since we can not display multiple trees in a row, we are displaying these variables one after the other (ignoring their names) (<any>child).name = null; <del> this.appendToRepl({ output: '', expression: child, sev: Severity.Info, source }, event.body.category === 'important'); </del> <ins> this.appendToRepl({ output: '', expression: child, sev: outputSeverity, source }, event.body.category === 'important'); </ins> }); }); return;

return; } <del> const outputSeverity = event.body.category === 'stderr' ? Severity.Error : event.body.category === 'console' ? Severity.Warning : Severity.Info; </del> if (event.body.category === 'telemetry') { // only log telemetry events from debug adapter if the debug extension provided the telemetry key // and the user opted in telemetry
Change:
<img width="285" alt="image" src="https://user-"
strange as 1000 is a number <img width="1060" alt="Screenshot 2023-01-20 at 3 28 32 PM" src="https://user-"
value is here, not sure why <img width="1246" alt="Screenshot 2023-01-20 at 3 34 09 PM" src="https://user-"
Oh, changed the default value to 10 and it worked. I think 1000 is viewed as too high somewhere so it gets set to '' <img width="1052" alt="Screenshot 2023-01-20 at 3 39 55 PM" src="https://user-"
also tried because some other settings w high default values use that and it still didn't work
I some logging and it's because converts it to , and then the inputbox doesn't know how to handle the comma

Discussion:
import { Emitter, Event } from 'vs/base/common/event'; import { KeyCode } from 'vs/base/common/keyCodes'; import { Disposable, DisposableStore, dispose, isDisposable, toDisposable } from 'vs/base/common/lifecycle'; <del> import { isIOS, language } from 'vs/base/common/platform'; </del> <ins> import { isIOS } from 'vs/base/common/platform'; </ins> import { escapeRegExpCharacters } from 'vs/base/common/strings'; import { isDefined, isUndefinedOrNull } from 'vs/base/common/types'; import { localize } from 'vs/nls';

template.onChange = undefined; template.inputBox.value = typeof dataElement.value === 'number' ? <del> dataElement.value.toLocaleString(language) : ''; </del> <ins> dataElement.value.toString() : ''; </ins> template.inputBox.step = dataElement.valueType.includes('integer') ? '1' : 'any'; template.inputBox.setAriaLabel(dataElement.setting.key); template.onChange = value => {
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.75.0 Insiders OS Version: Win 10 Steps to Reproduce: Initially discovered in The VSCode Settings show select dropdowns having seemingly transparent background, so the options' texts are mixing with the document flow beneath the dropdown. It is probably a CSS regression in 1.75.0 Insiders because 1.74.3 doesn't exhibit this problem !
See already

Discussion:
private styleList() { const background = this.styles.selectBackground ?? ''; <del> const listBackground = this.styles.selectListBackground ? this.styles.selectListBackground : background; </del> <ins> const listBackground = dom.asCssValueWithDefault(this.styles.selectListBackground, background); </ins> this.selectDropDownListContainer.style.backgroundColor = listBackground; this.selectionDetailsPane.style.backgroundColor = listBackground; const optionsBorder = this.styles.focusBorder ? this.styles.focusBorder : '';
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: Visual Studio Code CLI 1.74.3 OS Version: Microsoft Windows [Version 10.0..963] (Windows/ARM64) Steps to Reproduce: through device code authentication to the device in VS Code's remote explorer the CLI side, observe: , seems not to be pointing to anything that can be found.
Note that everything works splendidly if replacing with in this URL. Then the server is found and the connection succeeds.

Discussion:
Platform::DarwinARM64 => "server-darwin-arm64", Platform::WindowsX64 => "server-win32-x64", Platform::WindowsX86 => "server-win32", <del> Platform::WindowsARM64 => "server-win32-arm64", </del> <ins> Platform::WindowsARM64 => "server-win32-x64", // we don't publish an arm64 server build yet </ins> } .to_owned() }
Change:
Opening a file (running out of sources): Activating extension '' failed: TelemetrySender.sendEventData must be a function.
This isn't fixed in the latest insiders build! I replaced my older .app file with the latest insiders and am now stuck with this error - it's happening for the Python extension, no less! Anyway I can download an older insiders build perhaps?
switching to the "Pre-Release Version" of Python ! solved the issue for me - did you try it?
Confirmed that is right -- switching to pre-release version did fix it for me as well. Thank you!
I don't see the Switch to Pre-Reease Option in here, must I activate something?
My fix to: Activating extension 'ms-' failed: TelemetrySender.sendEventData must be a function. was: pip install pyzmq --upgrade I was working with a remote connection. I also try unistalling everthing in the remote server, switch Jupyter and Python extension to PRE-RELEASE but only updating pyzmq package work. VSCODE version: 1.75.1 JUPYTER extension version: v2023.1. PYTHON extension version: v2023.2.0 Activating extension 'ms-' failed: TelemetrySender.sendEventData must be a function.

Discussion:
] }, "dependencies": { <del> "@vscode/extension-telemetry": "0.7.2-preview", </del> <ins> "@vscode/extension-telemetry": "^0.7.4-preview", </ins> "vscode-languageclient": "^8.1.0-next.2", "vscode-uri": "^3.0.6" },

] }, "dependencies": { <del> "@vscode/extension-telemetry": "0.7.2-preview", </del> <ins> "@vscode/extension-telemetry": "^0.7.4-preview", </ins> "request-light": "^0.6.0", "vscode-languageclient": "^8.1.0-next.2" },

dependencies: "@types/node" "*" <del> "@vscode/extension-telemetry@0.7.2-preview": version "0.7.2-preview" resolved "https://registry.yarnpkg.com/@vscode/extension-telemetry/-/extension-telemetry-0.7.2-preview.tgz#1db9c7117c3d82859e61d123786c8aebdf70f2fa" integrity sha512-X9/kIknUt+5xNZzmiunY0yqcpwwIAxUhb4hADjUtgSbkJjp+SjjxeFbLx7u0cWBJPweGxrrcWe3RUiu6s5hETw== </del> <ins> "@vscode/extension-telemetry@^0.7.4-preview": version "0.7.4-preview" resolved "https://registry.yarnpkg.com/@vscode/extension-telemetry/-/extension-telemetry-0.7.4-preview.tgz#318d6bc54064e5f443b25dfb42fec724d888c36b" integrity sha512-6OkvjCc+DaC9B26t3hj7vuAxf1ONm/p4LrVvFrapa+jBCKxXXUaV1Asz6+QxYaPfd4Ws/MlnFfCvlgvv3uYRwQ== </ins> dependencies: "@microsoft/1ds-core-js" "^3.2.8" "@microsoft/1ds-post-js" "^3.2.8"
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?: No (Extension Bisect does not identify a particular extension) <!-- 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.74.3 OS Version: Windows_NT x64 10.0. (Windows 10 22H2) Whenever I open a new window, I want to quickly open one of my recent folders by clicking an item in the Recent section of the welcome page. And so often, instead, I open a walkthrough by accident because walkthroughs are lazily loaded and cause the Recent section to move to the left. Typically, the walkthroughs take 3 seconds to load after the Recent section is shown. This is a small issue but still impedes my productivity/satisfaction with this awesome product. :-) ! Possible ideas for mitigation: change the layout so that Recent items are always shown on the left (avoid content jumping at all) maintain a cache of walkthrough items? provide a setting to disable the display of walkthroughs on the welcome page
Nice, thank you!

Discussion:
showOnStartupLabel, )); <ins> recentList.setLimit(5); </ins> const layoutLists = () => { if (gettingStartedList.itemCount) { this.container.classList.remove('noWalkthroughs'); reset(leftColumn, startList.getDomElement(), recentList.getDomElement()); reset(rightColumn, featuredExtensionList.getDomElement(), gettingStartedList.getDomElement()); <del> recentList.setLimit(5); </del> } else { this.container.classList.add('noWalkthroughs'); <del> reset(leftColumn, startList.getDomElement()); reset(rightColumn, recentList.getDomElement(), featuredExtensionList.getDomElement()); recentList.setLimit(10); </del> <ins> reset(leftColumn, startList.getDomElement(), recentList.getDomElement()); reset(rightColumn, featuredExtensionList.getDomElement()); </ins> } setTimeout(() => this.categoriesPageScrollbar?.scanDomNode(), 50); };

this.container.classList.remove('noExtensions'); reset(leftColumn, startList.getDomElement(), recentList.getDomElement()); reset(rightColumn, featuredExtensionList.getDomElement(), gettingStartedList.getDomElement()); <del> recentList.setLimit(5); </del> } else { this.container.classList.add('noExtensions'); reset(leftColumn, startList.getDomElement(), recentList.getDomElement()); reset(rightColumn, gettingStartedList.getDomElement()); <del> recentList.setLimit(10); </del> } setTimeout(() => this.categoriesPageScrollbar?.scanDomNode(), 50); };
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: Code space VS code OS Version: Codespaces Steps to Reproduce: is the file for initializing docker in codespace: space is not automatically port forwarding or I'm not able to manually add the port forwarding. 've tried with and without --host in
any help here? much appreciated!
since you have in your I would expect Codespaces to forward the port when you connect to the Codespace. For that, I would recommend you report an issue over in If you don't include the property then we should see that something is listening on 3000 and forward it. However, we don't forward ports that already have something listening on them at the time that VS Code connects to the Codespace. I think that your is happing a bit sooner than we expect and then we don't forward the port. Since you do have configured we should still forward the port. I'll make a fix for this. It should be in a VS Code insiders build by the end of the week.

Discussion:
continue; } <ins> if (!attributes) { attributes = await this.remoteExplorerService.tunnelModel.getAttributes(this.remoteExplorerService.tunnelModel.candidates); } const portAttributes = attributes?.get(value.port); </ins> const address = makeAddress(value.host, value.port); <del> if (this.initialCandidates.has(address)) { </del> <ins> if (this.initialCandidates.has(address) && (portAttributes?.onAutoForward === undefined)) { </ins> continue; } if (this.notifiedOnly.has(address) || this.autoForwarded.has(address)) {

continue; } <del> if (!attributes) { attributes = await this.remoteExplorerService.tunnelModel.getAttributes(this.remoteExplorerService.tunnelModel.candidates); } const portAttributes = attributes?.get(value.port); </del> if (portAttributes?.onAutoForward === OnPortForward.Ignore) { this.logService.trace(`ForwardedPorts: (ProcForwarding) Port ${value.port} is ignored`); continue;