Discord username (optional)
No response
Operating System
MacOS
Operating System and Version
13.3.1
Local Shell Version
5.9
Remote Shell Version
5.9
Warp Version
v0.2023.05.18.01.08.stable_04
I have tried commenting out my system & user rcfiles and warp still will not bootstrap
Screenshots
No response
Include shell xtrace output
There's not much on the output, but...
WARP_DEBUG_MODE=1 ssh RDbvv6bB8YDL9KexhQ3ACCwTA@nyc1.tmate.io
Invalid command
Connection to nyc1.tmate.io closed.
Not sure how relevant it is, but it can be easily reproduced by installing tmate, and starting a new session on a new Warp tab (it works fine hosting the session!), then copying the ssh session (Warp fails with both the normal and readonly addresses), and trying to connect using a new Warp tab.
Connection will work normally by invoking a subshell and running ssh through it, though.
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa
None
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None
Discord username (optional)
No response
Operating System
MacOS
Operating System and Version
13.3.1
Local Shell Version
5.9
Remote Shell Version
5.9
Warp Version
v0.2023.05.18.01.08.stable_04
I have tried commenting out my system & user rcfiles and warp still will not bootstrap
Screenshots
No response
Include shell xtrace output
There's not much on the output, but...
Not sure how relevant it is, but it can be easily reproduced by installing
tmate, and starting a new session on a new Warp tab (it works fine hosting the session!), then copying thessh session(Warp fails with both the normal and readonly addresses), and trying to connect using a new Warp tab.Connection will work normally by invoking a subshell and running ssh through it, though.
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa
None
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None