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

[jimratliff]

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

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

[jimratliff]

Danny, I thought I’d update you that this is still a reliable problem. It’s so predictable, that it’s part of my workflow. So it’s not really a problem: When a command fails (and it helpfully suggests trying it with `sudo` 😉), I look up in the upper right of Warp’s window to find that Warp has a new update. I install the update, re-activate my venv, and go about my business. So I’m not complaining. Just wanted to be clear that the problem hasn’t been solved. Since I know what the issue is, it’s not a problem. It could certainly confound others who don’t know what to attribute it to. Thanks! Jim Jim Ratliff ***@***.*** https://virtualperfection.com/jim

…

On May 23, 2024, at 4:24 PM, Danny Neira ***@***.***> wrote: 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. For example there was a new release today, did this Warp update trigger the error as well? — Reply to this email directly, view it on GitHub <#4928 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAFMXEV4COLPTGMSZUVQKTZDZ3DLAVCNFSM6AAAAABH3K3BZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRYGE4DMMZZGI>. You are receiving this because you were mentioned.