-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Links sometimes stop working completely in terminals #184046
Comments
Thanks for creating this issue! To help narrow it down, please take the time to follow below steps. Thanks a lot and happy coding 🙏 Is the issue caused by an Extension?Stop VS Code and from the command line (NOT the integrated terminal in Code), execute: If you see it is an issue with the extension, please run the command Please report the issue to the extension causing this. Is the issue caused by VS Code Core?If the issue is not caused by an extension, it is maybe caused by your configuration. Try to run If it still reproduces, it was maybe fixed already in our nightly release. Please download from https://code.visualstudio.com/insiders/ and see if you can reproduce the issue. Finally, to help us narrow down what change caused the issue, please run the following command to find the build. It will start previous releases of VS Code insiders to see where the regression was introduced:
Thanks! |
Was this just a one off or is it reliably reproducible? There is some issue where hovers/underlines will stop working sometimes, but I think you can still ctrl/cmd+click them in that case. |
This is definitely reproducible, but I'm unable to narrow down which extension causes it. I also noticed that it happens only after reloading the extension host. There are no links at all in that case, ctrl+click does nothing.
I've now done the bisect 4 times, each time waited longer after reloading in case this is just happening with a delay. The behavior is always the same. From that, I'd say it is caused by some extension, not VSCode itself |
I've seen this as well but very rarely, sometimes links are just completely broken for the terminal. I did notice last time that the link detection was happening by checking the logs, but no underlines showed up |
Any info I could collect when it happens? |
I mainly need a repro case to debug against. Some info which would be good to clarify:
|
Links are detected it seems:
But I cannot CTRL+click them - nothing happens, no underline, no navigation. |
This is probably extension-related, as I couldn't reproduce on insiders until I started the settings sync with stable. If there's a way that you can load VSCode with the same extensions I have, you should be able to reproduce this way: Empty folder with file test.txt:
Repro:
|
If this is true I wonder if the extension is never resolving the request and our timeout doesn't work or something. This is good info thanks! I'll try have a look into this again next week |
I just tested and it looks like extensions can cause this. I added |
This issue happens quite consistently as of (1.84.0). It seems to be based upon how long the terminal is open or how much content was displayed in the terminal. My feeling is that it is the later. I do not believe it is a third party extension issue, since restarting Extension-Host doesn't not fix the issue. The workaround is to delete and re-open the terminal. Typical scenario: |
Might be related to #203437 |
If this is verifiable by successfully opening a link from a node process then this is verified. |
The repro for this was difficult, I think the fast that I haven't seen it happen in 3 weeks is good enough for verification. We can always reopen if it pops back up. |
I haven't seen this happen in a few weeks now 👍🏻 |
Type: Bug
In Node.js processes in the integrated terminal, CTRL-hovering a potential link no longer turns it into a link. This makes it very cumbersome to go to errors that TypeScript reports. The same text in a bash terminal is working fine:
node-zwave-js-1685615971489.mp4
VS Code version: Code 1.78.2 (b3e4e68, 2023-05-10T14:47:05.613Z)
OS version: Linux x64 5.19.0-42-generic snap
Modes:
Sandboxed: Yes
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
Extensions (70)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: