Pending task after CTRL+C about message-io HOT 12 CLOSED

Hi.

It seems the internal thread is still running when you do ctrl+c. You should call NodeHandler::stop() before. To perform clean exits when the user makes ctrl+c I recommend https://github.com/Detegr/rust-ctrlc to handle the signal before the OS kill the process

from message-io.

Ok but if i un DiscoverServer in a tokio task, I also ctrlc::set_handler(... in main outside of that task.
How would I access discovery or dsserver ?

from message-io.

This depends on how your architecture is built. I would send an event that the task could receive. Also, the NodeHandler is clonable and sendable, so you could store any copy of them where you want to then call .stop() before the program exits.

from message-io.

indeed i clone the entire DiscoveryServer (that implements run() and stop())

This is what I do in main
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=3ed82949b6852827866aaf5ee6cc07cf

I run the server in a tokio task and i catch a ctrlc signal from main and call stop() from the cloned Arc<Mutex>

I see a signal has been catched but nothing is actually stopped

from message-io.

I checked the code and it seems the mutex is locked at line 29, before you perform the stop() called. Could you try to move the println() after this line and check if it's printed?

from message-io.

yes i already tried that and indeed it prints
Mutex { data: <locked>, poisoned: false, .. }

from message-io.

the discovery.run() does something like

    pub fn run(&mut self) -> std::io::Result<()> {
        let node_listener = self.node_listener.take().unwrap();

        node_listener.for_each(move |event| match event.network() {
...
...

from message-io.

If I understand well the code you pasted and you shared now, your run() call will keep processing forever (until you call stop()). During this processing, the mutex is locked, so, when you try to lock again to make the stop() call, it is already locked. If your problem is getting the NodeHandler under the mutex, remember that you can clone it, and then use the cloned NodeHandler without making the lock()

from message-io.

Exactly, run() runs forever.
How can i call stop() directly if that's behind a Mutex ?

from message-io.

A solution could be:

1. Create your DiscoveryServer instance.
2. get the NodeHandler from the discovery server and clone it.
3. Create the mutex over the discovery server.
4. lock() and call run().
5. use the node_handler.stop() (which is out of the mutex) at ctrl_c signal.

from message-io.

You only need to clone NodeHandler which is already clonable, you do not need to clone the entire DiscoveryServer.

from message-io.

lol it worked! It's a bit ugly but thank you so much!!

from message-io.