Lando commands fail silently when run from a code-server terminal

OS/Web Information

• Web Browser: Edge, Safari (iOS)
• Local OS: Windows, iPadOS
• Remote OS: Windows 10
• Remote Architecture: WSL2 running Ubuntu 20.04, ZSH (same issue with Bash)
• code-server --version: 3.9.3 fe2dc2deb08e378069891b622bb62ad1d261d1b1

Problem description

For reasons I don’t understand, a single specific terminal command won’t run (silently fails) when executed under code-server’s terminal. This does not happen in the ‘normal’ terminal and does not happen in VS Code’s terminal. They are all using exactly the same system (confirmed but entering a command in one, then cycling back through the history in another and confirmed the same commands are executed).

Steps to Reproduce

1. Install Lando
2. Run lando version in any terminal (except the terminal of code server) and confirm there is output
3. Open code server and enter lando version in the terminal and confirm there is no output

Expected

Terminal should output:

$ lando version
$ v3.1.2

Actual

There is no output after running the command:

$ lando version

An exit code of 4 is shown if $? is entered afterwards

Logs

I ran:

code-server --log debug and entered the command in the terminal.

1. The most recent files from ~/.local/share/code-server/coder-logs - **There are two files here (stderr, stdout), both empty.**
2. The browser console. **Attached in logs.zip below**
3. The browser network tab. **Attached in logs.zip below**

logs.zip

Screenshot

lando version in the WSL2 terminal:

lando version in the code-server terminal:

Notes

This issue can be reproduced in VS Code: No, the issue does not happen in VS Code.

[tanc]

I’ve updated the issue on the Lando side, lets see what the maintainers think over there. A very curious issue!

[tanc]

Yes I don’t think it’s lando code itself… I’m just trying different tags to see if any don’t work. I suspect its something about the way its packaged and installed but no idea why that would be an issue at this point.

Confirmed, running off different tags from the source (and doing a yarn install to be sure) doesn’t seem to make any difference, the tagged version is correctly displayed in code-server’s terminal.