Re: If you use HBlink OR dmr_utils, you need to read this
Cort N0MJS <n0mjs@...>
Well this is awesome – someone using HBink3 AND some great questions…. comments inline
I am working on some better ways to handle monitor stuff more efficiently, and it’s based on JSON, not pickles, and only sends update information once a reporting client gets the initial “full” feed… but that’s a ways off.
The bug was found when I was porting the initial commits of bridge.py, so it actually was “fixed” there before bridge.py in hblink3 ever worked. We’ve verified on the local system that the odd one-way traffic on a BM group that had plagued us for some time is resolved!
It’s very, very close. I have a version I need to actually try and chase bugs on. I expect very few at this point, but I need to get some more reporting of errors in the callbacks on asyncio so that the problems don’t just quietly happen without a traceback. Next time I have about 2 hours to work and use the KS-DMR network as my testbed, it should be good to go.
I would LOVE to hand off the monitor stuff to someone else. I mostly built the hbmonitor to demonstrate some of my ideas about how a monitor app might look. It’s simple, and could be much more – drill-downs, etc. ANYONE willing to pick up the torch on that will see me working extra hard to standardize what HBlink & friends uses as an output format, etc.
Since it looks like you have experience with asyncio….. any guesses why Uvloop performed like absolute crap, but asyncio kicked butt like it was supposed to?
Thanks for the comments and well worded questions, Spencer.
0x49 DE N0MJS