fixes(hls): adds fallback to MP4 in case the Mime type is not identified by parser#3325
fixes(hls): adds fallback to MP4 in case the Mime type is not identified by parser#3325joeyparrish merged 5 commits intoshaka-project:masterfrom surajkumar-sk:hls
Conversation
|
I saw people adding names to the contributor's list and authors list. Do I qualify to add my name to the list |
| .toBeRejectedWith(Util.jasmineError(error)); | ||
| } | ||
|
|
||
| it('if unable to guess mime type', async () => { |
There was a problem hiding this comment.
Can you please add a new test case for the fallback to mp4? You could use this as a template, but the new test should not be nested within describe('Errors out', () => {
Thanks!
Sure. You can add your name in this PR. The list hasn't been perfectly maintained over the years, and new projects at Google don't have CONTRIBUTORS files at all. So the source of truth for who is a contributor is actually the commit log. Because the list has been poorly-maintained for so long, it may be replaced by some other system of acknowledgement in the future. |
|
Here's the longer reply. You may regret asking me such a loaded question. 😄
We are a small team at Google. There are currently only 3 people working full-time on Shaka Player, and for reasons I can't really get into, we spent a few months recently with only 1 person working on the project full-time. As the core team of maintainers, we are working on a few high-priority features, while also fixing bugs, and managing issues and PRs. We're doing about as much as we possibly can by ourselves. So everything else is left to the Shaka Player community. This particular issue is a low priority for us. The issue only affects servers that don't support HEAD requests (which are these anyway?) serving content that has no recognizable file extension. But for a service provider with this exact setup, it would be a higher priority for them. The beauty of open source is that you can have very different priorities from us. If you care about something enough, you can read and modify the source to get what you want. As maintainers, the best thing we can do to get the most done on the project is to be available to provide expertise, to coach and guide contributors, and to help them identify solutions. Perhaps one of us could have done this particular thing more quickly, but by helping members of the community contribute to the issues they care about, we're getting more done overall in parallel.
I don't think we can make it perfect. Though you remind me of two sayings that I love: Shaka Player will never be "done", because requirements will always change and no project will ever be bug-free. But some day the world may lose interest, or the project may no longer be needed. We'll make it as good as we can, for as long as we can, but some day this project will die, as all projects will. We will never be bug-free, strive as we might. And we will never have the perfect feature set for every user. In fact, some users want us to remove features that others see as a requirement. We literally can't be the best solution for everyone. Since perfection is unachievable, it's important to decide where we settle, and what "good enough" means for us, and not obsess over what we can't get done. Some issues will remain on the backlog until they become important enough for us to devote our limited time to them, or until someone like you comes along who has the time and energy to work on them. I hope this is useful context, and that you'll forgive me for being so long-winded. 😄 |
joeyparrish
left a comment
There was a problem hiding this comment.
Looks good to me otherwise. Thanks!
test/hls/hls_parser_unit.js
Outdated
| await testHlsParser(master, media, manifest); | ||
| }); | ||
|
|
||
| it('if unable to guess mime type through Header Request', async () => { |
There was a problem hiding this comment.
The name of this test doesn't make sense. In the previous version, it was inside a describe called "Errors out", leading to the complete name "Errors out if ..."
Here, this might be a better name: it('falls back to mp4 if HEAD request fails'
Though we sometimes break this rule a bit, in Jasmine, the "it" functions should read like a sentence about the thing under test: "it falls back to mp4 if ..."
These lines hit very differently, it felt very emotional.
That's definitely useful. and I don't know why the inner me pronounces those sentences as a prophet giving a lecture about a divine event. 😂 Thank you for taking the time and replying. |
I'm an emotional guy! This will be me when I leave the project some day: 😭🤙 |
|
Hope the thing for which you will leave this project, will be worth it. 😊 |
How about retirement? |
|
well, you can still join our group of contributors. but I don't know about how retirement might feel, if it's worth it or not, I am still a student who is figuring out his youth. that's probably a question you yourself should answer. 😊 |
Plan ahead, I always say. 😄 |
|
I can't even if I want to. There are just so many technologies that interest me that I think I'll probably never retire. 😵 |
|
All tests passed! |
Not true! Cap retired. (Spoiler) |
|
Thanks for your contribution! |
|
Yeah he did, but he is a soldier(a good man), thanos too.. let me change my statement . |
Fixes #3142 Backported to v3.0.x Change-Id: I09a48c30e76da5a4a93d58263d3a94abf7ed69ed
Fixes #3142 Backported to v2.5.x Change-Id: I8980cf47f16de50827c42cfebad7c67792156481
Description
#3142Screenshots (optional)
Type of change
Checklist:
./build/all.pyand the build passes./build/test.pyand all tests pass