Run cannot be ended or deleted if process crashed
See original GitHub issue🐛 Bug
When a training script is canceled before completion or when it crashes, the run remains in In Progress
state and cannot be deleted, even when clicking Delete
in the run’s settings tab.
To reproduce
Expected behavior
Environment
- Aim Version 3.14.0
- Python version
- pip version
- OS (e.g., Linux)
- Any other relevant information
Additional context
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Unable to delete EXE after it crashes even though process not ...
Your process is not being terminated all the way. Since it is not list in the task manager, you can use PSKILL to...
Read more >Attempt to delete the physical volume store while geometry ...
When I increase the energy of primary protons, that these pass throughout the first volume (box), these WARNINGS happen and the run crashed....
Read more >4 Ways to Solve the Cannot Delete Files Error
To see all the files and running processes, open Start Task Manager and close from there the files by clicking End Task. 2....
Read more >Elixir, A Little Beyond The Basics - Part 7: supervisors
Crashing Supervisor Except... By design, Supervisors will terminate themselves if a supervised process is being restarted too fast and too often. ...
Read more >How To Fix explorer.exe Crashing In Windows 10 - YouTube
The “ Process ” tab of the Task Manager window shows you apps and background processes currently running on your PC. Scroll down...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
minimal version of the workaround seems to be something like:
There might be need to remove respective locks in
.aim/seqs/locks/
as well