successtheman
commented
9 months ago I updated the above post adding the log contents in a collapsible details section for convenience
Closed successtheman closed 9 months ago
successtheman
commented
9 months ago I updated the above post adding the log contents in a collapsible details section for convenience
rocky4546
commented
9 months ago The new HTTPX library is throwing an exception caused by the provider not responding to the request. I'll check and probably update the exceptions list of things to catch to include this exception. Can you provide the exact channel you were using?
successtheman
commented
9 months ago Well it's odd because it's not an exact channel, it happens when editing the task and adding an interval or attempting to delete said interval. However, I will try a bunch of channels and see if I can reproduce it from starting streams as well and report back
rocky4546
commented
9 months ago The issue has nothing to do with the scheduler and everything to do with the streaming service. It might be a coincidence that it happened while you were doing something in the scheduler, but the log shows the errors were associated with streams. In all cases, the exception starts with /app/lib/streams/m3u8_queue.py file. This file is started in its own process and is totally separate from the scheduler. It is created when a channel is requested from internalproxy. The exceptions show that the trace does go through the decorator, which catches all bad exceptions, but with a new HTTPX lib, not all exceptions have been listed (especially those indirectly associated with HTTPX). Anyway, I will go over the exceptions found and add the ones needed. This will still cause the stream to not run, since the provider is unable to respond to requests, but it will not have the trace dump.
successtheman
commented
9 months ago The issue has nothing to do with the scheduler and everything to do with the streaming service. It might be a coincidence that it happened while you were doing something in the scheduler, but the log shows the errors were associated with streams. In all cases, the exception starts with /app/lib/streams/m3u8_queue.py file. This file is started in its own process and is totally separate from the scheduler. It is created when a channel is requested from internalproxy. The exceptions show that the trace does go through the decorator, which catches all bad exceptions, but with a new HTTPX lib, not all exceptions have been listed (especially those indirectly associated with HTTPX). Anyway, I will go over the exceptions found and add the ones needed. This will still cause the stream to not run, since the provider is unable to respond to requests, but it will not have the trace dump.
I was mistaken and posted the wrong error originally, the error when creating data update intervals is this one (happened as soon as I clicked create and tried to add a 3 hour update interval for Pluto TV while testing)
Exception in thread Thread-7:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.8/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/app/lib/schedule/scheduler.py", line 78, in _queue_thread
self.process_queue(queue_item)
File "/app/lib/schedule/scheduler.py", line 254, in process_queue
self.add_trigger(_queue_item['trigger'])
File "/app/lib/schedule/scheduler.py", line 298, in add_trigger
self.create_trigger(trigger['area'], trigger['title'],
File "/app/lib/schedule/scheduler.py", line 309, in create_trigger
trigger = self.scheduler_db.get_trigger(uuid)
File "/app/lib/db/db_scheduler.py", line 357, in get_trigger
trigger = self.get_dict(DB_TRIGGER_TABLE + '_by_uuid', (_uuid,))
File "/app/lib/db/db.py", line 195, in get_dict
self.sql_exec(sqlcmd, _where, cur)
File "/app/lib/db/db.py", line 67, in sql_exec
return _cursor.execute(_sqlcmd, _bindings)
sqlite3.InterfaceError: Error binding parameter 0 - probably unsupported type.
Fixed a number of the httpcore exceptions, but can't test it, so it should work, just not sure. As for creating trigger exception. I tracked it down to a change made 10 months ago. it has been fixed in RC08.
I get an error when trying to set intervals for the EPG updates in the webui, and I am not sure what is causing it so I thought I would share the log output here. It happens sometimes when trying to create a new task interval or delete an old one. It also seems to happen periodically when the task is supposed to actually run if I do somehow manage to get it to add a new task interval. I've attached the log output below and also indicated how to get the error to show in the screenshot.
I should note that it occurs with both the m3u plugin and plutotv as well
python_threadingerror_12-18-23.log
I am also pasting the log output here for convenience (Expand details to view it)