Repository navigation
subcribe_all example seems to be broken #55
Description
https://harp-tech.org/python/examples/events/#subscribe-to-events
This example was meant to capture a read dump from the board. However the subscribe_all uses the default filter for events only. At a minimum we should consider fixing the documentation.
However, we should also consider whether subscribe_all should simply subscribe to ALL message types in addition to all registers. It feels like the most common case.
Activity
Poofjunior commentedon Sep 8, 2026
FWIW, I think the default behavior of subscribing to all events only is OK.
It's going to be less common to want to subscribe to read/write replies. And DUMP is a good example of this less-common behavior since register contents are dumped per-register as READ replies instead of EVENTs.
I would suggest changing the example to
print_any_replyinstead and then having a separate example showing how you can subscribe to read-and-write replies in addition to events.