Split TURN test when using "UDP + TCP"
Open
Nobody has claimed this yet.
bug
feature: frontend 🖌️
feature: WebRTC 🚡
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Setup a TURN server that only supports TCP
- Set "UDP + TCP" in the admin settings
Expected behaviour
The test should fail, as we don't receive candidates via UDP
Actual behaviour
Test succeeds as we received any candidate (TCP in this case)
Talk app
Talk app version: 21.0.2
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
Locate the TURN-related test in the JavaScript test suite and review how candidates are accepted when the setting is "UDP + TCP". Reproduce it with a TCP-only TURN server; done means the test distinguishes UDP candidates and fails when none are received.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100