| #820 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze and extract meaningful infor...
|
open |
medium |
2026-02-09 00:04 |
- |
|
| #819 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 21:51 |
- |
|
| #818 |
Application crashes on startup
The application immediately crashes upon launch without displaying any error message or loading scre...
|
open |
medium |
2026-02-08 21:39 |
- |
|
| #817 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 21:07 |
- |
|
| #816 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 20:56 |
- |
|
| #815 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 20:51 |
- |
|
| #814 |
Bug Report Analysis Required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 20:44 |
- |
|
| #813 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 20:22 |
- |
|
| #812 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 19:53 |
- |
|
| #811 |
Bug Report Analysis Required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 19:44 |
- |
|
| #810 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-08 18:23 |
- |
|
| #809 |
Bug report analysis required
The provided bug report is empty or lacks sufficient details to analyze. Please include specific inf...
|
open |
medium |
2026-02-07 23:24 |
- |
|
| #808 |
Fix connection registration window
orchestrator.py:488-495 - Connection registered AFTER try block begins, creating window for zombie c...
|
in-progress |
high |
2026-01-02 20:50 |
- |
|
| #807 |
Fix rate limiter lease atomicity
orchestrator.py:431-469 - Rate limit consumed in separate transaction from task execution. Crash bet...
|
in-progress |
high |
2026-01-02 20:50 |
- |
|
| #806 |
Standardize JumperClient to use singleton pattern
23+ locations bypass singleton pattern with direct JumperClient() calls. Need to replace with get_ju...
|
closed |
high |
2026-01-02 20:50 |
- |
|
| #805 |
Review check_event race condition
check_event() in jumper_client.py:1353-1390 uses simple SELECT without locking. Another thread could...
|
closed |
critical |
2026-01-02 20:50 |
- |
|
| #804 |
Add workflow_run_id to async logging task spawn
inline_executor.py:664-671 spawns logging task WITHOUT workflow_run_id parameter. Creates orphaned w...
|
closed |
critical |
2026-01-02 20:50 |
- |
|
| #803 |
Fix schema mismatch for register_worker_heartbeat
Function exists in TWO schemas (highway and public) with different signatures. Migration 47 created ...
|
wont-do |
critical |
2026-01-02 20:50 |
- |
|
| #802 |
jumper_client.get_run_checkpoint fallback without tenant_id
Issue E: jumper_client.py get_run_checkpoint had fallback code path that allowed checkpoint queries ...
|
closed |
medium |
2026-01-02 20:23 |
- |
|
| #801 |
EventLogger missing workflow_run_id filter in sequence counter
Issue D: event_logger.py sequence counter query only filtered by jumper_run_id, not workflow_run_id....
|
closed |
medium |
2026-01-02 20:23 |
- |
|