[NEEDS CODE REVIEWER] (time-out related) Fix detect_deletions disable gating and harden timeout handling#333
Conversation
|
Can we please get this merged? Would like to use V2 but this timeout issue is preventing me from connecting to my qbittorrent instance |
|
hi @tomerh2001 , I am truly sorry I haven't looked into your PR in such a long time. I do appreciate very much that you took the time to contribute. Unfortunately, I don't have the time to look into it still. Would you be willing to act as a formal contributor? If yes, I will add you, and if I find others (from open PRs), hopefully you can review each others PR and they can be merged. Thanks for letting me know, and apologies again for my radio silence. Would love to have you on board! |
|
Hey @tomerh2001, thank you for contributing! I am currently reviewing this as part of clearing the open PR backlog with @ManiMatter. Read through against the linked issues — code looks solid, two small asks before I'd approve. Linkage confirmed:
Ask 1 — auto-close keywords: Heads-up — overlap with #346: Code-wise: error boundaries are scoped tightly (per ARR group, per download-client job, per qbit cookie refresh), |
Summary
detect_deletionsgating so disabled jobs do not start folder watchers (main.pynow checks.enabled).JobParams.__bool__so object truthiness consistently reflects job enabled state.general.request_timeout(and envREQUEST_TIMEOUT) instead of a hardcoded 15s timeout inmake_request.request_timeoutand add regression tests.Why
detect_deletionsruns even when disabled).Validation
python3 -m pytest -qpython3 -m pylint main.py src/job_manager.py src/utils/common.py src/settings/_general.py src/settings/_jobs.py src/settings/_user_config.py tests/jobs/test_job_manager.py tests/settings/test_general.py tests/settings/test_jobs.py tests/utils/test_common.py