warpdotdev-devx[bot]
commented
1 year ago Hey @ravi-devarakonda Thanks for letting us know, this is because the sudo subshell on the remote machine isn't bootstrapped the way the SSH session or other subshells would be. We'll post any updates on this thread if/when this issue is being worked on. Unfortunately, there isn't a viable workaround at this time, any time you enter a subshell within an SSH session ( i.e. sudo su, bash, etc. ) the Warp wrapper will be temporarily disabled and will revert to the traditional waterfall input/output from traditional terminals.
To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.
ravi-devarakonda
supermanc88
zachbai
dannyneira
Discord username (optional)
No response
Describe the bug
I have my input position set to default (pinned to bottom). When I login to a remote server, at random times, the input position is not respected and it goes to the classic behavior.
The remote server is bash. I have tested it both ways, by keeping the ssh wrapper on and off. Same behavior.
To reproduce
It has happened on multiple occasions. I have notice that it mostly happens:
Expected behavior
The Input position is respected.
Screenshots
No response
Operating system
MacOS
Operating system and version
13.4.1
Shell Version
zsh 5.9 (x86_64-apple-darwin22.0)
Current Warp version
v0.2023.08.08.08.04.stable_00
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
Although it has happened on regular sessions too, it happened the most when I was connected to a VPN.
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:b8107fdf-ba31-488d-b103-d271c89cac3e
None