libp2p / libp2p/unified-testing
Follow up perf interop: dotnet TLS and dialer stability
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
## Context
The perf migration branch improved build/toolchain alignment and startup robustness for Go/JS/dotnet images, but a subset of interop cases still fail.
## Remaining failure focus
- `js-v3.x -> dotnet-v1.0 (tcp, tls, yamux)` fails TLS negotiation (`could not negotiate /tls/1.0.0`).
- Some `dotnet-v1.0` dialer paths can stall after earlier failures.
## Why this issue
Track follow-up interoperability work separately from the migration stabilization changes already landed in `all-stars-perf-migration`.
## Next steps
- Validate dotnet security protocol registration/selection against libp2p JS TLS expectations.
- Re-run focused matrix on dotnet listener/dialer permutations.
- Confirm full matrix behavior after targeted fixes.
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 the focused JS-to-dotnet TLS matrix, then inspect dotnet security protocol registration and selection alongside the listener and dialer permutations. The work is done when TLS negotiation succeeds, stalled dialer paths are resolved, and the full interoperability matrix passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, javascript
- Domain
- networking, security, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100