swarm: TestDialSimultaneousJoin
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
https://github.com/libp2p/go-libp2p/runs/7060208469?check_suite_focus=true
```
=== RUN TestDialSimultaneousJoin
dial_test.go:584: third dial succedded; conn: /ip4/127.0.0.1/udp/65434/quic (12D3KooWGEcD5sW5osB6LajkHGqiGc3W8eKfYwnJVVqfujkpLWX2)>
dial_test.go:594:
Error Trace: dial_test.go:594
Error: Received unexpected error:
failed to dial 12D3KooWGEcD5sW5osB6LajkHGqiGc3W8eKfYwnJVVqfujkpLWX2:
* [/ip4/127.0.0.1/tcp/49901] failed to negotiate security protocol: context deadline exceeded
Test: TestDialSimultaneousJoin
dial_test.go:566: second dial succedded; conn: /ip4/127.0.0.1/udp/65434/quic (12D3KooWGEcD5sW5osB6LajkHGqiGc3W8eKfYwnJVVqfujkpLWX2)>
--- FAIL: TestDialSimultaneousJoin (0.26s)
Contributor guide
No contributing guide indexed for this repository
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 reproducing TestDialSimultaneousJoin from the linked run, then inspect dial_test.go around lines 566–594. Determine why the third simultaneous dial succeeds while another dial fails during security negotiation. Done means the test passes reliably without the unexpected context deadline error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100