warpdotdev / Warp

Warp is the agentic development environment, built for coding with multiple AI agents.
https://warp.dev
Other
24.02k stars 488 forks source link

Warp Stuck At "Loading prompt..." when trying to ssh to remote machine with full disk #6577

Open gaber-ridango opened 1 month ago

gaber-ridango commented 1 month ago

Pre-submit Checks

Describe the bug

when I try to ssh to server that has 0% free disk space the shell gets stuck at "Loading prompt..." and it freezes. I can ssh to those servers with other terminal apps.

Version: v0.2025.06.04.08.11.stable_01 on mac os.

To reproduce

Have a server with 0% free space on /

Expected behavior

ssh should still open, be usable, maybe alert to 0% free storage

Screenshots, videos, and logs

No response

Operating system (OS)

macOS

Operating system and version

15.5 (24F74)

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

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

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

None

Advait-M commented 1 month ago

Hey! Thanks for reporting - guessing this is due to the bootstrapping logic Warp needs to run (i.e. Warpifying a session) for features such as blocks, etc. to work.

Curious, is this a common case you run into?

I've flagged this internally, however, unfortunately this likely won't be something we can prioritize fixing soon (not sure if a fix is feasible as well, given the logic we need to run).

gaber-ridango commented 1 month ago

Hey, thanks for the quick reply!

This has happened to me three times so far. Once I noticed the pattern, I tested it on purpose by filling up the disk on a test server, and I was able to consistently reproduce the issue in Warp (while other terminals still worked). That’s how I confirmed it was due to the 0% free space.

I understand this might not be a high priority or easy to fix, but I figured it’s worth flagging since it does impact usability in some scenarios.