Tasks aren't re-scheduled upon a restart, so they won't always exist. To avoid the warning, we can either add a simple check that the tasks exists before cancelling. Alternatively, we can cache the silenced channels in redis and re-schedule tasks when the bot restarts. A notification is supposed to be sent if there are active silenced channels during shutdown, but this mechanism is a victim to #1012.
I prefer the re-scheduling option. Does anyone else have thoughts on which way to go?
Tasks aren't re-scheduled upon a restart, so they won't always exist. To avoid the warning, we can either add a simple check that the tasks exists before cancelling. Alternatively, we can cache the silenced channels in redis and re-schedule tasks when the bot restarts. A notification is supposed to be sent if there are active silenced channels during shutdown, but this mechanism is a victim to #1012.
I prefer the re-scheduling option. Does anyone else have thoughts on which way to go?