MayaTheShy 4be2d7be8f fix: replace sleep(0) with os.pullEvent() + add diagnostic logging ...

sleep(0) wakes the processor only on timer ticks, causing a
1-tick delay. os.pullEvent() with no filter wakes the processor
on ANY event — including the modem_message that triggered the
capture — so items are processed in the same event cycle.

Added logging to capture and processor tasks:
- NET-CAP: logs each queued message with type and queue depth
- NET-PROC: logs each message being processed
- Both log on startup to confirm they're running

2026-03-29 00:02:07 -04:00

41 KiB

Raw Blame History

View Raw