jiebi/CodeConvo huggingface dataset:
Code change:
Issue Type: <bFeature Request</bVSCode uses different conventions for the problem counters in the problems view and in the status bar. The problems view displays: 1 2 ... 999 1K 2K ... 10K+ and the tooltip shows the actual number. The status bar displays: for errors/warnings: 1 2 ... 99+ and the tooltip doesn't show the actual number. for infos: 1 2 ... (always the actual number), the tooltip doesn't show the actual number. <img width="118" alt="problems-view" src="https://user-"<img width="108" alt="status-bar" src="https://user-"VS Code version: Code 1.21.0 (, 2018-03-07T10:54:22.798Z) OS version: Darwin x64 17.4.0 <!-- generated by issue reporter --
assigning to you. I personally would adopt the status bar to the problems view. Everything over 99 is not very informative anyways.

Related discussion:
text: } })); <del> let updateStatus = (element: HTMLDivElement, icon: HTMLDivElement, stats: number): boolean => { if (stats > 0) { element.innerHTML = stats.toString(); $(element).show(); $(icon).show(); return true; </del> <ins> const manyProblems = nls.localize('manyProblems', "10K+"); const packNumber = n => n > 9999 ? manyProblems : n > 999 ? n.toString().charAt(0) + 'K' : n.toString(); let updateLabel = (stats: MarkerStatistics) => { error.innerHTML = packNumber(stats.errors); error.title = errorIcon.title = errorTitle(stats.errors); warning.innerHTML = packNumber(stats.warnings); warning.title = warningIcon.title = warningTitle(stats.warnings); if (stats.infos > 0) { info.innerHTML = packNumber(stats.infos); info.title = infoIcon.title = infoTitle(stats.infos); $(info).show(); $(infoIcon).show(); </ins> } else { <del> $(element).hide(); $(icon).hide(); return false; </del> <ins> $(info).hide(); $(infoIcon).hide(); </ins> } }; <del> let manyMarkers = nls.localize('manyMarkers', "99+"); let updateLabel = (stats: MarkerStatistics) => { error.innerHTML = stats.errors < 100 ? stats.errors.toString() : manyMarkers; warning.innerHTML = stats.warnings < 100 ? stats.warnings.toString() : manyMarkers; updateStatus(info, infoIcon, stats.infos); }; </del> this.markerService.onMarkerChanged((changedResources) => { updateLabel(this.markerService.getStatistics()); });
Code change:
<!-- Do you have a question? Please ask it on --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.21.0 OS Version: macOS 10.13.1 Google Japanese Input it a new VSCode instance on keyboard, then hit enter, and do it again a few times : the suggestions should never overlap w/ text. Actual: the suggestions overlap w/ text. ! Does this issue occur when all extensions are disabled?: Yes This is not an issue with the default Japanese IME that comes w/ macOS. This setting seems to . (You'll lose some functionalities)  
Same Here
same here
Same Here
The suggestion box that shows up in this case is not the one for suggestWidget. This seems like a native control which I dont believe VS Code controls cc Is this a regression? Did this work as expected in earlier versions of VS Code and stopped working recently?
I think it is probably caused by the position adjustment of the textarea, Google IME tries to put the candidate list at the proper position, but I don't have a stable reproduce yet.
Sorry, I am a new user to VSCode so not sure if this is a regression.
I can repro it consistently. !
Not just VSCode but Adobe Brackets seems to have the same issue as well - and for that, apparently, the issue is on CodeMirror: If it's an Electron issue not sure if upgrading Electron to 2.x or 3.x fixes it. This was not an issue on Atom (even when Atom was using Electron 1.x).
I also searched through Twitter, and people have been reporting this since April 2015. Definitely not a regression.
Same Here ! !
Is there anything I can do to help? Also saw this reported on Teratail, a Japanese Stackoverflow clone, about a week ago.
※ (temporary)(workaround)Google (…) <img width="637" alt="2018-09-26 11 51 35" src="https://user-"
Translating what said: Temporary workaround: go to Google Japanese Input preferences, <img width="271" alt="screen shot 2018-09-26 at 6 58 30 pm" src="https://user-"go to ("suggest") and uncheck (disable suggestion from input history) (disable live conversion) Then click button at the bottom. Then it no longer overlaps.
thanks for your help. This issue was caused by how we implement our editor (virtualize everything but has a tiny textarea around the virtual cursor) and Google IME doesn't work the same as the OS builtin IME. I don't have a good idea how to hint Google IME about the position but your solution works perfectly for this issue. For anyone who is using English as system language, the preference with the workaround will look like below: <img width="637" alt="image" src="https://user-"
thanks for the follow-up! Just for completeness: Google maintains "a subset of Google Japanese Input in the form of source code under OSS license without any warranty nor user support" at (), though they're .
Same here
same here
same here OS: windows 10 Language: Chinese IME: Sogou Pinyin, Baidu Pinyin !

Related discussion:
text: top, left, canUseZeroSizeTextarea ? 0 : 1, this._lineHeight ); <ins> // In case the textarea contains a word, we're going to try to align the textarea's cursor // with our cursor by scrolling the textarea as much as possible this.textArea.domNode.scrollLeft = 1000000; </ins> return; }
Code change:
VSCode Version: 1.21.0 OS Version: Windows 10 Redstone 4 Steps to Reproduce: create a configuration type: { "type": "node", "request": "launch", "name": "Stuff", "program": "${workspaceFolder}Stuff" }, Save correct behavior in drop down where you can select that item. the exact same item (change only the program path, leave name the same) as a second configuration. { "type": "node", "request": "launch", "name": "Stuff", "program": "${workspaceFolder}Stuff2" }, your new item missing in drop down because you used same name. same name, by changing "Stuff" to "Stuff2" { "type": "node", "request": "launch", "name": "Stuff2", "program": "${workspaceFolder}Stuff2" }, your new config shows up but you can not select it. (Hover over does not highlight item, clicking does not select item) VSCode correct behavior. Does this issue occur when all extensions are disabled?: Yes
working on this. fairly certain it's related to terminal disposal and issue drop-down options get updated before the instance count is changed. non- atomic from select box view. It would be very helpful for your review once I have something finalized , I think the order of execution is very critical here.
thanks for looking into this. I can review the PR once it is ready. We can verify if that is the same issue by opening F1 developer tools and checking the debug console for potential errors.
I was able to partially reproduce your issue. While I did not have a problem with two debug configurations with the same name, I did see the hover issue. It it appears that you can still select the item with the keyboard so it's actually probably a misplaced disable class within the CSS. It is also still possibly related to another index problem with a twist on the results. StayTuned. !
One thing I left out that I should have mentioned is I also have configurations spanning mutiple workspaces. This issue was in a single workspace, however I have multiple configs which it merges together.
cc: I can reproduce this in several ways. It appears to be an odd "sticky" class label within the list. I have a fix , I would consider the work around. I will commit tomorrow with comments to at least avoid the problem for now. do you use insiders to check after I merge?
I do not currently, but I can, I'll check it after the merge and let you know.
Merged into master. Should be a next insiders. I am not closing this issue as I still think this is a workaround.

Related discussion:
text: if (optionDisabled) { dom.addClass((<HTMLElement>data.root), 'option-disabled'); } else { <del> // TODO: verify if there is a list issue with old classes on rows // This class removal should not be necessary </del> <ins> // Make sure we do class removal from prior template rendering </ins> dom.removeClass((<HTMLElement>data.root), 'option-disabled'); } }
Code change:
Refs: I like that the relatedInformation message has a nice different verbatim font and that makes it differ well enough, I suggest to not use a different background as imho the effect does not look that nice and we do not do it anywhere else to my knowledge. Also in the F8 we do not use a special background !
Yeah, it's the default rendering we have for markdown. Not sure I have change that without making people sad...
Also, the bullets do not appear in the Problems pane or when F8. Why have them here?

Related discussion:
text: hoverMessage.appendMarkdown('n'); for (const { message, resource, startLineNumber, startColumn } of relatedInformation) { hoverMessage.appendMarkdown( <del> `* [${basename(resource.path)}(${startLineNumber}, ${startColumn})](${resource.toString(false)}#${startLineNumber},${startColumn}): `${message}` n` </del> <ins> `* [${basename(resource.path)}(${startLineNumber}, ${startColumn})](${resource.toString(false)}#${startLineNumber},${startColumn}): ` </ins> ); <ins> hoverMessage.appendText(`${message}`); hoverMessage.appendMarkdown('n'); </ins> } hoverMessage.appendMarkdown('n'); }
Code change:
When creating a breakpoint in an active debug session and this breakpoint cannot be verified, the resulting icon is almost invisible: ! The problem is that the icon's stroke is too thin. In previous versions the icon had a thicker stroke: ! I suggest that we restore the previous icon.
Agree that it is a bit too light. I do not just want to take the previous icon since the color and style are different. Thus it would be great if could tackle this Also fyi
Not quite as strong as in the 'before' above, but stronger. Marking verified. !

Related discussion:
text: <del> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><defs><style>.icon-canvas-transparent,.icon-vs-out{fill:#f6f6f6;}.icon-canvas-transparent{opacity:0;}.icon-disabled-grey{fill:#848484;}</style></defs><title>breakpoint-function-unverified</title><g id="canvas"><path class="icon-canvas-transparent" d="M16,0V16H0V0Z"/></g><g id="outline" style="display: none;"><path class="icon-vs-out" d="M13.7,13H2.3L8,2.741Z"/></g><g id="iconBg"><path class="icon-disabled-grey" d="M8,4.8,4,12h8ZM8,6.859,10.3,11H5.7Z"/></g></svg> </del>  No newline at end of file <ins> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><defs><style>.icon-canvas-transparent,.icon-vs-out{fill:#f6f6f6;}.icon-canvas-transparent{opacity:0;}.icon-disabled-grey{fill:#848484;}</style></defs><title>breakpoint-function-unverified</title><g id="canvas"><path class="icon-canvas-transparent" d="M16,0V16H0V0Z"/></g><g id="outline" style="display: none;"><path class="icon-vs-out" d="M13.95,13H2.05L8,2.291Z"/></g><g id="iconBg"><path class="icon-disabled-grey" d="M8,4.35,3.75,12h8.5ZM8,6.924l2.125,3.826H5.875Z"/></g></svg> </ins>  No newline at end of file
Code change:
When creating a breakpoint in an active debug session and this breakpoint cannot be verified, the resulting icon is almost invisible: ! The problem is that the icon's stroke is too thin. In previous versions the icon had a thicker stroke: ! I suggest that we restore the previous icon.
Agree that it is a bit too light. I do not just want to take the previous icon since the color and style are different. Thus it would be great if could tackle this Also fyi
Not quite as strong as in the 'before' above, but stronger. Marking verified. !

Related discussion:
text: <del> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><defs><style>.icon-canvas-transparent,.icon-vs-out{fill:#f6f6f6;}.icon-canvas-transparent{opacity:0;}.icon-disabled-grey{fill:#848484;}</style></defs><title>breakpoint-log-unverified</title><g id="canvas"><path class="icon-canvas-transparent" d="M16,0V16H0V0Z"/></g><g id="outline" style="display: none;"><path class="icon-vs-out" d="M13.414,8,8,13.414,2.586,8,8,2.586Z"/></g><g id="iconBg"><path class="icon-disabled-grey" d="M8,4,4,8l4,4,4-4ZM5.414,8,8,5.414,10.586,8,8,10.586Z"/></g></svg> </del>  No newline at end of file <ins> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><defs><style>.icon-canvas-transparent,.icon-vs-out{fill:#f6f6f6;}.icon-canvas-transparent{opacity:0;}.icon-disabled-grey{fill:#848484;}</style></defs><title>breakpoint-log-unverified</title><g id="canvas"><path class="icon-canvas-transparent" d="M16,0V16H0V0Z"/></g><g id="outline" style="display: none;"><path class="icon-vs-out" d="M13.664,8,8,13.664,2.336,8,8,2.336Z"/></g><g id="iconBg"><path class="icon-disabled-grey" d="M8,3.75,3.75,8,8,12.25,12.25,8ZM5.518,8,8,5.518,10.482,8,8,10.482Z"/></g></svg> </ins>  No newline at end of file
Code change:
When creating a breakpoint in an active debug session and this breakpoint cannot be verified, the resulting icon is almost invisible: ! The problem is that the icon's stroke is too thin. In previous versions the icon had a thicker stroke: ! I suggest that we restore the previous icon.
Agree that it is a bit too light. I do not just want to take the previous icon since the color and style are different. Thus it would be great if could tackle this Also fyi
Not quite as strong as in the 'before' above, but stronger. Marking verified. !

Related discussion:
text: <del> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><defs><style>.icon-canvas-transparent,.icon-vs-out{fill:#f6f6f6;}.icon-canvas-transparent{opacity:0;}.icon-disabled-grey{fill:#848484;}</style></defs><title>breakpoint-unverified</title><g id="canvas"><path class="icon-canvas-transparent" d="M16,0V16H0V0Z"/></g><g id="outline" style="display: none;"><path class="icon-vs-out" d="M12.632,8A4.632,4.632,0,1,1,8,3.368,4.638,4.638,0,0,1,12.632,8Z"/></g><g id="iconBg"><path class="icon-disabled-grey" d="M8,4.211A3.789,3.789,0,1,0,11.789,8,3.788,3.788,0,0,0,8,4.211ZM8,10.79A2.79,2.79,0,1,1,10.79,8,2.794,2.794,0,0,1,8,10.79Z"/></g></svg> </del>  No newline at end of file <ins> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><defs><style>.icon-canvas-transparent,.icon-vs-out{fill:#f6f6f6;}.icon-canvas-transparent{opacity:0;}.icon-disabled-grey{fill:#848484;}</style></defs><title>breakpoint-unverified</title><g id="canvas"><path class="icon-canvas-transparent" d="M16,0V16H0V0Z"/></g><g id="outline" style="display: none;"><path class="icon-vs-out" d="M12.632,8A4.632,4.632,0,1,1,8,3.368,4.638,4.638,0,0,1,12.632,8Z"/></g><g id="iconBg"><path class="icon-disabled-grey" d="M8,4.211A3.789,3.789,0,1,0,11.79,8,3.788,3.788,0,0,0,8,4.211ZM8,10.29A2.29,2.29,0,1,1,10.29,8,2.292,2.292,0,0,1,8,10.29Z"/></g></svg> </ins>  No newline at end of file
Code change:
Issue Type: <bBug</bNavigate to any reccomended extension with a screen reader. The reader will read the extension name, followed by "[object Object]", rather than showing that the extension has been reccomended and why. VS Code version: Code 1.24.0 (, 2018-06-06T17:35:40.560Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </detailsExtensions: none <!-- generated by issue reporter --

Related discussion:
text: const extRecommendations = this.extensionTipsService.getAllRecommendationsWithReason(); if (extRecommendations[extension.id.toLowerCase()]) { <del> data.root.setAttribute('aria-label', extension.displayName + '. ' + extRecommendations[extension.id]); </del> <ins> data.root.setAttribute('aria-label', extension.displayName + '. ' + extRecommendations[extension.id.toLowerCase()].reasonText); </ins> addClass(data.root, 'recommended'); data.root.title = extRecommendations[extension.id.toLowerCase()].reasonText; }
Code change:
I've attempted to find any other requests for this but didn't seem to see any. At the moment the CVS context menu shows: ! Only "Pop latest stash" and "Pop stash..." are visible. Is it possible to change the default stash behaviour to "apply" rather than "pop"? Additionally, is it possible to add two lines under "Pop stash..." for the same actions, just using apply: Apply latest stash Apply stash... I just lost a few hours and considerable amount of hair when a popped stash was deleted. I then had to sift through doing on each . Having "Apply stash..." easily accessible might be nicer.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.676 --<!-- potentialduplicatescomment --
I suggest to simply add and commands.
is anyone working on this, if not, I'll like to pick it up as a
looks like it might already be done in
yeah, just confirmed, Thanks. If I may ask, is there any rule around tagging an issue that is being worked on as it would be multiple efforts if I happen to have started it without anyone's knowledge. I've been scouting for an issue with no assignee to work on :-( Thanks for the catch tho!

Related discussion:
text: "command": "git.stashPopLatest", "title": "%command.stashPopLatest%", "category": "Git" <ins> }, { "command": "git.stashApply", "title": "%command.stashApply%", "category": "Git" }, { "command": "git.stashApplyLatest", "title": "%command.stashApplyLatest%", "category": "Git" </ins> } ], "menus": {
Code change:
I've attempted to find any other requests for this but didn't seem to see any. At the moment the CVS context menu shows: ! Only "Pop latest stash" and "Pop stash..." are visible. Is it possible to change the default stash behaviour to "apply" rather than "pop"? Additionally, is it possible to add two lines under "Pop stash..." for the same actions, just using apply: Apply latest stash Apply stash... I just lost a few hours and considerable amount of hair when a popped stash was deleted. I then had to sift through doing on each . Having "Apply stash..." easily accessible might be nicer.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.676 --<!-- potentialduplicatescomment --
I suggest to simply add and commands.
is anyone working on this, if not, I'll like to pick it up as a
looks like it might already be done in
yeah, just confirmed, Thanks. If I may ask, is there any rule around tagging an issue that is being worked on as it would be multiple efforts if I happen to have started it without anyone's knowledge. I've been scouting for an issue with no assignee to work on :-( Thanks for the catch tho!

Related discussion:
text: { "command": "git.stashPopLatest", "when": "config.git.enabled && gitOpenRepositoryCount != 0" <ins> }, { "command": "git.stashApply", "when": "config.git.enabled && gitOpenRepositoryCount != 0" }, { "command": "git.stashApplyLatest", "when": "config.git.enabled && gitOpenRepositoryCount != 0" </ins> } ], "scm/title": [
Code change:
I've attempted to find any other requests for this but didn't seem to see any. At the moment the CVS context menu shows: ! Only "Pop latest stash" and "Pop stash..." are visible. Is it possible to change the default stash behaviour to "apply" rather than "pop"? Additionally, is it possible to add two lines under "Pop stash..." for the same actions, just using apply: Apply latest stash Apply stash... I just lost a few hours and considerable amount of hair when a popped stash was deleted. I then had to sift through doing on each . Having "Apply stash..." easily accessible might be nicer.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.676 --<!-- potentialduplicatescomment --
I suggest to simply add and commands.
is anyone working on this, if not, I'll like to pick it up as a
looks like it might already be done in
yeah, just confirmed, Thanks. If I may ask, is there any rule around tagging an issue that is being worked on as it would be multiple efforts if I happen to have started it without anyone's knowledge. I've been scouting for an issue with no assignee to work on :-( Thanks for the catch tho!

Related discussion:
text: "when": "scmProvider == git" }, { <ins> "command": "git.stashApply", "group": "5_stash", "when": "scmProvider == git" }, { "command": "git.stashApplyLatest", "group": "5_stash", "when": "scmProvider == git" }, { </ins> "command": "git.showOutput", "group": "7_repository", "when": "scmProvider == git"
Code change:
I've attempted to find any other requests for this but didn't seem to see any. At the moment the CVS context menu shows: ! Only "Pop latest stash" and "Pop stash..." are visible. Is it possible to change the default stash behaviour to "apply" rather than "pop"? Additionally, is it possible to add two lines under "Pop stash..." for the same actions, just using apply: Apply latest stash Apply stash... I just lost a few hours and considerable amount of hair when a popped stash was deleted. I then had to sift through doing on each . Having "Apply stash..." easily accessible might be nicer.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.676 --<!-- potentialduplicatescomment --
I suggest to simply add and commands.
is anyone working on this, if not, I'll like to pick it up as a
looks like it might already be done in
yeah, just confirmed, Thanks. If I may ask, is there any rule around tagging an issue that is being worked on as it would be multiple efforts if I happen to have started it without anyone's knowledge. I've been scouting for an issue with no assignee to work on :-( Thanks for the catch tho!

Related discussion:
text: "command.stash": "Stash", "command.stashPop": "Pop Stash...", "command.stashPopLatest": "Pop Latest Stash", <ins> "command.stashApply": "Apply Stash...", "command.stashApplyLatest": "Apply Latest Stash", </ins> "config.enabled": "Whether git is enabled", "config.path": "Path to the git executable", "config.autoRepositoryDetection": "Configures when repositories should be automatically detected.",
Code change:
I've attempted to find any other requests for this but didn't seem to see any. At the moment the CVS context menu shows: ! Only "Pop latest stash" and "Pop stash..." are visible. Is it possible to change the default stash behaviour to "apply" rather than "pop"? Additionally, is it possible to add two lines under "Pop stash..." for the same actions, just using apply: Apply latest stash Apply stash... I just lost a few hours and considerable amount of hair when a popped stash was deleted. I then had to sift through doing on each . Having "Apply stash..." easily accessible might be nicer.
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.676 --<!-- potentialduplicatescomment --
I suggest to simply add and commands.
is anyone working on this, if not, I'll like to pick it up as a
looks like it might already be done in
yeah, just confirmed, Thanks. If I may ask, is there any rule around tagging an issue that is being worked on as it would be multiple efforts if I happen to have started it without anyone's knowledge. I've been scouting for an issue with no assignee to work on :-( Thanks for the catch tho!

Related discussion:
text: 'use strict'; import { Uri, commands, Disposable, window, workspace, QuickPickItem, OutputChannel, Range, WorkspaceEdit, Position, LineChange, SourceControlResourceState, TextDocumentShowOptions, ViewColumn, ProgressLocation, TextEditor, MessageOptions } from 'vscode'; <del> import { Ref, RefType, Git, GitErrorCodes, Branch } from './git'; </del> <ins> import { Ref, RefType, Git, GitErrorCodes, Branch, Stash } from './git'; </ins> import { Repository, Resource, Status, CommitOptions, ResourceGroupType } from './repository'; import { Model } from './model'; import { toGitUri, fromGitUri } from './uri';