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

fix strange rtp header padding #1075

Closed
wants to merge 2 commits into from
Closed

Conversation

buptlsp
Copy link

@buptlsp buptlsp commented May 6, 2023

refer to #1073

@buptlsp buptlsp closed this May 9, 2023
@ibc
Copy link
Member

ibc commented May 9, 2023

Why have you closed this PR @buptlsp?

@buptlsp
Copy link
Author

buptlsp commented May 9, 2023

I have mentioned this issue for more than 2 weeks, but no one has replied to me. Maybe you guys don't think it's important, but in reality it affects our company a lot money per day. So I had to change it privately. if you guys merge again, I need extra time to fix conflict.

I probably don't have enough confidence that you guys will think this is right. after all I've only been studying webrtc and c++ for a few months.

@buptlsp
Copy link
Author

buptlsp commented May 9, 2023

I solved the last problem with #1022. but it's too complicated to create a pr, I have change a lot of places in private. mybe I should close the issue first?

@jmillan
Copy link
Member

jmillan commented May 10, 2023

I have mentioned this issue for more than 2 weeks, but no one has replied to me. Maybe you guys don't think it's important,

Please have some patience. This project is maintained mostly out of working hours. Meaning we cannot always just leave everything and review the PRs as they come.

@jmillan
Copy link
Member

jmillan commented May 10, 2023

Closing the PR because there has been no response is not the way to go. You can kindly ask for feedback if you find you didn't get response in a reasonable time period though.

@jmillan
Copy link
Member

jmillan commented May 10, 2023

Also, in the meantime you can be the one telling us:

  • "I've tested and it works as expected"
  • "It does not imply any performance penalty / It does imply some performance penalty" etc.

Reviewing a PR that you've already tested and with which you have some confidence also helps the reviewing process.

@buptlsp
Copy link
Author

buptlsp commented May 10, 2023

Well, I'll be more patient next time. I actually found some other issues, and I'll submit pr when I've confirmed them.

This pr is in grey testing. I have wrote the problems I found in the review. I'll resubmit when I have done my testing.

@ibc
Copy link
Member

ibc commented May 10, 2023

I have mentioned this issue for more than 2 weeks, but no one has replied to me. Maybe you guys don't think it's important, but in reality it affects our company a lot money per day. So I had to change it privately. if you guys merge again, I need extra time to fix conflict.

Literally we have spent a week off due to work and we are super busy with many things (some of them indeed related to mediasouop). Please, more patient next time ;)

@ibc
Copy link
Member

ibc commented May 10, 2023

BTW these kind of changes definitely need fuzzer testing (see mediasoup/docs/Fuzzer.md).

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

Successfully merging this pull request may close these issues.

None yet

3 participants