The logic of the DaemonClient was changed in aiida-core==2.3 such that the timeout of the stop_daemon call is different from what is used by the is_daemon_running property. This can lead to the stop call going through just fine but is_daemon_running still returning True straight after. This usually resolves after a while but this false positive can cause the tests to fail when the session is closing. The stopped_daemon_client was already fixed in aiida-core by adding a manual grace period for is_daemon_running to start returning False. Here the same fix is added for daemon_client by overriding it until it has been fixed in aiida-core.
The logic of the
DaemonClientwas changed inaiida-core==2.3such that the timeout of thestop_daemoncall is different from what is used by theis_daemon_runningproperty. This can lead to the stop call going through just fine butis_daemon_runningstill returningTruestraight after. This usually resolves after a while but this false positive can cause the tests to fail when the session is closing. Thestopped_daemon_clientwas already fixed inaiida-coreby adding a manual grace period foris_daemon_runningto start returningFalse. Here the same fix is added fordaemon_clientby overriding it until it has been fixed inaiida-core.