Open kuhnchris opened 1 year ago
You are not missing anything. There's an issue with skipping as mentioned in #280 and other issues. When it was first built the skip
flag was purely for things like the number of retries and been exceeded and then the media was marked to be permanently skipped internally. This was extended with a UI button that marked media to skip and unskip, however, this is now also managed by various other internal conditions where the skip
flag can be reset if you reset some tasks or update a source and some other events (because if you change the source requirements your skipped media may now be able to be downloaded, so it makes sense to unskip the media so it gets retried again in case it is now available).
Really what this needs is a skip
flag which is managed internally by tubesync and the downloader, and another manual_skip
flag which can be set through the web UI so a single skip
flag isn't re-used for both purposes, and both of these states need to be checked when tasks and signals are run.
OK, that makes sense, didn't know about #280, my bad. Your suggestion makes sense tho, I'll try to see if I can add a manual_skip
to the Media model and try to find the places to adapt the code accordingly (mostly signal.py and views.py I suppose) - I may have to request a review on the PR from you then, as you do certainly know better if I missed a place or two - keeping you posted. :-)
Hi, maybe I'm still missing "something" here, but I have following use-case: One of these aaaaaaaaaaaaages old videos (Mighty Mushin' Emo Rangers) I tried to add/download was (errorously) marked as "not able to be downloaded", so I actually wanted to "skip" the media for now, but it keeps getting re-un-skipped by
signals.py->media_post_save
.Am I missing something here?