Simon Frei

The problem is all these operations are blocking, there's no way to pass a context/deadline to them. So even if the hang was detected, the goroutines would stick around. Anyway...

That's actually it: Due to all the wrapping in quic conns, the deadline we set on the tls conn before closing is not applied to the underlying udp conn. And...

Looking at the quic server code it would be doable to add a write timeout via `net.PacketConn.SetWriteDeadline` in the `sendQueue`, possibly configurable through the `*Config` parameter. @marten-seemann Does that approach...

> Not sure I understand how that's supposed to work. It's still the same underlying net.PacketConn, so the deadline would apply to all connections. The deadline would indeed apply to...

I hid the off-topic/non-constructive comment and response to it above. And generally if you are old enough, please remember your experience on not feeding trolls. If you're too young for...

Folders aren't per device. You can't have the same folder for Device A at a distinct path from the same folder for Device B. Now it might be in your...

> concern that the currently-unmaintained gogo protobuf will break when Go 1.19 is released, similarly to how quic-go broke with 1.18; What's that concern based on? quic-go is not a...

I think understanding URLs is enough steps above kindergarden that it warrants a ui enhancement requst for a small, non-emoji status indication about what kind of connection is active besides...

There's already a token passed around that needs to match - this might very well cause a failure already (with a then misleading message about mismatching passwords). Also 2G? o.O...

Related (possibly duplicate): https://github.com/syncthing/syncthing/issues/6927