Matthias Frei

For what it's worth, this issue is not reproducible with the latest [rules_go v0.33.0 release](https://github.com/bazelbuild/rules_go/releases/tag/v0.33.0). Judging just from the release notes, this is likely due to the updated `org_golang_x_xerrors`, just...

Thanks for your reply and sorry for being imprecise. Sure, yes I've considered that packets might lost -- by "transmitted", I meant "transmitted and acknowledged".

Ok sure, if the ACKs are lost, then the proposed `CloseSync` will time out eventually. It's ok that this can still fail, but it would be useful to have the...

This must be a misunderstanding, the suggested API does not "break" in case of packet loss. Perhaps the function names that I suggested are misleading? The idea is that it...

Thanks for reconsidering this! In the meantime, I took a cursory look at how this is handled in a few other quic implementations; In quiche, there is an `is_draining` method...

> So `go list` might need to provide a flag to filter out pruned modules for this to work thinking :thinking:? After some digging, I now believe that the information...

> Overall, there is not a lot of benefit in doing these "pruning" for go_repository in a monorepo: go_repository rules are lazy by default and will only get executed/downloaded if...

The minimal change to support `netip.AddrPort` for `Read/WriteBatch` in both `x/net/ipv4` and `x/net/ipv6`: ```go type Message struct { Buffers [][]byte OOB []byte Addr net.Addr AddrPort netip.AddrPort // + Specifies destination...

The comment `// populated by callee` on `IPMsg.Addr` does not seem right for the write APIs. I see that the there is no `int flags` arguments on the Read/Write functions,...