fix(debrid): run torbox usenet availibility batch checks in sequence

[webstreamr]

first step to avoid 5/s errors in this endpoint. if requests are done in batches because they are more than 100, then they will run in sequence instead of parallel per add-on

Summary by CodeRabbit

Release Notes

Bug Fixes

• Improved error handling and validation for Torbox USENET cached availability checks. Error messages are now more descriptive and informative, including comprehensive details about failures. This enhancement increases visibility into issues when they occur, allowing for faster issue resolution and strengthening the overall reliability of USENET cache checking on Torbox.

[coderabbitai]

Walkthrough

Refactored Torbox USENET cached availability checks to replace parallel batch processing with sequential execution, whilst introducing enhanced error propagation and API response validation to improve error diagnostics and control flow clarity.

Changes

Cohort / File(s)	Summary
Torbox API Error Handling packages/core/src/debrid/torbox.ts	Replaced parallel Promise.all batching with sequential for-of loop. Added enhanced error propagation with statusCode, statusText, headers, and body details. Introduced API response shape validation with explicit array type checking. Consolidated duplicate error construction into single error path.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰✨ A rabbit hops through sequential dreams,
Where batches flow like gentle streams,
With errors caught in crystal light,
And validation holding tight—
The code now bounces, clean and bright! 🎯

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: converting parallel batch processing to sequential execution for Torbox USENET availability checks.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@packages/core/src/debrid/torbox.ts`:
- Around line 210-218: The thrown DebridError in the instant-availability check
loses its structured metadata when later passed into convertTorBoxError; update
the catch/rehydration logic (the handler that currently calls convertTorBoxError
around the catch at line ~259) to detect DebridError instances and re-throw them
directly (if (err instanceof DebridError) throw err;) instead of converting,
otherwise continue to call convertTorBoxError(err) for non-DebridError errors so
statusCode/statusText/headers remain intact.

🧹 Nitpick comments (1)

packages/core/src/debrid/torbox.ts (1)

220-231: Add type: 'api_error' for consistency.

Other DebridError constructions in this file include type: 'api_error' (e.g., lines 144, 287, 327). Consider adding it here for consistency and better error classification.

♻️ Proposed fix

           if (!Array.isArray(result.data.data)) {
             throw new DebridError(
-              'Invalid response from Torbox API. Expected array, got object',
+              'Invalid response from Torbox API. Expected array',
               {
                 statusCode: result.metadata.status,
                 statusText: result.metadata.statusText,
                 code: 'UNKNOWN',
                 headers: result.metadata.headers,
                 body: result.data,
+                type: 'api_error',
               }
             );
           }

[webstreamr]

TorBox increased limits to 300/m which should be enough. Aiostreams should still switch to POST using more hashes, maybe 500 per call in sequence as ST does for torrents.

For that TorBox-App/torbox-sdk-js#2 is needed