puterboy
puterboy
I added some more logging to show exactly what is being enqueued and dequeued. The following log shows that the right data is entering the queue but (sometimes) it gets...
Now here is an example where it goes wrong with just one entry in the queue (the middle stanza is the corrupted one): ``` N: Enqueue JSON: {"model":"Nexus-TH","id":180,"channel":1,"battery_ok":1,"temperature_C":22.9,"humidity":70,"protocol":"Nexus, FreeTec NC-7345,...
Note that the log dequeue is before I have given back the `xQueueMutex` that I added to empthyQueue -- both adding and popping from the JsonQueue *should* be safe.
Actually, I think the problem is with the `push`, since the following only pushes a shallow copy of jsonDoc onto the stack. ``` JsonBundle bundle; bundle.doc = jsonDoc; jsonQueue.push(bundle); ```...
Tested and solves the problem (at least for me) As mentioned in the PR, this really is a critical bug that should be patched ASAP since it can theoretically corrupt...
Fixed as per above PR
Note now that you are emptying the queue with jsonDispatch that assumes an origin key, you could save some processes if you stored the origin and the rest of the...
That would of course be fine.
Please also look at my note above regarding creating a new version of `jsonDispatch` to avoid having to serialize and deserialize. In that vein, it may make sense to create...
Of course! Great platform! And kudos for all the work you have put into it...