Sitsofe Wheeler

@jo-ale35 are you able to deduce which part of the JSON is malformed?

> Is this a fair restatement of the situation? Sounds like it. It's a bit tough on people who are wrapping the existing format but I would think they would...

FWIW looking at https://en.wikipedia.org/wiki/JSON_streaming the solutions there don't really solve the original problem which seems to be a desire to have strictly well formed json that can be read with...

The job that would generate this behaviour is something like this: ``` $ fio --size=8k --filename=/tmp/fio.tmp --name=emptylogs --disable_clat=1 --write_lat_log=el $ du el_* 0 el_clat.1.log 8 el_lat.1.log 0 el_slat.1.log ``` It's...

Nice start! Any chance you can fix up the warnings too and eyeball the resulting GUI?

@hulbs9nw Looking at https://docs.oracle.com/cd/E36784_01/html/E36874/ctime-r-3c.html and it says the `ctime_r` protype is the following: ``` char *ctime_r(const time_t *clock, char *buf, int buflen); ``` but your message is saying it is...

The fix will be something like changing ``` #define os_ctime_r(x, y, z) ctime_r((x), (y), (z)) ``` to ``` #define os_ctime_r(x, y, z) ctime_r((x), (y)) ``` but there is a question...

@hulbs9nw can you re-checkout your repo to (making it pristine), edit `os/os-solaris.h` and change ``` #define os_ctime_r(x, y, z) ctime_r((x), (y), (z)) ``` to ``` #define os_ctime_r(x, y, z) ctime_r((x),...

@axboe good point.

@alanc - thank you for explaining this!