You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* test(providers): fix mock_db._create signature to match db_create_terminal
The integration-test mock_db fixture's _create() side-effect lagged behind
db_create_terminal(), which now takes allowed_tools (positional) and caller_id
(keyword). create_terminal() therefore raised "TypeError: _create() got an
unexpected keyword argument 'caller_id'" at fixture setup, erroring all 7
kiro/q CLI integration tests.
Add allowed_tools and caller_id (both default None) to the mock signature and
record them in the stored metadata. test_real_kiro_initialization_and_idle now
passes; the remaining kiro status-detection timing assertions are unrelated.
* test(kiro): await asyncio.sleep in async integration tests so StatusMonitor runs
The async kiro integration tests polled status with blocking time.sleep(),
which starves the asyncio StatusMonitor task on the same event loop: the FIFO
buffer never drains, status stays latched at IDLE, and the PROCESSING/COMPLETED
assertions fail (while the permission-prompt waits never see output and skip).
Make _wait_for_status / _wait_for_permission async and replace the in-test
blocking sleeps with await asyncio.sleep() so the monitor coroutine runs.
Verified against real kiro-cli 2.10.0: the file now reports 3 passed, 4 skipped
(was 2 failed plus skips masking the same starvation). Root cause confirmed via
a probe — blocking sleep reproduces IDLE-forever with an empty buffer; awaiting
yields IDLE -> PROCESSING -> COMPLETED.
0 commit comments