Gandalf/sofarr
Public Access
0
0
Fork 0
Code Issues 1 Pull Requests Actions 1 Packages Projects Releases 59 Wiki Activity

BUG: Permanent qBittorrent Sync API Fallback Degradation #29

New Issue
Closed
opened 2026-05-22 15:39:43 +01:00 by Gandalf · 1 comment
Gandalf commented 2026-05-22 15:39:43 +01:00
Owner
Copy Link
Copy Source

When a transient qBittorrent query failure occurs during active background polling, the client falls back to legacy mode. However, the background poller uses getDownloadsByClientType() which fails to call resetFallbackFlag(), stucking the client in legacy list queries permanently until restarted.

When a transient qBittorrent query failure occurs during active background polling, the client falls back to legacy mode. However, the background poller uses getDownloadsByClientType() which fails to call resetFallbackFlag(), stucking the client in legacy list queries permanently until restarted.
Gandalf added the Kind/Bug label 2026-05-22 15:41:15 +01:00
Gandalf commented 2026-05-22 16:00:42 +01:00
Author
Owner
Copy Link
Copy Source

Resolution: Patched server/utils/downloadClients.js to call client.resetFallbackFlag() on qBittorrent clients within the getDownloadsByClientType() loop (matching the getAllDownloads() behavior). Added a unit test in downloadClients.test.js to verify this fallback flag reset on polling routes.

Resolution: Patched server/utils/downloadClients.js to call client.resetFallbackFlag() on qBittorrent clients within the getDownloadsByClientType() loop (matching the getAllDownloads() behavior). Added a unit test in downloadClients.test.js to verify this fallback flag reset on polling routes.
Gandalf added the Area/Download Clients label 2026-05-28 11:57:15 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Area/Docker
Docker image and container packaging
 Area/Download Clients
Download client integrations
 Area/Frontend
Client-side UI and build tooling
 Area/History
History and completed downloads views
 Area/Logging
Log streaming, file handling, and debug infrastructure
 Area/Matching
Matching and correlation logic
 Area/Proxy
Upstream service proxy routes
 Area/SSE
Server-Sent Events and real-time streaming
 Area/Webhooks
Webhook processing and reliability
 Compat/Breaking
Breaking change that won't be backward compatible
 Compat/Non-Breaking
Non-breaking compatibility change
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Area/Download Clients Kind/Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Gandalf
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Gandalf/sofarr#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?