When terminating the application while poll-type inputs are waiting
for initial values from other ApplicationModules, we need to interrupt()
those blocking initial-value reads.

This requires a corresponding change in DeviceAccess to allow calling
interrupt() without wait_for_new_data.

Closes #379

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 #7879

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.

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

* fix: Ignore data validity through return channels

* chore: Minor linter fixes

* fix: Do not modify model while iterating in XML generator

* fix: Change XML generator for TriggerReceivers

Give it a chance to comply with the XSD we provide

* fix: Update XML output XSD for changed output

 - Add Void and Boolean
 - Add TriggerReciever
 - Make class optional

* chore: Update test for XML generator

Add a DeviceModule whose absence was causing the XML generator to fail unnoticed

Modifying the model while visiting is not allowed because the
modification invalidates the iterators used for visiting. This lead in
this case to a very subtle crash (segfault) only appearing under very
specific circumstances (only when running in ctest and only on some
Ubuntu 20.04 machines).

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.