Ilya Shipitsin

thanks!

well, the question was "should we try to open an issue automatically if it fails or not" )) currently, yes, it is expected to be resolved, we can close this

similar report on "resumption" test FATAL: bug condition "first_pkt->type == QUIC_PACKET_TYPE_INITIAL && (first_pkt->flags & (1UL

[logs.zip](https://github.com/user-attachments/files/16444341/logs.zip)

surprisingly enough, but pulling fresh quic-go image "fixed" 0-RTT test. but "resumption" failures are very stable

meanwhile I'm trying to figure out how to collect core dump in dockerized env

should this issue be open for backporting ? or it might be closed?

here's longer report ``` 1032 p = l->bind_conf->frontend; 1. Condition l->rx.proto, taking false branch. 2. var_compare_op: Comparing l->rx.proto to null implies that l->rx.proto might be null. 1033 li_set_affinity2 = l->rx.proto...

can you collect logs from "Event Viewer" --> "Windows Logs" --> "Application" --> (Source: MsiInstaller)

btw, do you have wireguard installed ?