golang/go

net: add some more practical tests for TCP keep-alive mechanism

Open

#65,834 opened on Feb 21, 2024

View on GitHub
 (1 comment) (1 reaction) (1 assignee)Go (19,008 forks)batch import
NeedsInvestigationTestinghelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This is a tracking issue of testing the TCP keep-alive mechanism in Go.

The current test suites are based on this previous discussion. They were good enough back then, but they might miss something like #65809, which directs us here, to investigate the possibility of introducing some additional tests that will reflect the real world.

CC @bcmills @ianlancetaylor @neild

Contributor guide

Research direction
Review the existing TCP keep alive tests in the Go net package and the linked discussions (go review 542275 and 565315) to understand the current test coverage and the missing real world scenarios. Investigate issue #65809 for specific failures. Then design and implement additional tests that simulate practical TCP keep alive behavior.
Tech stack
go
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoTCP networking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70