v1.11.0

This release adds support for pushing run information to a new Kafka topic, aliecs.run. It also adds a distinction between start of SOR, end of SOR, start of EOR, and end of EOR (respectively SOSOR, EOSOR, SOEOR, EOEOR), and ensures the lifetime of these values is consistent both within the core and when pushed to controlled tasks. Furthermore, it fixes an issue which prevented FairMQ devices from quitting cleanly from their ERROR state.

• aliecs.run topic and timestamps:

  • [core] Emit run SOSOR/EOSOR/SOEOR/EOEOR events to aliecs.run topic
  • [core] Ensure SOEOR/EOEOR events are pushed in case of kill
  • [core] Push run_end_time_ms at EOR both camelCase and snake_case
  • [core] Clear all old run timestamps on SOSOR
  • [core] Clarify timestamp variables naming

• FairMQ devices behaviour:

  • OCTRL-888 [occ] If we see FairMQ's ERROR state, we should exit

v1.10.0

This release adds support for subdirectories within component configuration prefixes, and removes component configuration entry versioning. Specifically this means that all existing timestamped component configuration entry keys are not transparent any more, and must be referenced explicitly if desired. The recommendation is to redeploy the full component configuration tree.

• Component configuration subpaths:
  • [apricot] allow for arbitrary number of entry subfolders in HTTP service
  • [apricot] test the HTTP handler for Apricot
  • [common] OCTRL-805 allow to group entries in subfolders
  • [common] get rid of the concept of versioning and timestamps
  • [common] add multiple unit tests concerning configuration, include fixes

v1.9.2

This patch release adds snake_case versions of all special SOR parameters (see https://github.com/AliceO2Group/Control/blob/master/docs/handbook/configuration.md#variables-pushed-to-controlled-tasks) to make task compatibility easier between FLP and EPN contexts.

• [core] Push all AliECS-provided run parameters as snake_case+camelCase

v1.9.1

This patch release includes a fix for a core freeze, as well as a feature flag to disable Kafka event production for debugging.

• [core] added internal non mutexed method getParentRolePath to task.go
• [core] added the ability to turn off kafka sending

v1.9.0

This release fixes multiple race conditions in the AliECS core.

• Race conditions:

  • [core] fixed race condition for getTasks in roster.go
  • [core] race condition fix in aggregator.role
  • [core] Added missing mutex around eventStream in environment
  • [core] OCTRL-886 correctly use mutex in environment/manager.go
  • [core] OCTRL-889 proper usage of mutex in environment.go

• Miscellaneous fixes:

  • add a test for GetTasks and GetRoles
  • Bump golang.org/x/net from 0.22.0 to 0.23.0
  • [core] inform, not warn if there is one executor on a node
  • [doc] update the release documentation

v1.8.3

This patch release solves the issue with 824 billion tasks seen in GetEnvironments regardless of the architecture used to build the core, reported in OCTRL-882

• golang bump to 1.22

v1.8.2

This patch release is a fix attempt for OCTRL-881

• [build] added coverage step to makefile
• [core] keeping created kafka writers in global object

v1.8.1

OCTRL-851 [core] do not attempt to transition inactive tasks

v1.8.0

This release includes a fix to non-critical role handling, and adds production of role events to the aliecs.role topic.

• Workflow state handling:
  • [core] non-critical roles should never update parents state
  • [core] test state propagation across role trees
  • [core] remove obsolete workaround to make ERROR state always win
• aliecs.role topic:
  • [core] Emit role events to aliecs.role topic

v1.7.3

This patch release fixes a minor build failure due to recent build system changes.

• [occ] make directory for protofiles