#130 Add disruption resilience test to prevent SQL-bypass regression

closed high Created 2025-11-27 06:53 · Updated 2025-11-27 08:15

Description

Edit
Create a test that specifically validates the SQL-path bypass scenario doesn't regress. The test should: 1. Submit a workflow that takes longer than claim_timeout 2. Simulate claim expiration (not actual worker kill) 3. Verify workflow_run.status syncs to 'failed' when task fails via SQL This catches regressions where: - Trigger is accidentally dropped - New queue is added without trigger - Code changes bypass the trigger Test location: tests/integration/test_disruption_resilience.py Also add CI check for trigger coverage on all queues.

Comments

Loading comments...

Context

Loading context...

Audit History

View All
Loading audit history...