You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 31, 2023. It is now read-only.
If I open VS Code “in WSL” (with Remote - WSL), the Context Menu > Bitburner: Push File To The Game function has no effect. The file does not appear in game. If I open it “in Windows,” it works as advertised.
This is true whether the files are in the Windows or WSL filesystem.
I'm on Win 10 21H2, WSL2 with Ubuntu.
The text was updated successfully, but these errors were encountered:
Per a reply in Discord, I tried "host": "0.0.0.0" in config.json. The log shows Starting http server on port 9990 - listening on 0.0.0.0, but the behavior described above does not change.
At first, I misread that as "my solution only works for names with .local at the end". But you were telling them what to run to print the value your solution needs.
Wouldn't the true DNS name (FQDN) be better? I mean, yeah it typically defaults to $(hostname).local. But it might differ...and I don't know off the top of my head the correct way to query that name in Linux.
It's annoying that text based names for computers are so complex still.
If I open VS Code “in WSL” (with Remote - WSL), the Context Menu > Bitburner: Push File To The Game function has no effect. The file does not appear in game. If I open it “in Windows,” it works as advertised.
This is true whether the files are in the Windows or WSL filesystem.
I'm on Win 10 21H2, WSL2 with Ubuntu.
The text was updated successfully, but these errors were encountered: