Pre-submit Checks
Describe the bug
I am having multiple issues of:
I'm sorry, I couldn't complete that request.
Request failed with error: Transport(reqwest::Error { kind: Decode, source: hyper::Error(Body, Error { kind: Io(Custom { kind: BrokenPipe, error: "stream closed because of a broken pipe" }) }) })
I have tried local work-arounds, to deal with connection disruptions, however with no luck.
The "broken pipe" error message appears across multiple system configurations, confirming it is not just a local network problem.
Searched Warp bug directory, and found a few similar issues being reported: |
Probable Cause:
- The error is related to the underlying reqwest and hyper libraries, often triggered by network interruptions, connection closures, or decoding problems at the transport layer.
- There are no user-level workaround which can be seen in the bug reports above which has been established, aside from basic troubleshooting (restarting, checking network), which does not consistently prevent the bug.
To reproduce
Please see the above description, and related bug reports which contains further information:
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
15.6.1 (24G90)
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
Pre-submit Checks
Describe the bug
I am having multiple issues of:
I have tried local work-arounds, to deal with connection disruptions, however with no luck.
The "broken pipe" error message appears across multiple system configurations, confirming it is not just a local network problem.
Searched Warp bug directory, and found a few similar issues being reported: |
Probable Cause:
To reproduce
Please see the above description, and related bug reports which contains further information:
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
15.6.1 (24G90)
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