I've uploaded portalocker 3.1.1, which includes a patch that "fixes"
this issue, where basically upstream just handles the error properly with
a new exception.
Quoting upstream [0]:
That looks like the current "fix" is at least effective in that it throws the correct exception now.
Beyond that I'm not sure what else I can do honestly. It appears that the filesystem doesn't support read only locks for this case.
For cases like these I created the RedisLock that work across multiple
networked systems and is not limited by filesystems at all.
There's also a small chance that lockf as opposed to flock works in this case it can be changed by overriding the LOCKER attribute:
However, I'm going to let this bug open since the package still has problems supporting lock on NFS
[0]:
https://github.com/wolph/portalocker/issues/92#issuecomment-2179532676
-- josue
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAmgVNa4ACgkQAVCdXKtK /T9KBA//WGRDjY2LnaWYXWHKhsJ3xYoe3oHNR+KXwVV7Y7g1npDV4FKGm5TNs6bk zUq3RIFjObKL+CNvkPv8k6rrW3Lr/I/0yJn247KreY3l4MJHGZIAyBNig0KzU390 ajlpkgHInsW6CBIskiJ/zILkvArgKbxE1iYuH4vj6bzv8MJfL2ELIdz0evdWr6k2 5UtHWxnaqLb7ECocmZReuXvnpgZPyX3yp/MyASCsftcu9lauQs8OC5QrijlDiAEF AkIF/Kd1fT6sTDUVA8d/24YmqcHnjWEQTb3NoFQz8spFZ3WesthZoVOWwqU82poS +0g7TXfy9WA8WifEwHHVK0m0djdSuoP2LbeNTvs0ud/OsUyR+3i0aiFMB4HjJ9kX FwDQodaJO8DQMWlCvn5RiG7nEs2DTSOrkUcG6p58zVSvyxNLRZykSFWSGggj9pVa nM/fehl9Zy1qY/gM5JfPSXBUT19seAHWQNuEZCe66sfh/tLFA+eDGeONQfRwSbnK 1+B2ThGNFa+9Y74pS2Y60uC2QBRnovo7k3rTRnhPYHM/rLhOyN+FMsWlnI5biVj3 smnVTV+Wu9BX5/qM6eNCsE6+cfQz82Dgj5r5cmxsoG9jnagh78QJgsux78Evwre6 b/QvfC5SDYXcTwsA0jVGbY8TSwH+FOg2f1lG0mdaIKljHl4tLVc=
=if9B
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)