Lucas Pardue

Personally I've had no issues with the JSON-SEQ format. The [RFC 7464](https://datatracker.ietf.org/doc/html/rfc7464) is clear on various edge cases that might arise when parsing truncated logs. There is no equivalent IETF...

A middleground might be to subset JSON-SEQ and state something along the lines of "In addition to the formatting rules defined in JSON-SEQ, it is RECOMMENDED that loggers do not...

Maybe an interesting point is that xquic logs to slog/clog and then converts to json via python: https://github.com/alibaba/xquic/blob/main/scripts/qlog_parser.py And tangentially there's an issue on msquic for translation from their preferred...

Speaking personally with no hats, I don't think we should spend QUIC WG time relitigating all of the finer details of JSON encoding and parsing, for some newline delineated format....

As a very boring example - what media type would a handrolled ndjson use? Right now we have proposed to piggy back off of the existing `json-seq` suffix to use...

[client-1928a4431b958983545fe79a00fcf7a670f39d8e.zip](https://github.com/user-attachments/files/16465771/client-1928a4431b958983545fe79a00fcf7a670f39d8e.zip) unzips to client-1928a4431b958983545fe79a00fcf7a670f39d8e.sqlog, which is a JSON-SEQ file that includes some pretty printing e.g. ``` {"qlog_version":"0.3","qlog_format":"JSON-SEQ","title":"quiche-client qlog","description":"quiche-client qlog id=1928a4431b958983545fe79a00fcf7a670f39d8e","trace":{"vantage_point":{"type":"client"},"title":"quiche-client qlog","description":"quiche-client qlog id=1928a4431b958983545fe79a00fcf7a670f39d8e","configuration":{"time_offset":0.0}}} { "time": 0.0, "name": "transport:parameters_set", "data": {...

Media types were defined in response to https://github.com/quicwg/qlog/issues/158, where @kazuho said > At the moment, we use a custom ndjson format, but if we are to use qlog, there has...

wrt to vim, this is expected behaviour as described in https://vimdoc.sourceforge.net/htmldoc/options.html#%27ruler%27 because it chooses to render record separator as `^^` > If the number of characters displayed is different from...

> You'd need something like grep packet_sent | grep max_stream_data | wc. This breaks as soon as the event is not in one line. Adding `jq -c --seq . |`...

This needs to be raised on the QUIC mailing list before then, to reach that the broadest set of people