mirror of
https://github.com/rmcrackan/Libation.git
synced 2026-09-12 21:57:19 -04:00
Allamagoosa
b6875591f0
EffectiveConcurrentDownloads clamps the setting by Environment.ProcessorCount, so a test asking for three books at once starts only two on a small machine, waits out its ten second patience and fails. Reproduced with DOTNET_PROCESSOR_COUNT=2: three failures and a thirty-four second run, against five seconds and none on a sixteen core box. The CI matrix includes runners small enough to hit it. Machine capability is now overridable, and the dispatch tests pin it to the concurrency they are asking about. The clamp itself is unchanged in the app. Two tests for the seam while it is there, since neither the point-of-use clamp nor the hint had any coverage: that a machine smaller than the setting holds the loop down without rewriting what the user asked for, and that ConcurrencyHint says so and falls silent when the machine can keep up.