[ The road to RC ] Todo's

[p0psicles]

This list will be used as a roadmap towards RC and later the merge to Master.
The list is meant for finishing already started features or bugfixes.

General

• Bump Database version

Manual Search

• Episode snatched with manual search doesn't change its status to snatched in show overview Fixed update searchQueueItem with status of snatchQueueItem when snat… #451
• Result snatches should be queued in a separate thread, as opposed to currently being queued in the searchQueueScheduler thread. [Manual Search] Added a ForcedSearchQueue scheduler for processing forced searches and failed downloads. #395
• A forced search (also used by manual search) should be queued in a separate thread, as opposed to currently being queued in the searchQueueScheduler thread. [Manual Search] Added a manualSnatchScheduler to handle SnatchQueue items #366
• The snatchSelection page should display snatch/download/failed download history, like how it's displayed in the displayShow page.
• Disable season search if season has still unaired episodes
• Add season pack manual searching [Manual Search] Season manual search #389

General bugs

• Fix URL limit (I guess that's about Fix for the massEdit table selecting allot of shows. #434)
• Queue show removals, as to wait for all threads to finish and make sure it can be removed safe [APP SUBMITTED]: Thread-16 :: [55af592] No Show Object found for show with indexerID: 305687 #244 Added a global list that's updated with shows that have been deleted. #567
• Fix unicode issues during post processing Fix unicode issues during post processing. #390
• Fix tmdb certificate error a6a504a
• Not saving NZB cats
• Check IMDB for showinfo results in keyErrors like KeyError: 'runtimes' [APP SUBMITTED]: 'year' ::: NOTE: This error happened when updating ::: #379 Fix KeyError in IMDb info #391 Initial rewrite of loadIMDbInfo() #385
• Updated ConfigObj does not properly save non-ascii values. (Revert for RC until we can finish the ConfigObj validators) @medariox can you verify this is fixed now?

Subliminal

• Limit the amount of "2016-04-15 10:18:22 DEBUG FINDSUBTITLES :: [1f87e70] Found subtitle" messages. Found subtitle isn't really "informative". @ratoaq2
• Improve performance or throttle subtitleFinder thread cpu usage. As a search is bringing my dualcore Atom on it knees. Wonder what it will do to a low end arm device. Give the CPU a break while searching for subs #472

@pymedusa/contributors

[labrys]

You don't need to query the full history, just the history for that particular episode. The idea is to know which releases have already been snatched in the past so the user doesn't try the same one again. More specifically you only need to query for snatched/downloaded statuses in the history.

[fernandog]

@p0psicles need only one fix for manual search
main thread updated

[p0psicles]

Yeah and we still need allot of bugfixes before we can start moving to RC1.

Also personal note! Need to send mail to contact@anizb.org with requests to add us as a compatible client, when we merge to master.

[OmgImAlexis]

If anyone needs access to our pymedusa.com email let me know as I have it setup. It'll look a little better to use that instead of a personal email.

[p0psicles]

If we focus on this list from now, we're very close to release: https://github.com/pymedusa/SickRage/milestones/RC1
But then we should lay low on the "improvements" and definitely stop working on new features.

@pymedusa/developers What do you guys think?

[ratoaq2]

Related to:

Limit the amount of "2016-04-15 10:18:22 DEBUG FINDSUBTITLES :: [1f87e70] Found subtitle" messages. Found subtitle isn't really "informative". @ratoaq2

This is what subliminal will log::
https://github.com/Diaoul/subliminal/blob/develop/subliminal/providers/legendastv.py#L426
https://github.com/Diaoul/subliminal/blob/develop/subliminal/providers/legendastv.py#L94
Found subtitle <%s [%s] %r>' % (self.__class__.__name__, self.id, self.name)

The issue is that the web page that shows the logs doesn't escape the log and the information between <and > is not displayed. What is the expectation here? To fix it and display the correct log message with all characters and information or to suppress it?

[labrys]

@ratoaq2 I would think try displaying. If we find that's still too verbose we can suppress it. Either imo would be better than an uninformative message.

[labrys]

Closing this as release to v0.1.0rc1 complete. If no issues present in the next couple days lets RTM.