Open jbotello7381 opened 1 year ago
Thanks for submitting @jbotello7381 , Sorry to hear about this idrac connection issue, we'll bring up with Engineering and post any updates/followup on this thread.
@jbotello7381 We suggest you explicitly use /usr/bin/ssh
when connecting to a non-Bourne shell, or disable the SSH wrapper if that's too much of a hassle.
See more here: https://docs.warp.dev/features/ssh
and here: https://docs.warp.dev/help/known-issues#ssh
We're working on supporting enabling/disabling the SSH wrapper on a per-host basis, but no ETA on that yet.
Discord username (optional)
No response
Describe the bug
It seems when connecting to an idrac IP via ssh, warp terminal send extra commands that racadm can't interpret and the server close the session. I don't have this problem with iterm2.
via iterm2
To Reproduce
Just open warp, and ssh a idrac IP endpoint. This is dell server out of band interface.
Expected behaviour
I should get
racadm>>
prompt, which seems to happen, but i believe the racadm help is prompted because the extra commands that are send, and racadm doesn't understand and kick you out.Screenshots
No response
Operating System
MacOS
OS Version
13.0.1 (22A400)
Shell Version
zsh --version zsh 5.8.1 (arm-apple-darwin21.3.0) bash --version GNU bash, version 3.2.57(1)-release (arm64-apple-darwin22) Copyright (C) 2007 Free Software Foundation, Inc.
Warp Version
v0.2023.02.07.08.03.stable_01
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None