Greptile Summary

Fixes a critical thread starvation issue by switching EventHandler coroutines from Dispatchers.Default (limited to max(2, numCPU) threads) to Dispatchers.IO (scales up to 64 threads). The change affects three scope.launch calls that perform database I/O and Python wrapper operations.

The changes are:

• startEventHandling(): draining pending announces at startup
• drainPendingMessages(): draining pending messages at startup
• handleMessageReceivedEvent(): processing incoming message events

All three operations involve database persistence (persistenceManager) and Python wrapper calls (wrapperManager), making Dispatchers.IO the appropriate dispatcher choice. This prevents message processing from being blocked during heavy operations like large file propagation.

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The change correctly addresses a real concurrency issue by switching from Dispatchers.Default to Dispatchers.IO for I/O-bound operations. The affected operations perform database persistence and Python wrapper calls, which are blocking I/O operations that should use the IO dispatcher. The change follows Kotlin coroutine best practices and is consistent with similar code in the codebase (e.g., MessageCollector, ConversationLinkManager, and multiple withContext(Dispatchers.IO) calls in ReticulumServiceBinder).
• No files require special attention

Important Files Changed

_{Last reviewed commit: 3809cd4}

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!