meeb

@psperry can you share your logs of the actual error you're encountering? "Expected outfile does not exist" is not the actual error. Is this related to your media formats being...

@Themis3000 from your linked logs: `[WARNING] Worker with pid 24813 was terminated due to signal 9` (repeated lots). Signal 9 is SIGKILL, something is killing our workers externally, as if...

Well, if you have 403's in addition to something on your NAS killing processes you're certainly in for an unreliable experience. Neither of those are really anything to do with...

Exceptions raised by the worker won't block tasks and they are designed to be informative traces in the container logs so raising exceptions on failures is working properly as designed....

The back-off and retries are already quite extensive, media items will be retried for up to a day or two. Do you need more attempts than this?

If you delete formats and thumbnails from the metadata then thumbnails can't be downloaded and downloading media won't work as the media format can't be evaluated. This occurs on model...

There isn't a sane way to reduce the metadata storage (it'll need to be in the SQLite database or stored per-media-item on disk) without significantly reducing generally used functionality so...

I don't think this is anything specifically to do with tubesync. That's a Python error caused by resource exhaustion. Common causes would be the drive the container is stored on...

tubesync doesn't call `yt-dlp` with a command in a shell, it calls it via the Python API directly so there isn't a command that can be easily displayed (without making...

I can't see any reason why the sponsor segment wouldn't get truncated. I'll add in some logging that puts the `yt-dlp` API call parameters into the logs, that should hopefully...