jiebi/CodeConvo huggingface dataset:
Change:
Testing The description of 'git.branchRandomName.dictionary' could be improved to say that each value represents a segment.

Discussion:
"type": "array", "markdownDescription": "%config.branchRandomNameDictionary%", "items": { <del> "type": "string" </del> <ins> "type": "string", "enum": [ "adjectives", "animals", "colors", "numbers" ], "enumDescriptions": [ "%config.branchRandomNameDictionary.adjectives%", "%config.branchRandomNameDictionary.animals%", "%config.branchRandomNameDictionary.colors%", "%config.branchRandomNameDictionary.numbers%" ] </ins> }, "default": [ "adjectives",

"config.branchProtectionPrompt.alwaysCommit": "Always commit changes to the protected branch.", "config.branchProtectionPrompt.alwaysCommitToNewBranch": "Always commit changes to a new branch.", "config.branchProtectionPrompt.alwaysPrompt": "Always prompt before changes are committed to a protected branch.", <del> "config.branchRandomNameDictionary": "List of dictionaries used when the branch name that is randomly generated. Supported values: `adjectives`, `animals`, `colors`, `numbers`.", </del> <ins> "config.branchRandomNameDictionary": "List of dictionaries used for the randomly generated branch name. Each value represents the dictionary used to generate the segment of the branch name. Supported dictionaries: `adjectives`, `animals`, `colors` and `numbers`.", "config.branchRandomNameDictionary.adjectives": "A random adjective", "config.branchRandomNameDictionary.animals": "A random animal name", "config.branchRandomNameDictionary.colors": "A random color name", "config.branchRandomNameDictionary.numbers": "A random number between 100 and 999", </ins> "config.branchRandomNameEnable": "Controls whether a random name is generated when creating a new branch.", "config.branchValidationRegex": "A regular expression to validate new branch names.", "config.branchWhitespaceChar": "The character to replace whitespace in new branch names, and to separate segments of a randomly generated branch name.",
Change:
[ ] Notebooks (.ipynb files) [X] Interactive Window and/or Cell Scripts (.py files with #%% markers) During using folding and unfolding the text "cells hidden ..." is rendered inappropriate. The problems occur when many usages of folding are. There is an example: ! There is an example file: 67.2 v2022.4. No response No response No response No response Local
Thanks for filing this issue, we've run into similar issues in the past. The animated gif really helps here. thanks
Rendering collapsed cells is core code.
Have we? I don't remember seeing this before. But I can repro it

Discussion:
const foldHintTop = element.layoutInfo.previewHeight; this._container.style.top = `${foldHintTop}px`; <del> } else if (element.foldingState === CellFoldingState.Expanded) { </del> <ins> } else { </ins> DOM.hide(this._container); } }
Change:
Issue Type: <bBug</ba theme, or setting, that assigns to any opaque color (example below ). Actual result: <img width="365" alt="image" src="https://user-"Expected result: <img width="318" alt="image" src="https://user-"VS Code version: Code 1.67.2 (, 2022-05-17T18:20:57.384Z) OS version: Darwin x64 21.4.0 Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions disabled<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
This is coming in from //cc
I think the fix is not good, I saw a slow editor loading and the watermark was shining through. I think with your change now, there is a time when the new editor is not yet there but the watermark is on top. Typically the watermark should go away as soon as a new editor starts to load, please check.
Any ideas how I can reproduce a slow editor loading? Even open slower custom editors like the hex editor on my computer doesn't seem to cause any issues
! I typically add this in :
I've reverted the Z-index change due to the watermark still showing on slow editor loads will investigate next milestone. Appears that the letter press and command hints are on two separate style sheets entirely.
This is fixed with recent changes to the watermark rendering.

Discussion:
text-align: center; white-space: nowrap; overflow: hidden; <ins> /* Watermark should show even over opaque backgrounds */ z-index: 1000; </ins> } .monaco-workbench .part.editor > .content.empty > .watermark > .watermark-box {
Change:
This is the current definition of : Unfortunately, it loses the names of the parameters: ! However, if we change the definition to this: The parameter names are kept: ! I don't know how this affects type-checking performance though.
I think you should just submit this as a PR :)

