miroir/crates
jedarden 6a8f9ffa0a P2.5 Task reconciliation: Fix multi-threaded runtime test
The test_task_registry_impl_captures_all_node_tasks test was failing
because TaskRegistryImpl::register_with_metadata() uses
tokio::task::block_in_place() internally, which requires a
multi-threaded tokio runtime.

Fixed by adding `#[tokio::test(flavor = "multi_thread")]` to the
test so it runs with a proper multi-threaded runtime.

All 13 P2.5 tests now pass:
- test_fan_out_to_3_nodes_captures_all_task_uids
- test_task_registry_impl_captures_all_node_tasks (fixed)
- test_get_task_while_nodes_processing_returns_processing
- test_get_task_while_one_node_still_enqueued_returns_processing
- test_one_node_failure_results_in_failed_status
- test_multiple_node_failures_aggregates_all_errors
- test_in_memory_registry_survives_request_lifetime
- test_registry_survives_multiple_concurrent_requests
- test_list_tasks_filters_by_status
- test_list_tasks_with_limit_and_offset
- test_count_returns_total_tasks
- test_task_timestamps_are_set_correctly
- test_exponential_backoff_polling_completes

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-23 22:53:02 -04:00
..
miroir-core P2.4 Index lifecycle endpoints: implementation verification 2026-05-23 22:28:33 -04:00
miroir-ctl P3: Phase 3 Task Registry + Persistence — COMPLETE 2026-05-02 16:50:42 -04:00
miroir-proxy P2.5 Task reconciliation: Fix multi-threaded runtime test 2026-05-23 22:53:02 -04:00