warpdotdev / Warp

Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
https://warp.dev
Other
20.23k stars 335 forks source link

Cannot scroll when in second SSH session (from another SSH session) e.g. Jumpbox #4436

Open ElijahLynn opened 4 months ago

ElijahLynn commented 4 months ago

When I SSH into a Jumpbox (from local fish shell) scrolling works fine, but if I SSH into another server from the Jumpbox then scrolling does not work.

Discord username (optional)

No response

Operating System

MacOS

Operating System and Version

14.1.2 (23B92)

Local Shell Version

Fish 3.6.1

Remote Shell Version

4.4.20(1)-release

Warp Version

v0.2024.02.27.08.01.stable_03

I have tried commenting out my system & user rcfiles and warp still will not bootstrap

Screenshots

No response

Include shell xtrace output

No output in Fish with set WARP_DEBUG_MODE 1

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

No, this same issue happens in Warp and other terminals.

Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa

None

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

dannyneira commented 4 months ago

There are some known issues with the nested SSH session, so you may be best suited by disabling the Wrapper in Settings > Features > SSH Wrapper. You'll lose Warp features like blocks in SSH session, but the jumpbox nested sessions should work like in a normal terminal.

ElijahLynn commented 4 months ago

Thanks, really appreciate the workaround. I just tested with and without the wrapper, on a different server, (I don't have authorization to access the server I experienced the issue with right now). But next time it comes up I'll be sure to try it as I think that will work!

ElijahLynn commented 3 months ago

Also, because of your response, I realized this too. https://github.com/warpdotdev/Warp/issues/4466