[2026-11-19] eagle: work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.json work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.md work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md work/zoom-transcripts/2026-10-27 Apple Weekly Team Meeting - Zoom ID -I3aVYDWTkKZ_VTRLdjGnA/transcript.json work/zoom-transcripts/2026-10-27 Apple Weekly Team Meeting - Zoom ID -I3aVYDWTkKZ_VTRLdjGnA/transcript.md work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.json work/zoom-transcripts/2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA/transcript.md work/zoom-transcripts/index.json work/zoom-transcripts/sync-status.json
This commit is contained in:
1 parent
75fd91b92c
commit
192aaee4be
10 files changed
+1065
-447
No files matched your search
-85
@@ -23,91 +23,6 @@
|
||||
"time": "21:31:26",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:31:34",
|
||||
"speaker": "Anne Hildebrand",
|
||||
"text": "And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me."
|
||||
},
|
||||
{
|
||||
"time": "21:31:58",
|
||||
"speaker": "Viktor Jansson",
|
||||
"text": "Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates."
|
||||
},
|
||||
{
|
||||
"time": "21:32:56",
|
||||
"speaker": "Kirby (she/they)",
|
||||
"text": "Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think."
|
||||
},
|
||||
{
|
||||
"time": "21:37:23",
|
||||
"speaker": "russell holt",
|
||||
"text": "Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle."
|
||||
},
|
||||
{
|
||||
"time": "21:39:42",
|
||||
"speaker": "Emanuele Feliziani",
|
||||
"text": "Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell."
|
||||
},
|
||||
{
|
||||
"time": "21:42:36",
|
||||
"speaker": "Jon Russo",
|
||||
"text": "Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks."
|
||||
},
|
||||
{
|
||||
"time": "21:44:56",
|
||||
"speaker": "Stephen",
|
||||
"text": "Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone."
|
||||
},
|
||||
{
|
||||
"time": "21:45:37",
|
||||
"speaker": "Spencer",
|
||||
"text": "Yes."
|
||||
},
|
||||
{
|
||||
"time": "21:45:38",
|
||||
"speaker": "Stephen",
|
||||
"text": "Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now."
|
||||
},
|
||||
{
|
||||
"time": "21:47:35",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…"
|
||||
},
|
||||
{
|
||||
"time": "21:47:45",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "I think that's Brett Stevens."
|
||||
},
|
||||
{
|
||||
"time": "21:47:46",
|
||||
"speaker": "Stephen",
|
||||
"text": "Oh, yeah, that was part of mine, sorry."
|
||||
},
|
||||
{
|
||||
"time": "21:47:48",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:47:48",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week."
|
||||
},
|
||||
{
|
||||
"time": "21:49:17",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should."
|
||||
},
|
||||
{
|
||||
"time": "21:49:37",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "We do have, yes, specialties."
|
||||
},
|
||||
{
|
||||
"time": "21:49:40",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good."
|
||||
}
|
||||
]
|
||||
}
|
||||
-17
@@ -15,20 +15,3 @@ source: "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA"
|
||||
- **21:31:08 · Gabriel Weinberg:** Hello? That was a nice fade out. Um… Okay… No new team members, no AOR updates. Um, we had one company update, there's no name by it.
|
||||
- **21:31:23 · Anne Hildebrand:** Sorry, that was me. Um, yes, this is Anne. Uh, just a reminder to check your inboxes for the outcome of the compensation review.
|
||||
- **21:31:26 · Gabriel Weinberg:** Yeah.
|
||||
- **21:31:34 · Anne Hildebrand:** And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me.
|
||||
- **21:31:58 · Viktor Jansson:** Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates.
|
||||
- **21:32:56 · Kirby (she/they):** Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think.
|
||||
- **21:37:23 · russell holt:** Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle.
|
||||
- **21:39:42 · Emanuele Feliziani:** Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell.
|
||||
- **21:42:36 · Jon Russo:** Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks.
|
||||
- **21:44:56 · Stephen:** Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone.
|
||||
- **21:45:37 · Spencer:** Yes.
|
||||
- **21:45:38 · Stephen:** Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now.
|
||||
- **21:47:35 · Julia Abreu:** We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…
|
||||
- **21:47:45 · Gabriel Weinberg:** I think that's Brett Stevens.
|
||||
- **21:47:46 · Stephen:** Oh, yeah, that was part of mine, sorry.
|
||||
- **21:47:48 · Gabriel Weinberg:** Yeah.
|
||||
- **21:47:48 · Julia Abreu:** Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week.
|
||||
- **21:49:17 · Gabriel Weinberg:** Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should.
|
||||
- **21:49:37 · Julia Abreu:** We do have, yes, specialties.
|
||||
- **21:49:40 · Gabriel Weinberg:** Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good.
|
||||
+650
@@ -23,6 +23,656 @@
|
||||
"time": "18:10:09",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process."
|
||||
},
|
||||
{
|
||||
"time": "18:10:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:10:23",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do you have any, like, extra steps?"
|
||||
},
|
||||
{
|
||||
"time": "18:10:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, so generally it fails from the second try on this exact test page that is attached there."
|
||||
},
|
||||
{
|
||||
"time": "18:10:37",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So after, after I, I killed the, the, the…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:10:41",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Web extension, web process. I should reload the page?"
|
||||
},
|
||||
{
|
||||
"time": "18:10:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, in general."
|
||||
},
|
||||
{
|
||||
"time": "18:10:49",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do I need to do it, like, quickly, or do I need to, like…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:53",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Wait a bit."
|
||||
},
|
||||
{
|
||||
"time": "18:10:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Usually… yeah. I don't know, within one second, just kill the process, then reload the page."
|
||||
},
|
||||
{
|
||||
"time": "18:11:02",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:11:03",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…"
|
||||
},
|
||||
{
|
||||
"time": "18:11:20",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, artificial."
|
||||
},
|
||||
{
|
||||
"time": "18:11:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis."
|
||||
},
|
||||
{
|
||||
"time": "18:11:52",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:11:52",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess."
|
||||
},
|
||||
{
|
||||
"time": "18:12:35",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I can hear you, I cannot see you."
|
||||
},
|
||||
{
|
||||
"time": "18:12:36",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something."
|
||||
},
|
||||
{
|
||||
"time": "18:13:10",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Did your laptop display died?"
|
||||
},
|
||||
{
|
||||
"time": "18:13:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this."
|
||||
},
|
||||
{
|
||||
"time": "18:15:02",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yes. So, so the first…"
|
||||
},
|
||||
{
|
||||
"time": "18:15:04",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Pixel fire for the pixel, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:15:06",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "First PR is the pixels, yeah? So the one from the PR."
|
||||
},
|
||||
{
|
||||
"time": "18:15:09",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it."
|
||||
},
|
||||
{
|
||||
"time": "18:15:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?"
|
||||
},
|
||||
{
|
||||
"time": "18:15:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue."
|
||||
},
|
||||
{
|
||||
"time": "18:16:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:16:39",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "In, like, lab condition."
|
||||
},
|
||||
{
|
||||
"time": "18:16:40",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Can you say. Which one was the last PR?"
|
||||
},
|
||||
{
|
||||
"time": "18:16:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "The last one, uh, 7459. This one."
|
||||
},
|
||||
{
|
||||
"time": "18:17:00",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah, I got it, yeah, the network one, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:17:11",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag."
|
||||
},
|
||||
{
|
||||
"time": "18:18:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…"
|
||||
},
|
||||
{
|
||||
"time": "18:18:48",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Just to get the pixels… yeah, I guess so. I guess so we can make the pixel."
|
||||
},
|
||||
{
|
||||
"time": "18:18:59",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag."
|
||||
},
|
||||
{
|
||||
"time": "18:19:11",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, I agree."
|
||||
},
|
||||
{
|
||||
"time": "18:19:12",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be."
|
||||
},
|
||||
{
|
||||
"time": "18:19:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:19:23",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that."
|
||||
},
|
||||
{
|
||||
"time": "18:19:57",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…"
|
||||
},
|
||||
{
|
||||
"time": "18:22:09",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But which base? I, I don't, I don't get it, like, fully, like, with me."
|
||||
},
|
||||
{
|
||||
"time": "18:22:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension."
|
||||
},
|
||||
{
|
||||
"time": "18:22:28",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:22:29",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures."
|
||||
},
|
||||
{
|
||||
"time": "18:22:44",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Mhmm. But it's only only on update, like, when we uninstall and install again, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:22:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially."
|
||||
},
|
||||
{
|
||||
"time": "18:23:14",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four."
|
||||
},
|
||||
{
|
||||
"time": "18:23:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work."
|
||||
},
|
||||
{
|
||||
"time": "18:23:53",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…"
|
||||
},
|
||||
{
|
||||
"time": "18:24:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, Zip?"
|
||||
},
|
||||
{
|
||||
"time": "18:24:07",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it."
|
||||
},
|
||||
{
|
||||
"time": "18:24:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today."
|
||||
},
|
||||
{
|
||||
"time": "18:24:30",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:24:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension."
|
||||
},
|
||||
{
|
||||
"time": "18:25:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But it's only McCoy, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:25:32",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases."
|
||||
},
|
||||
{
|
||||
"time": "18:26:37",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, do you estimate to get them done this week?"
|
||||
},
|
||||
{
|
||||
"time": "18:26:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, yeah. Yeah, so the point here is to timebox it to…"
|
||||
},
|
||||
{
|
||||
"time": "18:26:45",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "To merge it this week, and so we can, like, get it internally next week, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:26:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week."
|
||||
},
|
||||
{
|
||||
"time": "18:27:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so you would mean to merge it to… Release branches."
|
||||
},
|
||||
{
|
||||
"time": "18:27:17",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, if it's possible."
|
||||
},
|
||||
{
|
||||
"time": "18:27:22",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:27:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags."
|
||||
},
|
||||
{
|
||||
"time": "18:27:43",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it."
|
||||
},
|
||||
{
|
||||
"time": "18:27:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "18:28:01",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart."
|
||||
},
|
||||
{
|
||||
"time": "18:28:08",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal."
|
||||
},
|
||||
{
|
||||
"time": "18:28:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free."
|
||||
},
|
||||
{
|
||||
"time": "18:28:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm, okay."
|
||||
},
|
||||
{
|
||||
"time": "18:28:24",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that."
|
||||
},
|
||||
{
|
||||
"time": "18:28:30",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, I'll… I'll keep you pinged, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:28:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And… Please ping me when you have the following one, because I want to, like…"
|
||||
},
|
||||
{
|
||||
"time": "18:28:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:28:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:28:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it."
|
||||
},
|
||||
{
|
||||
"time": "18:28:58",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:29:04",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "18:29:04",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And the others, like, later in the week."
|
||||
},
|
||||
{
|
||||
"time": "18:29:07",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:29:08",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I agree."
|
||||
},
|
||||
{
|
||||
"time": "18:29:09",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, and yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:29:10",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Just to try to get them out as soon as possible to get some results."
|
||||
},
|
||||
{
|
||||
"time": "18:29:16",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…"
|
||||
},
|
||||
{
|
||||
"time": "18:29:48",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "No doubt."
|
||||
},
|
||||
{
|
||||
"time": "18:29:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get."
|
||||
},
|
||||
{
|
||||
"time": "18:30:08",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:30:14",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time."
|
||||
},
|
||||
{
|
||||
"time": "18:30:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…"
|
||||
},
|
||||
{
|
||||
"time": "18:30:41",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…"
|
||||
},
|
||||
{
|
||||
"time": "18:31:06",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?"
|
||||
},
|
||||
{
|
||||
"time": "18:31:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported."
|
||||
},
|
||||
{
|
||||
"time": "18:31:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:31:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this."
|
||||
},
|
||||
{
|
||||
"time": "18:31:51",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?"
|
||||
},
|
||||
{
|
||||
"time": "18:32:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so."
|
||||
},
|
||||
{
|
||||
"time": "18:32:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…"
|
||||
},
|
||||
{
|
||||
"time": "18:32:20",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:32:39",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you."
|
||||
},
|
||||
{
|
||||
"time": "18:32:49",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes."
|
||||
},
|
||||
{
|
||||
"time": "18:33:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Have you assigned me to all of the PRs? Because, uh, I see them…"
|
||||
},
|
||||
{
|
||||
"time": "18:33:15",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you."
|
||||
},
|
||||
{
|
||||
"time": "18:33:29",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I think, like, something is broken with the…"
|
||||
},
|
||||
{
|
||||
"time": "18:33:33",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, yeah, I'll… I'm on it."
|
||||
},
|
||||
{
|
||||
"time": "18:33:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up."
|
||||
},
|
||||
{
|
||||
"time": "18:33:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer."
|
||||
},
|
||||
{
|
||||
"time": "18:33:54",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I don't know, like, you have the filter, like, review requested."
|
||||
},
|
||||
{
|
||||
"time": "18:34:00",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:34:01",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "They can…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:01",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests."
|
||||
},
|
||||
{
|
||||
"time": "18:34:07",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:14",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "18:34:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Me? I only get two of them."
|
||||
},
|
||||
{
|
||||
"time": "18:34:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay. 7, 4, 5, 5, 7."
|
||||
},
|
||||
{
|
||||
"time": "18:34:26",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Which is weird."
|
||||
},
|
||||
{
|
||||
"time": "18:34:29",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:34:40",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "For the resolutions. Angus."
|
||||
},
|
||||
{
|
||||
"time": "18:34:43",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so maybe it's like, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:34:46",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, so currently two more in stock."
|
||||
},
|
||||
{
|
||||
"time": "18:34:50",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay. So it's it's in the stack, so I can get them from from the list. Right?"
|
||||
},
|
||||
{
|
||||
"time": "18:34:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "18:34:56",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, cool. Can I help you in any other way?"
|
||||
},
|
||||
{
|
||||
"time": "18:34:59",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good."
|
||||
},
|
||||
{
|
||||
"time": "18:35:15",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do you need any other help?"
|
||||
},
|
||||
{
|
||||
"time": "18:35:18",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good."
|
||||
},
|
||||
{
|
||||
"time": "18:35:46",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one."
|
||||
},
|
||||
{
|
||||
"time": "18:35:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Sure. Okay, thank you."
|
||||
},
|
||||
{
|
||||
"time": "18:36:03",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Thank you."
|
||||
}
|
||||
]
|
||||
}
|
||||
+130
@@ -15,3 +15,133 @@ source: "https://us01mynotes.zoom.us/QvxllpCuTTSLGEZp-R6jQw"
|
||||
- **18:10:01 · Michal Smaga:** Good.
|
||||
- **18:10:01 · Alex Martemyanov:** I'm pretty good. Jumping between windows. Yes.
|
||||
- **18:10:09 · Michal Smaga:** Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process.
|
||||
- **18:10:22 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:10:23 · Michal Smaga:** Do you have any, like, extra steps?
|
||||
- **18:10:27 · Alex Martemyanov:** Uh, so generally it fails from the second try on this exact test page that is attached there.
|
||||
- **18:10:37 · Michal Smaga:** So after, after I, I killed the, the, the…
|
||||
- **18:10:37 · Alex Martemyanov:** Okay.
|
||||
- **18:10:41 · Michal Smaga:** Web extension, web process. I should reload the page?
|
||||
- **18:10:47 · Alex Martemyanov:** Yes, in general.
|
||||
- **18:10:49 · Michal Smaga:** Do I need to do it, like, quickly, or do I need to, like…
|
||||
- **18:10:53 · Alex Martemyanov:** Um…
|
||||
- **18:10:53 · Michal Smaga:** Wait a bit.
|
||||
- **18:10:55 · Alex Martemyanov:** Usually… yeah. I don't know, within one second, just kill the process, then reload the page.
|
||||
- **18:11:02 · Michal Smaga:** Yeah.
|
||||
- **18:11:03 · Alex Martemyanov:** If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…
|
||||
- **18:11:20 · Michal Smaga:** Yeah, artificial.
|
||||
- **18:11:22 · Alex Martemyanov:** artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis.
|
||||
- **18:11:52 · Michal Smaga:** Yeah, yeah, yeah.
|
||||
- **18:11:52 · Alex Martemyanov:** So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess.
|
||||
- **18:12:35 · Michal Smaga:** I can hear you, I cannot see you.
|
||||
- **18:12:36 · Alex Martemyanov:** Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something.
|
||||
- **18:13:10 · Michal Smaga:** Did your laptop display died?
|
||||
- **18:13:13 · Alex Martemyanov:** Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this.
|
||||
- **18:15:02 · Michal Smaga:** Yes. So, so the first…
|
||||
- **18:15:04 · Alex Martemyanov:** Pixel fire for the pixel, yeah.
|
||||
- **18:15:06 · Michal Smaga:** First PR is the pixels, yeah? So the one from the PR.
|
||||
- **18:15:09 · Alex Martemyanov:** Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it.
|
||||
- **18:15:18 · Michal Smaga:** Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?
|
||||
- **18:15:24 · Alex Martemyanov:** Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue.
|
||||
- **18:16:38 · Michal Smaga:** Mm-hmm.
|
||||
- **18:16:39 · Alex Martemyanov:** In, like, lab condition.
|
||||
- **18:16:40 · Michal Smaga:** Can you say. Which one was the last PR?
|
||||
- **18:16:45 · Alex Martemyanov:** The last one, uh, 7459. This one.
|
||||
- **18:17:00 · Michal Smaga:** Yeah, yeah, yeah, I got it, yeah, the network one, yeah.
|
||||
- **18:17:11 · Alex Martemyanov:** So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag.
|
||||
- **18:18:36 · Michal Smaga:** And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…
|
||||
- **18:18:48 · Alex Martemyanov:** Just to get the pixels… yeah, I guess so. I guess so we can make the pixel.
|
||||
- **18:18:59 · Michal Smaga:** Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag.
|
||||
- **18:19:11 · Alex Martemyanov:** Yeah, I agree.
|
||||
- **18:19:12 · Michal Smaga:** Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be.
|
||||
- **18:19:22 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:19:23 · Michal Smaga:** Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that.
|
||||
- **18:19:57 · Alex Martemyanov:** Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…
|
||||
- **18:22:09 · Michal Smaga:** But which base? I, I don't, I don't get it, like, fully, like, with me.
|
||||
- **18:22:13 · Alex Martemyanov:** The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension.
|
||||
- **18:22:28 · Michal Smaga:** Okay.
|
||||
- **18:22:29 · Alex Martemyanov:** And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures.
|
||||
- **18:22:44 · Michal Smaga:** Mhmm. But it's only only on update, like, when we uninstall and install again, right?
|
||||
- **18:22:45 · Alex Martemyanov:** And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially.
|
||||
- **18:23:14 · Michal Smaga:** Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four.
|
||||
- **18:23:24 · Alex Martemyanov:** Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work.
|
||||
- **18:23:53 · Michal Smaga:** So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…
|
||||
- **18:24:05 · Alex Martemyanov:** Uh, Zip?
|
||||
- **18:24:07 · Michal Smaga:** thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it.
|
||||
- **18:24:27 · Alex Martemyanov:** Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today.
|
||||
- **18:24:30 · Michal Smaga:** Yeah, yeah, yeah.
|
||||
- **18:24:37 · Alex Martemyanov:** No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension.
|
||||
- **18:25:31 · Michal Smaga:** But it's only McCoy, right?
|
||||
- **18:25:32 · Alex Martemyanov:** I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases.
|
||||
- **18:26:37 · Michal Smaga:** So, do you estimate to get them done this week?
|
||||
- **18:26:37 · Alex Martemyanov:** So, yeah. Yeah, so the point here is to timebox it to…
|
||||
- **18:26:45 · Michal Smaga:** To merge it this week, and so we can, like, get it internally next week, right?
|
||||
- **18:26:45 · Alex Martemyanov:** Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week.
|
||||
- **18:27:11 · Michal Smaga:** Okay, so you would mean to merge it to… Release branches.
|
||||
- **18:27:17 · Alex Martemyanov:** Yes, if it's possible.
|
||||
- **18:27:22 · Michal Smaga:** So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?
|
||||
- **18:27:31 · Alex Martemyanov:** Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags.
|
||||
- **18:27:43 · Michal Smaga:** Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it.
|
||||
- **18:27:55 · Alex Martemyanov:** Mmhm.
|
||||
- **18:28:01 · Michal Smaga:** So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart.
|
||||
- **18:28:08 · Alex Martemyanov:** Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal.
|
||||
- **18:28:18 · Michal Smaga:** I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free.
|
||||
- **18:28:24 · Alex Martemyanov:** Mm-hmm, okay.
|
||||
- **18:28:24 · Michal Smaga:** If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that.
|
||||
- **18:28:30 · Alex Martemyanov:** Okay, I'll… I'll keep you pinged, yeah.
|
||||
- **18:28:31 · Michal Smaga:** And… Please ping me when you have the following one, because I want to, like…
|
||||
- **18:28:37 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:28:38 · Michal Smaga:** Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah.
|
||||
- **18:28:47 · Alex Martemyanov:** Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it.
|
||||
- **18:28:58 · Michal Smaga:** Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah.
|
||||
- **18:29:04 · Alex Martemyanov:** Mmhm.
|
||||
- **18:29:04 · Michal Smaga:** And the others, like, later in the week.
|
||||
- **18:29:07 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:29:08 · Michal Smaga:** Yeah, I agree.
|
||||
- **18:29:09 · Alex Martemyanov:** So, and yeah.
|
||||
- **18:29:10 · Michal Smaga:** Just to try to get them out as soon as possible to get some results.
|
||||
- **18:29:16 · Alex Martemyanov:** And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…
|
||||
- **18:29:48 · Michal Smaga:** No doubt.
|
||||
- **18:29:53 · Alex Martemyanov:** into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get.
|
||||
- **18:30:08 · Michal Smaga:** Yeah.
|
||||
- **18:30:14 · Alex Martemyanov:** We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time.
|
||||
- **18:30:31 · Michal Smaga:** So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…
|
||||
- **18:30:41 · Alex Martemyanov:** Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…
|
||||
- **18:31:06 · Michal Smaga:** Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?
|
||||
- **18:31:13 · Alex Martemyanov:** Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported.
|
||||
- **18:31:36 · Michal Smaga:** Okay.
|
||||
- **18:31:37 · Alex Martemyanov:** And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this.
|
||||
- **18:31:51 · Michal Smaga:** Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?
|
||||
- **18:32:05 · Alex Martemyanov:** Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so.
|
||||
- **18:32:11 · Michal Smaga:** Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…
|
||||
- **18:32:20 · Alex Martemyanov:** Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah.
|
||||
- **18:32:39 · Michal Smaga:** Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you.
|
||||
- **18:32:49 · Alex Martemyanov:** Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes.
|
||||
- **18:33:11 · Michal Smaga:** Have you assigned me to all of the PRs? Because, uh, I see them…
|
||||
- **18:33:15 · Alex Martemyanov:** Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you.
|
||||
- **18:33:29 · Michal Smaga:** Yeah, I think, like, something is broken with the…
|
||||
- **18:33:33 · Alex Martemyanov:** Yeah, yeah, I'll… I'm on it.
|
||||
- **18:33:36 · Michal Smaga:** No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up.
|
||||
- **18:33:47 · Alex Martemyanov:** Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer.
|
||||
- **18:33:54 · Michal Smaga:** I don't know, like, you have the filter, like, review requested.
|
||||
- **18:34:00 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:34:01 · Michal Smaga:** They can…
|
||||
- **18:34:01 · Alex Martemyanov:** Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests.
|
||||
- **18:34:07 · Michal Smaga:** Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…
|
||||
- **18:34:14 · Alex Martemyanov:** Yep.
|
||||
- **18:34:18 · Michal Smaga:** Me? I only get two of them.
|
||||
- **18:34:24 · Alex Martemyanov:** Okay. 7, 4, 5, 5, 7.
|
||||
- **18:34:26 · Michal Smaga:** Which is weird.
|
||||
- **18:34:29 · Alex Martemyanov:** Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…
|
||||
- **18:34:38 · Michal Smaga:** Okay.
|
||||
- **18:34:40 · Alex Martemyanov:** For the resolutions. Angus.
|
||||
- **18:34:43 · Michal Smaga:** Okay, so maybe it's like, yeah.
|
||||
- **18:34:46 · Alex Martemyanov:** Yeah, so currently two more in stock.
|
||||
- **18:34:50 · Michal Smaga:** Okay. So it's it's in the stack, so I can get them from from the list. Right?
|
||||
- **18:34:55 · Alex Martemyanov:** Yep.
|
||||
- **18:34:56 · Michal Smaga:** Okay, cool. Can I help you in any other way?
|
||||
- **18:34:59 · Alex Martemyanov:** Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good.
|
||||
- **18:35:15 · Michal Smaga:** Do you need any other help?
|
||||
- **18:35:18 · Alex Martemyanov:** Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good.
|
||||
- **18:35:46 · Michal Smaga:** Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one.
|
||||
- **18:35:58 · Alex Martemyanov:** Sure. Okay, thank you.
|
||||
- **18:36:03 · Michal Smaga:** Thank you.
|
||||
+230
@@ -23,6 +23,236 @@
|
||||
"time": "20:03:30",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "The meeting is at the wrong time in Europe this week, so some people may be missing because of that."
|
||||
},
|
||||
{
|
||||
"time": "20:03:38",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "I totally lost track of which one's which, that's fine, I was just pulling up rotations so we can get started anyway. Hello, everyone. Nice to see you all. Quick run through our rotations as usual. Bartek is on iOS drives this week, followed by Brindy and then Hassan. Echoist triages Jorge this week, followed by Rachel, and then Alessandro. For release duties, iOS this week, Bartosz, followed by Mihao, and then Pete. And macOS is Tom this week, followed by Juan, and then Joseph. Any issues, go ahead and flag those in Asana as usual, please. Sam, you have an announcement to share with us. I think you're, yes."
|
||||
},
|
||||
{
|
||||
"time": "20:04:27",
|
||||
"speaker": "SS",
|
||||
"text": "Right, this is the AOR change. Sorry, I don't have the agenda pulled up. Uh, yes, uh…"
|
||||
},
|
||||
{
|
||||
"time": "20:04:29",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Thank you. Yes, sorry."
|
||||
},
|
||||
{
|
||||
"time": "20:04:34",
|
||||
"speaker": "SS",
|
||||
"text": "Is George here? Yes, he is. George has taken over secondary of the VPN AOR from me after running some projects to get us better observability into the VPN, so… Thank you. Nice work. Yes, also that."
|
||||
},
|
||||
{
|
||||
"time": "20:04:48",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Excellent. Thank you and congratulations."
|
||||
},
|
||||
{
|
||||
"time": "20:04:50",
|
||||
"speaker": "SS",
|
||||
"text": "So also also. Also, what Jacek said in the chat is accurate."
|
||||
},
|
||||
{
|
||||
"time": "20:04:58",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Yeah, I mean, I guess this is as good a time as any way to remind people that AOR, DRI ships are not written in stone. They are changeable. If you want one and don't have one, want a particular one, want to get out of one. We can talk about it. You don't even have to talk to me. You can make a proposal. They are changeable. Thank you. Dominic, CI usage update from you."
|
||||
},
|
||||
{
|
||||
"time": "20:05:25",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Uh, yes. Um… It's pretty early in the agenda here. But okay, anyway. I have this… Artifact. Here, that I can share with you. Or not. Doesn't work. One second, I'm sorry. Um… Oh, yes. So anyway, I was looking at… I was looking at, um… And CI time. In the recent months and just to… just to have a look, just to get a feeling of how… Bitrise works or doesn't work. Here's the link, but let me also share it with you. Show my screen, I guess. I'm, uh, I mean, uh, so, uh… I have this… job hours and runs per month since February. Uh, it was going up and down, and at some point, uh, job runs… Pretty steady at… 5,500 a month, whereas job hours are going down. Quite drastically, actually, because it's at 1700 for September. And it has never been below 2000 earlier this year. Not sure about January, but anyway. Yeah, which is interesting. And also… Average… Job duration. It goes… it went down to 18.9 minutes from over 30. This is only for the PR checks, so VSK, DBP, iOS, and macOS PR checks only. in the monorepo, uh, which… Looks like… Uh, confirming that Bitrise is doing the job. Uh, but my initial… uh, motivation to… to run this was to see if we should consider getting more machines from Bitrise, because maybe we're running more jobs. Which was my assumption. Because… Code is cheap these days, relatively cheap. cheaper than it used to be, and uh… because of that, we might be opening more pull requests, running more workflows, and so on and so on, so maybe we need more machines, because we would have paid more for GitHub anyway. not sure if it's the case yet. October is not here, even though it's 27th, and I did yesterday, but in October, we enabled… Required checks. in the repository, which means all the checks run on all pull requests now, so naturally there's higher volume of checks, and it wasn't fitting this graph nicely. So I guess we'll have a new baseline in October, and then. We'll be comparing against that in the following months. That's what I have. Tommy has any thoughts?"
|
||||
},
|
||||
{
|
||||
"time": "20:08:50",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "When did we actually fully switch to Bitrise?"
|
||||
},
|
||||
{
|
||||
"time": "20:08:53",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Um… September 14th?"
|
||||
},
|
||||
{
|
||||
"time": "20:08:59",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "So that would, because they're faster, that would drive down our run times while jobs remain steady potentially, which it looked like that actually showed in the data you were just showing, right?"
|
||||
},
|
||||
{
|
||||
"time": "20:08:59",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yes. So, one correction. September 14th was when we got the final deal in place, but… around 10th of August, I think it was 11th of August when we started the POC, and we were already on Bitrise, uh, with a significant, uh, amount of our jobs."
|
||||
},
|
||||
{
|
||||
"time": "20:09:25",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Right. Right, so things will go faster, which means we would see less time per job overall, right?"
|
||||
},
|
||||
{
|
||||
"time": "20:09:27",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Well, yeah. Yes, yes."
|
||||
},
|
||||
{
|
||||
"time": "20:09:33",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Perfect."
|
||||
},
|
||||
{
|
||||
"time": "20:09:34",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "And let's see if we see more jobs overall. I mean, like I said, in October, there are already more jobs, but let's see about November, December, and so on."
|
||||
},
|
||||
{
|
||||
"time": "20:09:39",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Yep. Yeah."
|
||||
},
|
||||
{
|
||||
"time": "20:09:45",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Jeff, from Partnerships, has been on a 3-week vacation, but he's coming back tomorrow, or Thursday, and we might catch up with Bitrise. I'm… I'm on calls with Beatrice anyway, once a month, so I might reach out to them. Amen. Time we want, uh, to… to discuss that. Yeah, I think we should probably wait, still wait a bit. But yeah, it should be possible. Well, it is possible. He told me it's possible, of course."
|
||||
},
|
||||
{
|
||||
"time": "20:10:22",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Cool. Well, thank you. That's an interesting update."
|
||||
},
|
||||
{
|
||||
"time": "20:10:22",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "That's it. Thank you very much."
|
||||
},
|
||||
{
|
||||
"time": "20:10:26",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Diego, two items from you."
|
||||
},
|
||||
{
|
||||
"time": "20:10:31",
|
||||
"speaker": "DR",
|
||||
"text": "Really? I'm not prepared. Um, is that the demos from last week?"
|
||||
},
|
||||
{
|
||||
"time": "20:10:36",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "I think so, yeah, the passkeys issue and the Bitwarden extension."
|
||||
},
|
||||
{
|
||||
"time": "20:10:40",
|
||||
"speaker": "DR",
|
||||
"text": "Okay, I don't have a passkeys issue ready demo, but I'm going to explain what happened briefly and then just so everybody knows what's going on with that. So we had an issue with passkeys in macOS. Um… The browser stops asking for passkey authorization. You don't see the prompt anymore after a while. Uh, it wasn't clear what was going on. Um, apparently what happens is that, uh, Safari… doesn't suffer from this because they're allowed to make as many requests to the authentication service as they want for Passkey. So if they make. Two requests, the… The service is going to honor both requests and show the UI for both. But in the case of our browser, we can only make one request at a time. And WebKit isn't, um, handling that properly. They're not cleaning up, uh… They're not cleaning up the requests. When you do certain actions with the windows, like, for example, if you click on the button. In one window, and then open another window, and have another request, the second one is not gonna show. And at some point, these interactions were breaking passkeys completely to the point where they didn't work anymore for the user. So what we did? We implemented a workaround where we're, again, hooking into private APIs for WebKit to make. The APIs release the passkey requests correctly. And I have pending tasks that I haven't been able to get to yet to open, fix. a PR to fix the issue in WebKit initially, because there's an issue in WebKit where it's not canceling the request, right? And another issue where we're gonna be updating our communications with Apple, because previously, I think Dominic was talking with them about this at some point, and we didn't have a good, uh… minimum example of how… what the issue was to show them. So we're gonna provide something to them as well. Uh, this is also what triggered the idea, I don't know if you saw that apple that I reposed, to… uh, start encouraging more our interactions with the WebKit, uh, team, and proposing changes, and… You know, even submitting PRs, if that makes sense. Um… So yeah, that's it. And the second you saw on Friday, if you were there, which is that we have now Bitwarden extensions and 1Password extensions in the browser. which you can use. I think Dominic posted about it today, I think, or yesterday, I can't remember."
|
||||
},
|
||||
{
|
||||
"time": "20:13:35",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yesterday."
|
||||
},
|
||||
{
|
||||
"time": "20:13:35",
|
||||
"speaker": "DR",
|
||||
"text": "Um, yeah. And if you want to give it a go, it would be great. You need to be an internal user. Let me see if I have it installed here. Doc. Mm-hmm. It's here. All right. No, I don't have it installed. Sorry. I wasn't ready for the demos today. But yeah, that's it for me. Thanks, everybody."
|
||||
},
|
||||
{
|
||||
"time": "20:14:08",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "I wanted to ask. Because we, uh, run this entire thing about passkeys on macOS, but… We didn't check iOS at all, right? But I think… Does it work the same on iOS? I don't recall anymore. We probably also had that entitlement requested for iOS or not."
|
||||
},
|
||||
{
|
||||
"time": "20:14:30",
|
||||
"speaker": "DR",
|
||||
"text": "I don't know, honestly. That's a good question. I'm going to take note now."
|
||||
},
|
||||
{
|
||||
"time": "20:14:33",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "20:14:35",
|
||||
"speaker": "DR",
|
||||
"text": "To look into that. But it's possible we're going to be seeing the same issue. I don't know, because the entitlement that we would need for that not to be an issue is… I don't think Apple is giving that away, and I don't think we have that on iOS, so it may be an issue there as well. Uh… But yeah, I mean, the request to make the WebKit submission to fix this. Would fix it for all. browsers. But it would be interesting to know if it's breaking in iOS. I agree."
|
||||
},
|
||||
{
|
||||
"time": "20:15:09",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, of course. Now that I think of it, I… I'm not looking at iOS feedback that much, but probably we don't have? feedback about passkeys not working in the iOS app?"
|
||||
},
|
||||
{
|
||||
"time": "20:15:24",
|
||||
"speaker": "DR",
|
||||
"text": "I did look at some point and I didn't find much from iOS, but then I didn't follow up to check if it was causing trouble."
|
||||
},
|
||||
{
|
||||
"time": "20:15:26",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "There's only one recorder."
|
||||
},
|
||||
{
|
||||
"time": "20:15:33",
|
||||
"speaker": "DR",
|
||||
"text": "Which is the interesting bit."
|
||||
},
|
||||
{
|
||||
"time": "20:15:35",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Mm-hmm. Cool, thanks. One last thing about extensions is that, and this hasn't been announced anywhere, but we also support Dark Reader. If any one of you fancies Dark Reader, you can install it from Chrome Web Store. Just go to Chrome Web Store, search for Dark Reader and install it and it works. It works much better than whatever we had for Dark Reader, uh, integrated behind the scenes, and that thing is going away at some point. But yeah. We also support iCloud Passwords, which is a terrible extension, but it's the only way to connect a browser that's not Safari. with passwords up. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "20:16:23",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Awesome, thank you. And thank you, Diego, for rolling with that. If you have tasks or anything that are related to those that you could pop into the agenda at some point, that would help people find some more of this history, too. That'd be great. Uh, if not, that's fine. Very handy, that'd be…"
|
||||
},
|
||||
{
|
||||
"time": "20:16:36",
|
||||
"speaker": "DR",
|
||||
"text": "Yeah, I'm gonna… no, I'm gonna look them up now, yeah, and then I'll…"
|
||||
},
|
||||
{
|
||||
"time": "20:16:40",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Cool. Thank you. Feel free to drop them in the agenda. That'd be fine. And then the last thing on the agenda, Alex, is a postmortem from you."
|
||||
},
|
||||
{
|
||||
"time": "20:16:50",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, hey, it's the postmortem for VS Code support. So actually the migration to support VS Code and Carstore initially. I'll… So, the… Originally, the project started more than a year ago as a Huggies project. It grew out of… general AUR optimization and refactoring work related to storyboards, removal, modularization, and other. And, uh… Uh, my half-day's effort was to try to integrate it to Cursor in that time, and, uh, it's shown that the approach is actually working. Uh, we could… potentially in, uh, use CorpStore and, uh, integrate with it, having, uh, syntax, uh, highlighting, uh, documentation, and, uh, jump to symbol, builds, and so on, and debugging. Ah, so it's, uh… the project was, uh… formed from the steps remaining to make it work. But first of all, it included all the. AUR work that was already started, like storyboards removal, uh, some of, uh, flags organization and other stuff, and, uh… It had no kickoff as it was kind of running in my background between top priorities, and that's why it took so long to finish. Uh… and uh… Yeah, it had. It had some some issues visibility issues, I'd say so. First of all, did it achieve its success criteria and its purpose? So I think strong. Yes, so. in most of the work. or preparation was finished. Some of it is… It's moved out of the project back to the AUR, but the amount of work needed to make it work was done, and it would have been done in scope of the AUR as the tech debt pending probably someday. Uh, but yeah, this project gave it kind of, um, shape and served as an umbrella for those, uh. I think it's… Vs code. Cursor was completed, at least on my end. It's available in my public repo. If anybody is interested and requires a small github githook to integrate into project. and uses mostly native means, and fully compatible with Xcode, and does not replace or harm Xcode experience. So what went well and I could highlight? Yeah, each of the project steps were shipped as a small and separate refactors. Each one was an improvement on its own. There were several tech designs. First of all, the first tech design of. Modernization and Cursor support was originally discussed and approved when we mostly adopted Cursor, and it seemed like a good target. Uh, and it had a follow-up this year, recently, that was, uh, that was canceled. And… Basically, it was the same tech design, but it was really discussed after… after some… changes and when we build closer to completion. And with EXPO27 release, the integration was much simpler than the original plan, and did not require most controversial parts of the project. So this was discussed with the team, and. Yeah, the decision was made to not to move forward with it, but have a small… Small fixes or small adaptation that allow it to complete. Yeah, so the setup is usable. I use it instead of Xcode, except for release deals or Ui tests. And, uh… Yeah, basically it's moving, it's moving. seemingly moving forward to make… and Apple is moving forward to make, uh, it's more open and more viable with other dev tools, if anybody wants to experiment with it. Uh, and the work, I think, I could also show, highlight that the work is not completed here. Uh, we still have a lot of tech debt to solve, a lot of, uh, modelization efforts to be done there."
|
||||
},
|
||||
{
|
||||
"time": "20:21:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And it continues, basically. What didn't go well? Uh, there was, uh, an incident on macOS 12, uh, because it's generally not tested in our, uh, in our setup, as we already discussed in the incident post-mortem last time. Uh, while we still support, officially support, the SmuckOS version, we are not testing it effectively. And, uh, this, uh, gave me some thoughts of how could it be improved, probably. So, first of all, I… experiment… I experiment locally with, uh, testing… testing harness and agent harness, supporting macOS 12 as well. And, uh… later on, I'll try to… Push it forward to… Okay. Uh, to be able to actually test it. So, first of all, I've made an effort to, uh… to split. with actual UI test builds from macOS runners to one macOS builder, unified between different versions, so runners won't have. I have to build it every time, and this is improvement on its own. It improves build times, basically. And another is testing hardness to support Mac OS 12. So it's not… it's not open as a pull request to review yet, but it's working. Uh, so it's proof that it can work, and we can… could move forward with it, and probably rent some, uh, older machines somewhere in the cloud, and uh… have it tested. The second suggestion here would be to, uh, improve our processes, so I didn't, uh, complete the proposal yet, with all this, uh, performance review stuff, the priority. Uh, but yeah, I was planning to, uh… at a proposal. to require writing UI tests for any modified or added user-facing features and extend coverage overall as it does not require so much effort. We only need some Agentic work to analyze. coverage to suggest some tests and basically push it one by one. Um… Another issue was a tab bar disappearing. It was spotted during the internal testing. Basically, general work. And again, UI testing would support it. Yeah. Next thing is, uh, related to the visibility. Uh, so basically, demand for the VS Code integration and commercial integration was checked too late, as the project was, uh, done as in my background. So in its purpose, its aim was mostly my personal and included most tension, while most of the project was not related to actual VS Code migration, but served as an. Umbrella project to… Granted. Uh, this was, uh… This was only touched on the last stage, and uh… Probably we… While the project was progressing in the days before, we could have discussed it during some of Apple Weekly. But maybe not since. the actual implementation and the actual step that required this discussion was raised just in time, when Xcode 27 was available, and this step was about to be made. So. yeah, there were some issues with visibility, but it's mostly related to my… to me doing this project as my… not as my top priority, but it's generally your work when I have time for it. Okay. Yeah, and another outcome from it is the project goal was from the round one IDE support, as I already told, basically to migrate to VS Code and eat. might separate some tension and questions. Whether do we need to migrate to Vs code while again, 85% of the project was not related to actual Vs code migration and was general refactoring and improvements. It's, yeah, mostly related to the issue number two. of… Basically, basically, that's it, everything we discussed, and uh… I'll…"
|
||||
},
|
||||
{
|
||||
"time": "20:26:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "push forward with the Ui testing suggest proposal, and. older version testing, which is a requirement, especially with the more and more usage of Agentic workflows, where we have, like, 95 to 98% of. perfect, there are 8-time code, but there is still this 2% that is not perfect, and it tends to fail in the most critical scenarios. And it becomes a requirement, so… it's not the implementation, uh, that needs to be tested more, but the test… actual testing. And, uh, we need to… Obviously, we need to raise our quality assurance. Versuses. Let's see. Yeah, and the remaining factors will be handles. I have them tracked in the AOR. Not much of priority again, but they are on my plate. That's it. Any comments, any questions?"
|
||||
},
|
||||
{
|
||||
"time": "20:28:14",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Cool. Thank you, Alex. For the other refactors and stuff that are going to happen as part of the AOR. I think we just need to make sure that the value of those are clear in their own steps, right? Rather than, like you said, rather than focusing them on a VS Code support item, we'll just talk about each of those and what they bring to the team in their own right."
|
||||
},
|
||||
{
|
||||
"time": "20:28:35",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, so they were originally part included in this project, but we should separate cleanup targets. So each of the dependencies is not used by multiple targets, but has its own framework, setting up testing harness."
|
||||
},
|
||||
{
|
||||
"time": "20:28:40",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Yep. Yeah. Yeah, and a lot of that is in line with the modularization desires that we've had anyway, so."
|
||||
},
|
||||
{
|
||||
"time": "20:28:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "supporting UI person. Yep, yep."
|
||||
},
|
||||
{
|
||||
"time": "20:28:58",
|
||||
"speaker": "Jonathan Jackson",
|
||||
"text": "Excellent. Cool. Thank you. Appreciate it. Anything else from anyone before we wrap our meeting for the day? Remember that today is the first of three days for career advisors to be writing, uh, assessments for their advisees, so… We will all probably be heads down on that. I guess if you have questions, career advisors, if you have any questions that I can help with, go ahead and let me know. Feel free to reach out. Thanks, everyone. Good to see you all."
|
||||
}
|
||||
]
|
||||
}
|
||||
+46
@@ -15,3 +15,49 @@ source: "https://us01mynotes.zoom.us/-I3aVYDWTkKZ_VTRLdjGnA"
|
||||
- **20:02:36 · Jorge Leandro Perez:** So, Tokyo 2027? Yes!
|
||||
- **20:02:45 · Pikor:** And then we need that cool t-shirt, because someone created a Hug Days project with designs of t-shirts from the past, and the backend meetup had really one nice one with the. Japanese, um… I guess it said Dactago didn't check it, but if we would have that nice t-shirt of… Our meetup, that would be cool.
|
||||
- **20:03:30 · Dominik Kapusta:** The meeting is at the wrong time in Europe this week, so some people may be missing because of that.
|
||||
- **20:03:38 · Jonathan Jackson:** I totally lost track of which one's which, that's fine, I was just pulling up rotations so we can get started anyway. Hello, everyone. Nice to see you all. Quick run through our rotations as usual. Bartek is on iOS drives this week, followed by Brindy and then Hassan. Echoist triages Jorge this week, followed by Rachel, and then Alessandro. For release duties, iOS this week, Bartosz, followed by Mihao, and then Pete. And macOS is Tom this week, followed by Juan, and then Joseph. Any issues, go ahead and flag those in Asana as usual, please. Sam, you have an announcement to share with us. I think you're, yes.
|
||||
- **20:04:27 · SS:** Right, this is the AOR change. Sorry, I don't have the agenda pulled up. Uh, yes, uh…
|
||||
- **20:04:29 · Jonathan Jackson:** Thank you. Yes, sorry.
|
||||
- **20:04:34 · SS:** Is George here? Yes, he is. George has taken over secondary of the VPN AOR from me after running some projects to get us better observability into the VPN, so… Thank you. Nice work. Yes, also that.
|
||||
- **20:04:48 · Jonathan Jackson:** Excellent. Thank you and congratulations.
|
||||
- **20:04:50 · SS:** So also also. Also, what Jacek said in the chat is accurate.
|
||||
- **20:04:58 · Jonathan Jackson:** Yeah, I mean, I guess this is as good a time as any way to remind people that AOR, DRI ships are not written in stone. They are changeable. If you want one and don't have one, want a particular one, want to get out of one. We can talk about it. You don't even have to talk to me. You can make a proposal. They are changeable. Thank you. Dominic, CI usage update from you.
|
||||
- **20:05:25 · Dominik Kapusta:** Uh, yes. Um… It's pretty early in the agenda here. But okay, anyway. I have this… Artifact. Here, that I can share with you. Or not. Doesn't work. One second, I'm sorry. Um… Oh, yes. So anyway, I was looking at… I was looking at, um… And CI time. In the recent months and just to… just to have a look, just to get a feeling of how… Bitrise works or doesn't work. Here's the link, but let me also share it with you. Show my screen, I guess. I'm, uh, I mean, uh, so, uh… I have this… job hours and runs per month since February. Uh, it was going up and down, and at some point, uh, job runs… Pretty steady at… 5,500 a month, whereas job hours are going down. Quite drastically, actually, because it's at 1700 for September. And it has never been below 2000 earlier this year. Not sure about January, but anyway. Yeah, which is interesting. And also… Average… Job duration. It goes… it went down to 18.9 minutes from over 30. This is only for the PR checks, so VSK, DBP, iOS, and macOS PR checks only. in the monorepo, uh, which… Looks like… Uh, confirming that Bitrise is doing the job. Uh, but my initial… uh, motivation to… to run this was to see if we should consider getting more machines from Bitrise, because maybe we're running more jobs. Which was my assumption. Because… Code is cheap these days, relatively cheap. cheaper than it used to be, and uh… because of that, we might be opening more pull requests, running more workflows, and so on and so on, so maybe we need more machines, because we would have paid more for GitHub anyway. not sure if it's the case yet. October is not here, even though it's 27th, and I did yesterday, but in October, we enabled… Required checks. in the repository, which means all the checks run on all pull requests now, so naturally there's higher volume of checks, and it wasn't fitting this graph nicely. So I guess we'll have a new baseline in October, and then. We'll be comparing against that in the following months. That's what I have. Tommy has any thoughts?
|
||||
- **20:08:50 · Jonathan Jackson:** When did we actually fully switch to Bitrise?
|
||||
- **20:08:53 · Dominik Kapusta:** Um… September 14th?
|
||||
- **20:08:59 · Jonathan Jackson:** So that would, because they're faster, that would drive down our run times while jobs remain steady potentially, which it looked like that actually showed in the data you were just showing, right?
|
||||
- **20:08:59 · Dominik Kapusta:** Yes. So, one correction. September 14th was when we got the final deal in place, but… around 10th of August, I think it was 11th of August when we started the POC, and we were already on Bitrise, uh, with a significant, uh, amount of our jobs.
|
||||
- **20:09:25 · Jonathan Jackson:** Right. Right, so things will go faster, which means we would see less time per job overall, right?
|
||||
- **20:09:27 · Dominik Kapusta:** Well, yeah. Yes, yes.
|
||||
- **20:09:33 · Jonathan Jackson:** Perfect.
|
||||
- **20:09:34 · Dominik Kapusta:** And let's see if we see more jobs overall. I mean, like I said, in October, there are already more jobs, but let's see about November, December, and so on.
|
||||
- **20:09:39 · Jonathan Jackson:** Yep. Yeah.
|
||||
- **20:09:45 · Dominik Kapusta:** Jeff, from Partnerships, has been on a 3-week vacation, but he's coming back tomorrow, or Thursday, and we might catch up with Bitrise. I'm… I'm on calls with Beatrice anyway, once a month, so I might reach out to them. Amen. Time we want, uh, to… to discuss that. Yeah, I think we should probably wait, still wait a bit. But yeah, it should be possible. Well, it is possible. He told me it's possible, of course.
|
||||
- **20:10:22 · Jonathan Jackson:** Cool. Well, thank you. That's an interesting update.
|
||||
- **20:10:22 · Dominik Kapusta:** That's it. Thank you very much.
|
||||
- **20:10:26 · Jonathan Jackson:** Diego, two items from you.
|
||||
- **20:10:31 · DR:** Really? I'm not prepared. Um, is that the demos from last week?
|
||||
- **20:10:36 · Jonathan Jackson:** I think so, yeah, the passkeys issue and the Bitwarden extension.
|
||||
- **20:10:40 · DR:** Okay, I don't have a passkeys issue ready demo, but I'm going to explain what happened briefly and then just so everybody knows what's going on with that. So we had an issue with passkeys in macOS. Um… The browser stops asking for passkey authorization. You don't see the prompt anymore after a while. Uh, it wasn't clear what was going on. Um, apparently what happens is that, uh, Safari… doesn't suffer from this because they're allowed to make as many requests to the authentication service as they want for Passkey. So if they make. Two requests, the… The service is going to honor both requests and show the UI for both. But in the case of our browser, we can only make one request at a time. And WebKit isn't, um, handling that properly. They're not cleaning up, uh… They're not cleaning up the requests. When you do certain actions with the windows, like, for example, if you click on the button. In one window, and then open another window, and have another request, the second one is not gonna show. And at some point, these interactions were breaking passkeys completely to the point where they didn't work anymore for the user. So what we did? We implemented a workaround where we're, again, hooking into private APIs for WebKit to make. The APIs release the passkey requests correctly. And I have pending tasks that I haven't been able to get to yet to open, fix. a PR to fix the issue in WebKit initially, because there's an issue in WebKit where it's not canceling the request, right? And another issue where we're gonna be updating our communications with Apple, because previously, I think Dominic was talking with them about this at some point, and we didn't have a good, uh… minimum example of how… what the issue was to show them. So we're gonna provide something to them as well. Uh, this is also what triggered the idea, I don't know if you saw that apple that I reposed, to… uh, start encouraging more our interactions with the WebKit, uh, team, and proposing changes, and… You know, even submitting PRs, if that makes sense. Um… So yeah, that's it. And the second you saw on Friday, if you were there, which is that we have now Bitwarden extensions and 1Password extensions in the browser. which you can use. I think Dominic posted about it today, I think, or yesterday, I can't remember.
|
||||
- **20:13:35 · Dominik Kapusta:** Yesterday.
|
||||
- **20:13:35 · DR:** Um, yeah. And if you want to give it a go, it would be great. You need to be an internal user. Let me see if I have it installed here. Doc. Mm-hmm. It's here. All right. No, I don't have it installed. Sorry. I wasn't ready for the demos today. But yeah, that's it for me. Thanks, everybody.
|
||||
- **20:14:08 · Dominik Kapusta:** I wanted to ask. Because we, uh, run this entire thing about passkeys on macOS, but… We didn't check iOS at all, right? But I think… Does it work the same on iOS? I don't recall anymore. We probably also had that entitlement requested for iOS or not.
|
||||
- **20:14:30 · DR:** I don't know, honestly. That's a good question. I'm going to take note now.
|
||||
- **20:14:33 · Dominik Kapusta:** Okay.
|
||||
- **20:14:35 · DR:** To look into that. But it's possible we're going to be seeing the same issue. I don't know, because the entitlement that we would need for that not to be an issue is… I don't think Apple is giving that away, and I don't think we have that on iOS, so it may be an issue there as well. Uh… But yeah, I mean, the request to make the WebKit submission to fix this. Would fix it for all. browsers. But it would be interesting to know if it's breaking in iOS. I agree.
|
||||
- **20:15:09 · Dominik Kapusta:** Yeah, of course. Now that I think of it, I… I'm not looking at iOS feedback that much, but probably we don't have? feedback about passkeys not working in the iOS app?
|
||||
- **20:15:24 · DR:** I did look at some point and I didn't find much from iOS, but then I didn't follow up to check if it was causing trouble.
|
||||
- **20:15:26 · Dominik Kapusta:** There's only one recorder.
|
||||
- **20:15:33 · DR:** Which is the interesting bit.
|
||||
- **20:15:35 · Dominik Kapusta:** Mm-hmm. Cool, thanks. One last thing about extensions is that, and this hasn't been announced anywhere, but we also support Dark Reader. If any one of you fancies Dark Reader, you can install it from Chrome Web Store. Just go to Chrome Web Store, search for Dark Reader and install it and it works. It works much better than whatever we had for Dark Reader, uh, integrated behind the scenes, and that thing is going away at some point. But yeah. We also support iCloud Passwords, which is a terrible extension, but it's the only way to connect a browser that's not Safari. with passwords up. Thank you.
|
||||
- **20:16:23 · Jonathan Jackson:** Awesome, thank you. And thank you, Diego, for rolling with that. If you have tasks or anything that are related to those that you could pop into the agenda at some point, that would help people find some more of this history, too. That'd be great. Uh, if not, that's fine. Very handy, that'd be…
|
||||
- **20:16:36 · DR:** Yeah, I'm gonna… no, I'm gonna look them up now, yeah, and then I'll…
|
||||
- **20:16:40 · Jonathan Jackson:** Cool. Thank you. Feel free to drop them in the agenda. That'd be fine. And then the last thing on the agenda, Alex, is a postmortem from you.
|
||||
- **20:16:50 · Alex Martemyanov:** Yeah, hey, it's the postmortem for VS Code support. So actually the migration to support VS Code and Carstore initially. I'll… So, the… Originally, the project started more than a year ago as a Huggies project. It grew out of… general AUR optimization and refactoring work related to storyboards, removal, modularization, and other. And, uh… Uh, my half-day's effort was to try to integrate it to Cursor in that time, and, uh, it's shown that the approach is actually working. Uh, we could… potentially in, uh, use CorpStore and, uh, integrate with it, having, uh, syntax, uh, highlighting, uh, documentation, and, uh, jump to symbol, builds, and so on, and debugging. Ah, so it's, uh… the project was, uh… formed from the steps remaining to make it work. But first of all, it included all the. AUR work that was already started, like storyboards removal, uh, some of, uh, flags organization and other stuff, and, uh… It had no kickoff as it was kind of running in my background between top priorities, and that's why it took so long to finish. Uh… and uh… Yeah, it had. It had some some issues visibility issues, I'd say so. First of all, did it achieve its success criteria and its purpose? So I think strong. Yes, so. in most of the work. or preparation was finished. Some of it is… It's moved out of the project back to the AUR, but the amount of work needed to make it work was done, and it would have been done in scope of the AUR as the tech debt pending probably someday. Uh, but yeah, this project gave it kind of, um, shape and served as an umbrella for those, uh. I think it's… Vs code. Cursor was completed, at least on my end. It's available in my public repo. If anybody is interested and requires a small github githook to integrate into project. and uses mostly native means, and fully compatible with Xcode, and does not replace or harm Xcode experience. So what went well and I could highlight? Yeah, each of the project steps were shipped as a small and separate refactors. Each one was an improvement on its own. There were several tech designs. First of all, the first tech design of. Modernization and Cursor support was originally discussed and approved when we mostly adopted Cursor, and it seemed like a good target. Uh, and it had a follow-up this year, recently, that was, uh, that was canceled. And… Basically, it was the same tech design, but it was really discussed after… after some… changes and when we build closer to completion. And with EXPO27 release, the integration was much simpler than the original plan, and did not require most controversial parts of the project. So this was discussed with the team, and. Yeah, the decision was made to not to move forward with it, but have a small… Small fixes or small adaptation that allow it to complete. Yeah, so the setup is usable. I use it instead of Xcode, except for release deals or Ui tests. And, uh… Yeah, basically it's moving, it's moving. seemingly moving forward to make… and Apple is moving forward to make, uh, it's more open and more viable with other dev tools, if anybody wants to experiment with it. Uh, and the work, I think, I could also show, highlight that the work is not completed here. Uh, we still have a lot of tech debt to solve, a lot of, uh, modelization efforts to be done there.
|
||||
- **20:21:58 · Alex Martemyanov:** And it continues, basically. What didn't go well? Uh, there was, uh, an incident on macOS 12, uh, because it's generally not tested in our, uh, in our setup, as we already discussed in the incident post-mortem last time. Uh, while we still support, officially support, the SmuckOS version, we are not testing it effectively. And, uh, this, uh, gave me some thoughts of how could it be improved, probably. So, first of all, I… experiment… I experiment locally with, uh, testing… testing harness and agent harness, supporting macOS 12 as well. And, uh… later on, I'll try to… Push it forward to… Okay. Uh, to be able to actually test it. So, first of all, I've made an effort to, uh… to split. with actual UI test builds from macOS runners to one macOS builder, unified between different versions, so runners won't have. I have to build it every time, and this is improvement on its own. It improves build times, basically. And another is testing hardness to support Mac OS 12. So it's not… it's not open as a pull request to review yet, but it's working. Uh, so it's proof that it can work, and we can… could move forward with it, and probably rent some, uh, older machines somewhere in the cloud, and uh… have it tested. The second suggestion here would be to, uh, improve our processes, so I didn't, uh, complete the proposal yet, with all this, uh, performance review stuff, the priority. Uh, but yeah, I was planning to, uh… at a proposal. to require writing UI tests for any modified or added user-facing features and extend coverage overall as it does not require so much effort. We only need some Agentic work to analyze. coverage to suggest some tests and basically push it one by one. Um… Another issue was a tab bar disappearing. It was spotted during the internal testing. Basically, general work. And again, UI testing would support it. Yeah. Next thing is, uh, related to the visibility. Uh, so basically, demand for the VS Code integration and commercial integration was checked too late, as the project was, uh, done as in my background. So in its purpose, its aim was mostly my personal and included most tension, while most of the project was not related to actual VS Code migration, but served as an. Umbrella project to… Granted. Uh, this was, uh… This was only touched on the last stage, and uh… Probably we… While the project was progressing in the days before, we could have discussed it during some of Apple Weekly. But maybe not since. the actual implementation and the actual step that required this discussion was raised just in time, when Xcode 27 was available, and this step was about to be made. So. yeah, there were some issues with visibility, but it's mostly related to my… to me doing this project as my… not as my top priority, but it's generally your work when I have time for it. Okay. Yeah, and another outcome from it is the project goal was from the round one IDE support, as I already told, basically to migrate to VS Code and eat. might separate some tension and questions. Whether do we need to migrate to Vs code while again, 85% of the project was not related to actual Vs code migration and was general refactoring and improvements. It's, yeah, mostly related to the issue number two. of… Basically, basically, that's it, everything we discussed, and uh… I'll…
|
||||
- **20:26:58 · Alex Martemyanov:** push forward with the Ui testing suggest proposal, and. older version testing, which is a requirement, especially with the more and more usage of Agentic workflows, where we have, like, 95 to 98% of. perfect, there are 8-time code, but there is still this 2% that is not perfect, and it tends to fail in the most critical scenarios. And it becomes a requirement, so… it's not the implementation, uh, that needs to be tested more, but the test… actual testing. And, uh, we need to… Obviously, we need to raise our quality assurance. Versuses. Let's see. Yeah, and the remaining factors will be handles. I have them tracked in the AOR. Not much of priority again, but they are on my plate. That's it. Any comments, any questions?
|
||||
- **20:28:14 · Jonathan Jackson:** Cool. Thank you, Alex. For the other refactors and stuff that are going to happen as part of the AOR. I think we just need to make sure that the value of those are clear in their own steps, right? Rather than, like you said, rather than focusing them on a VS Code support item, we'll just talk about each of those and what they bring to the team in their own right.
|
||||
- **20:28:35 · Alex Martemyanov:** Yes, so they were originally part included in this project, but we should separate cleanup targets. So each of the dependencies is not used by multiple targets, but has its own framework, setting up testing harness.
|
||||
- **20:28:40 · Jonathan Jackson:** Yep. Yeah. Yeah, and a lot of that is in line with the modularization desires that we've had anyway, so.
|
||||
- **20:28:53 · Alex Martemyanov:** supporting UI person. Yep, yep.
|
||||
- **20:28:58 · Jonathan Jackson:** Excellent. Cool. Thank you. Appreciate it. Anything else from anyone before we wrap our meeting for the day? Remember that today is the first of three days for career advisors to be writing, uh, assessments for their advisees, so… We will all probably be heads down on that. I guess if you have questions, career advisors, if you have any questions that I can help with, go ahead and let me know. Feel free to reach out. Thanks, everyone. Good to see you all.
|
||||
-280
@@ -23,286 +23,6 @@
|
||||
"time": "15:28:24",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Оф, Ол, Юзерс, Райт?"
|
||||
},
|
||||
{
|
||||
"time": "15:28:26",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, yes, from daily users. So it's still higher than the 1% threshold. And, uh… We've got two fixes more to be released next week. The RR6 reload. which can. Probably cover up to 30% of every 6 total reports. Uh, because it's not… It's not proof that… So usually LR6, when it's happening, it should be recovered normally by the kit. And we are handling some kind of case when it's not recovering. And, uh… The other one is, uh, braid, which may… affect… Yes. The upgrade failures, some hacks caused by it. So speculating on it another like 20 or 30%."
|
||||
},
|
||||
{
|
||||
"time": "15:29:25",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, those two errors are… On my like, in this week's internal. Yeah. So they will be public next week."
|
||||
},
|
||||
{
|
||||
"time": "15:29:33",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, and those are not the main part of the failures we are getting. So they are expected to have some effect."
|
||||
},
|
||||
{
|
||||
"time": "15:29:45",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But not that big, yeah."
|
||||
},
|
||||
{
|
||||
"time": "15:29:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "But it won't cross the one-person gap still, I think. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "15:29:55",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I think, like, probably the main reason is that we have exhausted the options, as you mentioned, like that, like the… The the the idle like thing was not we are not able to reproduce that one. So basically, probably, like…"
|
||||
},
|
||||
{
|
||||
"time": "15:30:10",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, so…"
|
||||
},
|
||||
{
|
||||
"time": "15:30:12",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah. Okay. My gut feeling would be to just, like, probably provide a summary of the current state of the, like."
|
||||
},
|
||||
{
|
||||
"time": "15:30:19",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "the reporting have maybe some kind of, like, a dashboard and and probably, like, revisit it next week when we have the numbers for the the last part of the fixes."
|
||||
},
|
||||
{
|
||||
"time": "15:30:26",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "15:30:32",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But probably I wouldn't hold the project any longer, like, for the next week."
|
||||
},
|
||||
{
|
||||
"time": "15:30:39",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um… So my suggestion, my thinking of the project for this week. So, first of all, we have this… A lot of feature flags introduced, and the pixels, metrics, and so on, and all of them are basically marked as temporary, and some of them are not, uh… Not even being reported. So there is some cleanup, I guess, to be done. For example, this graveyard fix, we are catching some… percent, lower than one percent, probably, of all the reported events that can match it, but I would not activate it, looking at it, looking at the numbers, so it's… Certainly not the main issue. And there is another one. Um, yeah, anyways, uh, so I was thinking to clean it up. To see… to check the… Safe fixes and remove the picture flags for them. To leave the more controversial, dangerous things behind the feature flags. that we are living. And, uh… Maybe should we remove the recorder thing and episode diagnostics? Maybe not this week, but the week after. Because we are generally… We've collected all the data that it could provide, I guess. And the main portion of it that remains, the neat quake. I think it's generally not covered by it in any sense. And that's…"
|
||||
},
|
||||
{
|
||||
"time": "15:32:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah…"
|
||||
},
|
||||
{
|
||||
"time": "15:32:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Certainly the main cause."
|
||||
},
|
||||
{
|
||||
"time": "15:32:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And… And apart from the episodes, the diagnostics, we… We have other pixels to measure the hangs, right? Or they are, like…"
|
||||
},
|
||||
{
|
||||
"time": "15:32:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Currently, there is only this episode thing. We have, uh, the pixels for reports, for user reports, that is separating. And yeah, currently this episode metric only includes like background events, the state of things and. initiating, basically, event."
|
||||
},
|
||||
{
|
||||
"time": "15:33:17",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So we would also, like, lose the visibility into the the the, like, the permanent hangs. Right?"
|
||||
},
|
||||
{
|
||||
"time": "15:33:25",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I'm sorry."
|
||||
},
|
||||
{
|
||||
"time": "15:33:25",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Like, the absolute…"
|
||||
},
|
||||
{
|
||||
"time": "15:33:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Actually, I was thinking, maybe not finished planning yet, but I was thinking about redoing the whole reporting thing. Centering it in the gray zone, like, uncovered. Places. So, we have… We have a sequence, like, the content script being injected. sending INIT, WebKit receiving the INIT. In the ground, receiving and handling the event. The config fetching. And… And the website fetching, that may also indicate some kind of… So there is a… Uh, corner case, when the config cannot be fetched. For whatever reason, if it hangs, it would give this kind of symptoms. But… Normally it should not hang. So I would… I'm hesitating to fix it. Um, before we have any data on this. And… Generally, they should not cause permanent headaches. We're done, right? But yeah, currently we are not, uh, tied to the… Extension lifecycle, but we are tied to the page loading lifecycle. And, uh… Also, we don't… we don't have a baseline for the navigations, so we can't tell of which percent of navigation actually have the extension radar, but we are… Diminishing it instead against, like, daily users or installs metrics. So, uh… Still maybe has not. the correct numbers. We don't understand, like, the… the whole picture of it, like how many navigations do actually succeed. And, uh, where exactly… You've got this, uh… Meaning, like, failure, for example. Maybe it is the init, maybe it's somewhere in the WebKit internals, or maybe it's on our side, like waiting for the config fetch or whatever. And that would include the extension modification itself already, the measurement points. And probably some… Thank you. Not episodes, but a summary of, uh… The hung state, so whenever we catch it, when any chain of this, any part of the chain fails, we could report where it has failed."
|
||||
},
|
||||
{
|
||||
"time": "15:36:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Thanks."
|
||||
},
|
||||
{
|
||||
"time": "15:36:23",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So I'm thinking, well, maybe we should just, uh… Check this week to implement this metrics. redoing… And uh… then put it on hold, basically, before we receive. I mean, data related."
|
||||
},
|
||||
{
|
||||
"time": "15:36:41",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So you suggest, like, doing it for roughly a week, probably, more? Do the cleanup."
|
||||
},
|
||||
{
|
||||
"time": "15:36:46",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, so…"
|
||||
},
|
||||
{
|
||||
"time": "15:36:48",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do the cleanup and implement those, like, long term metrics to have some kind of observability in this gray zone."
|
||||
},
|
||||
{
|
||||
"time": "15:36:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah. So, first of all, it should have… some permanent part, I guess, just so we keep it for… For catching the spikes or future breaks. And have some temporary metrics as well, but measuring the inside of the extension. because currently we have the okay. Everything seems fine. Background is loaded in less than 1 s. And then nothing. So and we don't have any idea and anything suspect that can be suspected for causing it."
|
||||
},
|
||||
{
|
||||
"time": "15:37:25",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah. Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "15:37:36",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So yeah, no hypothesis on that. What is actually breaking there? Except for a couple of issues inside the GS, but they are also… Kind of. Hmm. Do not seem so severe and causing this problems. So, that would be my point for today. Otherwise, I have no ideas for you."
|
||||
},
|
||||
{
|
||||
"time": "15:38:04",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, so… Yeah, so I think, like, the point that Russell is having is probably he wants to, like… have a clear understanding where the project will end, yeah, because we can, like, just probably, like, move it, move it, like, chase the, chase the, the, the, the finish line, like, forever."
|
||||
},
|
||||
{
|
||||
"time": "15:38:20",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "15:38:27",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "That's going away."
|
||||
},
|
||||
{
|
||||
"time": "15:38:29",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Well… I would highlight that we certainly have some improvement. We've found some actual bugs. Some of them are not even the case because they are really corner cases, but those are a real issue reproduced."
|
||||
},
|
||||
{
|
||||
"time": "15:38:44",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I understand, yeah, yeah, so probably no one is questioning that, yeah, but just, like, to have, like, a more… like, condensed or, like, focused, uh, wrap-up for the project, yeah, so I would suggest, like, yeah, I like the plan, and I think it makes sense, yeah, so I would… I would bring the… Uh, yeah, so I think… Two things need to be done, like, one is to do a project update and, like, recap the current data, and summarize, like, where we landed at. And probably, I would start with, uh… with the DRI task, and, like, respond to Russell, and, like… Present the plan that, like, we have those, like, we have those fixes, the updates, and link to the project update, that you have the, like. Two more fixes, like, that will come up in the next version, and you propose the plan to, uh. Uh, have the final week of the project to, like, clean up the, like, all… Unnecessary things and clean up the diagnostics that we set up in place for, like, nailing down the issues. And suggest like to to metrics to like keep track of like where we're at with the permanent hangs and maybe better visibility in what's happening."
|
||||
},
|
||||
{
|
||||
"time": "15:39:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Introduce some permanent. Yep."
|
||||
},
|
||||
{
|
||||
"time": "15:40:09",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and probably, like, we can see, like, what happens. Yeah, I… probably you want, like, if there's, like, a concrete plan that, like, this is the final week, and we just need to clean up the stuff, I don't think that there should be an issue. That's my feelings."
|
||||
},
|
||||
{
|
||||
"time": "15:40:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, yeah, I'll do it today, then, before the… before the meeting, hopefully."
|
||||
},
|
||||
{
|
||||
"time": "15:40:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and the meetings today are, like, the regular time, yeah."
|
||||
},
|
||||
{
|
||||
"time": "15:40:40",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I think it's one hour later shifted due to some times on things."
|
||||
},
|
||||
{
|
||||
"time": "15:40:46",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, but I think that…"
|
||||
},
|
||||
{
|
||||
"time": "15:40:46",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "All the meetings, actually."
|
||||
},
|
||||
{
|
||||
"time": "15:40:52",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Oh, didn't you have the time zone change for the winter time?"
|
||||
},
|
||||
{
|
||||
"time": "15:40:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "No, luckily I don't have time zone change, but unfortunately I do have the Easter."
|
||||
},
|
||||
{
|
||||
"time": "15:40:57",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "15:41:03",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And the western time zones changing and shifting my schedules up to the late night."
|
||||
},
|
||||
{
|
||||
"time": "15:41:08",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "the… Okay. Uh, yeah, so sounds good. Uh, like, I would ask you to, to, like, do the project update, and, like, provide the, the, the data analysis in some, some task, and, like, respond to us also."
|
||||
},
|
||||
{
|
||||
"time": "15:41:19",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "15:41:24",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So we have the clear understanding, and we can discuss it on the meeting if he has any."
|
||||
},
|
||||
{
|
||||
"time": "15:41:28",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, so…"
|
||||
},
|
||||
{
|
||||
"time": "15:41:29",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Further questions, but it sounds good to me."
|
||||
},
|
||||
{
|
||||
"time": "15:41:30",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Probably. Probably the cleanup is, uh… I think, to be done anyways, whether it comes into the project or just as a follow-up, but it would be necessary to do it anyways, and it's not…"
|
||||
},
|
||||
{
|
||||
"time": "15:41:40",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "15:41:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And it's not small, because there's multiple things in it, and it should be…"
|
||||
},
|
||||
{
|
||||
"time": "15:41:49",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah. Yeah, okay."
|
||||
},
|
||||
{
|
||||
"time": "15:41:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Some considerations whether things should be kept or cleaned up or enabled for everybody. So it seems like a natural part for a natural completion part of the project. But yeah, for the metrics. It also seems pretty natural to have some permanent metrics just in case we could detect if anything becomes worse. at some point. Okay, that would be it then. Thanks."
|
||||
},
|
||||
{
|
||||
"time": "15:42:32",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Cool. Yeah, that sounds good. Yeah, thank you for the chat."
|
||||
},
|
||||
{
|
||||
"time": "15:42:40",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, see you, see you later."
|
||||
}
|
||||
]
|
||||
}
|
||||
-56
@@ -15,59 +15,3 @@ source: "https://us01mynotes.zoom.us/qQ2bzU5KTiCGluiBYA-ROA"
|
||||
- **15:26:12 · Alex Martemyanov:** So yeah, I wanted to have a sync up on the project. And regarding the Russell's questioning. In the Advisor Sync thread. So whether do we do we wrap up or. Continuing something. Um… So, yeah, basically, at the current state, it seems, from my perspective, that we are. exhausted all the…
|
||||
- **15:26:44 · Alex Martemyanov:** hypothesis that we've got so far. And so there's been some fixes that are genuine and they are working. And, uh, according to the first day data I got today, there is a 30% drop of macOS over-reporting, so that was expected from the. Error page fix the data pollution. So. Currently, they are comparable with iOS and macOS. Uh, yes, locally, not yet in the… The data. So basically, I think we are matching iOS. Uh, roughly. And, uh… So the main numbers are… So for any failure, there is a drop in my voice from around thirty percent to around twenty percent. And, oh, sorry, from 20% to around 15%, so it's a 30% drop. And, uh, so otherwise it's pretty much steady. Uh, since there was no actual fixes, and uh… In permanent hang numbers, macOS had around. 2 to 3%. And now it's around steady. 1.9%.
|
||||
- **15:28:24 · Michal Smaga:** Оф, Ол, Юзерс, Райт?
|
||||
- **15:28:26 · Alex Martemyanov:** Uh, yes, from daily users. So it's still higher than the 1% threshold. And, uh… We've got two fixes more to be released next week. The RR6 reload. which can. Probably cover up to 30% of every 6 total reports. Uh, because it's not… It's not proof that… So usually LR6, when it's happening, it should be recovered normally by the kit. And we are handling some kind of case when it's not recovering. And, uh… The other one is, uh, braid, which may… affect… Yes. The upgrade failures, some hacks caused by it. So speculating on it another like 20 or 30%.
|
||||
- **15:29:25 · Michal Smaga:** So, those two errors are… On my like, in this week's internal. Yeah. So they will be public next week.
|
||||
- **15:29:33 · Alex Martemyanov:** Yes, and those are not the main part of the failures we are getting. So they are expected to have some effect.
|
||||
- **15:29:45 · Michal Smaga:** But not that big, yeah.
|
||||
- **15:29:47 · Alex Martemyanov:** But it won't cross the one-person gap still, I think. Thank you.
|
||||
- **15:29:55 · Michal Smaga:** Yeah, I think, like, probably the main reason is that we have exhausted the options, as you mentioned, like that, like the… The the the idle like thing was not we are not able to reproduce that one. So basically, probably, like…
|
||||
- **15:30:10 · Alex Martemyanov:** Yeah, so…
|
||||
- **15:30:12 · Michal Smaga:** Yeah. Okay. My gut feeling would be to just, like, probably provide a summary of the current state of the, like.
|
||||
- **15:30:19 · Michal Smaga:** the reporting have maybe some kind of, like, a dashboard and and probably, like, revisit it next week when we have the numbers for the the last part of the fixes.
|
||||
- **15:30:26 · Alex Martemyanov:** Okay.
|
||||
- **15:30:32 · Michal Smaga:** But probably I wouldn't hold the project any longer, like, for the next week.
|
||||
- **15:30:39 · Alex Martemyanov:** Um… So my suggestion, my thinking of the project for this week. So, first of all, we have this… A lot of feature flags introduced, and the pixels, metrics, and so on, and all of them are basically marked as temporary, and some of them are not, uh… Not even being reported. So there is some cleanup, I guess, to be done. For example, this graveyard fix, we are catching some… percent, lower than one percent, probably, of all the reported events that can match it, but I would not activate it, looking at it, looking at the numbers, so it's… Certainly not the main issue. And there is another one. Um, yeah, anyways, uh, so I was thinking to clean it up. To see… to check the… Safe fixes and remove the picture flags for them. To leave the more controversial, dangerous things behind the feature flags. that we are living. And, uh… Maybe should we remove the recorder thing and episode diagnostics? Maybe not this week, but the week after. Because we are generally… We've collected all the data that it could provide, I guess. And the main portion of it that remains, the neat quake. I think it's generally not covered by it in any sense. And that's…
|
||||
- **15:32:36 · Michal Smaga:** Yeah…
|
||||
- **15:32:37 · Alex Martemyanov:** Certainly the main cause.
|
||||
- **15:32:38 · Michal Smaga:** And… And apart from the episodes, the diagnostics, we… We have other pixels to measure the hangs, right? Or they are, like…
|
||||
- **15:32:55 · Alex Martemyanov:** Currently, there is only this episode thing. We have, uh, the pixels for reports, for user reports, that is separating. And yeah, currently this episode metric only includes like background events, the state of things and. initiating, basically, event.
|
||||
- **15:33:17 · Michal Smaga:** So we would also, like, lose the visibility into the the the, like, the permanent hangs. Right?
|
||||
- **15:33:25 · Alex Martemyanov:** I'm sorry.
|
||||
- **15:33:25 · Michal Smaga:** Like, the absolute…
|
||||
- **15:33:27 · Alex Martemyanov:** Actually, I was thinking, maybe not finished planning yet, but I was thinking about redoing the whole reporting thing. Centering it in the gray zone, like, uncovered. Places. So, we have… We have a sequence, like, the content script being injected. sending INIT, WebKit receiving the INIT. In the ground, receiving and handling the event. The config fetching. And… And the website fetching, that may also indicate some kind of… So there is a… Uh, corner case, when the config cannot be fetched. For whatever reason, if it hangs, it would give this kind of symptoms. But… Normally it should not hang. So I would… I'm hesitating to fix it. Um, before we have any data on this. And… Generally, they should not cause permanent headaches. We're done, right? But yeah, currently we are not, uh, tied to the… Extension lifecycle, but we are tied to the page loading lifecycle. And, uh… Also, we don't… we don't have a baseline for the navigations, so we can't tell of which percent of navigation actually have the extension radar, but we are… Diminishing it instead against, like, daily users or installs metrics. So, uh… Still maybe has not. the correct numbers. We don't understand, like, the… the whole picture of it, like how many navigations do actually succeed. And, uh, where exactly… You've got this, uh… Meaning, like, failure, for example. Maybe it is the init, maybe it's somewhere in the WebKit internals, or maybe it's on our side, like waiting for the config fetch or whatever. And that would include the extension modification itself already, the measurement points. And probably some… Thank you. Not episodes, but a summary of, uh… The hung state, so whenever we catch it, when any chain of this, any part of the chain fails, we could report where it has failed.
|
||||
- **15:36:18 · Michal Smaga:** Thanks.
|
||||
- **15:36:23 · Alex Martemyanov:** So I'm thinking, well, maybe we should just, uh… Check this week to implement this metrics. redoing… And uh… then put it on hold, basically, before we receive. I mean, data related.
|
||||
- **15:36:41 · Michal Smaga:** So you suggest, like, doing it for roughly a week, probably, more? Do the cleanup.
|
||||
- **15:36:46 · Alex Martemyanov:** Yeah, so…
|
||||
- **15:36:48 · Michal Smaga:** Do the cleanup and implement those, like, long term metrics to have some kind of observability in this gray zone.
|
||||
- **15:36:55 · Alex Martemyanov:** Yeah. So, first of all, it should have… some permanent part, I guess, just so we keep it for… For catching the spikes or future breaks. And have some temporary metrics as well, but measuring the inside of the extension. because currently we have the okay. Everything seems fine. Background is loaded in less than 1 s. And then nothing. So and we don't have any idea and anything suspect that can be suspected for causing it.
|
||||
- **15:37:25 · Michal Smaga:** Yeah. Mmhm.
|
||||
- **15:37:36 · Alex Martemyanov:** So yeah, no hypothesis on that. What is actually breaking there? Except for a couple of issues inside the GS, but they are also… Kind of. Hmm. Do not seem so severe and causing this problems. So, that would be my point for today. Otherwise, I have no ideas for you.
|
||||
- **15:38:04 · Michal Smaga:** Yeah, so… Yeah, so I think, like, the point that Russell is having is probably he wants to, like… have a clear understanding where the project will end, yeah, because we can, like, just probably, like, move it, move it, like, chase the, chase the, the, the, the finish line, like, forever.
|
||||
- **15:38:20 · Alex Martemyanov:** Okay.
|
||||
- **15:38:27 · Michal Smaga:** That's going away.
|
||||
- **15:38:29 · Alex Martemyanov:** Well… I would highlight that we certainly have some improvement. We've found some actual bugs. Some of them are not even the case because they are really corner cases, but those are a real issue reproduced.
|
||||
- **15:38:44 · Michal Smaga:** Yeah, I understand, yeah, yeah, so probably no one is questioning that, yeah, but just, like, to have, like, a more… like, condensed or, like, focused, uh, wrap-up for the project, yeah, so I would suggest, like, yeah, I like the plan, and I think it makes sense, yeah, so I would… I would bring the… Uh, yeah, so I think… Two things need to be done, like, one is to do a project update and, like, recap the current data, and summarize, like, where we landed at. And probably, I would start with, uh… with the DRI task, and, like, respond to Russell, and, like… Present the plan that, like, we have those, like, we have those fixes, the updates, and link to the project update, that you have the, like. Two more fixes, like, that will come up in the next version, and you propose the plan to, uh. Uh, have the final week of the project to, like, clean up the, like, all… Unnecessary things and clean up the diagnostics that we set up in place for, like, nailing down the issues. And suggest like to to metrics to like keep track of like where we're at with the permanent hangs and maybe better visibility in what's happening.
|
||||
- **15:39:58 · Alex Martemyanov:** Introduce some permanent. Yep.
|
||||
- **15:40:09 · Michal Smaga:** Yeah, and probably, like, we can see, like, what happens. Yeah, I… probably you want, like, if there's, like, a concrete plan that, like, this is the final week, and we just need to clean up the stuff, I don't think that there should be an issue. That's my feelings.
|
||||
- **15:40:27 · Alex Martemyanov:** Okay, yeah, I'll do it today, then, before the… before the meeting, hopefully.
|
||||
- **15:40:36 · Michal Smaga:** Yeah, and the meetings today are, like, the regular time, yeah.
|
||||
- **15:40:40 · Alex Martemyanov:** I think it's one hour later shifted due to some times on things.
|
||||
- **15:40:46 · Michal Smaga:** Yeah, but I think that…
|
||||
- **15:40:46 · Alex Martemyanov:** All the meetings, actually.
|
||||
- **15:40:52 · Michal Smaga:** Oh, didn't you have the time zone change for the winter time?
|
||||
- **15:40:55 · Alex Martemyanov:** No, luckily I don't have time zone change, but unfortunately I do have the Easter.
|
||||
- **15:40:57 · Michal Smaga:** Okay.
|
||||
- **15:41:03 · Alex Martemyanov:** And the western time zones changing and shifting my schedules up to the late night.
|
||||
- **15:41:08 · Michal Smaga:** the… Okay. Uh, yeah, so sounds good. Uh, like, I would ask you to, to, like, do the project update, and, like, provide the, the, the data analysis in some, some task, and, like, respond to us also.
|
||||
- **15:41:19 · Alex Martemyanov:** Mm-hmm.
|
||||
- **15:41:24 · Michal Smaga:** So we have the clear understanding, and we can discuss it on the meeting if he has any.
|
||||
- **15:41:28 · Alex Martemyanov:** Okay, so…
|
||||
- **15:41:29 · Michal Smaga:** Further questions, but it sounds good to me.
|
||||
- **15:41:30 · Alex Martemyanov:** Probably. Probably the cleanup is, uh… I think, to be done anyways, whether it comes into the project or just as a follow-up, but it would be necessary to do it anyways, and it's not…
|
||||
- **15:41:40 · Michal Smaga:** Yeah, yeah.
|
||||
- **15:41:47 · Alex Martemyanov:** And it's not small, because there's multiple things in it, and it should be…
|
||||
- **15:41:49 · Michal Smaga:** Yeah. Yeah, okay.
|
||||
- **15:41:53 · Alex Martemyanov:** Some considerations whether things should be kept or cleaned up or enabled for everybody. So it seems like a natural part for a natural completion part of the project. But yeah, for the metrics. It also seems pretty natural to have some permanent metrics just in case we could detect if anything becomes worse. at some point. Okay, that would be it then. Thanks.
|
||||
- **15:42:32 · Michal Smaga:** Cool. Yeah, that sounds good. Yeah, thank you for the chat.
|
||||
- **15:42:40 · Alex Martemyanov:** Okay, see you, see you later.
|
||||
@@ -86,8 +86,8 @@
|
||||
"note_modified_at": "2026-10-16T15:51:25.415Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA",
|
||||
"folder": "2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA",
|
||||
"sha256": "34ef73307fe86cc2d6f98caf57a719ae46937fb2d0efea3a18e03e21a42f1e00",
|
||||
"cues": 20
|
||||
"sha256": "86407aecffbf09effe200b26e80a01887ee197ba99d5caea70c124743fbee3fb",
|
||||
"cues": 3
|
||||
},
|
||||
"AEmGnEdJQfCMmCjwLyGtGA": {
|
||||
"title": "Зал персональной конференции Alex Martemyanov 2026-10-09 18:51(GMT+6:00)",
|
||||
@@ -254,8 +254,8 @@
|
||||
"note_modified_at": "2026-11-03T09:26:09.911Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/qQ2bzU5KTiCGluiBYA-ROA",
|
||||
"folder": "2026-11-03 Michal Smaga's Personal Meeting Room qQ2bzU5KTiCGluiBYA-ROA",
|
||||
"sha256": "dafb593da5838d0c82fa22918d30cd0e58dbe5d9a592b8a8c2c997d083a80638",
|
||||
"cues": 59
|
||||
"sha256": "646f7d0a50c8ad5f3297b8d28175a5649505ae798ba57fca5340d26536f0dd14",
|
||||
"cues": 3
|
||||
},
|
||||
"FZA-Gp3ATxiQ7cQaU5u5tg": {
|
||||
"title": "O-E 2026",
|
||||
@@ -278,8 +278,8 @@
|
||||
"note_modified_at": "2026-10-27T14:02:34.482Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/-I3aVYDWTkKZ_VTRLdjGnA",
|
||||
"folder": "2026-10-27 Apple Weekly Team Meeting - Zoom ID -I3aVYDWTkKZ_VTRLdjGnA",
|
||||
"sha256": "e2679b9fc63a1b4244db265a12dcba88b991d0060ea1fc01b02409bd749ea3e2",
|
||||
"cues": 3
|
||||
"sha256": "eca3ff1650275faccc26a7d030a207788f36bd194f860b5e232560613956f225",
|
||||
"cues": 49
|
||||
},
|
||||
"1T8djM8kQaOWNDk-yjDc9A": {
|
||||
"title": "Alex Martemyanov's Zoom Meeting",
|
||||
@@ -362,8 +362,8 @@
|
||||
"note_modified_at": "2026-10-19T12:37:38.903Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/QvxllpCuTTSLGEZp-R6jQw",
|
||||
"folder": "2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw",
|
||||
"sha256": "5cf16938df6ebe0110bec8e8b4311fcbe55a764bd2bb72f64faa049ba1777d9e",
|
||||
"cues": 3
|
||||
"sha256": "a4b3c5ce7fafb99496019591da19f9a103e35cf5f37ec42aa8f154021fdebcae",
|
||||
"cues": 133
|
||||
},
|
||||
"KcmYOq5_SQGPxdkdbhRx9A": {
|
||||
"title": "Dominik Kapusta's Personal Meeting Room",
|
||||
|
||||
@@ -1 +1 @@
|
||||
{"observed_at":"2026-11-19T12:18:13.202Z","scanned":24,"imported":2,"skipped":21,"withoutTranscript":0,"coverage":"partial","sections":[{"name":"Owned by me","pages":5,"notes":86,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":86,"gaps":["locator.waitFor: Timeout 20000ms exceeded.\nCall log:\n - waiting for locator('#docs-title')\n"],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
|
||||
{"observed_at":"2026-11-19T12:35:46.882Z","scanned":31,"imported":4,"skipped":27,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":86,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":86,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
|
||||
Reference in new issue
Block a user