Skip to content

ci: Add CI step for webrtc compatibility with libp2p-go#628

Open
lexnv wants to merge 3 commits into
masterfrom
lexnv/ci-webrtc
Open

ci: Add CI step for webrtc compatibility with libp2p-go#628
lexnv wants to merge 3 commits into
masterfrom
lexnv/ci-webrtc

Conversation

@lexnv

@lexnv lexnv commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

This PR adds a new CI step to check the compatibility of webrtc implementation with libp2p-go client from litep2p-perf: https://github.com/lexnv/litep2p-perf.

The CI step:

  • clones the repo and replaces litep2p dependency to github PR one
  • spawn the webrtc litep2p server
  • extract the certhash from the running logs
  • tests connectivity, substream code paths, and compatibility with the libp2p-go client

lexnv added 3 commits June 30, 2026 10:24
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@lexnv lexnv requested a review from a team June 30, 2026 10:59
Comment thread .github/workflows/ci.yml
}
trap cleanup EXIT

# Wait for the server to advertise its /webrtc-direct/certhash address

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this is necessary, litep2p takes the cert from the outside right? Could we generate a known certificate and have it being known? Then we would not need to parse the hash here. But only a nit, can be follow up or accept status-quo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants