QUIC panic: crypto/tls bug in quic-go v0.55.0

[ArchieIndian]

The seller serve (and network tests) crash with a panic in quic-go:

panic: crypto/tls bug: where's my session ticket?

goroutine 171 [running]:
github.com/quic-go/quic-go/internal/handshake.(*cryptoSetup).GetSessionTicket

This is a known issue in quic-go v0.55.0. It happens when a QUIC connection completes its handshake.

Impact: Seller node crashes after receiving a P2P connection, making end-to-end inference impossible.

Fix options:

1. Check if a newer quic-go version patches this
2. Downgrade to a stable quic-go version (v0.48 or similar)
3. Check Go version compatibility — this may require Go 1.24+ crypto/tls fixes

Reproduction:

go run ./cmd/seller serve --control-url http://localhost:8090 --email seller@test.com --password secret123
# Then from another terminal, connect as buyer with --bootstrap pointing to seller

Blocks all P2P inference testing.

[ArchieIndian]

Reproduced again on 2026-04-05. Same panic:

panic: crypto/tls bug: where's my session ticket?
goroutine 29 [running]:
github.com/quic-go/quic-go/internal/handshake.(*cryptoSetup).GetSessionTicket
    quic-go@v0.55.0/internal/handshake/crypto_setup.go:385

Steps:

1. Control plane running on :8090
2. Seller started: go run ./cmd/seller serve --control-url http://localhost:8090 --email seller@test.com --password secret123
3. Seller boots fine, prints peer ID, stays running
4. Buyer mesh started with --bootstrap pointing to seller
5. Buyer sends POST /v1/chat/completions
6. Seller panics on the incoming QUIC connection

Seller shows onDuty=true, models=1 before crash. The panic happens on the very first incoming P2P request.

This blocks all end-to-end testing. The matchmaker, control plane, billing, and API all work — only the QUIC transport layer crashes.