Aonnghus

I just installed `v3.14.0`, but the issue persists. Has the workaround been implemented in this release?

Hi @mahnerak! I did as you said, but couldn't find any `.aim/locks/index.softlock`. Instead, there is a `.aim/locks/run_index.softlock`. Whole output of the `find` command is as follows: ``` .aim/seqs/locks/0fddf91743dd454c8aee0824.softlock .aim/seqs/locks/7d55cba6860445d093ee3572.softlock .aim/seqs/locks/89a5fc80da67429fbaf830f1.softlock...

I tried to move my `.aim` folder to a `ext4` partition with `.softlock` files removed. I no longer have the warning message, however launching `aim up --repo /ext4/path/.aim` is still...

First of all, I don't have any `.repo_lock.softlock`, either in the `ext4` or the `nfs` repo. It is just `.repo_lock`. Then, I wrote the following code: ```python import time from...

Any news on this issue?

Any news on this issue ? That would really be a great addition to vscode !

Hi, any news on this issue?

The demo server has the same behaviour. I am running Windows 10 20H2, build 19042.2251. Since my first comment, I updated Firefox to v108.0.1

I just installed v3.15.1, it seems that the issue is now resolved. I'll close this issue and reopen if I find again the same behaviour while using Aim.