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
After CL 542275 was merged into the master branch, I played around with this new feature along with investigating some known issues like #64251. As a result of which, I discovered a few issues and potential improvements on different platforms.
For the starter, DragonFlyBSD switched the time unit for TCP keep-alive from milliseconds to seconds since v5.8 while Go still uses milliseconds up to now (CL 542275 wasn't aware of it):
I think that we need to keep Go in sync with that considering that Go makes no guarantee to support any older versions of DragonFlyBSD other than the latest one:
Generally only the latest release version only. We have a builder, but it’s not the most stable of our ports.
After CL 542275 was merged into the master branch, I played around with this new feature along with investigating some known issues like #64251. As a result of which, I discovered a few issues and potential improvements on different platforms.
For the starter, DragonFlyBSD switched the time unit for TCP keep-alive from milliseconds to seconds since v5.8 while Go still uses milliseconds up to now (CL 542275 wasn't aware of it):
go/src/net/tcpsockopt_dragonfly.go
Lines 13 to 20 in aaf8e84
I think that we need to keep Go in sync with that considering that Go makes no guarantee to support any older versions of DragonFlyBSD other than the latest one:
References:
The text was updated successfully, but these errors were encountered: