Updating pip in a FUSE cryptomator vault breaks venv

I store my programs in a cryptomator vault which uses a fuse virtual drive (The default on Linux), but when trying to update pip inside a venv I get an error, then any subsequent use of pip also throws an error and {path_to_venv}/lib/python3.12/site-packages/pip/ becomes empty.

I imagine this is an issue that would happen in any FUSE drive although I don't know how to test that.

Here are the logs

• OS : Fedora 40
• pip version: 23.3.2 updating to 24.2
• python version: 3.12.7

I already made a bug report on the github

Does anyone know a temporary workaround for this ?