74fae140b1
- close() on a getDb() handle runs as a "connection close" section and checks its generation: a handle kept from a previous profile rejects with DbConnectionClosedError instead of closing the current profile. - closeUnlocked never rejects: the state is cleared and the generation bumped before close(), a failing close of the old pool is logged with logWarn, connectToProfile still opens the next profile and closeDb() resolves without a connection. - The blocking alert names a getDb() call in a callback as a possible cause only: a long restore also waits 15 s. - The generation check of the transaction handle is documented as a defence, not reachable today. - Tests: the "behind the queue" alert (pins the reset of lockHolder), close() on a stale and on the current handle, a failing close during a switch and in closeDb(). Refs #408 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| adr | ||
| archive | ||
| analyse-onboarding-2026-09.md | ||
| api-contract-prices.md | ||
| architecture.md | ||
| audit-bilan-2026-05.md | ||
| guide-utilisateur.md | ||
| qa-onboarding.html | ||
| qa-refonte-seed-categories-ipc.md | ||
| qa-update-cycle.md | ||