PrefectHQ/prefect - CodSpeed

prefect

Blog Docs Changelog

Performance History

Latest Results

Handle unrelated artifacts without descriptions Signed-off-by: merobi-hub <merobi@gmail.com>

merobi-hub:add-openlineage

2 hours ago

Fix custom facet var name Signed-off-by: merobi-hub <merobi@gmail.com>

merobi-hub:add-openlineage

4 hours ago

Keep the public active contract and cover the upsert path Addresses the round-3 review. Schedule.active and the Cron/Interval/RRule defaults go back to plain bool True; whether active was set now rides on a private marker instead of leaking None into the public API. The preserve-on-redeploy logic also runs on the create/upsert path, not just PATCH, and two slug-less schedules that share a definition are rejected with a 422 instead of silently inheriting one active state.

apoorva-01:fix/19302-preserve-disabled-schedule-on-redeploy

22 hours ago

Fix sync_compatible resolution in synchronous transaction hooks (#17656)

hsusul:fix-transactions-sync-rollback-hooks

2 days ago

Harden Docket task delivery semantics

codex/docket-background-task-ha

2 days ago

fix: abandon (not crash) evicted runs when Kubernetes owns retries Closes #22620. With a Kubernetes work pool at backoffLimit > 0, a SIGTERM (eviction) made the in-pod engine finalize the run Crashed via handle_crash, but Kubernetes then retried the Job and re-ran the flow, so the run left a terminal state and executed twice. Add an "abandon" SIGTERM behavior: when backoffLimit > 0 the worker sets PREFECT_FLOW_RUN_EXECUTE_SIGTERM_BEHAVIOR=abandon, and the engine bubbles the raw SIGTERM without proposing a state. The run stays non-terminal while Kubernetes retries the pod; if retries are exhausted the worker's non-zero-exit crash proposal finalizes it. Prefect reschedule and k8s Job backoff remain mutually exclusive. A raw SIGTERM can reach an async flow as a cancellation rather than a TerminationSignal, so the bubble is gated on a latch set by the SIGTERM handler to avoid abandoning ordinary cancellations (e.g. flow timeouts).

chuqCTC:fix/22620-abandon-sigterm-backofflimit

2 days ago

fix: abandon (not crash) evicted runs when Kubernetes owns retries Closes #22620. With a Kubernetes work pool at backoffLimit > 0, a SIGTERM (eviction) made the in-pod engine finalize the run Crashed via handle_crash, but Kubernetes then retried the Job and re-ran the flow, so the run left a terminal state and executed twice. Add an "abandon" SIGTERM behavior: when backoffLimit > 0 the worker sets PREFECT_FLOW_RUN_EXECUTE_SIGTERM_BEHAVIOR=abandon, and the engine bubbles the raw SIGTERM without proposing a state. The run stays non-terminal while Kubernetes retries the pod; if retries are exhausted the worker's non-zero-exit crash proposal finalizes it. Prefect reschedule and k8s Job backoff remain mutually exclusive.

chuqCTC:fix/22620-abandon-sigterm-backofflimit

2 days ago

fix(concurrency): release lease when caller is cancelled after the future is running Co-Authored-By: bot_apk <apk@cognition.ai>

devin/1784924513-fix-cancelled-lease-acquire

2 days ago

Latest Branches

0%

Add OpenLineage integration#22475

2 hours ago

177b0c2

merobi-hub:add-openlineage

0%

Preserve a paused deployment schedule on redeploy#22396

22 hours ago

c0a33f5

apoorva-01:fix/19302-preserve-disabled-schedule-on-redeploy

0%

Fix sync_compatible resolution in synchronous transaction hooks#22626

2 days ago

68b3847

hsusul:fix-transactions-sync-rollback-hooks

© 2026 CodSpeed Technology

Home Terms Privacy Docs