Closed jg-24 closed 3 years ago
One of the things we could do is to just serve the next segment and ignore the error. Once all known segments are depleted we stop the stream.
1 week with the same version running and this hasn't happened again. I'd say any exception handling to try and account for the HTTP 500 response would be fine to close this and wait to see if it happens again.
Using locast2tuner 0.1.30 on Darwin 20.3.0
This looks like an opportunity to enhance exception handling and may not be anything that can be replicated easily. It doesn't appear there was anything in particular that triggered this event, likely something in the upstream locast network that got overwhelmed during high usage.