jiebi/CodeConvo huggingface dataset:
I am having an issue with this as well since updating versions. I attached some images. attempting to drag selected text into the object ! once selected tooltip stays in place permanently blocking destination ! I think once you hold down left click on a selection to start moving, the tooltip should always disappear. At least that is the behavior that you would expect in most applications.
+1 to this, also experiencing the same issue after updating versions
Also having this issue. The Hover Hide Delay is using the Hover Delay instead, so if you have a long delay before the tooltip appears, you will have a long delay before it disappears. If you set the Hover Delay to 0 and the Hover Hide Delay to 1000, should see the tooltip appear and disappear instantly
I have noticed and issue when using VS Code, in which the clicking outside of a tooltip will no longer dismiss hover tooltips. This occurs after leaving VS Code open for a while, including after a sleep/hibernate cycle. When this happens I have to restart VS Code, otherwise, clicking anywhere, including to initiate text selection does not dismiss any existing tooltip and the tool tip then interferes with the selection process. Perhaps there is a bug that is causing the described tooltip/click behavior to break after leaving VS Code open for some time. It might be related to this issue of tooltips being more sticky than intended. Version: 1.92.1 (user setup) Commit: Date: 2024-08-07T20:16:39.455Z Electron: 30.1.2 ElectronBuildId: Chromium: 124.0.6367.243 20.14.0 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.
Looked through the code a bit, and I think this is the issue this.hoverSettings = { enabled: hoverOpts.enabled, sticky: , hidingDelay: }; should be this.hoverSettings = { enabled: hoverOpts.enabled, sticky: , hidingDelay: hoverOpts.hidingDelay }; in and
supports your theory.
Hi thanks a lot for finding this error in the code. If you would like you can make a PR containing this finding, so we can merge your fix and you can participate as a community member in the project. If not I will make the fix that you mention :). Thanks for the catch.
Type: <bBug</bIn the latest release syntax highlighting in html files with included JavaScript is so far off it's unusable. I have a comment (which should be green) Syntax highlighting has the the correct color. is dark blue. is green again. is a different color blue. The color choices and what parts of words are highlighted seems random. VS Code version: Code 1.71.2 (, 2022-09-14T21:07:15.900Z) OS version: Darwin arm64 21.6.0 Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (105)</summaryExtensionVersion ------ html-snippets0.2.1 vscode-languagetool3.8.0 vscode-languagetool-en3.8.0 vscode-icalendar1.0.1 vscode-color0.4.5 code-gnu-global0.2.2 simple-react-snippets1.2.7 vscode-reveal-hugo0.2.5 doxdocgen1.4.0 vscode-postgresql-client25.7.11 vscode-mac-color-picker1.1.0 vscode-eslint2.2.6 vscode-instant-markdown1.4.7 vscode-springboot-snippets1.2.0 xml2.5.1 rust-syntax0.6.1 vscode-html-css1.13.1 EditorConfig0.16.4 vscode-npm-script0.3.28 esp-idf-extension1.5.0 vscode-diff1.4.2 markdown-table-formatter2.2.4 change-case0.0.6 vs-code-http-server-and-html-preview2.2.2 copilot1.47.6882 go0.35.2 CppSnippets0.0.15 rest-client0.25.1 flux1.0.4 mediawiki0.0.4 tablegenerator1.0.4 better-cpp-syntax1.15.19 react-component1.1.0 vscode-hacker-typer0.1.1 diff-tool0.0.1 hugo-shortcode-syntax1.0.0 vscode-github0.30.7 cortex-debug1.6.5 vscode-language-babel0.0.36 vscode-clang0.2.4 vscode-http-client0.34.0 prettify-json0.0.
3 mongodb-vscode0.9.3 mongoose-os-ide0.6.0 vscode-docker1.22.1 csharp1.25.0 data-workspace-vscode0.3.0 mssql1.16.0 sql-bindings-vscode0.3.0 sql-database-projects-vscode0.19.0 python2022.14.0 vscode-pylance2022.9.40 jupyter2022.8. jupyter-keymap1.0.0 jupyter-renderers1.0.9 remote-containers0.251.0 remote-ssh0.84.0 remote-ssh-edit0.82.0 remote-wsl0.66.3 vscode-remote-extensionpack0.21.0 cmake-tools1.12.27 cpptools1.12.4 cpptools-extension-pack1.3.0 live-server0.4.1 vsliveshare-pack0.4.0 vscode-react-native1.9.3 sqltools0.25.1 sqltools-driver-pg0.3.0 vetur0.36.0 particle-vscode-core1.15.4 particle-vscode-pack1.15.4 particle-vscode-snippets1.15.4 vscode-boot-dev-pack0.1.0 vscode-concourse1.39.0 vscode-manifest-yaml1.39.0 vscode-spring-boot1.39.0 platformio-ide2.5.4 r-debugger0.4.7 java1.10.0 r2.5.3 wordcount0.1.33 bash-debug0.3.9 rust-analyzer0.3.1221 sockscode-vscode1.0.1 stackery1.1.4 spellchecker1.4.0 markdowntable0.10.2 html-preview-vscode0.2.5 cmake0.0.17 vscode-arduino0.4.12 vscode-java-debug0.44.0 vscode-java-dependency0.21.0 vscode-java-pack0.25.2 vscode-java-test0.37.1 vscode-maven0.39.0 vscode-spring-boot-dashboard0.7.1 vscode-spring-initializr0.11.0 codetour0.0.58 gistfs0.4.1 vscode-wakatime19.3.0 full-react-snippets1.4.2 vscode-java-saber0.
1.2 markdown-all-in-one3.4.3 vscode-aspell0.1.4 propertylist0.0.2 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
<img width="940" alt="Screen Shot 2022-09-28 at 6 56 06 PM" src="https://user-"<img width="879" alt="Screen Shot 2022-09-28 at 6 15 54 AM" src="https://user-"
Does this reproduce in the with all ?
It sure does. <img width="517" alt="Screen Shot 2022-09-28 at 7 12 08 PM" src="https://user-"<img width="705" alt="Screen Shot 2022-09-28 at 7 13 25 PM" src="https://user-"
Please share the text of file that causes this
It ain't pretty ...
It's a template file for Hugo. Specifically a file called
same as semantic highlighting is broken for some reason
Reproduced with The special thing that there's a new line right after
Version: 1.78.0-insider (user setup) Commit: Date: 2023-04-04T09:32:52.453Z Electron: 22.4.3 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0. Sandboxed: Yes run from a Windows command prompt The tunnel starts and prints open VS Code, and open the output Note that the output is stuck at Missing are the message and the info that the tunnel is attached The UI thinks the tunnel is still connecting. Sometimes this also works, but when I try it, most of the time it is stuck
Can you please enable trace logging and share the output?
Nothing extra messages shown when the Desktop tunnel attaches:
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Still a problem in Version: 1.78.0-insider (user setup) Commit: Date: 2023-04-12T05:19:38.288Z Reproduces every time I try it
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
<!-- 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!
I'm still not seeing info in the log in VS Code that the tunnel is attached after from the command line and seeing the "Open this link in your browser". <img width="945" alt="image" src=""
the tunnel will not start unless you "Turn on Remote Tunnel Access"
<img width="730" alt="image" src=""Looks good to me after enabling tunnels in VS Code
Thanks. Enabling Tunnels in VS Code fixed it.
I got into screen reader optimized mode on Windows by using NVDA, but after closing NVDA, I don't know how to leave that mode. I tried clicking on the indicator in the taskbar, and also tried searching "accessibility" in the command palette for a command that would toggle it off. !
clicking on the indicator in the taskbar should work we should also have a toggle command in the command palette so that clicking isn't required and can reference that command in this help menu !
fyi for any input
Agree with the above. Also on vscode restart you should no longer be in screen reader mode if that is happening, it is a bug. take into account that the accessibility help dialog shown in the screenshot has not been polished since we introduced it. We could make sure the text is more concise and user friendly. Visually it should not be polished since this is targeted for screen reader users.
Try to set a custom keybinding for this command - I find it very handy
How do I get that status bar entry to show? I tried the following: Turn on NVDA when Manually set `"editor.accessibilitySupport": "on"
This command should work !
That still doesn't cause the status bar entry to show for me. I've checked the status bar show/hide menu and it's not in there either.
any interesting settings? https://user-
I was about to say I have the same issue, but then noticed that I had to go to a text editor to test out the feature. I was running the toggle command in the Settings editor.
Not being in a text editor was the problem! I was either in the settings editor or the endgame notebook.
<!-- 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.43.0 OS Version: n/a I have the set to in my settings: Given a Does not produce any warnings as expected. However in : The linter says
This has the same root cause as : script are owned by the html extension instead of by the JavaScript extension. Fixing that is difficult However we could have a small fix that just makes html understand the setting. Marking this as help-wanted
Hello I'd like to try my hands on fixing this issue. Can you give some pointers as to which files are good places to start?
This change will need to be made in the HTML extension Here's where we configure TypeScript for the html extension: You should: Pass the value for in with the initial configuration Make sure that the language service updates its value for when the VS Code setting changes
Is there another way to get the setting value other than vscode.workspace.getConfiguration()? The 'vscode' module cannot be found when I try to import it into javascriptMode. I think 'vscode' would have to be as a dependency in in order to import 'vscode'.
Right now I'm passing in a default 'false' for experimentalDecorators in the initial configuration and passing the settings into getJavascriptMode.doValidation to update compilerOptions and calling ts.createLanguageService(host) every time doValidation is invoked. It has the expected behavior, but is there a better way to update the compiler options without creating the service every time it runs validation?
Is called when the file is changed? If it is, try updating the object that it returns
I am reproducing this error now with the following code: I realize this is known, but I will add the mention with respect to . Here is the relevant docs page, if a person wanted to make a unit test using If anyone finds this in the future, if is set in , it should suppress this error. Additionally, both and files, in the root of the project, take precedence over that setting.
Quick pick and events are disposables: is a listeners are : , , , , , A few instances of pickers or events not being disposed or registered as disposable: [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] //cc
Thanks for catching these just taught me that there's a better way to use the quick pick API - with and that will avoid this
Interesting, curious to see how that change looks like, I have a lot more places:
! I see this sometimes, but it often gets fixed if I try again, or close and reopen the editor, etc. Right now it keeps happening and it's just impossible to click the hover. I don't know how this API works but I assume this is on vscode's side. Happy to set breakpoints and debug
I couldn't reproduce this so I'm not sure what's the root problem. However, I'm saving here a patch which simulates a hover very similar to the one in the gif: <img width="1141" alt="image" src="https://user-"diffn- editor.focusNotebookCell(newCell, newFocusMode, { focusEditorLine: 1 });n+ await editor.focusNotebookCell(newCell, newFocusMode, { focusEditorLine: 1 });n
I tried for quite a while but couldn't repro. I think there might be some settings that cause the issue reproduce. Does this reproduce when you comment out all your user settings?
Yeah, it reproes with all settings commented out
Thanks to via we could find a repro. Reproduces consistently when hovering at the end of the line: It turns out it has to do with the range the hover provider returns. If the hover provider returns a range that spans one line above the hover request, the hover will render one line above. If the hover provider returns a range that spans two lines above the hover request, the hover will render two lines above, etc. Here's a simplified patch: https://user-
To verify, use gitlens and hover over the end of the line at
Works great but raises the question, why does gitlens return a hover with a multiline range? And I get a highlight in this region, but it blinks and disappears on line 919, and on other lines, no highlight. !
PR to improve the highlight range at
I'm still seeing the original issue at
a deprecated extension, for example Bracket Pair Colorizer extensions viewlet -notice how it is not very visible that the extension is deprecated. If the user wants to migrate they have to click on "configure these settings" and uninstall the extension 's solve both of these things by rendering a "Migrate" button for deprecated extensions that have alternatives The migrate button would be similar to the Update button in looks, but it would either: Install the alternative extension, uninstall the deprecated one Uninstall the deprecated extension, open settings view with the desired settings shown
I do not like Migrate button for an extension like Bracket Pair Colorizer that needs settings to configured. It felt little weird to me enabling Migrate button for this extension and opening settings editor but not applying any settings to migrate. Hence I enabled this button only for those extensions with alternate extensions <img width="1120" alt="image (2)" src="https://user-"
that makes great sense, thanks! I plan to try this out as soon as there is a new insiders out. Feel free to close this issue then :)
I just tried the latest insiders which should have your changes. However I do not see the Migrate button in the Extensions details view. Also it would be cool if the button was also in the extensions viewlet. Similar to the button. !
Its because alternate extension is already installed and migrating is just uninstalling the the deprecated extension. I thought it might be too aggressive to show in Extensions Viewlet. What if users do not want to migrate and they always see it in extensions viewlet?
you are right. When I uninstall eslint all is good and the button gets rendered in the extension details - cool! Extensions viewlet - as for users not wanting to migrate and still seeing it - I think that is fine. It is the same if you do not want to update and you always see "reload required". It is an update, it is just an update to a different extension. I do not find this too aggressive, especially since we want to push users off deprecated extensions.
Makes sense. Showing Migrate action in extensions view (without extension name) <img width="293" alt="image" src="https://user-"
Awesome, thanks! Let's see what the users says about the full flow and how it goes during endgame :)
Type: <bBug</bCC In inline Copilot chat, "Regenerate" button is not readable by some screen readers, such as JAWS. This is because the button is labeled with title attribute. Please add aria-label so that JAWS can recognize the label. For better communication, I have recorded a gif: ! VS Code version: Code - Insiders 1.86.0-insider (, 2023-12-20T05:36:57.756Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (116)</summaryExtensionVersion ------ vscode-openapi4.19.2 android-dev-ext1.3.2 aiprm-lang0.0.2 Bookmarks13.4.2 openscad1.2.2 spellright3.0.118 zoterolatex0.4.1 mermaid-markdown-syntax-highlighting1.6.0 doxdocgen1.4.0 vscode-markdownlint0.53.0 vscode-eslint2.4.2 vscode-quick-select0.2.9 vscode-deno3.30.0 gitlens14.6.1 EditorConfig0.16.4 prettier-vscode10.1.0 vscode-firefox-debug2.9.10 shell-format7.2.5 vscode-google-translate1.4.13 codespaces1.16.5 copilot1.143.601 copilot-chat0.12. remotehub0.62.0 vscode-github-actions0.26.2 vscode-pull-request-github0.79.
cloudcode2.2.1 overleaf-workshop0.6.1 cslpreview0.2.2 easy-snippet0.7.5 path-autocomplete1.25.0 latex-workshop9.16.1 lilypond-syntax0.1.1 scheme0.2.0 better-cpp-syntax1.17.2 language-julia1.65.2 google-search0.0.1 vscode-lua-format1.3.8 lilypond-formatter0.2.3 lilypond-pdf-preview0.2.8 lilypond-snippets0.1.1 vslilypond1.7.3 zotero0.1.11 git-graph1.30.0 azure-dev0.8.0 vscode-azureappservice0.25.1 vscode-azurecontainerapps0.6.1 vscode-azurefunctions1.13.1 vscode-azureresourcegroups0.8.3 vscode-azurestaticwebapps0.12.2 vscode-azurestorage0.15.3 vscode-azurevirtualmachines0.6.5 vscode-cosmosdb0.20.0 vscode-docker1.28.0 vscode-edge-devtools2.1.3 black-formatter2023.7. flake82023.10.0 isort2023.11. python2023.23. vscode-pylance2023.12.101 jupyter2024.1. jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.329.0 remote-ssh0.108. remote-ssh-edit0.86.0 remote-wsl0.81.8 vscode-remote-extensionpack0.25.0 azure-account0.11.6 azure-repos0.38.0 cmake-tools1.16.32 cpptools1.19.1 cpptools-extension-pack1.3.0 js-debug-nightly2023.12.1817 powershell2023.11.1 remote-explorer0.5. remote-repositories0.40.0 remote-server1.6.
vscode-github-issue-notebooks0.0.130 vscode-node-azure-pack1.2.0 vscode-selfhost-test-provider0.3.22 vscode-serial-monitor0.11.0 vscode-speech0.3. vsliveshare1.0.5900 windows-ai-studio0.2.1 autodocstring0.6.1 pandocciter0.10.3 shiny-python0.1.5 shinyuieditor0.5.0 quarto1.109.0 r-debugger0.5.4 java1.25.1 vscode-xml0.26.1 vscode-yaml1.14.0 r2.8.2 multi-command1.6.0 AudioQ0.0.2 vscode-deepl1.0.10 abc-music0.4.0 lua3.7.3 latex-utilities0.4.10 cmake0.0.17 vscode-terminal-here0.2.4 windows-terminal0.7.0 errorlens3.16.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.2.30 vscode-arduino0.6. vscode-java-debug0.55.0 vscode-java-dependency0.23.3 vscode-java-pack0.25.15 vscode-java-test0.40.1 vscode-maven0.43.0 markdown-all-in-one3.5.1 grammarly0.25.0 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Thank you for the issue JooYoung. I cannot access the gif because it seems to be a private link.
Type: <bBug</bThis issue is related to the Julia extension. I filed an issue , but I also filing it here (as suggested by As per the initial post of the above link, all extension work perfectly fine when the Julia extension is disabled. here are dmp files as per VS Code version: Code 1.79.2 (, 2023-06-14T08:57:04.379Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (50)</summaryExtensionVersion ------ rainbow-brackets0.0.6 vscode-django1.10.0 python-environment-manager1.0.4 python-extension-pack1.7.0 code-runner0.12.0 copilot1.94.220 vscode-github-actions0.25.8 vscode-pull-request-github0.66.2 nbpreviewer1.2.2 language-julia1.47.2 vsc-python-indent1.18.0 vscode-github0.30.7 vscode-opn1.1.2 MagicPython1.1.0 vscode-azureappservice0.24.9 vscode-azureresourcegroups0.7.5 vscode-docker1.25.2 csharp1.26.0 isort2022.8.0 python2023.10.1 vscode-pylance2023.6.40 jupyter2023.5.
jupyter-keymap1.1.2 jupyter-renderers1.0.15 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.295.0 remote-ssh0.102.0 remote-ssh-edit0.86.0 remote-wsl0.79.5 vscode-remote-extensionpack0.24.0 azure-account0.11.5 cmake-tools1.14.34 cpptools1.16.3 cpptools-extension-pack1.3.0 powershell2023.6.0 remote-explorer0.4.0 remote-server1.2.1 autodocstring0.6.1 r-debugger0.5.4 r2.8.1 vscode-open0.1.0 spellchecker1.4.0 python0.2.3 rmarkdown0.0.14 cmake0.0.17 vscode-counter3.2.1 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 jinja0.0.8 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
As mentioned in the linked issue, it happens for me as well. I can reproduce it with Insiders version too and the same happens with a few older julia-vscode extensions I tested. <details<summaryVS Code version</summary</details
There seems to be an issue with spawning a process. The symbolicated logs seem to have the same form.
I'd expect that this happens when we try to spawn the Julia process that powers the LS. Any chance we can debug this further? I assume we can't handle libuv failing to spawn a process anywhere in the extension code, right?
As asked in the I want to add that I can reproduce this as well. From the linked thread:
Sorry for the delayed response, can you please provide the output of the following steps to understand the error 1) In a terminal set the following env variable 2) Launch VSCode from the same terminal session with arguments that redirect stdout and stderr to a file as seen below, replace the file paths where appropriate Additionally, once the extension host crashes open command palette in VSCode and run and attach the output from the tab of the developer tools that got opened.
unfortunately this is a fatal error that cannot be handled in the application layer. But we should be able to see the output of from the above logs.
I have done this, see attached.
Same here
Thanks for the logs, in both cases the launching of child process triggers a fatal error from at due to . I would like to understand if this can repro with outside VSCode since we haven't done any modification to the spawn API. I have simplified the Julia language server process spawn call from your logs into the following script, can you run it with node v18.15.0 which can be downloaded from , the steps would be 1) Save the following script to 2) Install v18.15.0 3) From terminal, run and attach the generated output
Apparrently Julia expects 8 arguments. Not sure why though.... if length(Base.ARGS) != 8 error("Invalid number of arguments passed to julia language server.") end
can you help with above error, I would like to create a minimal repro outside VSCode since this is an issue with
It seems we need additional arguments in in the .js file see or here
I two empty arguments in the file However, I have no idea if these arguments are relevant. Then things seem to work Are we expecting the server to shut down at the end? EDIT: the process only shuts down if I hit enter. If I don't press any key it keeps running and the last message is 'Received new data from Julia Symbol Server..." output is:
Thanks for fixing the test case No, I was expecting the error to show up
Can you run our bisect tool in the terminal . In each step install the Julia extension (if not present) and if the extension host terminates with the above error, mark it as bad commit. This would help us narrow down if a change from our side introduced the regression.
Looking at the above, the argument right after is In the test case, I set this argument to empty though
I think it is fine to skip the pipe name, looking at the code it is only responsible for monitory crashes from the language server.