mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 07:13:29 +00:00
fix(anamnesis): serialise the AI switch writes so a PUT cannot resurrect a section
This commit is contained in:
1 parent
8ae60e2cb3
commit
23f008c8bb
5 files changed
+74
No files matched your search
@@ -445,6 +445,25 @@ function lifeSwitches(
|
||||
) as Record<LifeAiSection, boolean>;
|
||||
}
|
||||
|
||||
/**
|
||||
* Serialise every read-modify-write of a profile's AI switches. Two routes
|
||||
* write the one array: this module's switch route and the about-me PUT, which
|
||||
* replaces its eight sections and carries the life switches over as stored.
|
||||
* Without a lock, a PUT that read the array before a concurrent switch-off
|
||||
* committed wrote the old value back and turned the section on again. A
|
||||
* transaction-scoped advisory lock covers the first write too, when there is
|
||||
* no row yet to lock.
|
||||
*/
|
||||
export async function lockAiSections(
|
||||
tx: Prisma.TransactionClient,
|
||||
userId: string,
|
||||
): Promise<void> {
|
||||
await tx.$queryRaw`
|
||||
SELECT 1 AS locked
|
||||
FROM pg_advisory_xact_lock(hashtextextended(${`ai-sections:${userId}`}, 0))
|
||||
`;
|
||||
}
|
||||
|
||||
/**
|
||||
* Switch life-circumstance sections in or out of the AI inclusion list. Only
|
||||
* the named sections change; the other stored values, the five about-me
|
||||
@@ -459,6 +478,7 @@ export async function updateLifeAiSections(
|
||||
base?: Date,
|
||||
): Promise<LifeAiSectionsOutcome> {
|
||||
return prisma.$transaction(async (tx) => {
|
||||
await lockAiSections(tx, userId);
|
||||
const row = await tx.userHealthProfile.findUnique({
|
||||
where: { userId },
|
||||
select: { aiIncludedSections: true, updatedAt: true },
|
||||
|
||||
Reference in new issue
Block a user