🐕 Batch: Revisiting Session Management

[DhanshreeA]

Summary

Session management in the Ersilia CLI has introduced the convenience to run multiple simultaneous models across different terminal "sessions", thereby increasing user productivity. However, the way Ersilia handles sessions currently, wherein a session is linked to a terminal process makes creates several complications especially in the following situations:

1. Session directories (typically found in ~/eos/sessions ) do not get cleared up if they contain files that don't have write permissions, meaning they don't get successfully deleted, leaving behind the session directory as well.
2. If a terminal is accidentally closed, or if a user's system crashes, or the docker engine crashes (in case of using Dockerized models), the session directories tend to remain on the system.
3. Then there is the case of not being able to simultaneously run more than one session with the same model 🐕 Batch: Running the same model in parallel #1223

For the 1st case, we have identified issues with log files or temporary directories from model containers present in mounted storage on the system owned by the root user from the container, and having 700 permission. These files cannot be deleted by a regular user without running sudo, therefore these files do not get removed, causing the entire session directory to remain on disk.

Objective(s)

• Clean up temporary log files from volume mounted docker containers
• Figure out how to remove orphaned session folders present on the system.
• Running same model in parallel sessions on the same system.

Documentation

No response