Skip to content
Snippets Groups Projects
  1. Nov 08, 2022
  2. Aug 26, 2022
  3. Aug 02, 2022
  4. Jun 28, 2022
  5. Jun 15, 2022
    • Dietrich Rothe's avatar
      consistently update error status and message · 78981e49
      Dietrich Rothe authored
      Introduce StatusWithMessage and StatusWithMessageReader which handle this.
      It is used in DeviceModule error reporting.
      This is a preparation in order that we can report errors consistently to DOOCS, in DoocsAdapter
      
      make StatusAggregator use StatusWithMessage
      
      it should output always status code + string
      on the input side, connects to either status or status + string
      corresponding string input is found automatically
      NOTE: DeviceModule API change, the status output variables are
      renamed from (status, message) to (status, status_message)!
      
      update testing of DeviceModule outputs
      
      because of API change of DeviceModule  (renamed message ->
      status_message)
      
      fix crash and improve message and test
      
      - fix crash due to incorrect handling of cast to Derived
      - improve message output
      - make existing tests pass
      - add test for status message of StatusAggregator
      
      move StatusWithMessageReaderBase and Status def to ControlSystemAdapter
      
      since it is required from ApplicationCore as well as from the adapters
      78981e49
    • Dietrich Rothe's avatar
      fix move operations for uninitialized VariableGroup · 70d24ad1
      Dietrich Rothe authored
      makes test move_invalid pass
      70d24ad1
  6. Apr 27, 2022
  7. Apr 25, 2022
  8. Apr 08, 2022
  9. Apr 05, 2022
  10. Mar 31, 2022
  11. Mar 30, 2022
  12. Mar 03, 2022
  13. Jan 28, 2022
  14. Jan 26, 2022
  15. Oct 05, 2021
  16. Jul 21, 2021
  17. Jul 20, 2021
  18. Jun 21, 2021
    • Martin Christoph Hierholzer's avatar
      DeviceModule: change initialValueMutex into latch · c8f41e59
      Martin Christoph Hierholzer authored
      The previous implementation using the mutex had two issues:
      
      1. The mutex was locked in a different thread than unlocked (DeviceModule constructor vs. handleException() thread). This results in undefined behaviour.
      2. The boost::shared_mutex::lock_shared() function is not an interruption point, so applications did not terminate while waiting for initial values. (boost::latch::wait() is an interruption point.)
      c8f41e59
  19. Jun 14, 2021
  20. Jun 11, 2021
  21. Jun 09, 2021
Loading