Nzbget scripts download#

new fields in RPC-method 'history': ServerStats (array), TotalArticles, SuccessArticles, FailedArticles.

new page in history dialog shows collected statistics.

number of successful and failed article downloads per news server.

added collecting of server usage statistical data for each download:.

new parameters 'NZBPP_HEALTH' and 'NZBPP_CRITICALHEALTH' are passed to pp-scripts.

new fields 'Health', 'CriticalHealth', 'Deleted' and 'HealthDeleted' are returned by RPC-Method 'history'.

new fields 'Health' and 'CriticalHealth' are returned by RPC-Method 'listgroups'.

for downloads having health less than critical health no par-check is performed (it would fail) Instead the par-check status is set to 'failure' automatically saving time of actual par-check.

par-check is now automatically started for downloads having health below 100% this works independently of unpack (even if unpack is disabled).

Nzbget scripts download#

health allows to determine download status for downloads which have unpack and/or par-check disabled for such downloads the status in history is shown based on health: success (health=100%), damaged (health ' critical) or failure (health ' critical).

health and critical health are displayed in download-edit dialog health is displayed in history dialog if download was aborted (HealthCheck=delete) this is indicated in history dialog.

new option 'HealthCheck' to define what to do with unhealthy (unrepairable) downloads (pause, delete, none).

if during download the health goes down below 100% a health badge appears near download name indicating the necessity of par-repair the indicator can be orange (repair may be possible) or red (unrepairable) if the health goes down below critical health.there is also a critical health which is calculated for each nzb-file based on number and size of par-files.100% health means no download errors occurred 0% means all articles failed.health indicates download status, whether the file is damaged and how much.new dialog to build filters in web-interface with instant preview.new dialog to see feed content showing status of each item (new, fetched, backlog) with ability to manually fetch selected items.new toolbar button 'Feeds' on downloads tab with menu to view feeds or fetch new nzbs from all feeds (the button is visible only if there are feeds defined in settings).button 'Preview Feed' on settings tab near each feed definition.new option 'FeedHistory' (section 'Download Queue').new options 'FeedX.Name', 'FeedX.URL', 'FeedX.Filter', 'FeedX.Interval', 'FeedX.PauseNzb', 'FeedX.Category', 'FeedX.Priority' (section 'Rss Feeds').De changelog voor deze uitgave kan hieronder worden gevonden. De opensourceapplicatie is beschikbaar voor Windows, OS X en Linux. Het kan onder meer automatisch bestanden repareren met par-bestanden en heeft een ingebouwde webinterface. Het programma is vergelijkbaar met SABnzbd.

Met dit programma kunnen bestanden van usenet gedownload worden. Since I use it consistently, I know that when I see aug at the beginning of a function, it's adding a property.Verleden week is versie 12.0 van NZBGet uitgebracht. So I'd rename your addPathProp function augPath and rename your addRunProp function augRun. One other potentially useful tip: I've settled on the naming convention of aug (short of 'augment') for adding a property or bit of info to an object. addRunProp means that x is something that will have a run property added to it). To figure out what x is, look at the function name (e.g.

You can think of x as the thing your function is operating on. Either come up with a descriptive name, or just use x. However the variable passed to addRunProp does not have the same structure as what is passed to addPathProp (the one passed to addRunProp requires an extra path prop). This is confusing since it implies the object has the same structure on each function call. It doesn't add any clarity to your function to have addModuleRunAndFilterInvalid split out into its own function, and returning the result of the pipe clarifies the purpose of the getScripts function itself.Īlso, in your code, you keep calling the object you're operating on dir. In both cases, I got rid of your addModuleRunAndFilterInvalid function. Const tryRequire = tr圜atch((path) => require(path).run, always(null)) Ĭonst path = scriptsPath(dir.name, 'index.js')įilter(x => typeof x.run = 'function'),