mirror of
https://github.com/penpot/penpot.git
synced 2026-10-30 06:20:32 +00:00
d3ca9a0b83
* 🎉 Move backend jobs to the unified job table substrate Replace the generic 'task' table with a unified 'job' table as the durable substrate for all backend jobs, and migrate every producer and consumer to it. The legacy 'task' table stops receiving writes but stays dormant (still cleaned by tasks-gc); upload-session chunking and the other post-branch upstream changes are preserved. New 0154 migration creates the 'job' table: dispatch and lifecycle columns (name, queue, priority, scheduled_at, retries, status, timestamps, props) plus optional user-facing ledger columns (profile_id, target, progress, error, result, resource_id, expires_at). No modified_at trigger: the application updates it on every write for lease and orphan detection. Partial indexes cover the dispatcher claim query, orphan scanning, and per-profile listing. New app.jobs public API: submit!/invoke!, heartbeats and progress reporting, a precompiled job-def registry (name, schema, handler, decoder, validator), an ephemeral request/response mode, and a management API for external workers. The dispatcher claims new/retry rows (FOR UPDATE SKIP LOCKED) with a plain JSON redis payload and marks lease-expired running rows as orphaned; the runner executes per-queue with the same retry conventions. New jobs GC (daily): deletes expired rows and retains internal terminal rows per :jobs-retention, touching referenced storage objects so storage-gc-touched reclaims them. Job resources live in a dedicated job-resource bucket with a reclaim branch in storage-gc-touched. All production call-sites (sendmail, delete-object, demo-purge, file-gc, offload, webhooks, quotes, nitrate bulk delete, snapshots, telemetry) and the ten cron tasks now submit through app.jobs; cron is a pure scheduler and the legacy worker registry, task-table inserts, and per-namespace handlers are removed. Includes migrations, dispatcher, runner, jobs, request/response, jobs GC, management API, and cron test suites. AI-assisted-by: glm-5.3-flash AI-assisted-by: muse-spark-1.3-contributor AI-assisted-by: kimi-k3 AI-assisted-by: mimo-v2.5 * ✨ Address review comments on jobs substrate Resolves the four open review threads on the jobs PR. Orphaned jobs are now marked aborted, a system-side terminal state with no retry: the dispatcher sweep stores the end event with outcome aborted in a single bulk insert in the same transaction, records the terminal outcome next to the orphaned counter, and reports an error log; orphans keep alerting through the log and the counter, with no user notification. The aborted state is terminal everywhere: the status CHECK, the sweep, the lifecycle writers, the jobs GC retention, the backlog gauges and the user status mapping, with tests covering each transition. The claim comment, the 2.20 doc version and the legacy task table notes are corrected, and objects-gc heartbeats per chunk. AI-assisted-by: muse-spark-1.3-contributor
47 lines
2.0 KiB
Clojure
47 lines
2.0 KiB
Clojure
;; This Source Code Form is subject to the terms of the Mozilla Public
|
|
;; License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
;; file, You can obtain one at http://mozilla.org/MPL/2.0/.
|
|
;;
|
|
;; Copyright (c) KALEIDOS INC
|
|
|
|
(ns backend-tests.worker-test
|
|
(:require
|
|
[app.common.schema :as sm]
|
|
[app.msgbus :as mbus]
|
|
[app.worker :as wrk]
|
|
[app.worker.cron :as wcron]
|
|
[app.worker.dispatcher :as wdisp]
|
|
[app.worker.runner :as wrkr]
|
|
[clojure.test :as t]))
|
|
|
|
;; The dispatcher's push and the runner's pop agree on the Redis list
|
|
;; only through this helper, so the test helpers use it too. That
|
|
;; keeps producer and consumer in sync by construction, but it also
|
|
;; means no other test would catch a malformed shape. This test pins
|
|
;; the physical format instead.
|
|
|
|
(t/deftest queue-key-pins-the-physical-redis-shape
|
|
(t/testing "tenant and queue compose the documented key"
|
|
(t/is (= "penpot.worker.queue:acme:default"
|
|
(wrk/queue-key "acme" :default))))
|
|
(t/testing "a string queue gives the same key as a keyword one"
|
|
(t/is (= "penpot.worker.queue:acme:default"
|
|
(wrk/queue-key "acme" "default"))))
|
|
(t/testing "hyphens travel through untouched"
|
|
(t/is (= "penpot.worker.queue:my-tenant:daily-cleanup"
|
|
(wrk/queue-key "my-tenant" :daily-cleanup)))))
|
|
|
|
;; Booting the backend asserts these integrant keys, and assert-key
|
|
;; compiles the schema first: a ref with no registered schema crashes
|
|
;; the boot with :malli.core/invalid-schema instead of asserting. The
|
|
;; component schemas lean on the shared registry (db pool, metrics,
|
|
;; redis client, msgbus, job defs), so the registry dependencies must
|
|
;; be loaded for them to compile, like the full system does.
|
|
(t/deftest worker-component-schemas-resolve-every-ref
|
|
(t/testing "cron, dispatcher and runner schemas compile"
|
|
(t/is (sm/schema? (sm/schema ::mbus/msgbus)))
|
|
(doseq [s [@#'wcron/schema:params
|
|
@#'wdisp/schema:dispatcher
|
|
@#'wrkr/schema:params]]
|
|
(t/is (sm/schema? (sm/schema s))))))
|