Intermittently, the CadenceBot=>Cadence (Icecast) stream might disconnect without producing an error event that we recognize. This leaves CadenceBot playing silence until restarted.
The status command added in #89 can detect this condition - It generates the message "Stream status: Disconnected (automatic reconnect failed - Will retry in 3 seconds)." followed three seconds later by a retry attempt to connect to the stream.
However, this depends on a user wondering why the stream is down and running status. We can do better. At the very least, we could poll the same condition checked by the status command to detect this error mode. But it would be good to try to find a mechanism to proactively detect the link dropping, and reconnect without having to poll for it.
Testing this may require some cooperation with @kenellorando to disable the stream, or some network security manipulation to block it off, as the developer prefers.
Intermittently, the CadenceBot=>Cadence (Icecast) stream might disconnect without producing an error event that we recognize. This leaves CadenceBot playing silence until restarted.
The status command added in #89 can detect this condition - It generates the message "Stream status: Disconnected (automatic reconnect failed - Will retry in 3 seconds)." followed three seconds later by a retry attempt to connect to the stream.
However, this depends on a user wondering why the stream is down and running status. We can do better. At the very least, we could poll the same condition checked by the status command to detect this error mode. But it would be good to try to find a mechanism to proactively detect the link dropping, and reconnect without having to poll for it.
Testing this may require some cooperation with @kenellorando to disable the stream, or some network security manipulation to block it off, as the developer prefers.