Create a new FileSystemResourceLocker
Configures the locker using the specified FileSystemResourceLockerArgs instance.
Acquires a lock on the requested identifier. The promise will resolve when the lock has been acquired.
Resource to acquire a lock on.
Initializer method to be executed on server start. This makes sure that no pre-existing (dangling) locks remain on disk, so that request will not be blocked because a lock was acquired in the previous server instance.
NOTE: this also removes locks created by the GreedyReadWriteLocker. (See issue: https://github.com/CommunitySolidServer/CommunitySolidServer/issues/1358)
Releases a lock on the requested identifier. The promise will resolve when the lock has been released. If there is no lock on the resource, an error should be thrown.
Resource to release the lock on.
A resource locker making use of the proper-lockfile library. Note that no locks are kept in memory, thus this is considered thread- and process-safe. While it stores the actual locks on disk, it also tracks them in memory for when they need to be released. This means only the worker thread that acquired a lock can release it again, making this implementation unusable in combination with a wrapping read/write lock implementation.
This proper-lockfile library has its own retry mechanism for the operations, since a lock/unlock call will either resolve successfully or reject immediately with the causing error. The retry function of the library however will be ignored and replaced by our own LockUtils' retryFunction function.