[NEEDS CODE REVIEWER] (time-out related) Adding timeout property to instances.

[eadgbear]

My instances are a bit overloaded, so adding some timeout parameters to them would be really useful for me

[ManiMatter]

hi @eadgbear

many thanks for your PR.

I am very much under water and can't spend time on decluttarr much more. Therefore, I am looking for contributors who can help maintain & review code. Would you be willing to start co-developing decluttarr together with whomever signs up otherwise?

That would be highly appreciated. Then the next person who will join can look into this PR, and would highly apprecaite if you could look at some of the existing ones (for example #333, which also deals with request timeout).

Thanks for letting me know.

[eadgbear]

hi @eadgbear

many thanks for your PR.

I am very much under water and can't spend time on decluttarr much more. Therefore, I am looking for contributors who can help maintain & review code. Would you be willing to start co-developing decluttarr together with whomever signs up otherwise?

That would be highly appreciated. Then the next person who will join can look into this PR, and would highly apprecaite if you could look at some of the existing ones (for example #333, which also deals with request timeout).

Thanks for letting me know.

I'm willing to give it my best!

[ManiMatter]

Awesome, thank you for volunteering. I just gave you contributor access.

[lolimmlost]

Hey @eadgbear, Thanks for contributing! I am reviewing as part of clearing the open PR backlog with @ManiMatter.

The per-instance timeout is real value:
Threading timeout through every make_request site for arr + qbit + sabnzbd is the kind of plumbing nobody wants to do but somebody had to. Tests look thorough.

Heads-up — overlap with #333:
#333 also adds general.request_timeout (same name, same default of 15s) plus the missing crash-handling half that issue #317 actually complains about. They'll conflict on merge — only one can introduce that setting.

Suggested path: wait for #333 to land (closes #329 and #317, two high-prio bugs), then rebase this on top to drop the duplicated general.request_timeout bits and keep just the per-instance override layer. Users get both: global default + per-instance override. Happy to help if the rebase is messy.

Linkage: worth referencing #317 in the body — this addresses one half of it (configurable timeout), even if #333 ends up the merged closer.
@ManiMatter any thoughts on this?

[ManiMatter]

@lolimmlost - Sounds like a good strategy, agree.

[ManiMatter]

@eadgbear - I see that your invite to become a collaborator has expired:

Let me resend a new invite to you. Please have a a look if you receive it, if not, please let me know!

[ManiMatter]

@eadgbear .. ping? :)