SSH Loading Prompt Hangs & "warptmp" Directory Creation

Open
#3,588 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
macos
Domain
cli, networking

Research direction

No source file, test, or entry point is identified in the report. Start by reproducing SSH on macOS 13.4.1 with Warp v0.2023.08.22.08.03 and compare the Loading prompt and warptmp behavior with other terminals; done means the prompt loads and commands can be entered without unwanted directory creation.

Written by the indexing model from the issue text.

Description

area:shell-terminal area:ssh bug needs-info ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

When using SSH, I encounter a "Loading prompt..." which doesn't finish. This doesn't seem to be a problem in other terminals. Also for some reason the warp terminal wants to create the "warptmp..." directory. I haven't been able to find a setting to disable this.

To reproduce

Just use ssh as you normally would

Expected behaviour

The prompt loads and I can enter commands.

Screenshots

warp_issues

Operating system

MacOS

Operating system and version

13.4.1

Shell Version

5.0.17

Current Warp version

v0.2023.08.22.08.03.stable_00

Regression

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

Recent working Warp date

No response

Additional context

No response

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

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

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

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.