Connect to itself in the dry-run mode
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
When the replayer runs in the dry-run mode, it doesn't create connections, we can't check the create connection performance, like dialing failure.
I suggest the replayer listens on a port and the replayer connect to itself without sending commands.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the replayer's dry-run mode and its connection setup. Determine how it can listen on a port and connect to itself without sending commands, then verify that connection-creation behavior such as dialing failure can be exercised in dry-run mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100