Skip to content

Check for lingering RTEs on subsystem entry #2610

@t-b

Description

@t-b

A recent issue with an lingering RTE 1 highlighted again that bugs like this are very difficult to diagnose and fix. While we wait for IP to get better in this regard (issue 5595) we could also try to make it easier to localize.

One idea would be that we add PerformSubsystemEntry() (which does the same as AssertOnAndClearRTError) calls when we enter a new subsystem:

  • Logbook reading/writing
  • Amplifier
  • SweepFormula
  • NWB
  • PressureControl
  • Publish
  • Wavebuilder
  • Databrowser/SweepBrowser
  • AnalysisBrowser
  • Cache
  • Async Framework
  • Configuration

In that way we should catch lingering RTEs earlier and also have them more localized.

Metadata

Metadata

Assignees

No one assigned

    Labels

    PureEngineeringIssues which makes the live of MIES developers betterbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions