Claude cd41422660 Use a concurrency limiter for ScreenScraper, honoring account threads ...

ScreenScraper enforces a per-account *thread* (concurrency) cap rather than
a request rate. Requests can take several seconds, so spacing out request
starts at 1/s could still leave multiple requests overlapping in flight,
exceeding the cap and getting rejected with ScreenScraper's custom HTTP codes.

- Add ConcurrencyLimiter: a runtime-resizable, loop-agnostic limiter that
  bounds simultaneous in-flight operations (held for the whole request via
  async context manager), instead of spacing request starts.
- Switch the ScreenScraper service from the req/s RateLimiter to a module-level
  ConcurrencyLimiter defaulting to a single thread.
- Recognize contributor/donor accounts: parse `ssuser.maxthreads` from each
  response and raise the concurrency allowance to match, so supporters scrape
  with their full thread count instead of the conservative default.

Adds unit tests for the limiter (blocking, wake-on-release, runtime resize)
and for the ScreenScraper slot-holding and thread-allowance updates.

https://claude.ai/code/session_01133QQuWvq8Zm25DZMP9PVr

2026-06-06 16:02:13 +00:00

..

test_cache.py

my brain is numb

2026-03-07 23:08:54 -05:00

test_context.py

run trunk fmt

2026-04-02 10:21:43 -04:00

test_filesystem.py

changes from bot review

2026-05-19 07:52:43 -04:00

test_gamelist_exporter.py

run fmt

2026-05-16 08:58:20 -04:00

test_pegasus_exporter.py

fix tests

2026-04-06 12:34:49 -04:00

test_rate_limiter.py

Use a concurrency limiter for ScreenScraper, honoring account threads

2026-06-06 16:02:13 +00:00

test_router.py

misc: Apply import sorting

2025-09-04 11:17:00 -03:00

test_ssrf.py

fix test

2026-05-27 21:50:56 -04:00

test_validation.py

fix(security): move SSRF defense into the HTTP client path

2026-05-27 17:58:14 -04:00