You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Poll shutdown event.
match shutdown_rx.recv_timeout(Duration::from_secs(1)) {
// Break the loop either upon stop or channel disconnect
Ok(_) | Err(mpsc::RecvTimeoutError::Disconnected) => break,
// Continue work if no events were received within the timeout
Err(mpsc::RecvTimeoutError::Timeout) => (),
};
I can't understand where it should be. Process can be stopped only by killing task (taskkill /F /IM consum-api.exe)
The text was updated successfully, but these errors were encountered:
The code is not what we need. The idea implemented in commit 67c9cc1 is to pass signal receiver to warp, and send it from service event handler. And that works, but sometimes gives an error, and another stopping retry or two is needed to stop. Not sure what happens in that case, probably some panic? Not sure how can we log that though...
The problem is that we miss polling code:
I can't understand where it should be. Process can be stopped only by killing task (
taskkill /F /IM consum-api.exe
)The text was updated successfully, but these errors were encountered: