-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add @maintenance
decorator to methods that cannot be executed concurrently
#6
Comments
Also:
|
In AiiDA, we will try to put all safeguards to avoid problems. Putting a decorator properly is a bit tricky, so I am moving this to a 'nice to have'. This will need to be properly documented, though... |
After careful thinking: while one could implement guards (e.g. a decorator We note that however such logic was implemented in AiiDA I will therefore close this, and the docs will be added as part of #3 |
Add a guard to avoid maintenance methods (repack, delete, add directly to packs) are performed in parallel.
Add decorator that opens a lock file in exclusive mode, and stops if someone else is already performing maintenance operations.
Possibly check (both this, and the one that locks a pack) that they have a finally block that releases the lock.
The text was updated successfully, but these errors were encountered: