Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webrtc: on browsers, display error messages from server #3448

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

aler9
Copy link
Member

@aler9 aler9 commented Jun 10, 2024

No description provided.

Copy link

codecov bot commented Jun 10, 2024

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 56.20%. Comparing base (1911294) to head (91a6245).

Files Patch % Lines
internal/protocols/webrtc/peer_connection.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3448      +/-   ##
==========================================
- Coverage   56.20%   56.20%   -0.01%     
==========================================
  Files         190      190              
  Lines       19049    19049              
==========================================
- Hits        10707    10706       -1     
- Misses       7520     7521       +1     
  Partials      822      822              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@aler9 aler9 changed the title webrtc: on browser, display error messages from server webrtc: on browsers, display error messages from server Jun 10, 2024
@aler9 aler9 merged commit 095921d into main Jun 10, 2024
7 of 8 checks passed
@aler9 aler9 deleted the feature/webrtc-msg branch June 10, 2024 13:41
Copy link
Contributor

This issue is mentioned in release v1.8.3 🚀
Check out the entire changelog by clicking here

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.

1 participant