Looks like dramatiq 2.0 changed the way stub_broker operates, which causes the tests to fail.
If we invoke the stub broker with fail_fast_default=False as noted in the changelog this gives us back the initial functionality. Though larger changes might be warranted.
This patch gets the tests passing by changing that value, perhaps that's all that's needed to allow 2.0 compat?
From a5d86b326f2c06fe9efeb378ac95e101bafec74a Mon Sep 17 00:00:00 2001
From: Chris Moultrie <821688+tebriel@users.noreply.github.com>
Date: Mon, 2 Mar 2026 10:56:27 -0500
Subject: [PATCH] test: add fail_fast_default=False for old behavior in
stub_broker
---
tests/conftest.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/conftest.py b/tests/conftest.py
index c64ac56..f353917 100644
--- a/tests/conftest.py
+++ b/tests/conftest.py
@@ -32,7 +32,7 @@ def check_redis(client: Any) -> None:
@pytest.fixture()
def stub_broker() -> Generator[dramatiq.Broker, None, None]:
- broker = StubBroker()
+ broker = StubBroker(fail_fast_default=False)
broker.emit_after("process_boot")
dramatiq.set_broker(broker)
yield broker
--
2.51.2I'll make a PR with this and a dramatiq-2 update for review.
Looks like dramatiq 2.0 changed the way stub_broker operates, which causes the tests to fail.
If we invoke the stub broker with
fail_fast_default=Falseas noted in the changelog this gives us back the initial functionality. Though larger changes might be warranted.This patch gets the tests passing by changing that value, perhaps that's all that's needed to allow 2.0 compat?
I'll make a PR with this and a dramatiq-2 update for review.