Prisma Dev WAL Polling Enters Aborted Socket Transactions and Breaks Shutdown
Is it fixed? Not yet.
Ongoing since Nov 16, 01:53 UTC. First reported Nov 16, 01:53 UTC.
What happened
In @prisma/dev@0.25.2 and @electric-sql/pglite-socket@0.1.3, internal WAL and streams work queries the PGlite instance while a client transaction is still aborted, causing a 25P02 error. This issue also occurs during server.close() with an aborted client transaction.
What caused it?
Internal WAL/Streams work queries the same PGlite instance while a client transaction is still in an aborted state following an expected SQL error, triggering error code 25P02.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
@prisma/dev: WAL polling enters aborted socket transactions (25P02) and breaks shutdown
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First report@prisma/dev: WAL polling enters aborted socket transactions (25P02) and breaks shutdown(opens GitHub issue in a new tab)
Package and version @prisma/dev@0.25.2 (current npm release), @electric-sql/pglite-socket@0.1.3 What happened? After a socket client commits a write, opens another transaction and receives an expected SQL error, internal WAL/Streams work queries the same PGlite instance while the client transaction is still aborted. It rejects with code 25P02: current transaction is aborted, commands ignored until end of transaction block. This also occurs during server.close() with an aborted client…
by anaibol 0upvotes 1comments
FAQ
What happened in the Prisma issue?
In @prisma/dev@0.25.2 and @electric-sql/pglite-socket@0.1.3, internal WAL and streams work queries the PGlite instance while a client transaction is still aborted, causing a 25P02 error. This issue also occurs during server.close() with an aborted client transaction.
What is affected by the Prisma issue?
Prisma (versions: @prisma/dev@0.25.2, @electric-sql/pglite-socket@0.1.3).
When did the Prisma issue start and end?
It started Nov 16, 01:53 UTC and is still ongoing (3 d 3 h so far). This page updates as it develops.
How do I get alerts for Prisma?
Subscribe to the Prisma RSS feed for every new Prisma incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Prisma is down. Prisma feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.