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: fix error when charset is in Content-Type (#3126) #3318

Merged
merged 1 commit into from
May 5, 2024

Conversation

aler9
Copy link
Member

@aler9 aler9 commented May 4, 2024

No description provided.

Copy link

codecov bot commented May 4, 2024

Codecov Report

Attention: Patch coverage is 25.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 52.66%. Comparing base (575d358) to head (7564703).

Files Patch % Lines
internal/protocols/httpp/content_type.go 0.00% 2 Missing ⚠️
internal/protocols/webrtc/whip_client.go 0.00% 2 Missing ⚠️
internal/servers/webrtc/http_server.go 50.00% 0 Missing and 2 partials ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3318   +/-   ##
=======================================
  Coverage   52.66%   52.66%           
=======================================
  Files         193      194    +1     
  Lines       20011    20015    +4     
=======================================
+ Hits        10538    10541    +3     
- Misses       8616     8617    +1     
  Partials      857      857           

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

@aler9 aler9 merged commit 5d0ebde into main May 5, 2024
7 of 8 checks passed
@aler9 aler9 deleted the fix/content-type branch May 5, 2024 08:47
Copy link
Contributor

github-actions bot commented May 5, 2024

This issue is mentioned in release v1.8.1 🚀
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.

None yet

1 participant