Kikobeats / superlock / 40714436558

100%

push

github

fix(create): make release idempotent per acquisition (#43)

Every holder of a createLock got the same release function, and the free
path handed out one cached promise that resolved to it. Calling release a
second time added a slot back and dequeued a waiter, even when the slot now
belonged to another holder. A mutex then ran two holders at once, and a
semaphore could exceed its limit for good.

Each acquisition now gets its own release closure that frees its slot only
on the first call. A distinct function per holder needs a distinct resolved
promise, so the free path allocates one again with Promise.resolve. That is
the cost of the fix: no shared function can tell a stale call from the
current holder's call.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

121 of 121 branches covered (100.0%)

Branch coverage included in aggregate %.

12 of 12 new or added lines in 1 file covered. (100.0%)

317 of 317 relevant lines covered (100.0%)

3372.94 hits per line