Avatar for the PrefectHQ user
PrefectHQ
prefect
BlogDocsChangelog

Performance History

Latest Results

Distinguish a cancelled start future from a started one Review feedback on #23016. `task_status._future.done()` does not mean the worker reported the run as started. The cancellation that reaches this handler also cancels the future `TaskGroup.start` is awaiting, so it is done on both paths, and the guard therefore fired for a run whose infrastructure was still being provisioned. Measured inside the cancelled frame: started, then cancelled done=True cancelled=False cancelled while provisioning done=True cancelled=True `started()` resolves the future with a result; a cancelled future never carried one. Test both ways round: with the extra clause removed, the new test crashes a run that had not started. The `except Exception` branch below is unaffected — an exception there does not cancel the future, so its `not done()` still means what it says.
alekseevpavel04:fix/crash-runs-on-worker-shutdown
4 hours ago
Make event JSON test independent of UI URL
mikemikimike:fix-event-url-template-22957-work
11 hours ago
test(server): focus recorder upsert coverage on behavior
chuqCTC:fix/task-run-recorder-insert-compilation
18 hours ago
perf(server): reduce task run recorder insert compilation
chuqCTC:fix/task-run-recorder-insert-compilation
18 hours ago
Apply suggestion from @znicholasbrown
cancel-paused-runs-oss
20 hours ago

Latest Branches

CodSpeed Performance Gauge
0%
Crash flow runs interrupted by worker shutdown#23016
4 hours ago
8dddf89
alekseevpavel04:fix/crash-runs-on-worker-shutdown
CodSpeed Performance Gauge
0%
11 hours ago
048721b
mikemikimike:fix-event-url-template-22957-work
CodSpeed Performance Gauge
0%
18 hours ago
391393e
chuqCTC:fix/task-run-recorder-insert-compilation
© 2026 CodSpeed Technology
Home Terms Privacy Docs