Discussion:
* Given a list of arguments as a tuple, attempt to extract the leading, non-service arguments * to their own tuple. */ <del> export type GetLeadingNonServiceArgs<Args> = Args extends [...BrandedService[]] ? [] : Args extends [infer A, ...BrandedService[]] ? [A] : Args extends [infer A, ...infer R] ? [A, ...GetLeadingNonServiceArgs<R>] : never; </del> <ins> export type GetLeadingNonServiceArgs<TArgs extends any[]> = TArgs extends [] ? [] : TArgs extends [...infer TFirst, BrandedService] ? GetLeadingNonServiceArgs<TFirst> : TArgs; </ins> export interface IInstantiationService {
Change:
!
updated Insider's and the problem remains
I think this is the same as We will need to always send the exit code and have it get evaluated on the renderer against the extracted command name to fix these problems.
sometimes reproduces on mac
you can check if this is the same issue () by running a command a few times and then when is run if it's a single entry or multiple in the output.
interesting to me that it allows repro on linux/WSL and does so inconsistently on mac. here's linux: !
K, let's try understand this a little better then, that shouldn't happen as the initial history id is 0:
Oh I figured out when it reproes on mac - if you run the same command in a different terminal, then the second and beyond ones don't have an exit code
Running the command again in the terminal where you first ran the command works every time and does not repro on mac. So mac steps are: in terminal 1 - again in terminal 1 - in terminal 2 - Linux: a terminal and run any command - placeholder decoration shown for the first one regardless of exit code
It would be nice to fix this since is the default shell used
Think I see the problem, PR incoming.

Discussion:
builtin return fi <ins> __vsc_initialized="0" </ins> __vsc_in_command_execution="1" __vsc_last_history_id=0

__vsc_command_complete() { builtin local __vsc_history_id=$(builtin history | tail -n1 | awk '{print $1;}') <del> if [[ "$__vsc_history_id" == "$__vsc_last_history_id" ]]; then builtin printf "033]633;D007" else builtin printf "033]633;D;%s007" "$__vsc_status" __vsc_last_history_id=$__vsc_history_id </del> <ins> # Don't write the command complete sequence for the first prompt without an associated command if [[ "$__vsc_initialized" == "1" ]]; then if [[ "$__vsc_history_id" == "$__vsc_last_history_id" ]]; then builtin printf "033]633;D007" else builtin printf "033]633;D;%s007" "$__vsc_status" __vsc_last_history_id=$__vsc_history_id fi </ins> fi __vsc_update_cwd }

if [ -n "$RPROMPT" ]; then RPROMPT="$__vsc_prior_rprompt" fi <ins> __vsc_initialized="1" </ins> __vsc_in_command_execution="1" __vsc_command_output_start }
Change:
Issue Type: <bBug</bEditor: Insert Spaces and Editor: Detect Indentation on a new file, the indent mode is "Spaces: 4" some codes with tab as indentation language is automatically detected, but the indent mode is still "Spaces: 4" VS Code version: Code 1.67.2 (, 2022-05-17T18:15:52.058Z) OS version: Windows_NT x64 6.1.7601 Restricted Mode: No <details<summaryExtensions (3)</summaryExtensionVersion ------ vscode-css-formatter1.0.2 copilot1.25.6056 format-html-in-php1.7.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I'm having trouble reproducing: https://user-
I mean, the indent mode should be detected automatically on pasting to a blank file, at the same time as detecting language
The feature request here is that would also invoke (given the setting is set to true).
, opening up for help wanted if someone wants to contribute a PR for this.

Discussion:
} else { this.modelService.setMode(textModel, this.languageService.createById(candidateLanguage.id)); } <ins> const opts = this.modelService.getCreationOptions(textModel.getLanguageId(), textModel.uri, textModel.isForSimpleWidget); textModel.detectIndentation(opts.insertSpaces, opts.tabSize); </ins> } } }
Change:
a sample extension, add that and notice the environment wasn't set This also breaks the JS Debug Terminal and the node-terminal debug type. I hit this on zshell on OSX with shell integration turned on
Oh, this only happens when shell integration is turned on. Downgrading the "important" label
is missing from the slc when shell integration is enabled !
it's on the instead
Hi, I had a similar regression on our internal extension that open a terminal with preconfigured environement

Discussion:
this.shellLaunchConfig.args = defaultProfile.args; this.shellLaunchConfig.icon = defaultProfile.icon; this.shellLaunchConfig.color = defaultProfile.color; <del> this.shellLaunchConfig.env = defaultProfile.env; </del> } await this._createProcess();
Change:
The part of the button appears to be getting localized in the pseudo-language extension pack. !
Verified by code review.

