PrefectHQ/prefect - CodSpeed

prefect

Blog Docs Changelog

Performance History

Latest Results

perf(events): avoid legacy resource label setting lookup

chuqCTC:fix/cache-resource-label-limit

2 hours ago

perf(events): avoid legacy resource label setting lookup

chuqCTC:fix/cache-resource-label-limit

2 hours ago

Fix lost expiration index updates in the filesystem lease storage Two lease renewals landing close together could interleave inside _update_expiration_index: both read the same version of the shared expirations.json, and whichever one saved last silently threw away the other's write. The reaper only ever looks at that index to decide what's expired, so a single lost update was enough to revoke a lease that was still very much alive. This adds an asyncio.Lock around the read, modify, and write of the index so two updates can no longer race each other. It also has read_expired_lease_ids check the actual lease file before reporting something as expired, since that file is what renew_lease really stamps and the index is only meant to be a shortcut to it. If the index is ever stale for some other reason down the line, this keeps that stale entry from being fatal instead of harmless. Added a test that forces the interleaving deterministically (delaying the first read just enough for the second update to finish first) and one that backdates an index entry while leaving the lease file alone, confirming the reaper no longer trusts it blindly. Both fail against the old code and pass with the fix. Closes #22935

afonsojanu:fix/lease-expiration-index-race-22935

4 hours ago

fix(events): use current resource label setting

chuqCTC:fix/cache-resource-label-limit

7 hours ago

docs: fix the stated default and command in the alembic wrapper docstrings The default revision for `alembic_downgrade` changed from 'base' to '-1' in #11670, which also updated the CLI help text and the test, but the docstring kept saying "Defaults to 'base', downgrading all revisions". That is the behaviour #11670 set out to remove, so the API reference has been promising a full downgrade to base where the function actually steps back a single revision. The entry now states '-1' and points at 'base' for anyone who does want every migration reversed, matching the wording already used by `prefect server database downgrade --help`. The `alembic_upgrade` entry two functions above it names `alembic downgrade` as the command its revision is passed to, which is the upgrade path, so that is corrected in the same pass.

muhzuhaib:docs-alembic-wrapper-defaults

15 hours ago

fix(server): fix database locked when marking deployments ready

uinstinct:sqlite-busy-snapshot

17 hours ago

Merge branch 'main' into fe-marked-failed

uinstinct:fe-marked-failed

19 hours ago

Use a fixed encryption key in tests Co-authored-by: PrefectHQ/prefect service account <noreply@prefect.io> Co-Authored-By: bot_apk <apk@cognition.ai>

devin/1787864673-storage-document-fixture

23 hours ago

Latest Branches

0%

Use current settings for resource label validation#22959

2 hours ago

48c25cb

chuqCTC:fix/cache-resource-label-limit

0%

Fix lost expiration index updates in the filesystem lease storage#22971

4 hours ago

2637179

afonsojanu:fix/lease-expiration-index-race-22935

0%

docs: fix the stated default and command in the alembic wrapper docstrings#22968

15 hours ago

5538581

muhzuhaib:docs-alembic-wrapper-defaults

© 2026 CodSpeed Technology

Home Terms Privacy Docs