jiebi/CodeConvo huggingface dataset:
Code change:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --It would be ideal if the Testing user interface would allow to sort/filter based on duration. Use case: I have a large number of tests in my project and they're slow, I want to sort by duration to identify long running tests. !
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.595 --- <!-- score: 0.493 --<!-- potentialduplicatescomment --
I want to work on this shall I give it a try ?
Can I get a little help here ? I think I am not able to find the UI in the app. Is this screen capture same as above ? (Left panel) ! I made two tests locally, but I am not seeing the time it took to run the tests ?
You'll need to use to make the Test Explorer use the native experience.
Hey admin, i have just started my open source contribution journey. Can you assign this task to me? so that i can start working on it.
Feel free to submit a PR
Hey Conor, can I work on this issue
, I found that following changes will be needed adding a class to adding to export const enum TestExplorerViewSorting { ByLocation = 'location', ByStatus = 'status', } inside the file
The TestExplorerView is where it happens. You can do a "find all references" on and that'll give you a good indication of places to update
There is such a line for sort ByLocation , but not there for ByStatus , why is it so
What changes should be made to this file , please help me out
Have a pull request for this:

Related discussion:
text: export const enum TestExplorerViewSorting { ByLocation = 'location', ByStatus = 'status', <ins> ByDuration = 'duration', </ins> } export const enum TestExplorerStateFilter {
Code change:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --With , changes in a diff editor: [![enter image description here][1]][1] With , changes in a diff editor: [![enter image description here][2]][2] With , changes in a normal (non-diff) editor: [![enter image description here][3]][3] How to ignore changes in leading/trailing whitespace in a non-diff editor as well? If such a setting doesn't exist, please consider adding one. [1]: [2]: [3]:
I've removed the label, because this issue is about the hard-coded value . If that line of code would be commented out, I think everything would work as desired (the quick diff would respect the setting).
Maybe I'm misunderstanding, but this doesn't seem to work? ! In case it isn't clear in the picture, I just whitespace
I reproduced as well.
Turns out this isn't true.
Sorry about that!
No worries, I know you were just hinting.
Verification: There's a new setting to control this.

Related discussion:
text: fixedOverflowWidgets: true, minimap: { enabled: false }, renderSideBySide: false, <del> readOnly: false, ignoreTrimWhitespace: false </del> <ins> readOnly: false </ins> }; this.diffEditor = this.instantiationService.createInstance(EmbeddedDiffEditorWidget, container, options, this.editor);
Code 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.60.0 OS Version: MacOS 10.14.3 Steps to Reproduce: & paste into markdown file <kbd⌘</kbdand click the link .ext)
This is my first go at launching into the vscode code, but hopefully this information may be useful. Perhaps we could update the parsing of the URI schemes in general to strip out the angle brackets when editing markdown? See my findings below for why I'm suggesting this, but I'm also unsure of what problems and side effects doing that may cause. Main points of interest While the Command + Click doesn't follow the web link when you're a Markdown file, it does follow the link in the of the Markdown file. So I think markdown syntax is actually ok In debugging the project a little bit, I found that the link you try to follow that has angle brackets may be trying to or something similar (instead of open a web browser) In the function , I think the scheme of http(s) isn't recognized because of the < brackets in the link portion. See around line 18, where it tries to recognize the scheme, but doesn't recognize it when it tries calling In the file you can add a few new schemes, and then you're able to follow the link just fine. Though, this is probably not the final way the issue should be fixed

