Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] dbux is assuming `bash` in Windows resolves to MINGW/MSYS bash

See original GitHub issue

Bug Report

Bug Summary dbux seems to assume that running bash in Windows will start some sort of MINGW/MSYS bash such as Git bash. However, by default, the only bash.exe in Windows will be the wrapper that launches /bin/bash in the default WSL distro (if WSL is enabled).

Steps To Reproduce

Make sure WSL is installed
Open some JavaScript file and click “Start DBux”
See error in terminal

Expected behavior dbux should either not require a specific kind of bash installed at all or tell the user exactly what is expected and ask for its location if it’s not in PATH.

Actual behavior dbux launches bash which by default will by C:\Windows\System32\bash.exe (a helper to launch bash inside WSL). It then fails with a misleading file-not-found error message because it launches node from the shell which is now inside WSL and passes a Windows-style path to it.

The loading box [Dbux] : New version. Installing 1 library/ies (1-3 mins)... then stays there forever.

Attachments

Screenshots

System (please complete the following information):

OS: Windows 10
Dbux VSCode Extension version: 0.6.15

(I updated the bug description based on what the actual problem is, because my initial assumption was wrong.)

Issue Analytics

State:
Created a year ago
Reactions:2
Comments:27 (27 by maintainers)

Top GitHub Comments

4reactions

CherryDTcommented, Mar 25, 2022

Thank you!

I just realized this probably (?) has nothing to do with my terminal shell being configured to WSL bash in particular, as I first assumed - instead it seems you simply invoke bash, which will be the Linux bash if WSL is installed on the system (which, in my opinion, is no edge case for a JavaScript developer nowadays).

I fixed the issue by changing the new bash path option to C:\Program Files\Git\bin\bash.exe.

(By the way: In a WSL window, running DBux works fine.)

2reactions

CherryDTcommented, Mar 24, 2022

Ah I see what you mean (I didn’t realize it’s what’s used for running the code too, I thought it was just part of the installation process), yes if it’s configurable it should be fine.

Output channel log: sorry I (apparently wrongly) thought you meant what was already in the terminal.