Skip to content
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

Drop the DbCalcState #2197

Closed
sphuber opened this issue Nov 13, 2018 · 0 comments
Closed

Drop the DbCalcState #2197

sphuber opened this issue Nov 13, 2018 · 0 comments

Comments

@sphuber
Copy link
Contributor

sphuber commented Nov 13, 2018

The DbCalcState was used to both store the current state of JobCalculations, but also acted as a lock-mechanism, by only allowing progressive state changes. This last functionality is now the responsibility of the Runner. It is still useful to keep the job state, but this can now simply be furnished by an attribute. This also means that the specific IMPORTED state can be remove, since that is no longer applicable. It was supposed to stop imported calculations to be picked up by the daemon, since the old daemon determined which calculations had to be run, based on their DbCalcState.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant