Closed marcwitasee closed 2 years ago
@marcwitasee Does the example JSON indicate a malformed structure or the expected structure?
@jesteria Just updated the description. It's an example of a malformed JSON.
Oh wow that is screwy. FTR: it's quite hard to tell what's wrong with such a large structure; luckily, computers: "line 148 column 1":
{
"Measurements":{
…
},
"Meta":{
…
}
}
},
"dns_latency":{
"dns_query_avg_ms":28.6,
"dns_query_max_ms":67,
"error":false
},
"hops_to_target":{
"hops_to_google":10,
"error":false
},
"connected_devices_arp":{
"devices_active":21,
"devices_total":74,
"devices_1day":25,
"devices_1week":33
},
"test_bytes_consumed":0
}
}
So it looks like a regular measurements file with a few subsections recopied at the bottom. That's a mess.
If the code that writes this is just taking a proper Python dict
and writing it in one swoop, e.g.:
with open(…) as fd:
json.dump(data, fd)
…Then I don't really see how the code could be responsible, and rather the sync system might be doing something very bad.
(Of course the writer could be doing all sorts of things as well.)
seems to be fixed
Some JSON files with results from
nm-exp-active-netrics
are malformed. I've confirmed that this is occurring on the Raspberry Pi, as the file is malformed before it is uploaded to S3.Here is an example of a malformed JSON: