PrefectHQ/prefect - CodSpeed

prefect

Blog Docs Changelog

Performance History

Latest Results

Pass botname and Prefect asset to Mattermost notifier (OSS-8290) MattermostWebhook stopped passing botname to NotifyMattermost when it switched to adding the plugin instance directly, so the configured bot name was ignored. The plugin also got a default AppriseAsset, so the fallback username was "Apprise" instead of "Prefect Notifications".

devin/1791160966-mattermost-botname

2 hours ago

test: assert the botname reaches the outgoing Mattermost payload The test read plugin.user, an apprise-internal attribute reached through the block's private _apprise_client. The contribution guide asks for tests that assert user-visible behavior rather than private implementation details. It now patches requests.post and asserts on payload["username"], which is the name Mattermost actually displays. Without the fix it fails with assert 'Apprise' == 'Prefect Bot' instead of assert None == 'Prefect Bot'.

Ayoubhm07:fix/mattermost-botname

2 hours ago

fix: pass the configured botname to NotifyMattermost MattermostWebhook declares a botname field and surfaces it in the UI block form, but block_initialization stopped passing it when it was rewritten to add the NotifyMattermost instance directly instead of going through .url(). Seven of the eight fields survived that rewrite; user=self.botname did not. With self.user unset, apprise falls back to the asset app_id when building the webhook payload (apprise/plugins/mattermost.py:646), so every message is signed with the asset name regardless of what the user configured. The field is accepted, persisted, and then discarded with no exception, warning, or log. The keyword is user= rather than botname=: NotifyMattermost does not take a botname argument, it declares botname as an alias of user and relays **kwargs to URLBase, which reads user. This restores what #19780 established before the rewrite. Adds test_botname_is_passed_to_apprise to the existing TestMattermostWebhook class.

Ayoubhm07:fix/mattermost-botname

3 hours ago

Resolve API route dependencies on the event loop FastAPI runs a plain `def` dependency in its thread pool on every request. The server's API routes depend on several such functions, mostly `provide_database_interface`, so nearly every request handed CPU-only work to a worker thread and back. Routes now depend on `aprovide_database_interface`, an async wrapper that keeps `provide_database_interface` available to its synchronous callers, and on `provide_worker_lookups` instead of the `WorkerLookups` class. The remaining dependencies become `async def`; none has a synchronous caller. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fatih-acar:fix/async-api-dependencies

20 hours ago

fix(client): drop unreachable Retry-After branches flagged by pyright

Lesereingrape:fix/retry-after-header-parsing

1 day ago

test: freeze clock in HTTP-date Retry-After test (OSS-8289)

devin/OSS-8289-retry-after-http-date

1 day ago

Sync ui-v2 OpenAPI types Regenerated by the `service-sync-ui-v2-openapi` pre-push hook; picks up server schema changes already on `main` that weren't synced yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

nolantonio:ui-v2/sort-task-runs-by-duration

1 day ago

Stop the async flow engine from blocking its event loop on the suspension observer The suspension observer of a deployment flow run runs on its own thread and event loop, but the async engine waited for it on the calling thread: it blocked until the observer was ready when the run started, and joined the observer thread (up to 2 s, with the observer polling for stop every 0.2 s) when the run ended. When several flow runs share one event loop, each start and end stalled all of them. The async engine now awaits the observer's readiness and shutdown through futures that the observer thread resolves on the engine's loop. The observer stays on its own thread so it keeps receiving suspension events while flow code blocks the flow's thread, and it now wakes as soon as it is asked to stop instead of within 0.2 s. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fatih-acar:fix/async-suspension-observer

1 day ago

Latest Branches

0%

fix: pass `botname` to Mattermost notifier#23283

2 hours ago

955ea37

devin/1791160966-mattermost-botname

0%

Pass the configured botname to NotifyMattermost#23281

3 hours ago

a4852c8

Ayoubhm07:fix/mattermost-botname

0%

Resolve API route dependencies on the event loop#23279

20 hours ago

7892415

fatih-acar:fix/async-api-dependencies

© 2026 CodSpeed Technology

Home Terms Privacy Docs