mirror of
https://github.com/tubearchivist/tubearchivist-jf.git
synced 2026-03-24 05:26:49 +00:00
[GH-ISSUE #17] Can't create seasons in time, when videos count greate then 300 #14
Labels
No labels
duplicate
enhancement
help wanted
help wanted
invalid
pull-request
question
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tubearchivist/tubearchivist-jf#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @romanmindiyarov on GitHub (Oct 31, 2023).
Original GitHub issue: https://github.com/tubearchivist/tubearchivist-jf/issues/17
Timeouts accur for folders with a lot of files.
Need to increase number of attempts or sleep timeout in /app/src/series.py, string 212
@romanmindiyarov commented on GitHub (Oct 31, 2023):
Attempts for 516 videos
@bbilly1 commented on GitHub (Oct 31, 2023):
Does it eventually get created? It shouldn't matter how many videos there are in a season. But yes, if your JF is busy with other things, you'll might need to trigger it again manually: https://github.com/tubearchivist/tubearchivist-jf#limitations
@romanmindiyarov commented on GitHub (Oct 31, 2023):
Yes, it created successfully, but very slowly. If there are 2040 videos in the folder, then it takes even longer...
And yes, my server is not fast...
@romanmindiyarov commented on GitHub (Oct 31, 2023):
@bbilly1 commented on GitHub (Oct 31, 2023):
we need to have some sort of a timeout, otherwise this will run indefinitely and never fail, even if it will never create the seasons for reasons outside of the control of this script here. So just increasing the timeout to an arbitrary high number will not solve the problem.
Ultimately I don't assume you read in 2000 videos in batch all too often, so for these cases you should be able to just trigger it again manually, as documented.
Or alternatively you could implement a config var so you can configure the timeout to adjust it to low end hardware.