Files
pnpm/.changeset/libsql-remote-unique-violation.md
Zoltan Kochan f880d91124 fix(pnpr): recognise a unique violation reported by Turso (#17223)
The libsql auth backend classified a duplicate row only through SQLite
result codes. Turso's remote protocol reports it as a Hrana stream error
whose message carries the code name, so the counter seed on a second
start against the same database failed instead of being tolerated, and
pnpr exited at startup. A taken username reported the same way answered
500 instead of the login or name-taken path.

Parse the Hrana message the way the lock-conflict check already does.
Related to https://github.com/pnpm/tasks/issues/183.
2026-10-22 17:36:24 +02:00

277 B

@pnpm/pnpr
@pnpm/pnpr
patch

pnpr now starts against a Turso auth database it has already set up. The second start failed with a unique-constraint error on the user counter. Registering a username that is already taken on Turso now gets the same answer as on a local database.