| #137 |
API Key copy button not working and missing audit log
1. Copy button in secret display modal does not work when creating API key. 2. No audit log entry cr...
|
closed |
critical |
2025-11-27 19:18 |
- |
|
| #131 |
Circuit breaker + retry misalignment - tasks exhaust retries during CB cooldown
PROBLEM: When circuit breaker opens, tasks fail with ProtectedCallError. With no retry_strategy (def...
|
closed |
critical |
2025-11-27 07:04 |
- |
|
| #128 |
CRITICAL: Heartbeats not persisted - use separate connection
During disruption testing, heartbeat tests fail because heartbeats are NOT being committed to the da...
|
closed |
critical |
2025-11-27 06:28 |
- |
|
| #127 |
CRITICAL: workflow_run.status not updated when task permanently fails
During disruption testing, tasks exhaust max_attempts and go to 'failed' state, but workflow_run.sta...
|
closed |
critical |
2025-11-27 06:19 |
- |
|
| #125 |
CRITICAL: All workers use same worker_id - breaks claim isolation
All 8 workers use hardcoded worker_id='highway_worker_1' from config.ini, ignoring ABSURD_WORKER_ID ...
|
closed |
critical |
2025-11-27 06:04 |
- |
|
| #124 |
Fix: Event deduplication at storage level
LONG-TERM FIX for guaranteed event uniqueness.
Problem: Even with idempotency keys, race conditions...
|
closed |
critical |
2025-11-27 05:39 |
- |
|
| #123 |
Fix: Implement incremental checkpoint commits
MEDIUM-TERM FIX for progress preservation during crashes.
Problem: Checkpoints are committed atomic...
|
closed |
critical |
2025-11-27 05:39 |
- |
|
| #122 |
Fix: Add idempotency keys to event emission
SHORT-TERM FIX for event duplication during retries.
Problem: EventLogger emits new events with inc...
|
closed |
critical |
2025-11-27 05:39 |
- |
|
| #121 |
Fix: Reduce claim_timeout from 30s to 10s for faster crash recovery
IMMEDIATE FIX for disruption resilience.
Location: engine/orchestrator.py:727, engine/cli/worker.py...
|
closed |
critical |
2025-11-27 05:39 |
- |
|
| #120 |
Investigation: test_workflow_without_heartbeat_still_works timeout during disruption
Test failed with: TimeoutError: Workflow events did not stabilize within 40 seconds. Parent issue: #...
|
closed |
critical |
2025-11-27 05:30 |
- |
|
| #119 |
Investigation: test_heartbeat_with_many_iterations timeout during disruption
Test failed with: TimeoutError: Workflow did not complete within 45 seconds. Parent issue: #116. Inv...
|
closed |
critical |
2025-11-27 05:30 |
- |
|
| #118 |
Investigation: test_standard_sleep_wake_event timeout during disruption
Test failed with: TimeoutError: Workflow did not complete within 60 seconds. Parent issue: #116. Inv...
|
closed |
critical |
2025-11-27 05:30 |
- |
|
| #117 |
Investigation: test_activity_auto_conversion timeout during disruption
Test failed with: TimeoutError: Workflow events did not stabilize within 120 seconds. Parent issue: ...
|
closed |
critical |
2025-11-27 05:30 |
- |
|
| #116 |
disruption caused several tests to fail
the following tests has failed during stress and disruption testing.
```
26.26s call tests/...
|
closed |
critical |
2025-11-27 05:29 |
- |
|
| #115 |
broken TestValidatorBannedBuiltins test
this test is broken, fix it
pytest -n0 tests/integration/test_validator.py::TestValidatorBannedBu...
|
closed |
critical |
2025-11-27 04:14 |
- |
|
| #114 |
Stress Test
I am going to run pytest in another terminal. You need to write a bash, in scripts/disrupt.sh, where...
|
closed |
critical |
2025-11-27 04:12 |
- |
|
| #108 |
Optimize DataShard logs: partition by tenant/workflow with path tracking
Restructure DataShard logs to data/<tenant>/<workflow>/... for efficient querying. Record paths in D...
|
closed |
critical |
2025-11-27 00:21 |
- |
|
| #103 |
activity pattern issue
The _execute_as_activity method at line 105 is dead code - it's called but never defined! The activi...
|
closed |
critical |
2025-11-26 22:12 |
- |
|
| #87 |
CRITICAL: DataShard log cleanup delayed until terminal state
datashard_logger.py:334-364 - Cleanup of workflow_state (replacing stdout/stderr with log_id) only p...
|
closed |
critical |
2025-11-26 20:51 |
- |
|
| #86 |
CRITICAL: DeadLetterService transactional atomicity requirement
dead_letter_service.py:14,60 - DLQ operations MUST use provided connection for atomicity with failur...
|
closed |
critical |
2025-11-26 20:51 |
- |
|