no such option --force for aim runs close --force

[ap--]

🐛 Bug

We're currently debugging why we can't resume a run. And we noticed that while the code here:

aim/aim/sdk/lock_manager.py

Lines 131 to 135 in a566d4a

	raise RunLockingError(
	f"Cannot acquire lock for Run '{run_hash}'. "
	f"Make sure no process uses Run '{run_hash}' and close it via Aim CLI:\n"
	f'`aim runs close --force {run_hash}`'
	)

recommends to use aim runs close --force, the option does not exists

To reproduce

run aim runs close --force <somerunid>

Environment

• Aim Version: 3.23.0

Thanks,
Andreas 😃

fyi: @jorenretel

[nickl1234567]

Hey, not sure if this is what you are struggling with, but I was and I want to leave the solution somewhere:
So in my case aim told me: aimrocks.errors.RocksIOError: b'IO error: While lock file: <path>/<id>/LOCK: Resource temporarily unavailable' when trying to resume a run. As you say aim runs close <id> did not work, and --force is not implemented. So the solution I came up with is: aim runs cp <id> --destination . assuming the aim directory is located in the current working directory. This command copies the run from the current aim repository and places it in the same repository (in my case) releasing the locks.