- WE WERE HERE TOGETHER OBJECTS BUGGED HOW TO
- WE WERE HERE TOGETHER OBJECTS BUGGED MANUAL
- WE WERE HERE TOGETHER OBJECTS BUGGED DOWNLOAD
Tsahi: And the reason it’s not enough is because if you’re from Google and you want to go and follow the steps, that’s still a lot of work. But you’re saying that this isn’t enough. Then they worked on the bisect and even came up with the actual steps that causes the problem.
Tsahi: We started with the bug, that Twilio found and filed: “we have a problem”. So what I did in this bug, I went ahead and made it into a jsFiddle.
WE WERE HERE TOGETHER OBJECTS BUGGED MANUAL
That’s manual that isn’t very easy to automate. And that is 10 steps and it’s a lot of manual action. It says, OK, step one, addTrack, then 10 steps and it says step 10 fails in Chrome 86. So we were looking at a bug Twilio filed, and after some back and forth we talked about earlier, they came up with this demo.īasically they had this demo, if I open the console. Tsahi” OK, so that would be doing something like what we’re doing every month here in kind of a jsFiddle, right? Philipp: So the thing is, you should provide very easy steps to run. Tsahi: So how can I help them out? Because at the end of the day, I want my bug fixed. So why should it be a problem for them to fix? Philipp: Well, all the Google people are very busy. I ran this bisect and I know this is commit 44. Philipp: Well, if you want to have this bug fixed, maybe you should spend some effort. Tsahi: OK, but that’s internal to Google, I don’t really care, I just want this bug fix. If it’s related, then maybe it’s time to ask the person what they think of this bug report. Philipp: At that point, I would say, OK, who made the change in commit 44? Is it WebRTC related? I got to the point where I know that the problem is, let’s say from this point of commit 44. Ran the tests on my application or whatever. Tsahi: OK, so I went ahead, did the downloads.
WE WERE HERE TOGETHER OBJECTS BUGGED DOWNLOAD
You basically download the version runs Chrome with that version, and then you can do the testing steps, close the browser and then say this is good or this is bad. There is a great script called bisect-builds.py, which downloads chromium versions and automate the process. You basically start with a good version and a bad version and then you go in the middle, decide if it is it good or is it bad? If it’s a good version. It’s typically a way to identify a change in git which change the behavior somehow. Philipp: A bisect is basically a binary search. Philipp: OK, can you do a bisect, which basically means taking the Chrome version 85 and version 86 and then you need to try to narrow down the number of changes to a single one. Philipp: OK, can you identify the version in which it is working and identify the version in which it is broken? So this is a new thing that is breaking for us. Tsahi: Yes, we tried it in the previous release, and it now runs well. Philipp: Well, does it work in an older version of Chrome? Tsahi: What do you mean? It doesn’t work now. That’s a great time, but what am I supposed to see?
Tsahi: OK, how do I do that, how do I help you in understanding that? Here’s a webrtc-internals dump on when the bug happens, I just publish them and pushed them into the bug.
Philipp: Well, if you haven’t proven that, it’s a bug in Chrome. Philipp: You expect me to follow these very complicated steps to understand your application and why should I spend so much time on that? And there are a certain set of steps that you need to take in order to get to that point where things don’t work. And on the other side you need to call and then you need to go back to that one, press the accept button, and then you need to mute on this end. After you log in, you need to go and assign yourself a specific role. Two of them, because you need to also join from another machine with another user. I also created for you a username and password. Philipp: OK, can you please provide a sample page so I can take a look? Tsahi: You threw the ball back at me and, well, definitely it is on your end, because if I do A, B and C and D and E, that turns into a crash. Philipp: Yes, and then if I where the Google Chrome developer, the Firefox or the Safari developer, I would ask: “OK, why do you think it’s a bug on my end? Why is it not the bug in your application”. So I’m going to just go file a bug and say: “you have a problem. Not only for you.įor me, this is how it looks, what we’re in is a kind of ping pong game.
WE WERE HERE TOGETHER OBJECTS BUGGED HOW TO
This time what we’re going to do is to explain how to exactly submit to bug to Chrome.īefore I begin, I want to show you how that feels on both ends, because filing a bug can be frustrating for everyone. Tsahi: Hi, and welcome to the WebRTC monthly Fiddle. Or just enroll to one of our excellent WebRTC training courses. Look us up here for the WebRTC Fiddle of the Month, created… once a month. 🎻 November 2020 fiddle Want to learn more about WebRTC?
0 kommentar(er)
