github-actions[bot]
commented
1 year ago This issue has been automatically marked as stale because it has not had activity in the last 5 months. It will be closed if no activity occurs in the next month. Please chat to us on the forum or ask for help on our chat if you have any questions or need further support with getting this issue resolved. You may also label an issue as pinned if you would like to make sure that it does not get closed by this bot.
Describe the bug
We started to hear a previous webstream back and forth in a show, while the webstream should have ended.
This happened after a quick fix in one of the show that was already playing, but I don't think it is relevant or it only allow a bug to reach the playout, I really don't know.
The webstream was initially defined with a length of 2 hours. We scheduled it in some of our shows, and after a while we changed the webstream length to 1 hour.
The scheduled webstream still references the same webstream ID, but the length doesn't match anymore. So we have inconsistent behavior such as:
The schedule is 2 hours
The show instance is 1 hour
Related to #1680
To reproduce
Untested yet:
Expected behavior
Maybe the webstreams should be immutable (just like files, where a new length would mean a new file) or we should recompute the schedule. I would expect #2157 to help a lot with this.
Relevant log output or error messages
No response
LibreTime version
3.0.0
Installation method and OS / Environment
Operating system: Debian 11 Method: Ansible
Installation details
No response
Client Environment
No response
Screenshots
No response