The fix in the DeviceManager is more like a work-around for a false
positive of gcc 13.

Dietrich Rothe authored 7 months ago and Dietrich Rothe committed 7 months ago

* most useful with StatusOutputs, where automatic propagation of
  'data invalid' status is often not wanted
* Change default behavior of StatusOutput and StatusWithMessage.
  By default, they no longer propagate DataValidity=invalid of owning module.
  They still propage DataValidity=invalid of explicitly set for the output.
* Adapt test of DataValidity propagation for StatusOutput
* Adapt test of StatusMonitor to new StatusOutput behaviour

Dietrich Rothe authored 7 months ago and Dietrich Rothe committed 7 months ago

"!sometag" is a negated tag which annihilates with "sometag"
negated tags can be added like normal tags, and are used to remove their counterparts

boost::thread::id seems not to be trivially copyable for the old boost
version, so we implement our own atomic access with a lock here.

This is another instance of the race conditioon fixed a few days ago
(with eb81711e).

The racy behaviour is acceptable, so the test is modified to accept it.

StatusAggregator was aggregating downstream aggregators according to their
input tags instead of the output tags.

Dietrich Rothe authored 9 months ago and Dietrich Rothe committed 9 months ago

CircularDependencyDetector was running into infinite recursion (causing
stack overflow) in a situation of two Modules which are both waiting on
each other for initial values

update project template

* feat: Add oven simulator script

chore(project-template): remove slicing object linter warning