jiebi/CodeConvo huggingface dataset:
And yes, if I uninstall the extension, install release, try to switch, the same happens over and over again. I discovered another bug: switch back to stable is not possible [2022-05-24 12:03:11.208] [remoteagent] [warning] Overwriting user extension with It always pushes me back to the pre-release. I think this may be related to keep local/remote on the same version/track. EDIT: Okay, actually this blocks everyone using insiders with the jupyter and/or other plugins in combination with remote ssh. Since insiders are updated daily, the "vs code server" is updated daily and the plugin is revert/installed again in the non preview version. So my hotfix has to applied daily which is really annoying. EDIT 2: I realised that the current (release today) stable "jupyter" version also has the latest insiders api implemented. So for now and for me that is solved - but the actual bug is still there, I can't switch to pre-release versions in a remote ssh setup.
Sorry that you are having this annoying issue and glad that you are able to reproduce it so that we can investigate. If you don't mind, can you please summarise your repro steps?
So, I now understand why it's a bit complex to reproduce this - I guess... I was even confused myself. So, currently the only way to reproduce it was for me: 1) deinstall the server (rm -rf .vscode-insiders-server) 2) connect/install + install jupyter extensions (local: pre-release) -pre-release installation successful 3) switch to release on remote 4) reload window -I am then on release try to switch to pre-release -issue appears. And now the important part: I realised that I still had the setting because within our company we had restrictions before... setting this to false also fixes the issue - even when it appeared before.
Thanks for the steps. I can reproduce it now and fixed. To verify: Open a remote window and set setting Install pre-release of ESLint extension Reload window Switch to release version of ESLint extension Reload window Switch to pre-release version of ESLint extension Make sure switch happens
Issue Type: <bBug</bThe source control pane allows discarding changes by right-clicking on selected items and then choosing "Discard Changes". If items are selected in a tree view, and part of the selection is a directory, then the confirmation dialog shows a wrong (impossible) number of files to be discarded. Steps: open vscode in a git directory, with no current changes switch to the source control pane, note the changes make sure that "View as Tree" mode is active select all three items in the treev view, comprising of 1 directory and 2 files right-click onto select items -"Discard Changes" //exp: Confirmation - "This will DELETE 2 untracked files" //act: Confirmation - "This will DELETE 3 untracked files" IOW, the directory is counted as a file. This is rather irritating if one expects to discard a very well-known number of files, only to discover that the UI confirmation dialog is off. VS Code version: Code 1.60.1 (, 2021-09-10T17:06:57.931Z) OS version: Linux x64 5.13.15-200.fc34.x8664 Restricted Mode: No <details<summarySystem Info</summary </detailsExtensions disabled<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Just noticed a simpler scenario: Just use tree view mode, have 1 file in the directory, and directly discard the directory. The confirmation dialog will ask for confirmation to delete 2 files, while there is 1 file only (the directory will not be touched by the git revert)
Funny enough - clicking on the "Discard All Changes" icon reports the correct number of files (2 files in the scenario above).
I see multiple options for implementing a fix for this: 1) Deduplicate the resources in the command 2) Deduplicate the resources in core before the are passed to the command as args
1 sounds great!
When I was debugging SVN extension () I saw this message in console: ! Then I've discovered that this promise is unhandled in another extension, after I've edited file and inserted breakpoint. Please provide some stacktrace or message of rejected Promise it's hard to find the root of the problem.
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the for VS Code. See also our guidelines. Happy Coding!
I think the ask here is that we improve our handler to display the call stack of the unhandled error...
Yeah, I got that. I have for that (thanks to
Version: 1.38.0 Commit: Date: 2019-09-03T21:47:00.464Z Electron: 4.2.10 Chrome: 69.0.3497.128 10.11.0 V8: 6.9.427.31-electron.0 OS: Darwin x64 18.0.0 Steps to Reproduce: 1 open multiple tabs and only save some of them. 2 commit and click <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.559 --- <!-- score: 0.518 --- <!-- score: 0.492 --- <!-- score: 0.483 --<!-- potentialduplicatescomment --
Oh yeah. Good catch. Want to submit a fix? Problem is
Hey, I am a new contributor here. I want to give a try on this issue.
Great. Go ahead.
<!-- 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.56.2 OS Version: MacOS Catalina 10.15.6 Steps to Reproduce: VSCode Version any typescript file (for example in ) /Ctrl + Click on any native dom method, for example , there should be a error message popups ! I thinks this is caused by the wrong type definition file path in below code:
Steps to Reproduce: a directory with Git initialized. "Incoming/Outgoing" section in the SCM pane appear. Could be done by either: Make sure the current branch has an upstream branch, then commit something. Or Set and to . the page. a change to a file. Expected result: the file appears under "Changes" section in SCM pane. Actual result: the "Changes" section doesn't appear in SCM pane. Expected result: the file appears under "Staged changes" section in SCM pane. Actual result: the "Staged changes" section doesn't appear in SCM pane. Happens on Firefox 121.0, Ubuntu 22.04. Doesn't seem to happen on Chromium 120 and WebKitGTK 2.42.3. Happens in GitHub Codespaces: Also happens with code-server: Also happens with OpenVSCode Server insider:
I'm experiencing the same or a very similar issue in latest code-server using Firefox. I can no longer open the repository in source control if there are any incoming/outgoing changes and instead am getting an exception in the browser console without the repository opening. Likely the reason the issue appears slightly differently for me is because I have multiple repositories in source control. For anyone else affected the following settings are making this issue to not occur:
Same here but not consistent: Version: 1.85.1 (user setup) Commit: Date: 2023-12-13T09:49:37.021Z Electron: 25.9.7 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.
could you please try VS Code Insiders and see if you are still able to reproduce the problem? I have fixed couple of issues in this area and it would be great if you could try Insiders to make sure that this issue is covered by my fixes as well. Thanks!
Tested with OpenVSCode-server insiders, which is rebased on top of commit ("Sanity Bounds for "window.zoomLevel" ( ()") [1]. The issue still exists.
code-server doesn't release insider builds, and I don't know how to test insider builds of GitHub codespaces' web UI, so I can't test those. (Off topic, but does GitHub codespaces provide an insider build for web interface by any chance?) [1]:
if you open a GitHub Codespace, you can click on the "Gear" icon in the activity bar, and there is a menu item to switch to VS Code Insiders. You can try that out and let me know if you are still able to reproduce the issue. Thank you!
Thank you. Tested with the GitHub Codespaces + VSCode insiders [1], the issue can still be reproduced. Interestingly, if I change the to and then to again, the "Source control" pane essentially freeze: the "Incoming/Outgoing" section doesn't comeback, and further changes to the working directory is not shown anymore (like, if you add another file, it doesn't show up, even after I click "Refresh" button). [1]
thanks for trying this out. Could you please confirm that this indeed can only be reproduce in Firefox and everything works as expected in a Chromium based browser (ex: Chrome, Edge, etc)? Could you please the developer tools console and see if there are any relevant errors there? Could you also invoke the "Git: Show Git Output" command and send me the contents of it?
Yes. This only happens in Firefox. It doesn't happen in Chromium [1], and Gnome Web (WebKit-based) [2]. <details[1] <preVersion: 1.86.0-insider Commit: Date: 2024-01-23T06:18:07.155Z Browser: Mozilla/5.0 (X11; Linux x8664) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 </pre[2] <preVersion: 1.86.0-insider Commit: Date: 2024-01-23T06:18:07.155Z Browser: Mozilla/5.0 (X11; Ubuntu; Linux x8664) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Safari/605.1.15 </pre</detailsThere seems to be.
As soon as I change to , this error pops up in the brower's console. And it seems to pop up every time I press "Refresh" in the source control pane too. <details<preUncaught (in promise) Error: Invalid comparison compare K K z w F E D C B z updateChildren Cc a promise callbackqueue Cc queue Cc W y fire z y z fire Lb wb reloadLocalUserConfiguration Hb updateValue updateValue Pc Mc b promise callbacktrigger Mc Lc ge y </pre</detailsHere it is. Although, I'm not sure how useful it is. <details<pre2024-01-23 10:40:31.442 [info] Log level: Info 2024-01-23 10:40:31.442 [info] Validating found git in: "git" 2024-01-23 10:40:31.442 [info] Using git "2.43.0" from "git" 2024-01-23 10:40:31.442 [info] git rev-parse --show-toplevel [126ms] 2024-01-23 10:40:31.442 [info] git rev-parse --git-dir --git-common-dir [9ms] 2024-01-23 10:40:31.442 [info] Open repository: /workspaces/core-base 2024-01-23 10:40:31.442 [info] git config --get commit.template [78ms] 2024-01-23 10:40:31.442 [info] git rev-parse --show-toplevel [65ms] 2024-01-23 10:40:31.481 [info] git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [22ms] 2024-01-23 10:40:31.483 [info] git rev-parse --show-toplevel [5ms] 2024-01-23 10:40:31.501 [warning] ENOENT: no such file or directory,
open '/workspaces/core-' 2024-01-23 10:40:31.523 [info] git rev-parse --show-toplevel [5ms] 2024-01-23 10:40:31.523 [info] git rev-parse refs/remotes/origin/main [23ms] 2024-01-23 10:40:31.630 [info] git status -z -uall [89ms] 2024-01-23 10:40:31.631 [info] git rev-parse --show-toplevel [70ms] 2024-01-23 10:40:31.674 [info] git rev-parse --show-toplevel [18ms] 2024-01-23 10:40:31.675 [info] git config --get commit.template [4ms] 2024-01-23 10:40:31.716 [info] git rev-parse --show-toplevel [26ms] 2024-01-23 10:40:31.718 [info] git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [12ms] 2024-01-23 10:40:31.736 [warning] ENOENT: no such file or directory, open '/workspaces/core-' 2024-01-23 10:40:31.755 [info] git rev-parse refs/remotes/origin/main [20ms] 2024-01-23 10:40:31.784 [info] git merge-base refs/heads/main refs/remotes/origin/main [30ms] 2024-01-23 10:40:31.855 [info] git status -z -uall [84ms] 2024-01-23 10:40:31.863 [info] git rev-list --count --left-right [17ms] 2024-01-23 10:40:33.111 [info] git config --local [138ms] 2024-01-23 10:40:33.
111 [warning] git config failed: Failed to execute git 2024-01-23 10:40:49.678 [info] git config --get commit.template [2ms] 2024-01-23 10:40:49.709 [info] git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [5ms] 2024-01-23 10:40:49.732 [warning] ENOENT: no such file or directory, open '/workspaces/core-' 2024-01-23 10:40:49.733 [info] git rev-parse refs/remotes/origin/main [1ms] 2024-01-23 10:40:49.768 [info] git status -z -uall [9ms] 2024-01-23 10:40:49.854 [info] git merge-base refs/heads/main refs/remotes/origin/main [2ms] 2024-01-23 10:40:49.873 [info] git rev-list --count --left-right [2ms] 2024-01-23 10:41:41.011 [info] git config --get commit.template [15ms] 2024-01-23 10:41:41.012 [info] git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [3ms] 2024-01-23 10:41:41.026 [warning] ENOENT: no such file or directory, open '/workspaces/core-' 2024-01-23 10:41:41.029 [info] git rev-parse refs/remotes/origin/main [2ms] 2024-01-23 10:41:41.049 [info] git status -z -uall [7ms] 2024-01-23 10:41:41.
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.52.1 OS Version: Windows 10 1909 Steps to Reproduce: then press to run extension any folder with some code. code lens show, then hover one of codelens. Actual Result: ! Is this an expected behavior of vscode extension? Or is there any configation to show it?
I believe this is expected behavior, however forwarding to so he can close
Yes. what tooltip to you expect when hovering over a code lens?
As , show maybe suitable I think.
Ah, I see. That actually makes sense and would be a simple change
Can I take a look at this issue and try to work on this?
This is where the dom-nodes for codelens are created: Using the title attribute on them should do the job
Is the native tooltip sufficient for the fix? Windows & MacOS :-------------------------: <img src="https://user-" width="400"Windows | MacOS :-------------------------:|:-------------------------: <img src="https://user-" width="400"| <img src="https://user-" width="400"
]- Identify accessibility bugs before check-in and make bug fixing faster and easier. #A11yTCS; #A11ySev2; #DesktopApp; #Win32; #Visual Studio Code Client; #BM-VisualStudioCodeClient-Win32-Jan2024; #WCAG1.4.11; #Non-text Contrast; #A11yWCAG2.1; Visual Studio Code insider version 1.86.0 Microsoft Windows 11 Enterprise (22H2) OS Build .3007 Visual studio insider the Visual Studio Code Marketplace, go to the GitHub Copilot extension page and click Install. a sample code and press CTRL+I to open the Copilot inline chat. that the contrast ratio of focus is on "Make request" button is (1.787:1) which is less than required. While navigating with Keyboard tab key to the "Make request" button the contrast ratio of focus is (1.787:1) which is less than required. While navigating with Keyboard Tab key to "Make request" button the contrast ratio of focus should be greater than or equal to required (3:1). Keyboard users will face difficulty while navigating through keyboard if the focus is not clearly visible to the user and ratio is less than required. !
Verified the issue in below environment: Visual Studio Code Insider Version: 1.87.0-insider (user setup) Issue is not fixed. Please find attachment for reference. Could you please confirm us in which build the fixes will be available. <img width="785" alt="203773_not fixed" src=""
The focus border now has increased contrast and is now the same colour as everywhere else in VS Code. We don't have any indication from users that this accent colour is a problem anywhere in the dark theme.
! VS Code Version: Version: 1.64.1 Commit: Date: 2022-02-07T17:17:47.733Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.13.0-28-generic OS Version: Ubuntu 20.04 Steps to Reproduce: a Jupyter notebook, just do Ctrl+H and put some strings in find and replace boxes.
Hi - Apology to bother. Is there any update on this issue or any work-around that I can do. Because without the replace-all functionality, it's becoming very hard to manage long notebooks in VSCode.
Just realized this is a regression from previously stable.
NOT Resolved in the latest stable version of code.
Not working on the latest Insiders Version: 1.66.0-insider (user setup) Commit: Date: 2022-03-29T07:31:54.286Z Electron: 17.2.0 Chromium: 98.0.4758.109 16.13.0 V8: 9.8.177.11-electron.0 OS: Windows_NT x64 10.0.
After updating to version 1.66.0 - I get the "Replace All" button activated (as in not grayed-out any more) - But it does NOT work. i.e. after clicking on the button naothing happens.
Hi, this is still not resolved after today's release to Version: 1.67.1 Below my current version details.
can you try again on VS Code Insiders? Otherwise, you'll have to wait for version 1.68.
Great its working in the Insider version. Thanks.
Issue Type: <bBug</bTesting: Steps: a with one or more npm scripts a and add one or more npm tasks but do not add a details field to each task the run tasks command that the npm scripts in have a details field shown but the npm task in does not Expected: All npm tasks/scripts to be rendered consistently. The npm task in should show the script as the detail field just like the ones in ! VS Code version: Code - Insiders 1.40.0-insider (, 2019-10-30T05:39:27.063Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (12)</summaryExtensionVersion ------ tslint1.0.44 vscode-github-releases-updater0.18.0 vscode-docker0.8.1 python2019.10. remote-containers0.82.0 remote-ssh0.47.2 remote-ssh-edit0.47.2 remote-ssh-explorer0.47.2 remote-wsl0.40.0 vscode-remote-extensionpack0.17.0 azure-account0.8.6 test-search-rg0.0.3 </details<!-- generated by issue reporter --
which of the tasks listed in your screen shot are from the If it , you have npm task detection turned on, and the script is also in your then it should show a detail (except for npm:install).
The npm install task is the one in
Sorry, seemed to close the issue by mistake while trying to paste a snippet from { "type": "npm", "script": "install", "problemMatcher": [] }
And this is in "scripts": { "test": "echo "Error: no test specified" && exit 1", "random": "do something else" },
Thank you! There is no detail to provide for install since it's not running a script defined in to pull the detail from. I figured there wasn't a good detail to show for it, but I'm all for it having a detail if there's something relevant we can put there. Is there something in particular that you want to see as the detail for the install task?
I just thought it should do similar to the scripts in the and show the script field?
I see, so it should just show "install" as the detail.
Upcoming behavior: !
<!-- 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.67.0 OS Version: Windows 10 Steps to Reproduce: Please add some margin there, I've Provided img below and pointed out that place with red clr It's Just Sticking each other !
Sorry can you clarify what you mean?
As, You can see in the img I've pointed out a terminal place with red clr circle where Source Control is there and ahead of it 1 Badge is there. So, Then it's below line and the Badge does not have any space/margin they both are sticking.
I see space between the badge and the active indicator,
I think it's too small.
I think these changes when the panel padding got updated with the secondary side bar. Not sure what else we can do besides add the padding back. It is quite tight right now.
Should be fixed now thanks to <img width="127" src="https://user-"
<img width="584" alt="image" src="https://user-"//cc for views
I assume this is nothing to do with the views instead its about how entires are rendered in list/tree. CC
Tree row contents are outside of the tree's jurisdiction, but are in fact responsibility of the widget user.
Timeline doesn't use the extension tree view and instead does it's own thing. I think works on timeline.
curious, do we have an understanding what caused this? it seems relatively recent?
Might be related to . any ideas here?
It was caused by , can you check? I see a visual difference not only with the alignment but also the spacing: Before <img width="254" alt="image" src="https://user-"After <img width="269" alt="image" src="https://user-"
it looks like timeline relies on the custom tree view css. I made a change in the nesting/ordering of elements in the tree view recently and I updated the css to reflect that. Because timeline relies on the css but doesn't actually use the custom tree view, this broke the timeline. I've opened a PR with a timeline specific css fix.
<!-- UNABLETOLOCATECOMMITMESSAGE issue --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased
<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.41 OS Version: Ubuntu 18.04 Steps to Reproduce: a debug adapter the pause feature the debug adapter and see that pause works the debug adapter using the restart button that pause no longer works <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No The commit is used to slow down fetching threads from a debug adapter. However, when using the default restart mechanism, is disposed (via and therefore no longer runs after restarting the debug adapter.
Thanks for filling this issue. Can you be so kind to fork Mock Debug and to create changes on top of it such that this issue is reproducable. Since I can not reproduce it using node - gif attached !
It looks like I was missing sending an so the same debug session was being reused after restart.
I also made this comment in the pull request: The says "A debug adapter is expected to send this event when it is ready to accept configuration requests (but not before the ‘initialize’ request has finished)." So either the specification needs to say "required" instead of "expected" or there is a bug in VS Code. VS Code doesn't seem to correctly handle the situation where the debug adapter never sends . Although the fix may be to create a new debug session object instead of the fix that I have proposed.
Simply removing the line that sends from the mock debug unfortunately extension doesn't seem to be enough to reproduce the problem, but since I found a workaround, I can't really justify spending more time on it.
did you verify that this works with the latest VS Code insiders as expected?