PrefectHQ/prefect - CodSpeed

prefect

Blog Docs Changelog

Performance History

Latest Results

Spell it `unparsable` to satisfy codespell The pre-commit `codespell` hook flags the standalone word on the assertion message. The other two uses sit inside a hyphenated word and an identifier, which codespell tokenizes whole and does not flag -- changing all three keeps the file internally consistent.

sujeito-operator:events-in-drop-invalid-event

9 hours ago

Log only the location and type of the validation failure The warning added in the previous commit formatted the ValidationError with %s. Pydantic's string form embeds `input_value`, so a rejected event would have its payload and resource labels written to the server log -- and ObfuscateApiKeyFilter removes only the configured Prefect API key, so anything else the client sent would stay there in the clear. Log the `loc` and `type` of each error instead, which is what is useful for diagnosing a misbehaving client anyway. The test now sends a sentinel value inside the rejected event and asserts it does not reach the log; it fails without this change.

sujeito-operator:events-in-drop-invalid-event

14 hours ago

Keep the incoming event stream open when one event fails validation `stream_events_in` validated each message with `Event.model_validate_json` inside the receive loop with nothing catching `ValidationError`. One event the server could not accept therefore escaped the loop and closed the websocket. Clients treat a closed socket as a transient network problem, so the refused event was discarded and every event the client had in flight was lost with it. Neither side reported anything: the server logged nothing, and the client's checkpoint ping is answered at the protocol level before the server rejects the message, so the client positively recorded the event as delivered. Validation failures are now caught per message. The offending event is dropped with a warning naming the reason, and the connection carries on serving every event after it.

sujeito-operator:events-in-drop-invalid-event

17 hours ago

fix(server): serialize db_vacuum tasks with a shared docket concurrency limit The db_vacuum cleanup tasks run against a maintenance pool with pool_size=1 and max_overflow=0. When docket runs them concurrently, sibling tasks time out after 30s waiting for the single connection. Give all vacuum tasks a shared ConcurrencyLimit keyed on a common maintenance_pool argument so they run one at a time. Addresses OSS-8167. Co-authored-by: Alex Streed <desertaxle@users.noreply.github.com>

devin1/oss-8167-db_vacuum-docket-jobs-run-concurrently-against-a-size-1

24 hours ago

test: restore development image expectations

ChidiebereNjoku:chore/remove-dev-cli

3 days ago

fix: MS Teams/Power Automate no longer works with new URL

Roshan931:prilog/fix-error-apprise-floor-too-low-to-parse-new-power-08-21-2026-8c56cd

3 days ago

docs: warn e2e AGENTS.md about shared-prefix cleanup races within a file (#22893) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

main

3 days ago

Do not overwrite in-flight schema form edits with stale parent values (#22905) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Alex Streed <alex.s@prefect.ioi>

main

3 days ago

Latest Branches

0%

Keep the incoming event stream open when one event fails validation#22914

10 hours ago

1b7ed8d

sujeito-operator:events-in-drop-invalid-event

0%

Serialize db_vacuum tasks with a shared docket concurrency limit#22913

24 hours ago

20012e5

devin1/oss-8167-db_vacuum-docket-jobs-run-concurrently-against-a-size-1

0%

chore: remove deprecated dev CLI subgroup and docker logic (#20607)#22507

3 days ago

cc169fd

ChidiebereNjoku:chore/remove-dev-cli

© 2026 CodSpeed Technology

Home Terms Privacy Docs