Standardize async offloading behind shared executor helper
This commit is contained in:
@@ -79,6 +79,7 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
|
||||
- Issue: Multiple services (`raw_config_io_service`, `log_service`, `jail_config_service`, `setup_service`, and others) manually call `asyncio.get_event_loop()` or `run_in_executor`, creating inconsistent async control flow and making event-loop compatibility harder to maintain.
|
||||
- Propose: Introduce a shared async offload abstraction or utility that uses `asyncio.to_thread` / dedicated thread pool executors, and refactor blocking I/O and CPU-bound helpers to consume that shared provider.
|
||||
- Test: Verify existing async service tests still pass after refactoring and add coverage for the new offload utility to ensure blocking work is properly delegated without event-loop blocking.
|
||||
- Status: completed
|
||||
|
||||
11. Eliminate duplicate setup persistence across bootstrap and runtime databases
|
||||
- Goal: Simplify setup persistence by establishing a single source of truth for runtime configuration data and reduce failure surface in first-run setup.
|
||||
|
||||
Reference in New Issue
Block a user