--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/CJwsb1H9mGg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/94e4b5cd-6005-4a52-916f-9e1a88137399n%40googlegroups.com.
On Nov 10, 2020, at 4:46 AM, Denis Telyukh <telyuk...@gmail.com> wrote:
More complex problem description with images: https://caddy.community/t/sometimes-http-2-request-hangs-up-need-help-with-debugging/10439/2
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a9ac428d-1389-4278-be9a-273ae95751b0n%40googlegroups.com.
On Nov 10, 2020, at 9:36 AM, Denis Telyukh <telyuk...@gmail.com> wrote:
1. Got some stuck requests2. netstat -atptcp 25 0 dionysius-pc:52340 server-52-85-47-1:https CLOSE_WAIT 1364/brave --type=utcp 25 0 dionysius-pc:40296 server-13-33-240-:https CLOSE_WAIT 1364/brave --type=u
3. A few second later netstat doesn't show any non-empty queues
4. But requests continue to hang (it will be endless)
On Nov 12, 2020, at 3:22 AM, Denis Telyukh <telyuk...@gmail.com> wrote:
Better problem description after deeper debugging: https://github.com/golang/go/issues/42534
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/abf3d089-bbd2-4607-b6c3-68a2237213bfn%40googlegroups.com.
On Nov 12, 2020, at 8:13 AM, Robert Engels <ren...@ix.netcom.com> wrote:
On Nov 12, 2020, at 8:42 AM, Denis Telyukh <telyuk...@gmail.com> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/ee1dd302-1231-4460-9d0d-0557a3e1d8b6n%40googlegroups.com.
One thing to note, gRPC uses http2. If there were a bug like this lurking in the library it would be far more common, so the most likely cause is specific to your code.
On Thursday, 12 November 2020 14:34:35 UTC, Robert Engels wrote:One thing to note, gRPC uses http2. If there were a bug like this lurking in the library it would be far more common, so the most likely cause is specific to your code.To the OP: have you tried running your code under the race detector?
--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/CJwsb1H9mGg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/8e2463b4-da04-4f1b-b09f-948d45954088o%40googlegroups.com.