Related discussion:
text: document: vscode.TextDocument, link: string, ): { uri: vscode.Uri, tooltip?: string } | undefined { <del> const externalSchemeUri = getUriForLinkWithKnownExternalScheme(link); </del> <ins> const cleanLink = stripAngleBrackets(link); const externalSchemeUri = getUriForLinkWithKnownExternalScheme(cleanLink); </ins> if (externalSchemeUri) { // Normalize VS Code links to target currently running version if (isOfScheme(Schemes.vscode, link) || isOfScheme(Schemes['vscode-insiders'], link)) {
Code 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.60.0 OS Version: MacOS 10.14.3 Steps to Reproduce: & paste into markdown file <kbd⌘</kbdand click the link .ext)
This is my first go at launching into the vscode code, but hopefully this information may be useful. Perhaps we could update the parsing of the URI schemes in general to strip out the angle brackets when editing markdown? See my findings below for why I'm suggesting this, but I'm also unsure of what problems and side effects doing that may cause. Main points of interest While the Command + Click doesn't follow the web link when you're a Markdown file, it does follow the link in the of the Markdown file. So I think markdown syntax is actually ok In debugging the project a little bit, I found that the link you try to follow that has angle brackets may be trying to or something similar (instead of open a web browser) In the function , I think the scheme of http(s) isn't recognized because of the < brackets in the link portion. See around line 18, where it tries to recognize the scheme, but doesn't recognize it when it tries calling In the file you can add a few new schemes, and then you're able to follow the link just fine. Though, this is probably not the final way the issue should be fixed

Related discussion:
text: } } <ins> /* Used to strip brackets from the markdown link <http://example.com> will be transformed to http://example.com */ export function stripAngleBrackets(link: string) { const bracketMatcher = /^<(.*)>$/; return link.replace(bracketMatcher, '$1'); } </ins> export default class LinkProvider implements vscode.DocumentLinkProvider { private readonly linkPattern = /([((![[^]]*?](s*)([^s()]+?)s*)]|(?:]|[^]])*])(s*)(([^s()]|([^s()]*?))+)s*(".*?")?)/g; private readonly referenceLinkPattern = /([((?:]|[^]])+)][s*?)([^s]]*?)]/g;
Code change:
Issue Type: <bBug</bthe settings UI. for a setting (e.g. "inlay"). the settings tab to a new editor group. Note that the search you entered previously has been cleared. https://user- VS Code version: Code 1.60.0 (, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 vscode-nginx-conf0.1.3 reorder-lines-by-length1.0.2 docs-view0.0.9 pgformatter1.17.0 vscode-eslint2.1.25 gitlens11.6.0 vscode-diff1.4.2 shell-format7.1.0 go0.27.2 postgresql0.0.2 rainbow-csv1.9.1 render-crlf1.5.21 template-string-converter0.5.3 python2021.9. vscode-pylance2021.9.2 jupyter2021.8. jupyter-keymap1.0.0 debugger-for-chrome4.13.0 nbsp-vscode0.0.1 vscode-commons0.0.6 vscode-yaml0.22.0 final-newline0.3.2 vscode-hexdump1.8.1 change-case1.0.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
A function called in is being called after the drop, which is correct. But, the function in the same file name isn't being called when the user does step 3 above. Another repro is to use the "move editor to X group" commands. Therefore, the fix doesn't have to do directly with dnd.

Related discussion:
text: this.defaultSettingsEditorModel = model; options = options || validateSettingsEditorOptions({}); <del> if (!this.viewState.settingsTarget) { if (!options.target) { </del> <ins> if (!this.viewState.settingsTarget || !this.settingsTargetsWidget.settingsTarget) { const optionsHasViewStateTarget = options.viewState && (options.viewState as ISettingsEditorViewState).settingsTarget; if (!options.target && !optionsHasViewStateTarget) { </ins> options.target = ConfigurationTarget.USER_LOCAL; } }
Code change:
Issue Type: <bBug</bthe settings UI. for a setting (e.g. "inlay"). the settings tab to a new editor group. Note that the search you entered previously has been cleared. https://user- VS Code version: Code 1.60.0 (, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 vscode-nginx-conf0.1.3 reorder-lines-by-length1.0.2 docs-view0.0.9 pgformatter1.17.0 vscode-eslint2.1.25 gitlens11.6.0 vscode-diff1.4.2 shell-format7.1.0 go0.27.2 postgresql0.0.2 rainbow-csv1.9.1 render-crlf1.5.21 template-string-converter0.5.3 python2021.9. vscode-pylance2021.9.2 jupyter2021.8. jupyter-keymap1.0.0 debugger-for-chrome4.13.0 nbsp-vscode0.0.1 vscode-commons0.0.6 vscode-yaml0.22.0 final-newline0.3.2 vscode-hexdump1.8.1 change-case1.0.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
A function called in is being called after the drop, which is correct. But, the function in the same file name isn't being called when the user does step 3 above. Another repro is to use the "move editor to X group" commands. Therefore, the fix doesn't have to do directly with dnd.

Related discussion:
text: return withUndefinedAsNull(cachedState); } <ins> override getViewState(): object | undefined { return this.viewState; } </ins> override setOptions(options: ISettingsEditorOptions | undefined): void { super.setOptions(options);
Code change:
Issue Type: <bBug</bthe settings UI. for a setting (e.g. "inlay"). the settings tab to a new editor group. Note that the search you entered previously has been cleared. https://user- VS Code version: Code 1.60.0 (, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 vscode-nginx-conf0.1.3 reorder-lines-by-length1.0.2 docs-view0.0.9 pgformatter1.17.0 vscode-eslint2.1.25 gitlens11.6.0 vscode-diff1.4.2 shell-format7.1.0 go0.27.2 postgresql0.0.2 rainbow-csv1.9.1 render-crlf1.5.21 template-string-converter0.5.3 python2021.9. vscode-pylance2021.9.2 jupyter2021.8. jupyter-keymap1.0.0 debugger-for-chrome4.13.0 nbsp-vscode0.0.1 vscode-commons0.0.6 vscode-yaml0.22.0 final-newline0.3.2 vscode-hexdump1.8.1 change-case1.0.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
A function called in is being called after the drop, which is correct. But, the function in the same file name isn't being called when the user does step 3 above. Another repro is to use the "move editor to X group" commands. Therefore, the fix doesn't have to do directly with dnd.

Related discussion:
text: this.focusSearch(); } <del> if (options.query) { this.searchWidget.setValue(options.query); </del> <ins> const recoveredViewState = options.viewState ? options.viewState as ISettingsEditorViewState : undefined; const query: string | undefined = recoveredViewState?.query ?? options.query; if (query !== undefined) { this.searchWidget.setValue(query); this.viewState.query = query; </ins> } <del> const target: SettingsTarget = options.folderUri || <SettingsTarget>options.target; </del> <ins> const target: SettingsTarget | undefined = options.folderUri ?? recoveredViewState?.settingsTarget ?? <SettingsTarget | undefined>options.target; </ins> if (target) { this.settingsTargetsWidget.settingsTarget = target; this.viewState.settingsTarget = target;
Code change:
Issue Type: <bBug</bthe settings UI. for a setting (e.g. "inlay"). the settings tab to a new editor group. Note that the search you entered previously has been cleared. https://user- VS Code version: Code 1.60.0 (, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 vscode-nginx-conf0.1.3 reorder-lines-by-length1.0.2 docs-view0.0.9 pgformatter1.17.0 vscode-eslint2.1.25 gitlens11.6.0 vscode-diff1.4.2 shell-format7.1.0 go0.27.2 postgresql0.0.2 rainbow-csv1.9.1 render-crlf1.5.21 template-string-converter0.5.3 python2021.9. vscode-pylance2021.9.2 jupyter2021.8. jupyter-keymap1.0.0 debugger-for-chrome4.13.0 nbsp-vscode0.0.1 vscode-commons0.0.6 vscode-yaml0.22.0 final-newline0.3.2 vscode-hexdump1.8.1 change-case1.0.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
A function called in is being called after the drop, which is correct. But, the function in the same file name isn't being called when the user does step 3 above. Another repro is to use the "move editor to X group" commands. Therefore, the fix doesn't have to do directly with dnd.

Related discussion:
text: this.settingsTreeModel.update(resolvedSettingsRoot); this.tocTreeModel.settingsTreeRoot = this.settingsTreeModel.root as SettingsTreeGroupElement; <del> const cachedState = this.restoreCachedState(); if (cachedState && cachedState.searchQuery || !!this.searchWidget.getValue()) { </del> <ins> // Don't restore the cached state if we already have a query value from calling _setOptions(). const cachedState = !this.viewState.query ? this.restoreCachedState() : undefined; if (cachedState?.searchQuery || this.searchWidget.getValue()) { </ins> await this.onSearchInputChanged(); } else { this.refreshTOCTree();
Code change:
Issue Type: <bBug</bthe settings UI. for a setting (e.g. "inlay"). the settings tab to a new editor group. Note that the search you entered previously has been cleared. https://user- VS Code version: Code 1.60.0 (, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 vscode-nginx-conf0.1.3 reorder-lines-by-length1.0.2 docs-view0.0.9 pgformatter1.17.0 vscode-eslint2.1.25 gitlens11.6.0 vscode-diff1.4.2 shell-format7.1.0 go0.27.2 postgresql0.0.2 rainbow-csv1.9.1 render-crlf1.5.21 template-string-converter0.5.3 python2021.9. vscode-pylance2021.9.2 jupyter2021.8. jupyter-keymap1.0.0 debugger-for-chrome4.13.0 nbsp-vscode0.0.1 vscode-commons0.0.6 vscode-yaml0.22.0 final-newline0.3.2 vscode-hexdump1.8.1 change-case1.0.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
A function called in is being called after the drop, which is correct. But, the function in the same file name isn't being called when the user does step 3 above. Another repro is to use the "move editor to X group" commands. Therefore, the fix doesn't have to do directly with dnd.

Related discussion:
text: } const query = this.searchWidget.getValue().trim(); <ins> this.viewState.query = query; </ins> this.delayedFilterLogging.cancel(); await this.triggerSearch(query.replace(/u203A/g, ' '));
Code change:
Issue Type: <bBug</bthe settings UI. for a setting (e.g. "inlay"). the settings tab to a new editor group. Note that the search you entered previously has been cleared. https://user- VS Code version: Code 1.60.0 (, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-css-formatter1.0.1 vscode-nginx-conf0.1.3 reorder-lines-by-length1.0.2 docs-view0.0.9 pgformatter1.17.0 vscode-eslint2.1.25 gitlens11.6.0 vscode-diff1.4.2 shell-format7.1.0 go0.27.2 postgresql0.0.2 rainbow-csv1.9.1 render-crlf1.5.21 template-string-converter0.5.3 python2021.9. vscode-pylance2021.9.2 jupyter2021.8. jupyter-keymap1.0.0 debugger-for-chrome4.13.0 nbsp-vscode0.0.1 vscode-commons0.0.6 vscode-yaml0.22.0 final-newline0.3.2 vscode-hexdump1.8.1 change-case1.0.0 markdown-all-in-one3.4.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
A function called in is being called after the drop, which is correct. But, the function in the same file name isn't being called when the user does step 3 above. Another repro is to use the "move editor to X group" commands. Therefore, the fix doesn't have to do directly with dnd.

Related discussion:
text: export interface ISettingsEditorViewState { settingsTarget: SettingsTarget; <ins> query?: string; // used to keep track of loading from setInput vs loading from cache </ins> tagFilters?: Set<string>; extensionFilters?: Set<string>; featureFilters?: Set<string>;
Code change:
Testing !
The binary is indeed available in the server folder but the libc library it is linked with does not exist on the image.
Ripgrep should also build for rust target in to support alpine images so that it is uses the musl c library.
I can add that, thanks
Ripgrep couldn't build under that target. My understanding is… when building with musl, it uses jemalloc, jemalloc uses backgroundthreadsruntime_support, and that doesn’t support our target. If we can figure out how to un set that flag on jemalloc that might work around it but i don’t know what consequences that would have
from it is not sure whether the bug is in jemalloc config or cargo, but the immediate working solution is to build the crate with I will see if that works.
May I know if there is some workaround for this bug for users? If not, I do not think its good to ship Alpine ARM 64 builds with broken experience.
It will require users to install package that will include the required libraries for the executable built using glibc.
Not with your PR, right And thanks for the PR!
Yup is not needed with the musl binary produced from the PR.
I didn't put up a PR to adjust to download for alpine. Can you take care of it ? Thanks!

Related discussion:
text: <ins> { "comments": { "lineComment": "//", "blockComment": ["/*", "*/"] }, "brackets": [ ["{", "}"], ["[", "]"], ["(", ")"] ] } </ins>  No newline at end of file
Code change:
Testing !
The binary is indeed available in the server folder but the libc library it is linked with does not exist on the image.
Ripgrep should also build for rust target in to support alpine images so that it is uses the musl c library.
I can add that, thanks
Ripgrep couldn't build under that target. My understanding is… when building with musl, it uses jemalloc, jemalloc uses backgroundthreadsruntime_support, and that doesn’t support our target. If we can figure out how to un set that flag on jemalloc that might work around it but i don’t know what consequences that would have
from it is not sure whether the bug is in jemalloc config or cargo, but the immediate working solution is to build the crate with I will see if that works.
May I know if there is some workaround for this bug for users? If not, I do not think its good to ship Alpine ARM 64 builds with broken experience.
It will require users to install package that will include the required libraries for the executable built using glibc.
Not with your PR, right And thanks for the PR!
Yup is not needed with the musl binary produced from the PR.
I didn't put up a PR to adjust to download for alpine. Can you take care of it ? Thanks!

Related discussion:
text: "languages": [{ "id": "csharp", "extensions": [ ".cs", ".csx" ], <del> "aliases": [ "C#", "csharp" ] </del> <ins> "aliases": [ "C#", "csharp" ], "configuration": "./csharp.configuration.json" </ins> }], "grammars": [{ "language": "csharp",
Code change:
Testing !
The binary is indeed available in the server folder but the libc library it is linked with does not exist on the image.
Ripgrep should also build for rust target in to support alpine images so that it is uses the musl c library.
I can add that, thanks
Ripgrep couldn't build under that target. My understanding is… when building with musl, it uses jemalloc, jemalloc uses backgroundthreadsruntime_support, and that doesn’t support our target. If we can figure out how to un set that flag on jemalloc that might work around it but i don’t know what consequences that would have
from it is not sure whether the bug is in jemalloc config or cargo, but the immediate working solution is to build the crate with I will see if that works.
May I know if there is some workaround for this bug for users? If not, I do not think its good to ship Alpine ARM 64 builds with broken experience.
It will require users to install package that will include the required libraries for the executable built using glibc.
Not with your PR, right And thanks for the PR!
Yup is not needed with the musl binary produced from the PR.
I didn't put up a PR to adjust to download for alpine. Can you take care of it ? Thanks!

Related discussion:
text: { "comments": { "lineComment": "#", <del> "blockComment": [ "''", "''" ] </del> <ins> "blockComment": [ "'''", "'''" ] </ins> }, "brackets": [ ["{", "}"],