peter
fad656988a
Backend - A run's outcome write sits outside the job's own try: a database blip after a run that succeeded no longer records it as failed (the row waits for the next start's sweep). - An interrupted run keeps what it spent (the sweep sums its quota rows, as finish does). - The Scheduler's ad-hoc row says running while any backfill runs, not only the newest. - recent_runs reads each job's last runs off its index instead of ranking the whole table. - An interval change is stored with its audit row in one transaction, then rescheduled. - One API instance per database is the stated contract (.env.example, jobruns). - Turning full history on for a channel already complete records no run. - Migration 0109 round-trips interrupted and ad-hoc runs; the run words' DB CHECKs are test-held to the enums; the account filter is one helper for the four activity reads. - An audit row says how many of its request's log lines are still kept. Frontend - An "All" period reaches every row still kept (runs and admin actions outlive 90 days). - Back/Forward is followed in place by the server log: a closing dialog no longer turns Live off; a pivot still opens a fresh log. - Runs moved over from the audit log read their one-liner in the reader's language. - Filter choices or accounts that failed to load say so beside the filters, with a retry. - An old server-log link keeps its account, text and range; a remembered retired page opens its tab. - A request whose lines are gone says so instead of linking to an empty list. - The log lines and the history rows share one row frame, and the server log one list frame with the other tabs; an empty list is announced; each day's quota is readable.
38 lines
1.5 KiB
Python
38 lines
1.5 KiB
Python
"""The words a background run's row is written with — the `job_runs` table's status and trigger.
|
|
|
|
One source for the literals: the scheduler writes them, the startup sweep rewrites `running`, the
|
|
model's CHECK constraints are built from these sets, and the dashboard reads them back (the frontend's
|
|
copies are held to them by `backendIds.contract.test.ts`). The migrated database's CHECKs are frozen
|
|
in its migration: a test holds them equal to these sets, so a new word fails until a migration adds
|
|
it (`test_runstatus.py`). The download pipeline's `cancelled`/`canceled` drift (`downloads/status.py`)
|
|
is why a status is never typed as a bare string.
|
|
"""
|
|
|
|
from enum import StrEnum
|
|
|
|
|
|
class RunStatus(StrEnum):
|
|
RUNNING = "running"
|
|
OK = "ok"
|
|
ERROR = "error"
|
|
# Sync was paused: the run was due and deliberately did nothing.
|
|
SKIPPED = "skipped"
|
|
# The process stopped while the run was going (a deploy, a crash): set at the next startup, so a
|
|
# row never claims to be running in a process that no longer exists.
|
|
INTERRUPTED = "interrupted"
|
|
|
|
|
|
class RunTrigger(StrEnum):
|
|
# The run's interval came round.
|
|
SCHEDULED = "scheduled"
|
|
# An admin pressed "run now" (or "run all").
|
|
MANUAL = "manual"
|
|
# A user's own action started work on one target (a channel's full history), outside the
|
|
# recurring jobs.
|
|
AD_HOC = "ad_hoc"
|
|
|
|
|
|
def sql_in(values: type[StrEnum]) -> str:
|
|
"""`'a', 'b'` — the IN-list a CHECK constraint names these values with."""
|
|
return ", ".join(f"'{v.value}'" for v in values)
|