Skip to content
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

Closed
1 of 2 tasks
nidrissi opened this issue Apr 11, 2023 · 7 comments
Closed
1 of 2 tasks

Localhost port forwarding bug reappeared #9947

nidrissi opened this issue Apr 11, 2023 · 7 comments

Comments

@nidrissi
Copy link

Windows Version

Microsoft Windows [version 10.0.22624.1546]

WSL Version

1.2.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.90.1

Distro Version

openSUSE Tumbleweed

Other Software

  • Visual Studio Code v1.77.1
    • WSL remote extension v0.77.0
    • LaTeX-Workshop v9.8.2

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

@tonyjthomas
Copy link

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.

@benhillis
Copy link
Member

/dupe #9944

Fix is inbound.

@microsoft-github-policy-service
Copy link
Contributor

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!

@nidrissi
Copy link
Author

@benhillis Are you sure it's a dupe? The issue looks completely different...

@nidrissi
Copy link
Author

Anyway, it is indeed fixed in WSL 1.2.1.0. Thank you!

@alanlivio
Copy link

Thank you @nidrissi. It worked for me as well by using WSL 1.2.1.0.
Best,

@jiasli
Copy link
Member

jiasli commented Apr 21, 2023

/dupe #9944

Fix is inbound.

@benhillis, #9944 is regarding 0x80370114 error. This issue doesn't seem to be a duplicate of #9944. Perhaps a duplicate of #9805?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants