sickgear / sickgear Goto Github PK

Branch: master @ py3.8.12

When considering to remove the SUBLIMINAL subtitles, can you please keep the subtitle flags on the View Show page indicating there are subtitles included in the video container (in the right language!).

It would be even nicer if it is possible to move the downloads which are flagged (with subtile) to the archived folder by the press of a button or if selected / set to archived.

Expectation | Result
Detection of existing subtitles | Workable system for not native English speakers!
Detection of manual added subtitles |

Thanks in advance.

Ps. Did I say please? I really enjoyed the work so far, but the subtitles really matter a lot.

Branch: master

Branch version commit hash: c69affb

Steps to reproduce:
1) Open subtitle config
2) Select more than one language
3) Click to download all subtitles

I've checked the subtitles in that language exists but subliminal only downloads english subtitles. I could try to solve this issue myself but I don't know how to redirect subliminal log message to the [edit: removed typo] log file. Any help would be appreciated.

Regards

Currently the WEB classification tiers are limit to:

• 720p WEB-DL
• 1080p WEB-DL
• 2160p UHD 4K WEB

A commonly available video type is SD WEB-DL typically used for back catalogue pre-internet shows.

Request a new tier be added to cater for this quality.

Hello,

We aim to close issues as soon as possible. However, feature requests (not issues) were lingering for no good reason. So.. to keep things tidy, these thread types are labelled "enhancement" as usual, but also labelled "incubate" then closed.

This thread links those closed threads, you can still add comment, they are not dead.

Feature Requests : Incubated Enhancement Requests

Before posting an issue, please check the FAQ as it is often updated... an example

Also, your issue might have already been asked, see closed issues

Essential help on [How-to] Report Issues

Finally, smash that star button - it's free just like the support on this open source project.

Thanks

p.s. Consider this before asking for help; you support Liverpool FC and I come into your club house wearing a Chelsea FC shirt - do you feel to give me a beer? Spam accounts are blocked.

I don't find the checkbox to delete the file from the torrent client after download, is that feature missing or do I just not find it?

BRANCH: develop @ py3.8.5 / COMMIT: b1274b8 @ 0.22.0

Steps to reproduce:
1) Add a tv show that is known to have Norwegian metadata to SG. For Example https://thetvdb.com/series/beforeigners aka fremvandrerne.
2) Observe that English info/titles are fetched.
...

Additional notes:
It seems that TheTVDb API v3 is confused. Because I edited SG code to hard code use language tag 'nb' on API requests, and it fetched the info correctly. I suspect that when migrating to v3 API they somehow merged the Norwegian (no) and Norwegian Bokmål (nb/nob) language codes. I tried reporting the "bug" on their forums, and it supposedly got ticketed, but nothing has happened. Hopefully it will be fixed for v4, but as a reminder this issue is created for whenever v4 gets released, and SG gets migrated to it. So that you can take a look at it then.

Hi,

I'm just throwing this out these as a possible area for improvement somewhere down the line.

Currently Ignored Words and Required Words are configurable, but I was wondering if it would be possible to implement a Preferred Words system too?

That way, I could set a preferred words of DDP5.1 and/or DTS and it would select those rather than releases with AC3 or AAC in the name. If no DDP5.1 or DTS releases existed, it would still download the AC3/AAC releases.

I'd also like to prefer x265 over x264 so it would be handy for this scenario too.

This is probably going to be a bit more complex than the current system, which simply eliminates potential downloads on an inclusive or exclusive basis. A Preferred Words system would probably need to rank the releases so the one with the most preferred words would be selected.

I'm not sure how easy it would be to include this, but presumably there must be some sort of selection criteria in the background which chooses the most appropriate release when multiple exact matches are found (based on name, quality, etc.)?

Thanks.

@clinton-hall
Unfortunately, I cannot get the new installer to work on my QNAP TS-253D.

What I did at first:

• By accident updated my firmware too far (5.0.1.2425) for old sickgear to stop working.
• Uninstalled old version
• Installed new version (entware etc all still installed)
• Opened sickgear and got "This site can’t be reached / refused to connect" on http://192.168.1.96:15625/

So what I tried then:

• Initialized my NAS after data backup so its 100% fresh with my old firmware: 5.0.0.2131
• installed Entware
• installed Sickgear through the new install file
• I opened sickgear and still got "This site can’t be reached / refused to connect" on http://192.168.1.96:15625/

Am I missing something?

I realize HEVC/x265 is not a "quality." However, it would be nice to be able to tell SickGear to "upgrade" shows to 1080p/720p x265 after already downloading a x264 (or whatever) SD/HD version of the show.

More and more release groups are starting to use x265, albeit usually delayed days after new episodes release. Those of us who collect shows for long-term storage would benefit from the smaller file sizes, even if the release becomes available days or even weeks after.

Today, we can add "x265" and/or "hevc" to the list of required words, but it would be preferred to not limit the search results that way to prevent completely missing out on an episode because an x265 version was never found.

Please add the Downloads column (the downloaded shows / the total number of shows) to the Bulk Change columns

Add this column

To this list on the Bulk Change page

version was latest version
branch was latest branch

Steps to reproduce:
1) clicked on link to update python in the gui
2) restart never completed
3) attempted windows chrome page refresh
4) could not connect
5) went to synolgy vs.7.2.1 update 4 package center and attempted to run.
6) received error message "Failed to run the package service. Package would not start! See: /var/log/packages/sickgear.log"
7) attempted to repair package
8) same error message
9) uninstalled package
10) restarted synology nas
11) installed spk from SickGear wiki installation page for Synology 7
12) same as above
13) uninstalled sickgear package
14) deleted sickgear folder from @appstore
15) rebooted synology nas
16) reinstalled spk from wiki
17) same as above

... etc.

 2024/04/01 16:59:38	uninstall sickgear 1.08 Begin /bin/rm -rf /volume1/@appstore/sickgear
2024/04/01 16:59:39	uninstall sickgear 1.08 End /bin/rm -rf /volume1/@appstore/sickgear ret=[0]
2024/04/01 16:59:39	uninstall sickgear 1.08 Begin /bin/rm -rf /volume1/@apptemp/sickgear
2024/04/01 16:59:39	uninstall sickgear 1.08 End /bin/rm -rf /volume1/@apptemp/sickgear ret=[0]
2024/04/01 16:59:40	uninstall sickgear 1.08 Begin postuninst
2024/04/01 16:59:40	uninstall sickgear 1.08 End postuninst ret=[1]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/mkdir -p /volume1/@appstore/sickgear -m 755
2024/04/01 17:00:14	install sickgear 1.08 End /bin/mkdir -p /volume1/@appstore/sickgear -m 755 ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/rm -rf /volume1/@appstore/sickgear
2024/04/01 17:00:14	install sickgear 1.08 End /bin/rm -rf /volume1/@appstore/sickgear ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/package /volume1/@appstore/sickgear
2024/04/01 17:00:14	install sickgear 1.08 End /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/package /volume1/@appstore/sickgear ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/rm -rf /var/packages/sickgear
2024/04/01 17:00:14	install sickgear 1.08 End /bin/rm -rf /var/packages/sickgear ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/mkdir -p /var/packages/sickgear -m 755
2024/04/01 17:00:14	install sickgear 1.08 End /bin/mkdir -p /var/packages/sickgear -m 755 ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/touch /var/packages/sickgear/installing
2024/04/01 17:00:14	install sickgear 1.08 End /bin/touch /var/packages/sickgear/installing ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/INFO /var/packages/sickgear/INFO
2024/04/01 17:00:14	install sickgear 1.08 End /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/INFO /var/packages/sickgear/INFO ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/rm -rf /var/packages/sickgear/scripts
2024/04/01 17:00:14	install sickgear 1.08 End /bin/rm -rf /var/packages/sickgear/scripts ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/scripts /var/packages/sickgear/scripts
2024/04/01 17:00:14	install sickgear 1.08 End /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/scripts /var/packages/sickgear/scripts ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/rm -rf /var/packages/sickgear/conf
2024/04/01 17:00:14	install sickgear 1.08 End /bin/rm -rf /var/packages/sickgear/conf ret=[0]
2024/04/01 17:00:14	install sickgear 1.08 Begin /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/conf /var/packages/sickgear/conf
2024/04/01 17:00:14	install sickgear 1.08 End /bin/mv -f /volume1/@tmp/synopkg/install.cMLpCe/conf /var/packages/sickgear/conf ret=[0]
2024/04/01 17:00:17	install sickgear 1.08 Begin postinst
2024/04/01 17:00:17	install sickgear 1.08 Clone main repository from: https://github.com/SickGear/SickGear.git to /volume1/@appstore/sickgear/app
2024/04/01 17:00:28	install sickgear 1.08 Application version:  3.30.16 (2024-03-24 20:30:00 UTC)
Defaulting to user installation because normal site-packages is not writeable
Collecting CT3 (from -r /volume1/@appstore/sickgear/app/requirements.txt (line 1))
  Using cached CT3-3.3.3.post1-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.whl.metadata (3.4 kB)
Using cached CT3-3.3.3.post1-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.whl (667 kB)
Installing collected packages: CT3
  Attempting uninstall: CT3
    Found existing installation: CT3 3.3.3.post1
    Uninstalling CT3-3.3.3.post1:
      Successfully uninstalled CT3-3.3.3.post1
Successfully installed CT3-3.3.3.post1
2024/04/01 17:00:35	install sickgear 1.08 End postinst ret=[0]
2024/04/01 17:00:35	install sickgear 1.08 Begin start-stop-status start
/var/packages/sickgear/scripts/start-stop-status: line 5: 14152 Illegal instruction     (core dumped) env LANG=en_US.UTF-8 "${PYTHON}" "${STARTMODULE}" -q --daemon --pidfile="${PIDFILE}" --datadir="${SYNOPKG_PKGVAR}" --port=${SYNOPKG_PKGPORT}
2024/04/01 17:00:40	install sickgear 1.08 End start-stop-status start ret=[3]
2024/04/01 17:00:40	(system) trigger sickgear 1.08 Begin start-stop-status stop
2024/04/01 17:00:40	(system) trigger sickgear 1.08 End start-stop-status stop ret=[0]
2024/04/01 17:14:27	start sickgear 1.08 Begin start-stop-status start
/var/packages/sickgear/scripts/start-stop-status: line 5: 18130 Illegal instruction     (core dumped) env LANG=en_US.UTF-8 "${PYTHON}" "${STARTMODULE}" -q --daemon --pidfile="${PIDFILE}" --datadir="${SYNOPKG_PKGVAR}" --port=${SYNOPKG_PKGPORT}
2024/04/01 17:14:29	start sickgear 1.08 End start-stop-status start ret=[3]
2024/04/01 17:14:29	(system) trigger sickgear 1.08 Begin start-stop-status stop
2024/04/01 17:14:29	(system) trigger sickgear 1.08 End start-stop-status stop ret=[0] 

Additional notes:

sickgear was working fine until i tried to update the python on March 31st

Good info helps replicate the issue and is the fastest way to get it resolved

Background: The result of a completed SABnzbd task is passed to the /autoProcessTV/sabToSickGear script which notifies SickGear to perform a media process.

The request is to add a new placeholder folder /autoProcessTV/mediacheck/ that will contain a system dependent binary that validates the integrity of a media file.

sabToSickGear will recursively scan parameter 1 from SAB, that is; The final directory of the job (full path) and for each filename with a valid media file extension, call the binary validator with the filename. Delete the file if the validator reports invalid media.

This means that any file that is;

• a valid media filename but has corrupt data will be deleted
• a valid media filename with 100% data integrity be left untouched for SG to process
• not a valid media filename ext, e.g. subtitles, nfo, will be left untouched for SG to process

I wanted to point out that opensubtitles.org put up a deprecation notice about the XML-RPC API on their Trac page.

any API running on OpenSubtitles.org is deprecated and not possible to register new user agents anymore, we plan to turn off OpenSubtitles.org API by the end of 2023. Please use new, stable ready-to-use ​OpenSubtitles.com REST API instead.

Apologies if this is more of a bug, but I am not sure how to categorise it. It's possible it's a 2-in-1.

Branch: develop

Branch version commit hash: 2ea74f3 @ 3.30.0

I have been limping along with NZBget since I opened #1240 way back when, but I really do prefer Sabnzbd, and I've finally had time to look into this. I run all apps in Docker, sickgear:develop, linuxserver/nzbget and linuxserver/sabnzbd.

Steps to reproduce:
1) With SOCKS disabled, add Sabnzbd and test - notice connection success
2) Enable SOCKS and test - notice failure and error in logs
3) Repeat the above 2 steps with NZBget and notice success for either

This seems to point to an issue with Sabnzbd, but I have no issues with any other containers and as far as I can tell the containers are setup correctly. Both NZB containers have the same settings and relevant ports are open.

With SOCKS on:

Sabnzbd: Unable to connect to host

2023-09-07 12:27:37 ERROR HOME^WEB_0 :: Error, no response from SABnzbd 2023-09-07 12:27:37 WARNING SG.HELPER :: Failed 6 times, skipping domain 192.168.1.10 for 0:50:43, last failure at 2023-09-07 11:18:21 with fail type: connection

NZBget: Success. Connected

2023-09-07 12:28:26 DEBUG HOME^WEB_1 :: NZBGet URL: http://nzbget:**************@192.168.1.10:6789/xmlrpc 2023-09-07 12:28:26 DEBUG HOME^WEB_1 :: Success. Connected

Additional notes:

Just for the sake of testing, I fired up Sonarr, and added the SOCKS and Sabnzbd configs. This experiences the same behavior which again points to Sabnzbd, but then Sonarr specifically has the option to bypass local addresses and specified addresses: https://wiki.servarr.com/sonarr/settings#proxy

I found the "Bypass Proxy for Local Addresses" checkbox didn't help, but adding the Sabnzbd host to "Ignored Addresses" did the trick:

Is there a possibility that SickGear could have these options to mitigate such issues? Thanks :)

Branch: main

Commit tag: 2c2e6bb

Steps to reproduce:
1) Upgrade sqlite3 to 3.45.1,1
2) try to start sickgear

Downgrading to sqlite3-3.45.0_1,1 'solves' the issue

2024-03-23 09:44:23 INFO     TORNADO :: Starting SickGear on https://0.0.0.0:8081/
2024-03-23 09:44:23 DEBUG    MAIN :: config_version -> 23
2024-03-23 09:44:23 DEBUG    MAIN :: Detected database version: v20016
2024-03-23 09:44:23 INFO     MAIN :: Database schema is up-to-date, no upgrade required
2024-03-23 09:44:23 INFO     MAIN :: Checking database structure...
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Initial Schema database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: InitialSchema upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Consolidate Providers database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: ConsolidateProviders upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Add Backlog Parts database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: AddBacklogParts upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Add Provider Failure Handling database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: AddProviderFailureHandling upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Add Indexer To Tables database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: AddIndexerToTables upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Add Generic Failure Handling database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: AddGenericFailureHandling upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Add Save Queues database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: AddSaveQueues upgrade not required
2024-03-23 09:44:23 INFO     MAIN :: Checking database structure...
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Initial Schema database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: InitialSchema upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Size And Provider database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: SizeAndProvider upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking History database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: History upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking History Status database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: HistoryStatus upgrade not required
2024-03-23 09:44:23 DEBUG    MAIN :: Checking Add Indexer To Tables database upgrade
2024-03-23 09:44:23 DEBUG    MAIN :: AddIndexerToTables upgrade not required
2024-03-23 09:44:23 INFO     MAIN :: No orphan episodes, check passed
2024-03-23 09:44:23 INFO     MAIN :: No UNAIRED episodes, check passed
2024-03-23 09:44:23 ERROR    MAIN :: DB error: no such column: null
2024-03-23 09:44:23 INFO     MAIN :: SickGear.Start() exception caught no such column: null: Traceback (most recent call last):
  File "/usr/local/sickgear/sickgear.py", line 824, in <module>
    SickGear().start()
  File "/usr/local/sickgear/sickgear.py", line 492, in start
    sickgear.initialize(console_logging=self.console_logging)
  File "/usr/local/sickgear/sickgear/__init__.py", line 660, in initialize
    return init_stage_2()
  File "/usr/local/sickgear/sickgear/__init__.py", line 1570, in init_stage_2
    db.sanity_check_db(my_db, mainDB.MainSanityCheck)
  File "/usr/local/sickgear/sickgear/db.py", line 413, in sanity_check_db
    sanity_check(connection).check()
  File "/usr/local/sickgear/sickgear/databases/mainDB.py", line 43, in check
    self.fix_scene_exceptions()
  File "/usr/local/sickgear/sickgear/databases/mainDB.py", line 257, in fix_scene_exceptions
    sql_result = self.connection.select(
  File "/usr/local/sickgear/sickgear/db.py", line 289, in select
    sql_results = self.action(query, args).fetchall()
  File "/usr/local/sickgear/sickgear/db.py", line 269, in action
    sql_result = self.connection.execute(query)
sqlite3.OperationalError: no such column: null

OS: FreeBSD 14.0-RELEASE-p5

Branch: master @ py3.9.5

Branch version commit hash: COMMIT: 5a1a122 @ 0.25.0

Steps to reproduce:
1) Enable failed download handling in SickGear
2) Disable Abort jobs that cannot be completed and Post-Process Only Verified Jobs in SABnzbd
3) Enable empty_postproc in SABnzbd
4) Wait for a download to fail
...

A sanitised version of the relevant logs can be found HERE.

According to the logs, multiple download locations on the initial search, but then after the download fails, these are not attempted.

P.S. Thanks for all the great work you put into this project. Really enjoying the new version. The actor thumbnails are great.

https://github.com/Flexget/Flexget/blob/develop/flexget/plugins/filter/series.py
is the file that flexget uses for its wait
http://flexget.com/wiki/Plugins/series/timeframe

midgetspy/Sick-Beard#466

seems to be sorta what was being asked but in a diffrent aspect and the same

Clarity: Id always prefer HDTV > SDTV if a HDTV is released on BTN id be willing to wait 1 hr if SD is up there to see if HDTV is released if after say 1 HR (user defined) it does not have HDTV download the SDTV.

Also: I would always prefer BTN > Torrentshack (rss feed) > Freshontv > Kat.ph.sh.whateverthe hell the extension is now

Lets say kat has the show doctor who (2005) s09e01 it was released at 12:00 i would be willing to wait 8 hrs for it to be on btn or torrentshack at the very least. If torrent shack has it i would be willing to wait 1hr for btn to have it. This is hard to explain but the above links have managed to do it in a way that works for what is being requested and both are python so it is possible. basically I never want to use freshon.tv or kat.ph unless i absolutely have to.

Branch: master

Branch version commit hash: docker @ 0.21.5

I have tried prefixing with socks and socks5, no improvement.

Steps to reproduce:
1) Enter a socks address in the proxy field
2) Save

1) Detail... Unable to determine SOCKS version from socks://192.168.0.200:9118
 2) Traceback (most recent call last):
 3)   File "/opt/SickGear/lib/sg_helpers.py", line 299, in get_url
 4)     response = session.get(url, timeout=timeout, **kwargs)
 5)   File "/opt/SickGear/lib/requests/sessions.py", line 550, in get
 6)     return self.request('GET', url, **kwargs)
 7)   File "/opt/SickGear/lib/cfscrape/__init__.py", line 54, in request
 8)     resp = super(CloudflareScraper, self).request(method, url, *args, **kwargs)
 9)   File "/opt/SickGear/lib/requests/sessions.py", line 537, in request
10)     resp = self.send(prep, **send_kwargs)
11)   File "/opt/SickGear/lib/requests/sessions.py", line 650, in send
12)     r = adapter.send(request, **kwargs)
13)   File "/opt/SickGear/lib/cachecontrol/adapter.py", line 53, in send
14)     resp = super(CacheControlAdapter, self).send(request, **kw)
15)   File "/opt/SickGear/lib/requests/adapters.py", line 412, in send
16)     conn = self.get_connection(request.url, proxies)
17)   File "/opt/SickGear/lib/requests/adapters.py", line 309, in get_connection
18)     proxy_manager = self.proxy_manager_for(proxy)
19)   File "/opt/SickGear/lib/requests/adapters.py", line 182, in proxy_manager_for
20)     manager = self.proxy_manager[proxy] = SOCKSProxyManager(
21)   File "/opt/SickGear/lib/urllib3/contrib/socks.py", line 192, in __init__
22)     raise ValueError("Unable to determine SOCKS version from %s" % proxy_url)
23) ValueError: Unable to determine SOCKS version from socks://192.168.0.200:9118

Additional notes:
There are no specific config settings, start with a blank config and just enter a socks proxy.