Open petersilva opened 7 months ago
no... that's not it... there is some decoding problem somewhere, but not clear what. EDIT: It isn't just having a T... there is something more subtle going on because it is intermittent... occurs rarely with messages, where other vanishingly similar messages are correctly processed.
It seems to be that when C implementation ingests v2 message, and then sends it out as v3, and then a second one gets the v3 and sends it as v2... something like that... but only sometimes... most messages are correct.
OK... so turning debug on, then found this:
so if the pubTime has a "T" in it, the C code fails to decode it properly.