Discussion:
return { command: { command: 'git.publish', <del> title: localize('scm button publish title', "$(cloud-upload) Publish Branch"), </del> <ins> title: localize('scm publish branch action button title', "{0} Publish Branch", '$(cloud-upload)'), </ins> tooltip: this.state.isActionRunning ? localize('scm button publish branch running', "Publishing Branch...") : localize('scm button publish branch', "Publish Branch"),

return { command: { command: rebaseWhenSync ? 'git.syncRebase' : 'git.sync', <del> title: localize('scm button sync title', "{0} {1}{2}", icon, behind, ahead), </del> <ins> title: `${icon} ${behind} ${ahead}`, </ins> tooltip: this.state.isActionRunning ? localize('syncing changes', "Synchronizing Changes...") : this.repository.syncTooltip,
Change:
Similar to add to get refresh tokens by default when using
verification steps: in an extension, ask for: run the extension and sign in when asked as a result of ^^^ Restart vscode Expected to not get asked for sign in again because was automatically.
I get this in my browser: The request is blocked. <long string of characters
I am also unable to complete the sign in flow in my browser.
I had a typo in my code snippet above so when you verify this again, please make sure you copy the code snippet fresh. I had instead of

Discussion:
if (!modifiedScopes.includes('profile')) { modifiedScopes.push('profile'); } <ins> if (!modifiedScopes.includes('offline_access')) { modifiedScopes.push('offline_access'); } </ins> modifiedScopes = modifiedScopes.sort(); let modifiedScopesStr = modifiedScopes.join(' ');
Change:
Similar to add to get refresh tokens by default when using
verification steps: in an extension, ask for: run the extension and sign in when asked as a result of ^^^ Restart vscode Expected to not get asked for sign in again because was automatically.
I get this in my browser: The request is blocked. <long string of characters
I am also unable to complete the sign in flow in my browser.
I had a typo in my code snippet above so when you verify this again, please make sure you copy the code snippet fresh. I had instead of

Discussion:
if (!scopes.includes('profile')) { scopes.push('profile'); } <ins> if (!scopes.includes('offline_access')) { scopes.push('offline_access'); } </ins> scopes = scopes.sort(); const scopeData: IScopeData = { scopes,
Change:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --Really not sure if this is a feature or a bug but it's been this way forever and it's not broken, so let's go with feature. Currently when you press f10 to step through code the pattern is something like this with a screen reader: What I actually care about is the code because I just pressed step. The rest of the message comes first and is almost always literally longer than the code. I'm not sure how hard this is to change but in my ideal world we'd get something more narrative--"stepped into " when the file changes, drop the redundant debugging paused, flip it around so it's like "a + b at line 12 ". There is probably something to be said more generally for considering "narrative" debugging but for this I really just care about being able to efficiently step through things, so honestly whatever is fine.
thanks a lot for this feedback this is very helpful. We can change what is getting read. So how about the following for your example: what do you think? Code pointer
Sounds fine to me!
yeah, that should be a lot better. Thanks.
To be clear I haven't tested, I'll make a point of doing that. Sorry for the double post.
no problem, you can try it out from tomorrow with VS Code insiders and let us know how it feels now. Thank you
I tested this with VoiceOver on OSX and it reads in the reordered way
Cool, I haven't had the time, I'm afraid. But if someone's checked it then I'm good with that.

Discussion:
const lineNumber = stackFrame.range.startLineNumber; if (lineNumber >= 1 && lineNumber <= model.getLineCount()) { const lineContent = control.getModel().getLineContent(lineNumber); <del> aria.alert(nls.localize({ key: 'debuggingPaused', comment: ['First placeholder is the stack frame name, second is the line number, third placeholder is the reason why debugging is stopped, for example "breakpoint" and the last one is the file line content.'] }, "{0}:{1}, debugging paused {2}, {3}", stackFrame.source ? stackFrame.source.name : '', stackFrame.range.startLineNumber, thread && thread.stoppedDetails ? `, reason ${thread.stoppedDetails.reason}` : '', lineContent)); </del> <ins> aria.alert(nls.localize({ key: 'debuggingPaused', comment: ['First placeholder is the file line content, second placeholder is the reason why debugging is stopped, for example "breakpoint", third is the stack frame name, and last is the line number.'] }, "{0}, debugging paused {1}, {2}:{3}", lineContent, thread && thread.stoppedDetails ? `, reason ${thread.stoppedDetails.reason}` : '', stackFrame.source ? stackFrame.source.name : '', stackFrame.range.startLineNumber)); </ins> } } }
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: 1.68 OS Version: Browser (windows) Steps to Reproduce: on command center in settings. Command center is not visible. If changing menu from compact to visible it is shown. In desktop it is shown in compact mode.
We have revisited our decision and reverted this change. There is a lengthly discussion in In our "defence", the classic menu rendering has gotten more responsive and will become the compact burger when space is rare. I think we can tweak this further for an even better experience https://user-
I don't really get this decision. This is not the default behavior, so if I decide to set it up like this, why can't I just have the command center without the other menus? It's like you do not support a certain setup which if a user like, why not provide him that? I don't really use most of the menu items, if I need something I just use the command center to find the command. why does it have to be all or nothing?
The title bar showing if CC is enabled has been brought back with other tweaks to improve the experience

Discussion:
return true; } <ins> // with the command center enabled, we should always show if (this.configurationService.getValue<boolean>('window.commandCenter')) { return true; } </ins> // remaining behavior is based on menubar visibility switch (getMenuBarVisibility(this.configurationService)) { case 'classic':
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?: 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: 1.68.0 OS Version: N/A Steps to Reproduce: a new Codespace the Get Started screen, scroll down and select "Just the right amount of UI"3. that "apperance" is not a valid English word. !

Discussion:
{ id: 'menuBarWeb', title: localize('gettingStarted.menuBar.title', "Just the right amount of UI"), <del> description: localize('gettingStarted.menuBar.description.interpolated', "The full menu bar is available in the dropdown menu to make room for your code. Toggle its apperance for faster access. n{0}", Button(localize('toggleMenuBar', "Toggle Menu Bar"), 'command:workbench.action.toggleMenuBar')), </del> <ins> description: localize('gettingStarted.menuBar.description.interpolated', "The full menu bar is available in the dropdown menu to make room for your code. Toggle its appearance for faster access. n{0}", Button(localize('toggleMenuBar', "Toggle Menu Bar"), 'command:workbench.action.toggleMenuBar')), </ins> when: 'isWeb', media: { type: 'svg', altText: 'Comparing menu dropdown with the visible menu bar.', path: 'menuBar.svg'
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.68.0 OS Version: Windows 11 Steps to Reproduce: custom cursor theme (such as a large version of Windows 11 colored vector cursor theme) over tab bar (not tab) Expected behavior: Colored/custom mouse pointer Observed behavior: "Grabby hand" cursor icon. Clicking and dragging the tab bar does nothing, so it doesn't make sense. Fix: Since clicking and dragging the bar does nothing, change it to the default arrow cursor. Screenshots: ! !
Duplicate of
This can't just be fixed by changing the CSS to something else? As I said, dragging the bar does nothing: this is about the UI of VScode implying something can be grabbed and dragged, not just that the cursor is ugly.
Yeah good point, lets ditch this ugly cursor, at least on platforms where not supported nicely.
Opening up for help wanted, to find a better, native cursor on Windows.
Lets just not use it and use cursor instead, same as tabs.
<!-- 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:
/* Editor Label */ <ins> .monaco-workbench .part.editor > .content .editor-group-container > .title { cursor: pointer; } </ins> .monaco-workbench .part.editor > .content .editor-group-container > .title .title-label, .monaco-workbench .part.editor > .content .editor-group-container > .title .tabs-container > .tab .tab-label { white-space: nowrap;

/* Drag and Drop */ <del> .monaco-workbench .part.editor > .content .editor-group-container > .title { cursor: grab; } </del> .monaco-editor-group-drag-image { display: inline-block; padding: 1px 7px;
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.68.0 OS Version: Ubuntu 20.04.4 LTS Steps to Reproduce: indenting to tabs cursor style to block the cursor at the start of a tab; its width increases to the tab stop Besides looking quite silly and different from other editors (e.g. Emacs or Jetbrains IDEs), the constant growing and shrinking is extremely nauseating when rapidly moving the cursor vertically.
Do you have a suggestion about what to do in these cases? Ensure a max width? Sometimes, the block cursor can sit on a glyph which is a lot wider than a typical character like e.g. .
In both Emacs and the Jetbrains IDEs the block cursor remains the width of a space when placed on a tab indent. I pasted your wide character in a test file and it grows to cover it in both environments as well. As far as I'm concerned that's a very pleasant behaviour. :-)
Just to make sure, my primary concern is not esthetics, which are always subjective, but the amount of screen flicker that is currently involved, since tabs at the beginning of lines in code have a very high density.
great, thanks Already enjoying it in insiders :-)

Discussion:
} const range = firstVisibleRangeForCharacter.ranges[0]; <del> const width = range.width < 1 ? this._typicalHalfwidthCharacterWidth : range.width; </del> <ins> const width = ( nextGrapheme === 't' ? this._typicalHalfwidthCharacterWidth : (range.width < 1 ? this._typicalHalfwidthCharacterWidth : range.width) ); </ins> let textContentClassName = ''; if (this._cursorStyle === TextEditorCursorStyle.Block) {