-
Notifications
You must be signed in to change notification settings - Fork 797
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
Localhost port forwarding bug reappeared #9947
Comments
I am experiencing the same issue. For me it manifested when attempting to use kubectl to hit a kind (or docker-desktop-k8s) cluster. I downgraded to 1.1.6 to work around it for the time being. |
/dupe #9944 Fix is inbound. |
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
@benhillis Are you sure it's a dupe? The issue looks completely different... |
Anyway, it is indeed fixed in WSL 1.2.1.0. Thank you! |
Thank you @nidrissi. It worked for me as well by using WSL 1.2.1.0. |
@benhillis, #9944 is regarding |
Windows Version
Microsoft Windows [version 10.0.22624.1546]
WSL Version
1.2.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
openSUSE Tumbleweed
Other Software
Repro Steps
In the VSCode LaTeX-Worskhop extension, open the PDF viewer.
Expected Behavior
The PDF should appear in a VSCode webview.
Actual Behavior
The tab stays blank. Opening the viewer's URL manually in Edge gives a "connection refused" error. See James-Yu/LaTeX-Workshop#3833 for someone with the same issue.
The issue had appeared in WSL 1.1 (see James-Yu/LaTeX-Workshop#3668) and was then fixed in v1.1.3 (see #9508). It seems that the faulty behavior was re-introduced in WSL 1.2.0.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: