Open blacelle opened 1 year ago
I agree it ought to handle concurrent invocations, or at the very least not fail while it waits in serial. In the short-term, the timeout goes from 5s to 50s if you set the system property lockFileGenerousTimeout
to true
.
The 50s generous timeout seems sufficient for my case. Thanks
This issue relates (in term of context) with https://github.com/diffplug/spotless/issues/1687
Through Spotless, I end needing to run concurrent P2 invocations in the same environment. It fails with:
This is recurrent in my use-case as I run multiple Spotless|P2 processes on the same machine.
I have no equivalent issue with maven, which handles smoothly concurrent invocations on a common/shared
~/.m2/repository
directory. Which makes me feel P2 could/should cover the same useCase.I would be fine if concurrent operations were kept pending until the lock is freed, instead of hard-failing. This may be a relevant optional behavior.