Closes #379

If the return channel of a FeedingFanOut was removed because it is
connected to the control system but not mapped there, the _returnSlave
is not set and hence all read operations on it were crashing.

We were holding an std::vector of an incomplete type
(VariableNetworkNode) in a struct (ProcessVariableProperties), which
is not allowed. This fix changes it into an std::vector of shared_ptrs.
Since we are exposing this vector via ProcessVariableProxy::getNodes(),
this presents a breaking API change. Since this is used mostly
internally, this should not break much.

Fixes #8357

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.

* fix: Ignore data validity through return channels

* chore: Minor linter fixes

ProcessVariableProxy::removeNode() was effectively taking a reference to
a shared pointer as an argument and is removing the same (effective)
shared pointer from a list. This poses a problem if the reference passed
points to the list directly and is the last shared pointer to this
object so it gets freed, because removeNode() is accessing the object
after removing it from the list.

vaeng authored 1 year ago and Martin Christoph Hierholzer committed 1 year ago

* The example app has been updated to show the implementation of the
new VersionInfoProvider module

- fix EntityOwner::constant() violates character restrictions
- Utilities::stripName() was broken in multiple ways. It has been
  changed into a true, reversible escaping algorithm and subsequently
  renamed into Utilities::escapeName().
- Utilities::unescapeName() is introduced.

BREAKING CHANGE: This commit will break applications which either
- rely on the names of device status PVs for devices which contain
  illegal characters (e.g. when using a CDD directly instead of a
  dmap file alias), or
- use Utilities::stripName() directly.

* Disable deprecation warnings
* Fix linter findings
* fix: Compiler warnings regarding internal linkage
* fix: Mask memory leak

---------

Co-authored-by: Martin Hierholzer <martin.hierholzer@desy.de>

InvalidityTracer and ConnectionMaker debug mode print now information
about circular networks