You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The
DbCalcState
was used to both store the current state ofJobCalculations
, but also acted as a lock-mechanism, by only allowing progressive state changes. This last functionality is now the responsibility of theRunner
. It is still useful to keep the job state, but this can now simply be furnished by an attribute. This also means that the specificIMPORTED
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 theirDbCalcState
.The text was updated successfully, but these errors were encountered: