search

aimhubio / aim

Aim 💫 — An easy-to-use & supercharged open-source experiment tracker.
https://aimstack.io
Apache License 2.0
5.23k stars 321 forks source link

no such option `--force` for `aim runs close --force` #3213

Open ap-- opened 2 months ago

ap-- commented 2 months ago

🐛 Bug

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

https://github.com/aimhubio/aim/blob/a566d4a2501c96a545a3c89d92af6ad7e7e0da99/aim/sdk/lock_manager.py#L131-L135

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

To reproduce

run aim runs close --force <somerunid>

Environment

Thanks, Andreas :smiley:

fyi: @jorenretel

nickl1234567 commented 2 months ago

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.