Closed qku closed 1 month ago
The issue only occurs if the module on the server is already active when the client connects to it. Then, the activate method of the managed module returns early to skip actual module activation:
However, the creation of the poll timer is then also skipped:
Deactivation of the module from the client therefore fails, since neither a poll timer was created nor sigStateChanged
was connected.
Version
Release v1.4.1
What is affected by the bug?
When deactivating a remote module on the client qudi instance, an exception is raised. After this, qudi cannot be quit normally anymore but only terminated from e.g. the console.
When does the bug occur?
Every time when trying to deactivating a remote module on the client qudi instance.
How do we replicate the issue?
can be replicated with e.g. data instream dummy or time series reader logic from iqo-modules
Expected behavior
qudi should not raise an error and shut down properly when requested to.
Relevant log output
Additional Comments
No response
Contact Details
No response