Ability to not save certain categories in history

[StockportJambo]

Hi there. Would be really nice if you could somehow have a flag which stops certain categories from being saved in the history after a successful download. Specifically XXX stuff really. 

I have to go through and manually remove anything I don't want others to see.

[shypike]

And they don't see your queue?

[StockportJambo]

It is a point, yes. 

But no, generally they don't. I usually download that stuff late at night and leave it running when everyone's gone to bed... and make use of the auto-shutdown feature. I then have to remember to delete all that naughty stuff from my history in the morning before others see it when they start their morning downloads.

It's a minor thing, it would help me enormously, and I suspect (I'm a programmer) it wouldn't be hard to code. So I thought I'd ask. 

[shypike]

I'd just erase the entire history every time
Sorry, I'm not going to spend time implementing this.
There are just too many caveats (how do you know an item should be erased, how will the UI be etc.)

You could fool around with the API.

[StockportJambo]

Nah, I like & use the history, I just want it optional for some categories - that's all.

I'll mess around with the API.

Cheers. 

[keithm]

Did anything come of this? I think it's actually a pretty useful feature...

[shypike]

Poses more questions than it solves:
- No history entry, OK that's straightforward
- What if the download fails, no entry either? You won't know what happened.
- Send an email when succeeded?
- Send an email when failed?

There's no way all this will get implemented in options.
It's all or nothing: trace or no trace.

[keithm]

Poses more questions than it solves:
- No history entry, OK that's straightforward
- What if the download fails, no entry either? You won't know what happened.
- Send an email when succeeded?
- Send an email when failed?

There's no way all this will get implemented in options.
It's all or nothing: trace or no trace.

What about this?

You seem to have two scenarios:
A) All
B) Nothing

It seems's you have answers to the questions you asked for both those scenarios right?

So, why not just do the logic right at the top level? So treat all categories by default as all (A), and those that are marked excluded as (B) Nothing.

[shypike]

What is relatively easy to implement is a (ini-file-only) option to suppress traceability
at the category level. So, something like this:

Code: Select all

[categories]
[[xxx]]
history=0
priority = -100
pp = ""
etc.

[keithm]

What is relatively easy to implement is a (ini-file-only) option to suppress traceability
at the category level. So, something like this:

Code: Select all

[categories]
[[xxx]]
history=0
priority = -100
pp = ""
etc.

That would be awesome if possible

[shypike]

Not sure yet.
What should happen when a job fails?
Without a history entry there's no retry option either.

[baz]

Not sure about everyone else here.... but I would only be using this feature for categories that I really don't care a whole lot about if they complete or not. For XXX, I'm sure a lot of people just tag a bunch and most/all finish. If one doesn't, oh well. If someone were to make a change in the .ini to disable history for a category, they would then also be agreeing to manually manage (deleting from disk in OS) failed jobs from their Incomplete dir.

[AutomaticCoding]

Was this ever implemented? I have a category that's only populated by RSS feeds, I really don't care if any of the files fail, I just want:-

If file downloads:-
1. Process it normally
2. Delete from history

If file fails:-
1. Process it normally
2. File failed for whatever reason
3. Delete all temporary data ("Currently downloading" files)
4. Delete all non-temporary data ("Downloaded files/unrared" files)
5. Delete from queue & database

The files are deleted relatively quickly anyway after they're downloaded automatically (Around 12 hours, automatically using the last modification/access time).

I'll poke around with the API a bit later, however, no point if it was already implemented.

[shypike]

There already an Scheduler event for removing failed jobs: "Remove failed jobs".
Other than that, no effort has been spent on making "secret" downloads.
Don't you guys have separate accounts for your spouse and kids?

[bitbot]

Here's a small Node script/container to tackle this job:

https://github.com/treyturner/sabnzbd-sanitizer