meeb
The raw response is returned early specifically by design. You would want to use the raw response to perform parsing yourself. Most of the time, this is because the response...
Thanks to the PR from @KolevVelyan in #55 this should be far easier to work around. I'll close this for now but feel free to open a new issue if...
Is the number of tasks going down? There's not enough information here to assist really. Anything else in the container logs?
try resetting tasks on the command line, like: ```bash docker exec -ti tubesync python3 /app/manage.py reset-tasks ```
Yeah obviously something isn't running correctly, the issue is there's nothing in your logs to indicate what the issue is. What processes are running in the container?
That shows that the task runner is running properly. I've no idea really why it's not processing tasks on your install if that is indeed the issue. Edit: any logs...
@YourWishes that error means your database schema is missing or corrupted. This isn't the same issue. What does this output? ```bash $ docker exec -ti tubesync python3 /app/manage.py migrate ```
This looks resolved, thanks @tcely !
Also the testdata (JSON spam in `testdata`) needs an update, some of those are a few years old now and almost certainly don't match the current output of `yt-dlp`.
Doesn't this break HTTP request logging for the container in general? As in, removes it from the standard stdout and writes it to disk? Also unless I've missed it this...