Files
frigate/frigate
Josh Hawkins e347a72918 return a 500 instead of raising when go2rtc is unreachable
The two go2rtc stream GETs had no exception handling or timeout, so a go2rtc outage raised a connection error with a traceback, and a hung go2rtc held the request open indefinitely. Both now catch request errors, log the cause, and use a timeout. The per-stream probe gets a 35s read timeout because go2rtc probes each source in turn, and one unresponsive source takes about 10s.
2026-10-22 16:54:46 -05:00
..
2026-10-16 13:49:16 -06:00
2026-10-19 04:57:35 -10:00
2026-09-19 08:10:36 -06:00
2026-10-18 04:50:25 -10:00
2026-10-10 15:01:33 -05:00
2026-10-18 04:50:25 -10:00
2026-10-18 04:50:25 -10:00
2026-10-22 16:54:46 -05:00
2021-01-26 21:40:33 -06:00
2026-10-10 15:01:33 -05:00
2026-03-26 12:54:12 -06:00
2026-10-10 15:01:33 -05:00