Issue 2081 / path_to_filesystem#2087
Conversation
|
@flesueur - I've extended test cases and found that your implementation is also breaking softlinks supported on Windows with same issue found originally on Linux during PROPFIND request, see e.g. this particular workflow run: https://github.com/Kozea/Radicale/actions/runs/24395680534/job/71253826211#step:5:731 Having your change from #2002 reverted by 94746cf it is working again and passing the test on Windows https://github.com/Kozea/Radicale/actions/runs/24409725117 Can you please investigate further on, if there is no proper solution then the performance impact would be only on filesystems detected during startup as not collision-free. |
… improve path_to_filesystem
…ustment (fix broken vfat support)
|
Sorry it was much more complex than what I expected ! I guess this part is still WIP but, anyway, I did not find any other way to solve it. Even going back to the original motivation I don't spontaneously find another good alternative :( . Thanks ! |
I think there is no other way then predetecting and making it faster by skip on unproblematic file system while keeping the old code for others. If you agree the block below can be removed again, anyhow forced to be not active at the moment: Radicale/radicale/pathutils.py Line 295 in 7d07962 |
|
Yes I think so, it is now useless and can be removed. |
path_to_filesystem()by pre-detection of collision-free file systemRelates to
path_to_filesystem()#2002