tstack
VSCode Terminal shows "error no error information"
lnav version
~~v0.12.2 is the latest~~
I have v0.12.4 installed via [eget](https://github.com/zyedidia/eget) tstack/lnav -f lnav --to=/usr/local/bin/lnav
Describe the bug
root@72a3f2f57b04:/workspace# env TERM=xterm-256color COLORTERM=24bit lnav -I .devcontainer/lnav/ /var/log/*.log
✘ error: unable to open TUI
reason: unable to initialize notcurses No error information
= help: The TERM value of “xterm-256color” is not known. Check for your terminal in https://github.com/dankamongmen/notcurses/blob/master/TERMINALS.md or use “xterm-256color”
That should say everything. I am a little puzzled... Initially, I tried without setting TERM and COLORTERM but got the same issue.
To Reproduce
- Create a project but on a remote server
- Connect to that server using "Remote - SSH" in VSCode
- Create, build and attach to a DevContainer
- In that DevContainer, install
lnav - Use
lnavand observe the error
Here's the full environment (with sensitives snipped):
SHELL=/bin/bash
COLORTERM=truecolor
TERM_PROGRAM_VERSION=1.98.1
SURREAL_DATABASE=<snip>
WORKSPACE_FOLDER=/workspace
SURREAL_PASS=<snip>
REMOTE_CONTAINERS_IPC=/tmp/vscode-remote-containers-ipc-56576cfa-3366-4ff3-8296-e6ce39226493.sock
PWD=/workspace
SURREAL_CLIENT_IP=socket
NODE_ENV=development
SURREAL_NO_BANNER=true
TZ=Europe/Berlin
VSCODE_GIT_ASKPASS_NODE=/vscode/vscode-server/bin/linux-x64/2fc07b811f760549dab9be9d2bedd06c51dfcb9a/node
container=podman
HOME=/root
LANG=en_US.UTF-8
CARGO_HOME=/usr/local/cargo
REMOTE_CONTAINERS=true
GIT_ASKPASS=/vscode/vscode-server/bin/linux-x64/2fc07b811f760549dab9be9d2bedd06c51dfcb9a/extensions/git/dist/askpass.sh
GOROOT=/usr/local/go
SURREAL_USER=<snip>
VSCODE_GIT_ASKPASS_EXTRA_ARGS=
TERM=xterm-256color
RUSTUP_HOME=/usr/local/rustup
REMOTE_CONTAINERS_SOCKETS=["/root/.gnupg/S.gpg-agent"]
VSCODE_GIT_IPC_HANDLE=/tmp/vscode-git-67f35156c5.sock
SURREAL_STRICT=true
GOPROXY=https://proxy.golang.org,direct
SHLVL=2
VSCODE_GIT_ASKPASS_MAIN=/vscode/vscode-server/bin/linux-x64/2fc07b811f760549dab9be9d2bedd06c51dfcb9a/extensions/git/dist/askpass-main.js
BROWSER=/vscode/vscode-server/bin/linux-x64/2fc07b811f760549dab9be9d2bedd06c51dfcb9a/bin/helpers/browser.sh
PATH=/root/.console-ninja/.bin:/usr/local/go/bin:/root/go/bin:/vscode/vscode-server/bin/linux-x64/2fc07b811f760549dab9be9d2bedd06c51dfcb9a/bin/remote-cli:/usr/local/go/bin:/root/go/bin:/usr/local/cargo/bin:/usr/local/go/bin:/root/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
SURREAL_HIDE_WELCOME=true
GOPATH=/root/go
SURREAL_NAMESPACE=<snip>
TERM_PROGRAM=vscode
SURREAL_AUTH=true
VSCODE_IPC_HOOK_CLI=/tmp/vscode-ipc-22e296b4-2fce-4b36-838d-a11080dbb1cf.sock
_=/usr/bin/env
OLDPWD=/proc/319
At startup, lnav sends some queries to the terminal to figure out what it is. Normally, the terminal responds very quickly. However, the VS Code terminal seems to be really slow in sending responses (it sends a bunch of small responses instead of big batches), so lnav timed out. I've increased the timeout, but .. that's not really an ideal solution...
I spent three hours trying to compile with the recent commit; but my maschines all OOM'd. In fact, one of them is still crawling. I am surprised it hasn't been OOM killed yet...probably a quirk due to that one running as a container in Proxmox.
Do you happen to have an x86-64 build against glibc? I fear I may not have the RAM (here at work, at least - i might but at home) required for the linking.
Thank you!
...forgot to switch accounts, apologies. Either way, I will try to see if I can build at home, but if you happen to have a build, that'd be neat!
FWIW, I got this error today within tmux:
Works fine within Ghostty. But, this used to work inside tmux.
在 Ghostty 中运行良好。但是，它以前在 tmux 中运行良好。
Interestingly enough, version 0.9.0 works without issue. I'm able to repro without SSH (but using devcontainer) on 0.12.4. It seems resolved on 0.13.0-beta4
same here, does not work in tmux with alacritty
FWIW, I got this error today within tmux:
Works fine within Ghostty. But, this used to work inside tmux.
