Bizarre permissions failures perhaps attributable to Warp wanting to be updated?

[jimratliff]

Dupe Check

• I have searched Warp bugs and there are no duplicates

Describe the bug

After coming back to Warp after a few hours away (it had been open the entire time, same pwd), I tried to execute commands I execute hundreds of times per day, but suddenly getting bizarre errors (e.g., Fatal Python error: init_import_site: Failed to import…, make: getcwd: Operation not permitted. I happened to glance to notice there was a notification that there was an update to Warp. I updated Warp, and everything was back to normal. So, whether it was the act of updating or the fact that Warp wanted to update, or just restarting Warp, Warp seemed to be the cause of the unusual errors I was getting.

To reproduce

I don't know how to reproduce it. It happened unexpectedly, and either restarting Warp alone or upgrading Warp fixed it.

Expected behavior

I expected not to see the errors I saw.

Screenshots

No response

Operating system

MacOS

Operating system and version

13.6.6

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0)

Current Warp version

v0.2024.05.14.08.01.stable_04

Regression

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

Recent working Warp date

Today, a few hours ago

Additional context

This is really just a heads up. Clearly there's not enough info here to be actionable. But I've never had a terminal app cause errors executing basic shell commands.

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

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

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

None

[dannyneira]

Hi @jimratliff Thanks for letting us know. it would be helpful if you provide Warp logs and note the date/time when the issue occurred. https://docs.warp.dev/help/sending-us-feedback#gathering-warp-logs

[jimratliff]

Danny, I had thought that problem was a bizarre one-off, but it just happened again, at 2024_05_23_1524 Pacific Time (2024-05-23T22:24Z). Here’s the error I got:

╭─(venv) ~/Documents/chessspyder/repos/chess-clerk ╰─ 🔶 pytest Fatal Python error: init_import_site: Failed to import the site module Python runtime state: initialized Traceback (most recent call last): File "<frozen importlib._bootstrap>", line 1176, in _find_and_load File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 690, in _load_unlocked File "<frozen importlib._bootstrap>", line 980, in exec_module File "<frozen site>", line 616, in <module> File "<frozen site>", line 599, in main File "<frozen site>", line 517, in venv PermissionError: [Errno 1] Operation not permitted: '/Volumes/Avocado/Users/ada/Documents/chessspyder/repos/chess-clerk/venv/pyvenv.cfg'

Recalling my previous experience, I looked to see whether there was an “Update” notification. There was. I updated Warp, restarted Warp and things were fine. I could re-activate my virtual environment and then execute pytest successfully. See attached for the latest log file. Jim Ratliff Founder Chess Spyder ***@***.*** <mailto: ***@***.***> chessspyder.com <https://www.chessspyder.com/> <https://twitter.com/chessspyder> <https://www.facebook.com/profile.php?id=100089039233279> <https://github.com/Chess-Spyder>

On May 21, 2024, at 2:45 PM, Danny Neira ***@***.***> wrote: Hi @jimratliff <https://github.com/jimratliff> Thanks for letting us know. it would be helpful if you provide Warp logs and note the date/time when the issue occurred. https://docs.warp.dev/help/sending-us-feedback#gathering-warp-logs — Reply to this email directly, view it on GitHub <#4928 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAFMXBWAEVKG3VKIPQ474DZDO6BNAVCNFSM6AAAAABH3K3BZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTGQ4TENZSG4>. You are receiving this because you were mentioned.



[dannyneira]

Interesting, does this error happen when python virtual environment is activated or is it already active when it happens?

You mentioned after some hours, but I'm trying to see if we can reproduce this by requesting an update.