Closed algesten closed 1 month ago
My one concern is that it's a breaking change for the API, and maybe details that a new user of str0m might not need.
I'm weighing this API vs adding a Rtc::last_timeout_reason()
, leaving the API as is, and giving us an API if we want to know the reason.
Rtc::last_timeout_reason()
like
Alright. Pushed the alternative API. Also fixed some timeouts that should have returned None.
Tested it seems to be working:
2024-05-25T15:51:07.036296Z ERROR something: Ice, Instant { tv_sec: 12329, tv_nsec: 182128520, } 2024-05-25T15:51:09.489807Z ERROR something: Stats, Instant { tv_sec: 12331, tv_nsec: 636220215, }
I like this change, it's easy for us to pull it if we want the information but doesn't brake the current API.
LGTM!
This is by suggestion from @xnorpx.