Skip to content

Reject acquire after pool destroy - #87

Closed
aouxwoux wants to merge 1 commit into
Vincit:masterfrom
aouxwoux:codex/reject-acquire-after-destroy
Closed

Reject acquire after pool destroy#87
aouxwoux wants to merge 1 commit into
Vincit:masterfrom
aouxwoux:codex/reject-acquire-after-destroy

Conversation

@aouxwoux

@aouxwoux aouxwoux commented Jul 2, 2026

Copy link
Copy Markdown

Fixes #81.

What changed

  • Reject acquire() immediately when the pool has already been destroyed.
  • Keep the existing aborted error message used for aborted pending acquires.
  • Preserve acquireFail event emission for the rejected acquire.
  • Add a regression test that verifies the acquire does not wait for acquireTimeoutMillis and does not remain queued.

Verification

  • npm run build
  • npm test
  • npm run lint

@aouxwoux aouxwoux closed this Aug 3, 2026
@aouxwoux aouxwoux changed the title [codex] Reject acquire after pool destroy Reject acquire after pool destroy Aug 3, 2026
@aouxwoux
aouxwoux deleted the codex/reject-acquire-after-destroy branch August 3, 2026 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

acquire times out if called after destroy

1 participant