-
I just started working on implementing qlog in quic-go. Maybe it's because I'm still fairly unfamiliar with qlog, but I feel like encoding things in JSON leads to some awkward hacks. Examples of these…
-
The [attached qlog files](https://github.com/quiclog/qvis/files/5093370/7a1de67a86b189180d.zip) seem to display correctly, but not all of the events for sending are matched to receive events.
For i…
-
**Description:**
Hello, as I've mentioned in the Discord server. When another player accepts a shared quest, it shows up as declined.
I created 2 new paladins for this test and made sure tha…
-
Transfer, blackhole and goodput tests fail consistently with certain clients (ngtcp2, quant, quiche, kwik, neqo) because the server-client combination is not able to transfer 10MB in the given time li…
-
see [qvis](https://qvis.edm.uhasselt.be/?#/sequence?file=https%3A%2F%2Finterop.seemann.io%2Flogs_2020-07-15T06%3A20%3A53UTC%2Fquic-go_neqo%2Fgoodput%2F1%2Fclient%2Fqlog%2Fserver-0a3b987a05eec43a.qlog&…
-
Currently, we rely on packet_* with a CONNECTION_CLOSE frame, but that's not always enough. E.g., the server can decide to drop a connection after a long timeout without sending a CONNECTION_CLOSE. Or…
rmarx updated
3 years ago
-
The story of logging in picoquic is a bit long. It started with a semi formal test log, then added an ad hoc binary log to capture congestion control and recovery issues. Both were upgraded over time.…
-
When running with aioquic.
```
client | Test case: handshake
client | panic: runtime error: invalid memory address or nil pointer dereference
client | [signal SIGSEGV:…
-
I have found a strange problem that when there exists some delays in network resulting in some unacked tail packets because ack-eliciting packets are not acknowledged within the expected period of PTO…
-
**Describe the bug**
It appears as though some implementations use a different epoch than 1970-01-01. This manifests in a very large skew in reported times in logs. There is code to make an adjustm…