Releases: AliceO2Group/Control
v0.9.3.1
v0.9.3
v0.9.2
This release improves error handling and reliability.
- Handling of unexpected task behavior:
- [core] Increase deployment timeout to 90s
- [core] Release tasks on failed post-create CONFIGURE
- [core] Do not GO_ERROR+unsubscribe on task failure
- Miscellaneous fixes:
- [executor] Make "cannot query task status" an Info message, not Error
v0.9.1
This release makes task cleanup run as part of the environment destroy operation by default.
- Task cleanup:
- [coconut] Add --keep-tasks option to env destroy (default: clear tasks)
- [core] Add keep tasks on env destroy flag in proto
- [core] Regenerate proto
- [core] Add GetTaskIds to task.Tasks
- [core] Implement task cleanup inside env destroy
v0.9.0
This release brings reliability improvements, as well as a task cleanup operation (coconut task clean).
- Task cleanup:
- [coconut] Implement task clean operation and improve error handling
- [core] Send task kill call from scheduler
- [core] Implement server side of tasks cleanup API call
- [core] task.Task now has a state/status
- [core] Allow sending control commands to non-locked tasks
- [core] Implement task cleanup in task.Manager
- [core] Update environment transitions for new interface in task.Manager
- [executor] Allow executor to create its own executorcommands
- [executor] Fix bug with bad final state in FairMQ transitioner
- [executor] Implement KILL event + improve error handling
v0.8.4
v0.8.3
v0.8.2
This release ensures run number type compatibility with Node.js and thoroughly improves InfoLogger integration.
-
Run numbers as uint32:
- [coconut] Make the run number a uint32
- [core] Make currentRunNumber uint32 in proto
- [core] Regenerate proto
- [core] Make the run number a uint32
-
InfoLogger overhaul:
- [core] New InfoLogger hook
- [core] Remove old InfoLogger kludge
- [core] Hook up InfoLogger hook
- [core] Remove workaround for InfoLogger<1.3
- [core] Build InfoLogger facility string from logrus prefix
- [core] Improve log output
- [core] Add run starting/stopping messages with run number
- [core] Correctly stringify incoming fields for InfoLogger
- [executor] Hook up InfoLogger hook
- [executor] Clean up log messages
v0.8.1
This release completes support for run numbers and provides some bug fixes.
-
Run number support:
- [coconut] Add support for run numbers and correct version information
-
Miscellaneous fixes:
- [build] Update dependencies to include go-git
- [core] Correctly report version in IDE builds
- [core] Fix typo in default instance name
- [core] Fix panic on invalid environment UUID
v0.8.0
This release adds support for run numbers, and includes an overhaul of the configuration mechanism.
Users should update their configuration files and/or o2control-core command invocation. For more information, run o2control-core --help and see hacking/settings.yaml and hacking/settings.yaml.example.
-
Configuration improvements:
- [core] Overhaul core configuration mechanism, now based on viper
- [core] Make confsys a singleton, accessible everywhere as the.ConfSvc()
- [core] Take advantage of singleton ConfSvc
-
Run number support:
- [core] Propagate run number to tasks in START_ACTIVITY transition
- [core] Gather common arguments (such as run number) before transition
- [core] Generate run number and push it down
- [core] Add run number to API and regenerate proto
- [core] Add environment.GetCurrentRunNumber
- [core] Run numbers start from 1, 0 is a null-value as in Protobuf
- [core] Implement run number in gRPC server
- [core] Make sure run number file exists before using it
- [occ] Push arguments to FairMQOptions before RUN transition
- [occ] Move RCOPrivate in own header and expose RunNumber
- [occ] Set run number on every transition
-
Miscellaneous fixes:
- [core] Fix error handling bug in task/manager