anhtahaylove 9492357360 fix(deepseek): release the PoW worker slot when spawning fails (#13097) ...

`solveInWorker` increments `activeWorkerCount` before constructing the Worker,
but the `cleanup()` that decrements it lives inside the promise executor and only
runs once the worker exists. Anything that throws first -- most obviously
`resolveWorkerPath()` when the worker script is missing, since it resolves
against `process.cwd()` -- leaves the counter permanently incremented.

With `MAX_CONCURRENT_WORKERS = 2`, two such failures wedge the solver for the
lifetime of the process: every later call rejects with "capacity reached (2)"
while no worker is actually running, and the real cause is hidden.

Construct the Worker inside a try/catch and release the slot before rejecting.

Fixes #13094

2026-09-09 20:58:23 -03:00

..

deepseek-pow-hash.js

fix(deepseek-web): replace unlicensed PoW artifacts (#11732)

2026-08-28 04:44:34 -03:00

deepseek-pow-worker.mjs

fix(deepseek-web): replace unlicensed PoW artifacts (#11732)

2026-08-28 04:44:34 -03:00

deepseek-pow.ts

fix(deepseek): release the PoW worker slot when spawning fails (#13097)

2026-09-09 20:58:23 -03:00