Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSH terminal randomly closes after running a command #4845

Open
danives opened this issue Apr 28, 2024 · 1 comment
Open

SSH terminal randomly closes after running a command #4845

danives opened this issue Apr 28, 2024 · 1 comment
Labels
Bugs Bugs, Hangs, Crash, and Freezes

Comments

@danives
Copy link

danives commented Apr 28, 2024

Discord username (optional)

HandsomeStrife

Describe the bug

When I SSH onto my AWS server, if I perform a git pull, or run a bash script, the warp terminal exits the SSH instance after performing the action.

To reproduce

In a git repository, continually perform git pull until an exit suddenly occurs.

Expected behavior

I would expect the SSH session to stay connected

Screenshots

Screenshot 2024-04-28 at 16 12 33

Operating system

MacOS

Operating system and version

Sonoma 14.0

Shell Version

GNU bash, version 3.2.57(1)-release (arm64-apple-darwin23

Current Warp version

v0.2024.04.23.08.01.stable_03

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

No response

Additional context

I can't replicate the issue using iTerm2, that seems to work fine.

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.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

@danives danives added the Bugs Bugs, Hangs, Crash, and Freezes label Apr 28, 2024
@dannyneira
Copy link
Member

Hi @danives so sorry to hear about this blocker. Warp has an SSH Wrapper that enables features (like the prompt, completions, etc.) on remote machines. This requires the default prompt on the remote machine to be either bash or zsh.

If that's already the default shell, as a workaround, you can try using adding command ssh to your Settings > Subshell menu, then use command ssh <user@server> to connect to sessions, this will enable Warp features with the subshell method instead of the ssh wrapper.

Or, you can also try disabling the SSH wrapper by navigating to Settings > Features. Blocks will stop working but with it disabling, SSH should work as normal.

https://docs.warp.dev/features/ssh
https://docs.warp.dev/features/subshells

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugs Bugs, Hangs, Crash, and Freezes
Projects
None yet
Development

No branches or pull requests

2 participants