You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my view, if there occurs a problem in the network or server, clear the timeout deadline may cause this goroutine stuck for a long time even forever.
I wonder why it was written like this, was there some reason I've missed it?
If necessary, I'd like to post an mr.
The text was updated successfully, but these errors were encountered:
Good question. I can only think it's to try to leave the connection open between operations, but the people maintaining this fork didn't write that code. If it can be safely removed, a PR is welcome but we should make sure that nothing breaks.
I found this line in conn.go
In my view, if there occurs a problem in the network or server, clear the timeout deadline may cause this goroutine stuck for a long time even forever.
I wonder why it was written like this, was there some reason I've missed it?
If necessary, I'd like to post an mr.
The text was updated successfully, but these errors were encountered: