PrefectHQ/prefect - CodSpeed

prefect

Blog Docs Changelog

Performance History

Latest Results

docs: document new "IfPossible" Docker image pull policy option (#22515) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

main

49 minutes ago

Add docker image pull policy "always if possible" (#22154) Co-authored-by: Michael Hadorn <michael.hadorn@usb.ch> Co-authored-by: root <xx> Co-authored-by: CDWH-Dev <cdwh@usb.ch>

main

2 hours ago

Handle repeated coarse-clock state timestamp collisions (OSS-8080) Make EnsureStateTimestampIsMonotonic bump a colliding proposed timestamp past the run's most recent state instead of only deduping against the immediately preceding state. This fixes the 3+-states-in-one-tick case (t -> t -> t) flagged in review, where the third state was previously treated as backdated and still collided with the first persisted state. A fast path returns early when the proposed timestamp is already strictly newer than the current state, so normal forward transitions incur no extra query. Non-colliding backdated timestamps are still preserved.

devin/1784105766-flow-run-state-monotonic-timestamp

2 hours ago

docs: Add release notes for `prefect-databricks==0.4.2` (#22514) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: desertaxle <alex.s@prefect.io> Co-authored-by: alex.s <ajstreed1@gmail.com>

main

3 hours ago

fix(suspension): poll continuously as a safety net for external suspension The FlowRunSuspendingObserver relied on the events websocket for detection and only started its polling loop as a fallback when the consumer task ended (websocket closed or errored). If a prefect.flow-run.Suspended event was dropped while the connection stayed open, the fallback never engaged and external suspension went unnoticed, so the flow ran until it was killed. This is the root cause of the flaky integration-tests/test_flow_suspension.py timeouts. Always run the polling loop as a safety net alongside the event consumer so suspension is detected within polling_interval regardless of event delivery, while keeping the websocket for low-latency detection. Co-Authored-By: bot_apk <apk@cognition.ai>

devin/1784126856-suspension-observer-polling-safety-net

3 hours ago

Preserve empty `pull: []` in `prefect deploy` instead of forcing `set_working_directory` (#22490) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Alexander Streed <alex.s@prefect.io>

main

3 hours ago

chore(deps): bump actions/setup-node from 6 to 7 (#22509) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

main

3 hours ago

Prevent duplicate server-minted state timestamps (OSS-8080) On coarse-resolution clocks (notably Windows, ~15.6ms) the server can mint identical timestamps for consecutive states of a run, violating the unique (run_id, timestamp) constraint and surfacing as a 409 IntegrityError. Add an EnsureStateTimestampIsMonotonic global universal transform, applied first in COMMON_GLOBAL_TRANSFORMS so it runs before the transforms that read proposed_state.timestamp. When a proposed state's timestamp collides with the run's current state, nudge it forward one microsecond; explicitly backdated states are left untouched. Covers flow and task runs uniformly. Closes #22511

devin/1784105766-flow-run-state-monotonic-timestamp

8 hours ago

Latest Branches

0%

Prevent duplicate server-minted state timestamps#22512

3 hours ago

0b7c70b

devin/1784105766-flow-run-state-monotonic-timestamp

0%

fix(suspension): poll continuously as a safety net so a dropped Suspended event can't hang a flow#22513

3 hours ago

51d89f7

devin/1784126856-suspension-observer-polling-safety-net

0%

Add Redis Sentinel support to prefect-redis#22377

6 days ago

2e26e73

fatih-acar:feat/redis-sentinel-on-22211

© 2026 CodSpeed Technology

Home Terms Privacy Docs