Marten Seemann

So what is the solution? How do I make execSync build again?

Hi @peter-evans, thank you for this super quick reply and the implementation! I just tried it out, and it looks like we're still running into GitHub's abuse detection mechanism, for...

@peter-evans We only do runs that deploy to all ~100 repositories infrequently - it creates a lot of noise. The next run will probably be adding Go 1.17 (which will...

Hi @peter-evans, thank you for your patience! We did another deployment today, and we ran into rate limits on a large number of jobs, for example here: https://github.com/protocol/.github/runs/3351001762?check_suite_focus=true. I'm not...

Hi @peter-evans, first of all, thanks again for all your work! It will probably be a while before we run another deployment. Deploying to 150 repos creates a lot of...

Looks like sending of Retry packets (https://github.com/lucas-clemente/quic-go/blob/332473668a992ce372c54c353b2bdc24344cf46e/server.go#L424-L436) is leading to a big backlog. Any idea why `net.(*UDPConn).WriteMsgUDP` would do that? > @imsodin: Here you go: [goroutine_debug_2.zip](https://github.com/syncthing/syncthing/files/8453923/goroutine_debug_2.zip) How do I open...

Got it, looks like they're actually stuck at `WriteMsgUDP`. Now one change we _could_ do in quic-go is to not spawn a separate Go routine for every retry, but only...

> They all try to write to the same *netFD protected by a lock which is held by one routine in iowait/netpoll since 1289min This sounds like a potential Go...

> 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...

Probably not. https://github.com/lucas-clemente/quic-go/issues/3409 would cause a connection to be dropped, but shouldn't result in a memory leak (unless your code doesn't properly deal with closed connections).