tokio-cron-scheduler VS tokio-cron-schedule

As I previously covered in my “Building a scheduler for a Rust application” post, I rely on Tokio Cron Scheduler for various routine background tasks, and one such task runs every 30 seconds (although the default value, it's configurable). This task checks if there are any pending notifications ready for dispatch. Fortunately, the extra 30-second delay doesn't significantly impact my use cases, but it allows me to manage the load more effectively. This approach works equally well for both near-real-time notifications and those scheduled for future delivery.

Am I missing something fundemental here? This came from a bug report.The code in question:

Release notes here.

Release notes here: https://github.com/mvniekerk/tokio-cron-scheduler/releases/tag/0.4

I believe your scheduler is effectively an infinite loop, and from a cursory look tokio_cron_scheduler doesn't gracefully shut down on your behalf. This means by joining you're waiting on an infinite loop, which I don't think should work? Does your program end if you ctrl + c it once?

My library tokio-cron-scheduler exposes what seems like a normal sync API but actually inside some of the functions it actually calls tokio::spawn() and returns a signal using std::sync::mpsc::channel().