warp_escape_json:1: can't create temp file for here document: permission denied

Open
#4,912 9 comments 0 reactions 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
bash, macos, rust, zsh

Research direction

The report names no source files, tests, or entry points. Start by reproducing the here-document permission error after Warp has been running for several days on macOS 14.4.1 with zsh or bash, then trace the temporary-file handling; done means commands run without this error in Warp while other terminals remain unaffected.

Written by the indexing model from the issue text.

Description

bug ready-to-implement triaged
Dupe Check
Describe the bug

No matter what command I execute, there will always be this error coming out
warp_escape_json:1: can't create temp file for here document: permission denied
image

Warp: v0.2024.05.07.08.02.stable_02
Mac: 14.4.1 (23E224)

To reproduce

After starting Warp for a period of time, maybe 4or 5 days, this issue will occur

Expected behavior

No response

Screenshots

No response

Operating system

MacOS

Operating system and version

14.4.1 (23E224)

Shell Version

zsh 5.9 (x86_64-apple-darwin23.0) GNU bash, version 3.2.57(1)-release (arm64-apple-darwin23)

Current Warp version

v0.2024.05.07.08.02.stable_02

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

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.