Stray number-commas in JSON (probably due to locale) break report function
so basically when I create a report which includes non-whole numbers, it included commas as seperators, so instead of
"size":1099492737024.000000
it had
"size":1099492737024,000000
(which was the only issue I saw immediately as a quick replace fixed the document)
which causes the JSON to break and the report page to be blank.
this is probably caused by me using German Locale where the decimal splitter is a comma. maybe try to get those numbers independent from locale.
All Comments (2)
Hello
Thanks for the detailed bug report - just to double-check, you are talking about the report generated from the "System Info Query" menu item?
You are quite right that the generated JSON should be locale-independent, and I've entered a backlog item to correct this. I'll post back here once I have an update on that.
In case you are interested, that feature is driven by siquery, which is open source.
Thanks and kind regards,
Richard Markievicz
sorry for the late reply, couldnt log in on my phone (apparently if you have U2F login as default but the browser cannot really deal with it for some reason I dont even get the change link so I can use password, lol)
yes exactly I mean the system info Query in the Actions menu.
also since I kindly got an enterprise license at my workplace (you can check my recently used IPs against the recent account creations if you are curious), so if I find stuff I'll be here.