libp2p / libp2p/unified-testing
Add zig-libp2p to ~failing?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
@MarcoPolo your minimal libp2p impl in zig is showing up with a bunch of failures: https://libp2p.io/status/transport/quic-v1/
There's three options and I wanted to get your take on them:
- remove it from the test matrix altogether and add it to "dormant implementations" list
- add it to the ~failing alias so it gets skipped in test runs that feed the dashboard
- fix it
Which one would you prefer?
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 with the linked QUIC v1 status report, then inspect the repository's test matrix, dormant implementations list, and ~failing alias. The work is complete once a maintainer-selected treatment for zig-libp2p is applied and the dashboard test runs reflect that choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- zig
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100