Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.6.0
-
0
-
Yes
-
Tools 2024-Q1
Description
What is the problem?
Currently our error messages are easy to misread:
failed to lock remote archive: failure trying to remove stale lockfile: the process '10016' running on 'hostname' already holds the lock
|
(cloud)
vs
failed to lock archive: failure trying to remove stale lockfile: the process '10016' running on 'hostname' already holds the lock
|
(archive/staging)
What is the solution?
We should alter this error message to make it clearer whether it is the staging directory lockfile or the cloud one