feat: platform backbone and field capture, first part (checkpoint)
Platform backbone (plan 2026-10-13-plattform-rueckgrat), reviewed tasks: - run roles api/worker/job/all with shared startup checks (Task 1) - schema and migration for DomainEvent, deliveries, JobRun, ThrottlerHit (Task 2) - audit, notifications and domain events written in the same transaction (Task 3) - dispatcher with SKIP LOCKED claims, retries and stale release (Task 4) - worker building blocks: tick, LISTEN/NOTIFY wake-up, health (Task 5) - worker process and entry points (Task 6) - throttler counters in Postgres (Task 19) - separate keys per purpose with key ring (Task 20) - public origin page without exact location (Task 22) - shop keys split into read and write (Task 23) - Kustomize base, components, overlay encry, CI validation (Task 26) Field capture T3 (plan 2026-10-13-t3-erfassung-am-stand), reviewed tasks: - brood frames, read endpoints, apiary overview and offline pack - network basics, offline queue v3, navigation sheets, form building blocks - new inspection with last-time hints and weather, varroa per day, treatment prefill, apiary page with round - inspection photo (Task 10) is implemented, review pending Not rolled out. Remaining tasks follow in later commits. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This commit is contained in:
1 parent
10cbe9bf2d
commit
c01a38835a
340 files changed
+25695
-1808
No files matched your search
@@ -0,0 +1,24 @@
|
||||
import { DbClient } from '../prisma/db-client';
|
||||
|
||||
/** LISTEN/NOTIFY channels the worker loops wait on, one per outbox. */
|
||||
export const WAKE_CHANNELS = {
|
||||
domainEvents: 'domain_event',
|
||||
calendarSync: 'calendar_sync',
|
||||
webhookDeliveries: 'webhook_delivery',
|
||||
} as const;
|
||||
|
||||
export type WakeChannel = (typeof WAKE_CHANNELS)[keyof typeof WAKE_CHANNELS];
|
||||
|
||||
/**
|
||||
* Wakes the worker loop behind `channel` before its next poll. The payload
|
||||
* is always empty: the loop reads its work from the table, so nothing can
|
||||
* leak through the channel or be slipped in as work. On a transaction
|
||||
* client Postgres sends the notification only on commit - a rolled-back
|
||||
* write wakes nobody. A lost notification only delays work until the poll.
|
||||
*/
|
||||
export async function notifyWorker(
|
||||
db: DbClient,
|
||||
channel: WakeChannel,
|
||||
): Promise<void> {
|
||||
await db.$executeRaw`SELECT pg_notify(${channel}, '')`;
|
||||
}
|
||||
Reference in new issue
Block a user