[2026-11-20] eagle: work/zoom-transcripts/2026-10-06 Jacek Łyp's Zoom Meeting 2026-10-06 20 44(GMT+6 00) gUhtLoqRTfSsTbZsann73A/transcript.json work/zoom-transcripts/2026-10-06 Jacek Łyp's Zoom Meeting 2026-10-06 20 44(GMT+6 00) gUhtLoqRTfSsTbZsann73A/transcript.md work/zoom-transcripts/2026-10-20 Apple Weekly Team Meeting - Zoom ID 2026-10-20 20 01(GMT+6 00) gBBa-iiUQLycw55WRV1tnw/transcript.json work/zoom-transcripts/2026-10-20 Apple Weekly Team Meeting - Zoom ID 2026-10-20 20 01(GMT+6 00) gBBa-iiUQLycw55WRV1tnw/transcript.md work/zoom-transcripts/index.json work/zoom-transcripts/sync-status.json work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.json work/zoom-transcripts/undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w/transcript.md

This commit is contained in:
Alexey Martemyanov committed 2026-11-20 15:10:40 +06:00
1 parent 552c3a08ca
commit 512d17ccc4
8 files changed
+3385 -7

No files matched your search

@@ -15,3 +15,305 @@ source: "https://us01mynotes.zoom.us/gUhtLoqRTfSsTbZsann73A"
- **20:44:49 · JŁ:** Hello.
- **20:44:51 · Alex Martemyanov:** Yeah, so… But I think… There should be a PR open for the… Privacy config files. For Jacek…
- **20:45:03 · JŁ:** Yeah, just. Just one one thing when when you are fixing Alex this, have you been able to reproduce it or not?
- **20:45:10 · Alex Martemyanov:** Yes, there is exact testing steps in the PR. So, basically, you have to skip the… got it. button press, and it puts you to the NTS restore loop. Uh, because the flag is set on when the button is clicked. Uh, so, the next time you open Duck AI, and you restart the app from that point, it will restart to the FHIR onboarding, locking in, uh, the Duck AI burning. So it's not a kind of blocking user experience, but it's a regression of user experience for sure.
- **20:45:48 · JŁ:** Okay, let me check it.
- **20:45:49 · Alex Martemyanov:** Uh, and, uh, disabling, there is no, there is no dedicated feature flag for this, uh, for this exact feature, but this is the whole, uh, tailored DACA AI. Onboarding flow. If we want to disable it, or maybe it's just easier to go with the…
- **20:46:07 · JŁ:** So sorry, if we disable it, what happens?
- **20:46:10 · Alex Martemyanov:** The whole dark AI onboarding vanishes.
- **20:46:14 · JŁ:** Okay.
- **20:46:17 · Alex Martemyanov:** So we learned to the old, uh, onboarding without the Duckinghide part.
- **20:46:20 · JŁ:** Mmhm.
- **20:46:22 · Alex Martemyanov:** So it kind of hurts the Duck AI, uh, product. But if we… if we push it to the hotfix or internal release, it just mitigates it right… right away.
- **20:46:22 · JŁ:** Okay. Yeah, yeah, so I think we need to…
- **20:46:33 · Alex Martemyanov:** So maybe it's easier, it's an easier option not to disable the feature flag. And just push it to the release. If it makes sense.
- **20:46:44 · JŁ:** I mean, uh. Not doing the hotfix or doing the hotfix.
- **20:46:50 · Alex Martemyanov:** I mean doing default fix without changing the feature flag.
- **20:46:54 · JŁ:** Okay.
- **20:46:57 · Bartek Waresiak:** Again… What's the plan? Sorry, I got lost because I just got into the infinite loop on my browser.
- **20:47:05 · JŁ:** Yeah, the… Okay, so like, you mean representation.
- **20:47:09 · Alex Martemyanov:** To release it. Related to 240 iOS release, so these…
- **20:47:14 · JŁ:** And…
- **20:47:18 · Alex Martemyanov:** This week's public release and make an assisted app store review. Right. How does it work?
- **20:47:35 · Hanyu Tang:** Okay, I can reproduce it on me.
- **20:47:41 · Alex Martemyanov:** Hmm? Sorry.
- **20:47:43 · Hanyu Tang:** I can reproduce it on me using the testing steps.
- **20:47:49 · Alex Martemyanov:** Cannot reproduce it. Why? On the broad branch.
- **20:47:54 · Hanyu Tang:** Yeah, I can refer to you soon. Uh, not your branch, on me.
- **20:47:57 · Alex Martemyanov:** Ah, you're good to be list. Okay.
- **20:48:00 · Hanyu Tang:** Yeah.
- **20:48:02 · Alex Martemyanov:** Yeah, it's not even produced, just exactly with the steps. So there is two main points, not pressing the button, and uh… staying on the CAI page when the app is, um… They're too dumb.
- **20:48:24 · Bartek Waresiak:** Again, not pressing which button.
- **20:48:25 · Alex Martemyanov:** The got it button. When there is a… you've got this screen. if you… Turn… turn down the app. If you turn it in the app at that stage, it won't record the correct state for the parallel marking. Then you have to ignore the… Final. the final onboarding button on one more thing that marks the onboarding as completed. and directly head to the address bar and start AI chat. So we detectively, uh… kind of lays over two issues that we stay in the state restoration, in the onboarding state restoration for the FHIR onboarding state, and the onboarding incomplete state. Because you didn't complete the onboarding in a normal way, and uh… instead of. completing the onboarding, the app considers the onboarding not finished and restores it to the FHIR onboarding state, because the DACA AI page was… There, when it was took down. So there is three factors activating this bug. And it should not have a huge effect on the users. Yes, I suppose.
- **20:50:02 · Bartek Waresiak:** Can I share my screen? Because I want to make sure that we are on the same page with this. So, basically… This is my application right now, okay?
- **20:50:16 · Alex Martemyanov:** Yep.
- **20:50:18 · Bartek Waresiak:** This is my application. And… they'll. If I kill it… And open it. I see this.
- **20:50:35 · Alex Martemyanov:** Yes. This is exactly the stage.
- **20:50:39 · Bartek Waresiak:** And… Pressing that… And I'll and starting any new new chat. And leaving this means that every restart I see that.
- **20:50:57 · Alex Martemyanov:** Yes.
- **20:51:00 · Bartek Waresiak:** And this is on the 240.
- **20:51:00 · Jonathan Jackson:** So if you would. So if you leave now, what happens?
- **20:51:03 · Bartek Waresiak:** Like the… And if I leave now…
- **20:51:06 · Jonathan Jackson:** Yep.
- **20:51:07 · Bartek Waresiak:** And come back, I'm back to onboarding.
- **20:51:12 · Alex Martemyanov:** Yep.
- **20:51:20 · Bartek Waresiak:** Can we control this with feature flag?
- **20:51:24 · Alex Martemyanov:** Uh, we can disable the docker, yeah, onboarding.
- **20:51:29 · Bartek Waresiak:** Like, I would say, like, I would disable it.
- **20:51:35 · JŁ:** The the question is disabling. It fixes it for the future users, or if someone is in the loop. It's going to fix it for them as well.
- **20:51:43 · Bartek Waresiak:** I would say eventually it should fix. This is not fully blocking the UI. I can press this. It's like the shitty experience. I can still use the app.
- **20:51:51 · Alex Martemyanov:** Yeah.
- **20:51:53 · Bartek Waresiak:** Right? If I kill this and resurface. it works, but if I, for any reason, end in the… And the flow in this. And kill.
- **20:52:11 · Jonathan Jackson:** So if you're in Duck AI when the app is quit, it brings you back with AI onboarding.
- **20:52:14 · Bartek Waresiak:** Yeah, this is insane loop. So every time I end up in the state that I've used Duck AI, I'm back to this annoying onboarding step.
- **20:52:26 · Jonathan Jackson:** Is that true for everybody who uses Duck AI at this point?
- **20:52:31 · Bartek Waresiak:** No, I think this is true for everyone that has onboarding state that is broken.
- **20:52:38 · Alex Martemyanov:** Yeah, so the ones who did not push the button.
- **20:52:38 · Jonathan Jackson:** So they stopped in the middle of the morning, basically. Okay.
- **20:52:42 · Bartek Waresiak:** Yep. So the friction.
- **20:52:44 · Jonathan Jackson:** So it's only for our new users who we're trying to push towards Duck AI.
- **20:52:48 · Bartek Waresiak:** Yes, exactly. That's the… that's exactly the impression I have. So, my… my intention here, like, intuitive intention would be to figure out.
- **20:52:50 · Alex Martemyanov:** Hmm. Okay.
- **20:52:52 · Jonathan Jackson:** Okay.
- **20:53:00 · Bartek Waresiak:** can feature flag. disable this. What kind of feature flag do we have for us for this?
- **20:53:08 · Alex Martemyanov:** We have, uh…
- **20:53:08 · Jonathan Jackson:** Yep.
- **20:53:10 · Bartek Waresiak:** Oh, I don't. For some reason.
- **20:53:12 · Alex Martemyanov:** Custom product page deck AI onboarding flow.
- **20:53:16 · Jonathan Jackson:** So we would disable the entire onboarding flow.
- **20:53:17 · Bartek Waresiak:** I don't have.
- **20:53:21 · Jonathan Jackson:** For Dec AI.
- **20:53:21 · Alex Martemyanov:** Yeah, try setting the flag.
- **20:53:24 · Bartek Waresiak:** Yeah, I need to log in to…
- **20:53:28 · Jonathan Jackson:** I don't know if that's necessarily better.
- **20:53:32 · Bartek Waresiak:** Not necessarily better what?
- **20:53:32 · Jonathan Jackson:** Because we wouldn't be giving, it sounds like we wouldn't be giving them a decade onboarding at all. Based on the flag name anyway.
- **20:53:41 · Alex Martemyanov:** That's… That depends.
- **20:53:46 · Jonathan Jackson:** Or is it only for people coming from a custom product page?
- **20:53:51 · Bartek Waresiak:** Like, this is the onboarding when you install the app.
- **20:53:51 · Alex Martemyanov:** You know.
- **20:53:54 · Jonathan Jackson:** Yeah, but Alex just shared the… what I think is the feature flag name, right, Alex?
- **20:53:59 · Alex Martemyanov:** On boarding. Hmm.
- **20:54:05 · Jonathan Jackson:** Okay.
- **20:54:06 · Bartek Waresiak:** Like the question is.
- **20:54:08 · Jonathan Jackson:** Do we have a mitigation?
- **20:54:08 · Bartek Waresiak:** This onboarding can effectively set people in this broken state.
- **20:54:14 · Jonathan Jackson:** Right.
- **20:54:14 · Bartek Waresiak:** Plus, we have people in this broken state that basically cannot recover.
- **20:54:20 · Jonathan Jackson:** Yeah. Mm-hmm.
- **20:54:22 · Bartek Waresiak:** So the question is. What's more important, to fix that on the actual users right now or to still keep presenting this onboarding? Potentially bringing in more bleeding.
- **20:54:35 · Jonathan Jackson:** Thank you. Yeah, yeah, yeah.
- **20:54:39 · JŁ:** Yeah, but… So I think we don't know if again, like the question I asked, if. disabling the flag fixes it for like fixes the people that are in the loop. you know, because if if it doesn't, then. I think we should just go with the hot fix as soon as possible, and if it does, then yeah, we could. We could turn the flag for today and still go with a hot fix. Probably like.
- **20:55:04 · Jonathan Jackson:** Yeah, I think we have parallel work streams here. We have one looking into what feature flag we have and what we can do to mitigate as quickly as possible. And we have another looking at what's the right hotfix.
- **20:55:17 · Alex Martemyanov:** No, basically the flags won't fix it. They will only fix it for the new users by not showing the onboarding step.
- **20:55:28 · Jonathan Jackson:** But the users would be stuck still.
- **20:55:30 · Alex Martemyanov:** Yep. who already have this issue, it's not gonna fix it.
- **20:55:34 · Jonathan Jackson:** Yeah. So then, Bartek, your question, I think, is right. Does disabling it and preventing new people from ending up in this position make sense or not?
- **20:55:46 · Bartek Waresiak:** Like, the question is, can we expedite the code fix to… have it rolled out as soon as possible. Like, basically, this is what we need. If we cannot fix this. With…
- **20:56:05 · Jonathan Jackson:** I mean, do we have a sense of what an actual fix looks like yet?
- **20:56:11 · Alex Martemyanov:** Yes, the pull request is open for the actual fix. It's basically resetting this log.
- **20:56:22 · Jonathan Jackson:** Okay. And this is iOS only, is that right?
- **20:56:26 · Alex Martemyanov:** Yes.
- **20:56:31 · JŁ:** Oh, okay, I think…
- **20:56:32 · Hassaan Elgarem:** So I I want to. Yeah, I want to share my screen and show like, I think, Jonathan and Alex, you're in there when we talked about that. But I I came across a different issue. I'm not sure if it's related or not. Let me show you. um… Okay. It's this one. So when going through the onboarding flow and then choosing like one of the pre-filled prompts, I reach the stuck. State. and it takes a very long time like we did it on the call before you joined, and we waited. Maybe I'm not sure, like more than a minute till something actually happened.
- **20:57:25 · Jonathan Jackson:** Fun.
- **20:57:25 · Hassaan Elgarem:** And only the only the only thing that's. Interactive is the Firebolt. Right now.
- **20:57:31 · Alex Martemyanov:** It's basically a known issue if you have a connection loss or a weak connection. It would behave like this, yes, and it's kind of intended behavior.
- **20:57:42 · Jonathan Jackson:** Do you have a reconnection?
- **20:57:42 · Alex Martemyanov:** So, they will fire buttons and… Yes, it's, uh, it's loading. Because it starts loading. Maybe there is, like… I don't know. There shouldn't be CPM compilation, but if it takes to one minute to load, it means that it's, yeah, it's loaded, basically.
- **20:57:55 · Bartek Waresiak:** Do we…
- **20:57:58 · JŁ:** Wait. Wait. It's crazy if it's intended, sorry.
- **20:58:05 · Bartek Waresiak:** Yeah, like, okay, like, I can buy it is acceptable. But… I would only make it acceptable if we have metrics to understand that this is not a problem on a wider scale. Do we have metrics? For how long does it take this initial load?
- **20:58:23 · Alex Martemyanov:** Nope, we don't.
- **20:58:27 · JŁ:** Probably some.
- **20:58:27 · Alex Martemyanov:** Okay.
- **20:58:28 · JŁ:** Someone would be good person to address it like he. He was doing some. And… SLIs. Air.
- **20:58:38 · Hassaan Elgarem:** So my my question here is to Alex like, if this problem is like an existing problem. But if this problem became more frequent, would it trigger more issues? Of the actual, like, loop that we are discussing.
- **20:58:54 · Alex Martemyanov:** Nope, it's just long loading. There is probably nothing to do on the native side about it.
- **20:58:58 · Jonathan Jackson:** Okay. Hassan, was that in a link condition scenario so your network was slow, or was that just a normal load?
- **20:59:07 · JŁ:** Sorry, sorry, I'm not, I'm not, I'm not buying it, like, it's, it's, it's a site, right? What does it mean? It's an intended behavior, and…
- **20:59:09 · Hassaan Elgarem:** No, I'm good.
- **20:59:14 · Jonathan Jackson:** Yeah.
- **20:59:18 · Alex Martemyanov:** We don't show the, uh… We don't show the content until it is completely loaded with all the contents.
- **20:59:26 · JŁ:** Okay, but… but, like, Hassan's on a Zoom here with great connectivity, like, how… I… I don't get it, like… Probably any site would load immediately, like.
- **20:59:39 · Alex Martemyanov:** Maybe there is a signal… But yeah, so we just seen the appearance of the text started after it appeared.
- **20:59:50 · Jonathan Jackson:** Yeah, but it looks like a broken state. It looks like the page has failed to render.
- **20:59:50 · Alex Martemyanov:** So, basically, the loading.
- **20:59:55 · Jonathan Jackson:** And so maybe that's the implementation right now, but I thought it was very broken.
- **20:59:58 · Alex Martemyanov:** No, it's, uh, it's not… it's not the… it's not the rendering failure, it's loading, because, uh, it's…
- **21:00:04 · Jonathan Jackson:** Yeah but the user clicks the user goes to that page on a good connection and they have to wait thirty seconds to a minute for anything to happen.
- **21:00:10 · Alex Martemyanov:** There is a signal.
- **21:00:10 · Jonathan Jackson:** That doesn't look…
- **21:00:11 · Bartek Waresiak:** One moment.
- **21:00:12 · Jonathan Jackson:** Yep.
- **21:00:13 · Bartek Waresiak:** What I would expect to happen when the button is pressed is that the question is transferred to the bubble, chat bubble. is sent to the backend. And we render the question that is being asked. Then we see generating response prompt that is ongoing and this didn't happen.
- **21:00:37 · Alex Martemyanov:** This is logical, but it's not the implementation. It's, uh… it's done this way to…
- **21:00:41 · Jonathan Jackson:** So…
- **21:00:45 · Alex Martemyanov:** show the blank screen until the answer is ready. So when the connection is final and the signal arrives in time, it should render just in time and appear without all this page flickering.
- **21:01:01 · Bartek Waresiak:** Was that raised in ship review and presented in such way?
- **21:01:01 · Alex Martemyanov:** But there was… Nope. during the ship review, there… the issue was not reproduced, and basically it appears during 2 seconds. And yes, it was, uh… this way during the ship review. So there was no bubble, nothing animated, and so on.
- **21:01:21 · JŁ:** I called Fernando. to this meeting. I just, it's hard for me to believe like.
- **21:01:26 · Jonathan Jackson:** Well, so, I mean, it sounds like… it sounds like that's maybe a separate user experience issue, which we should have a task for and address. Hasan, your question is still valid, though, related to the incident here.
- **21:01:29 · JŁ:** But.
- **21:01:30 · Alex Martemyanov:** Thank you.
- **21:01:32 · Bartek Waresiak:** Yeah, yeah.
- **21:01:37 · Jonathan Jackson:** Does that behavior put us into a position where more users are at risk of ending up in this loop state?
- **21:01:47 · Alex Martemyanov:** So there may be an issue with this front-end signal from Duck AI page that we used to start rendering, but as we've seen, the actual animation has started after a significant delay, so it means the signal is.
- **21:01:58 · Bartek Waresiak:** Okay.
- **21:02:01 · Alex Martemyanov:** synchronized with this appearance, this presentation slide.
- **21:02:01 · Jonathan Jackson:** Right. But if that's happening during onboarding, and the entry to the loop is hitting the fire button.
- **21:02:03 · Bartek Waresiak:** I, I have, I have…
- **21:02:07 · Jonathan Jackson:** It's going to encourage more people to hit the fire button than might otherwise.
- **21:02:11 · Alex Martemyanov:** Maybe.
- **21:02:12 · Bartek Waresiak:** I have one question.
- **21:02:12 · Hassaan Elgarem:** hitting the firewalls and and killing the app like killing the app like, if I'm in that state. I would think of killing the app, and that's what like triggers the loop. So.
- **21:02:14 · Jonathan Jackson:** Right. Because they think it's stuck. Yeah.
- **21:02:23 · Hassaan Elgarem:** I think they are related.
- **21:02:24 · Jonathan Jackson:** I don't know that we need a fix for the user experience issue we're talking about, but it is a factor in putting people into that state. From a behavior perspective, I'd buy that.
- **21:02:26 · Bartek Waresiak:** Yeah, like, the… from the perspective on onboarding, when I select Duck AI onboarding, when I select some random prompt. And it loads. When I delete this… When I use the fire button. It should work okay from that point onwards. Or is the condition flux set somewhere else? That's what I don't really follow.
- **21:03:15 · Alex Martemyanov:** The condition set, the flag is, the flag for the fire onboarding is set on the… Prior. Screen. I mean, when do you have this AI answer presented? Uh, it sets the state restoration, the onboarding set restoration plug. to… Awaited. So basically, yes, it may… It may indicate this.
- **21:03:45 · Bartek Waresiak:** So when I got the response.
- **21:03:49 · Alex Martemyanov:** When you get the response, the flag is turned on. And when you… Push the got it button, it's, uh, removed.
- **21:03:59 · Bartek Waresiak:** Okay, so I'm I'm trying to reproduce it right now. And I'm… Question to AI.
- **21:04:10 · JŁ:** In the meantime, Hassan, could you show Fernando the finding that you have as well? Another was was working on the Ki.
- **21:04:19 · Hassaan Elgarem:** Give me a minute to prepare it and I'll share my screen.
- **21:04:24 · JŁ:** Thank you. Okay, I'm going to focus now on the official part, so I will officially start the incident, okay, because… Yeah, I have issues with multitasking. So yeah, so I will leave you like I'll be here. But I will leave you guys to to questions, answers, and more investigation. And just ping me if anything.
- **21:05:03 · Bartek Waresiak:** No, like, it's like, sorry, but all of that just doesn't make sense to me. It's like super easy to trigger for me to enter the loop.
- **21:05:20 · Fernando Bunn:** What it is.
- **21:05:22 · Bartek Waresiak:** Like, I…
- **21:05:22 · Fernando Bunn:** Sorry, I don't know exactly what is going on.
- **21:05:24 · Bartek Waresiak:** Let me reinstall the app and share my screen again, so I will show you what I mean by super easy.
- **21:05:29 · Fernando Bunn:** Okay.
- **21:05:31 · Jonathan Jackson:** While you're doing that, the short version is, if you go through the Duck AI onboarding, it gets you to the point where it's given a random prompt to Duck AI. You hit the fire button, and then you quit the app. And from that point on, anytime you leave… anytime you quit the app while you're in the Duck AI experience, it will bring you back to the random prompt happening when you come back to the app. So it feels like you're stuck on onboarding and it basically keeps bringing you back to that. I don't know if you have to quit the app for that to happen or if it's like when you leave and come back after a while, if you were in Duck AI at that point.
- **21:05:56 · Fernando Bunn:** Mmhm.
- **21:06:06 · Jonathan Jackson:** I think it happens again. I'm not sure about that piece. But at the very least, when people relaunch the app at that point, they keep getting the Duck AI out.
- **21:06:13 · Fernando Bunn:** Okay. So if we relaunch the IPS2… Okay, let me… Yeah, yeah, yeah, you can see it.
- **21:06:17 · Bartek Waresiak:** Yeah, can you… Yeah, okay. Can you hear me as well?
- **21:06:22 · Fernando Bunn:** Yep.
- **21:06:23 · Bartek Waresiak:** Excellent. So this is like, I ignore this. It's in Polish, but it doesn't really matter. I ignore this.
- **21:06:29 · Fernando Bunn:** Mm-hmm.
- **21:06:29 · Bartek Waresiak:** I ignore the color, whatever, top, and now I want to. Check the AI about the stock market. Okay, so I'm waiting here. This looks good to me, right? I look nice. I'm supposed to clear it. Okay, so I'm clearing this. Excellent. This looks okay. I want to chat. Okay. I accept the terms. Everything looks good. Perfect. So I move away. And I'm in the loop.
- **21:07:14 · Alex Martemyanov:** So. Ah, you're telling there is no… you've got this step at that point?
- **21:07:18 · Bartek Waresiak:** Yeah, exactly.
- **21:07:20 · Alex Martemyanov:** Ah…
- **21:07:20 · Bartek Waresiak:** This is everything here.
- **21:07:22 · Alex Martemyanov:** That is the change. And when was it done?
- **21:07:26 · Bartek Waresiak:** This is the current production.
- **21:07:30 · Alex Martemyanov:** When was it changed? Maybe there is a phishing flag.
- **21:07:35 · Bartek Waresiak:** Like, this is, like, I'm hitting this literally every time I install the app.
- **21:07:40 · Alex Martemyanov:** Hmm, that changes things, and that explains why we started seeing it just now.
- **21:07:46 · Bartek Waresiak:** Oops, sorry, I'm…
- **21:07:47 · Alex Martemyanov:** If the onboarding was changed, so this…
- **21:07:51 · Bartek Waresiak:** Uh, I just real…
- **21:07:52 · Alex Martemyanov:** I think made of those.
- **21:07:52 · JŁ:** My pleasure.
- **21:07:53 · Fernando Bunn:** Just one thing, just to — sorry, just help me. OK.
- **21:07:53 · JŁ:** Can you…
- **21:07:55 · Bartek Waresiak:** Sorry, I have another call I need to jump on, but I believe this is a problem that needs to be surfaced, okay? So…
- **21:08:03 · JŁ:** Bartek, one more thing. Can you record the thing and upload it? Send me so we can have like a.
- **21:08:12 · Bartek Waresiak:** I, I can, like, give me, like, 2 minutes, okay?
- **21:08:12 · Fernando Bunn:** I'll try to do it here in the simulator, yeah.
- **21:08:13 · JŁ:** For experience. Thank you. Okay, sure.
- **21:08:16 · Fernando Bunn:** Just one thing, I don't know if it… like, it could give a hint on what's going on, okay? When I saw the onboarding thing, what it did, I didn't see the terms and conditions. anywhere…
- **21:08:28 · JŁ:** it…
- **21:08:29 · Fernando Bunn:** Is this expected?
- **21:08:31 · JŁ:** There… there were, like, I think, when the chat appeared. I think for the first chat, it didn't appear. I think there was a discussion on Mattermost today on OJ Channel about it. I think Picor asked about it. Let me search quickly.
- **21:08:35 · Fernando Bunn:** Yep. Yep. Okay. No, yeah, I saw the discussion, but…
- **21:08:48 · JŁ:** Shouldn't we already have a privacy information at this stage? And Chuck answered, we have dispensation to allow one prompt here without asking users to agree to the TOS.
- **21:08:59 · Fernando Bunn:** Oh, what prompts? Okay.
- **21:08:59 · JŁ:** So after… Yeah, so Bartek prompted again, and there was a button. So, so did this one work?
- **21:09:05 · Fernando Bunn:** Yeah, okay, so that's fine, okay, so that's fine.
- **21:09:08 · JŁ:** Yeah, but do you have?
- **21:09:09 · Fernando Bunn:** of…
- **21:09:10 · Hassaan Elgarem:** Fernando? Yeah, I have it ready. Let me show you.
- **21:09:11 · JŁ:** that that.
- **21:09:15 · Hassaan Elgarem:** The other thing.
- **21:09:17 · Fernando Bunn:** Audrey's name?
- **21:09:18 · Hassaan Elgarem:** Okay, so I went through the onboarding.
- **21:09:19 · Fernando Bunn:** Okay.
- **21:09:19 · JŁ:** Thank you. The other thing.
- **21:09:26 · Hassaan Elgarem:** And then ask AI, and then… And then I'm stuck in this state. for a while, like it normally takes like 30 to 30 seconds to one minute. And the only thing that I can I can interact with is the fire button. And once I do, actually, it starts pulsing. So it's a weird thing.
- **21:09:50 · Alex Martemyanov:** Okay, just go, just go on deleting it.
- **21:09:51 · Fernando Bunn:** And this is… and… And this is not… you're not using, kind of, uh…
- **21:09:58 · Hassaan Elgarem:** Natural condition or anything? Nothing.
- **21:09:58 · Fernando Bunn:** Uh…
- **21:10:00 · JŁ:** No, no, not using custom chat.
- **21:10:00 · Fernando Bunn:** Okay, it's vanilla, okay.
- **21:10:02 · JŁ:** Yes.
- **21:10:03 · Hassaan Elgarem:** No.
- **21:10:04 · JŁ:** And, yeah, and…
- **21:10:04 · Alex Martemyanov:** Maybe it's…
- **21:10:06 · JŁ:** I think Alex was mentioning that this is by design.
- **21:10:09 · Fernando Bunn:** What?
- **21:10:11 · JŁ:** that…
- **21:10:11 · Alex Martemyanov:** No, it's… basically, I don't see this behavior at my place, and… Even from Kyrgyzstan, it loads fast enough, and I don't think it's, uh… Frequent problem. Because it actually indicates it's not loading.
- **21:10:28 · JŁ:** Yeah, yeah, bye. Right. But am I right that you are saying that it's basically like the the connectivity issue. And.
- **21:10:36 · Alex Martemyanov:** It looks mostly like the connectivity issue.
- **21:10:37 · Fernando Bunn:** So how… I'll do it for those who just… Go to SKI and use a pre-filled answer there.
- **21:10:47 · Hassaan Elgarem:** Yeah. Okay.
- **21:10:51 · Fernando Bunn:** Yeah, it works fine here.
- **21:10:51 · Alex Martemyanov:** Yes, so we just loaded. It's either some routing issue, or DACRIA issue, or… And frankly, I don't know. How would you fix it without redesigning it really?
- **21:11:11 · Fernando Bunn:** So if I close this now…
- **21:11:11 · Alex Martemyanov:** With some lighting bubbling.
- **21:11:14 · Fernando Bunn:** I'm gonna see the look again.
- **21:11:15 · Alex Martemyanov:** Yeah, so that screen was high-five Bartek. When Bartek showed, demoed it, there was no high-five screen.
- **21:11:27 · Fernando Bunn:** Wait, I killed the app, and I went back, and I… I'm not on the KI anymore, so what… what happened with Barton.
- **21:11:28 · Hassaan Elgarem:** the…
- **21:11:34 · Alex Martemyanov:** Yeah, you just killed the app now.
- **21:11:36 · Fernando Bunn:** Yeah.
- **21:11:38 · Alex Martemyanov:** And you go back.
- **21:11:40 · Hassaan Elgarem:** But now it's fast, like now, like I don't have to wait or anything.
- **21:11:45 · Alex Martemyanov:** You're weird.
- **21:11:48 · Hassaan Elgarem:** So it's not really like a connection thing. Like, I think something is off.
- **21:11:55 · JŁ:** Hassan, can you actually trace it in a debugger? like, what is going on in the meantime, like, like, perhaps with a debugger and some, you know, some proxy, whatever thing, like, checking if there are any requests going in and out, okay? Like…
- **21:12:03 · Hassaan Elgarem:** That's right. But, like, this is… Yeah, yeah, yeah, I'll do that. I'll do that.
- **21:12:17 · JŁ:** Thank you so much.
- **21:12:18 · Hassaan Elgarem:** But again, like, if I kill the app and reopen, I'm back in this state again. That's the cherry on top, you know.
- **21:12:31 · JŁ:** So what you mean, like, you killed the app, and…
- **21:12:34 · Hassaan Elgarem:** like what I'm trying to reproduce the the original issue.
- **21:12:37 · JŁ:** Okay.
- **21:12:37 · Fernando Bunn:** But if you see the logs, what is happening there? Is the app actually trying to hit the KI and just latency or? Something else. Like, there's a lot to tell. Anything if you reopen it via Xcode?
- **21:12:52 · Hassaan Elgarem:** I'll try, I'll try, like, I'm… right now, the debugger is not attached, but, like, I'll try… I'll stop sharing. I'll try and let you know if I find something.
- **21:13:03 · Fernando Bunn:** Try to reproduce vertex stuff, but it's not working here.
- **21:13:04 · Alex Martemyanov:** What is this app? What's the app you're sharing? Some… It's not the simulator, is it?
- **21:13:22 · Hassaan Elgarem:** Sorry?
- **21:13:23 · Alex Martemyanov:** Vijay, what is the app you were sharing? It's not a simulator, is it?
- **21:13:27 · Hassaan Elgarem:** Okay. It's the new devices hub. Xcode 27, I think.
- **21:13:35 · Alex Martemyanov:** Is it the same on the regular simulator?
- **21:13:41 · Hassaan Elgarem:** Yeah, it should be, yeah.
- **21:13:41 · Alex Martemyanov:** Or a real device.
- **21:13:43 · Hassaan Elgarem:** It's like, uh…
- **21:13:44 · JŁ:** The same.
- **21:13:45 · Hassaan Elgarem:** Yep.
- **21:14:08 · Fernando Bunn:** Was anyone able to produce vertex stuff through Xcode or just from the App Store?
- **21:14:29 · Hassaan Elgarem:** Fernando, can you repeat your question? Sorry.
- **21:14:33 · Fernando Bunn:** I'm asking if anyone was able to reproduce bar type issue using Xcode or just via App Store. Just to see if the bug release has anything to do with it.
- **21:14:46 · Hassaan Elgarem:** Uh, yeah, like, I'm testing from the Xcode, and I'm able to reproduce the loop, but it's a loop plus the delay, like, I'm getting both issues.
- **21:14:55 · Fernando Bunn:** Oh, okay. Okay, so it's not just a release thing. Okay.
- **21:14:59 · Hassaan Elgarem:** Okay.
- **21:15:06 · Fernando Bunn:** Moving forward… Short story, uh… Skip. Excuse me. Next. Okay. Bago. So I go to Tokyo, explain the stock market. So at this moment, if I… First, close the app and kill it. I'll be on the loop, right? Like, I do not interact with the thing, or it doesn't matter.
- **21:15:43 · Alex Martemyanov:** You interact with it, you burn it. Use the fire button. Yeah, and then you kill it.
- **21:15:47 · Fernando Bunn:** Oh, I need to burn. Okay, then I see this. Should I go to…
- **21:16:02 · Alex Martemyanov:** Yes, and you enter… you activate the address bar, DACAI. And then you killed it again, and you got in the hoop.
- **21:16:11 · Fernando Bunn:** So we'll go to new chat.
- **21:16:13 · Hassaan Elgarem:** Start a new chat and then kill the app.
- **21:16:16 · Fernando Bunn:** Cool, again. Okay.
- **21:16:24 · JŁ:** You got it?
- **21:16:26 · Fernando Bunn:** Yep. Just want to see if I call from Xcode now. Seems bad. So I need to get to the loop. I need to do the same thing again, like fire button, kill the app, and…
- **21:16:45 · Alex Martemyanov:** Uh, yes, you fire button… Then you start Duck AI Chat again, and then you kill it up.
- **21:16:52 · Fernando Bunn:** Done.
- **21:16:53 · Alex Martemyanov:** It's only if you… if you give it 12, the exact AI chat is active.
- **21:16:53 · Fernando Bunn:** Queued up. Oh, I need to kill while he's acting.
- **21:17:00 · Alex Martemyanov:** Yes. So, uh… So what's the resolution we have? We need to rebase the PR to the current release, right? Two seven point. to… 4… 0… and have an expedited review, right? Basically, that's the only option.
- **21:17:28 · Fernando Bunn:** Can I just remove… Is this specific, the KI part and the onboarding behind FeatureFlight?
- **21:17:35 · Alex Martemyanov:** Yes.
- **21:17:37 · Fernando Bunn:** So it's already off.
- **21:17:37 · Alex Martemyanov:** The specific… It's… It's already off.
- **21:17:43 · Fernando Bunn:** But I just reproducing the episode. Okay, so maybe it didn't…
- **21:17:48 · Alex Martemyanov:** Yeah, we cannot disable it.
- **21:17:54 · Fernando Bunn:** Sorry, is it available in production or not?
- **21:17:58 · Alex Martemyanov:** Hmm?
- **21:17:59 · Fernando Bunn:** The onboarding… the Deck AI onboarding step is disabled in production right now, or not? Like, did we disable using a feature flag?
- **21:18:04 · Alex Martemyanov:** Mm-hmm. There is no feature flag.
- **21:18:07 · Fernando Bunn:** Oh.
- **21:18:09 · Alex Martemyanov:** I mean, there was, but it's… Not a thing already. And. So I didn't get it if, uh… Was there… you've got the screen or not?
- **21:18:30 · Fernando Bunn:** I'm going to see if I can reproduce from Axcode catalog. Let's try and compile it for a second. I don't have… Morocco.
@@ -23,6 +23,676 @@
"time": "20:05:36",
"speaker": "Jonathan Jackson",
"text": "Mm, got it."
},
{
"time": "20:05:37",
"speaker": "Tom Strba",
"text": "And I think I'm next week. Because I almost got a heart attack when you said that I am…"
},
{
"time": "20:05:40",
"speaker": "Dominik Kapusta",
"text": "Yes, this week is Diego. And sorry for not closing my task."
},
{
"time": "20:05:41",
"speaker": "Jonathan Jackson",
"text": "Okay."
},
{
"time": "20:05:45",
"speaker": "Tom Strba",
"text": "that I am this week."
},
{
"time": "20:05:45",
"speaker": "Jonathan Jackson",
"text": "This week… Why is Diego… I don't see a task… this is a macOS release we're talking about, right?"
},
{
"time": "20:05:52",
"speaker": "Tom Strba",
"text": "Yeah, I think Diego maybe marked it as complete in the beginning of the week, because there's just, like, triage…"
},
{
"time": "20:05:57",
"speaker": "Jonathan Jackson",
"text": "Yes, you're right, Tom, your block is the 26th to the 30th, because that task is missing, I didn't see it, I wasn't looking at the dates, I was just reading the list."
},
{
"time": "20:06:04",
"speaker": "Tom Strba",
"text": "That's okay. Just wanted to be sure."
},
{
"time": "20:06:07",
"speaker": "Jonathan Jackson",
"text": "Okay. Diego is responsible for the release this week. It sounds like he's actually doing that. Is that right?"
},
{
"time": "20:06:08",
"speaker": "Tom Strba",
"text": "Perfect."
},
{
"time": "20:06:14",
"speaker": "Jonathan Jackson",
"text": "He knows. Okay, cool. Thank you."
},
{
"time": "20:06:14",
"speaker": "Dominik Kapusta",
"text": "That's right."
},
{
"time": "20:06:18",
"speaker": "Jonathan Jackson",
"text": "Um, no problem. Okay. Anyway, think about starting your self reviews this week. If you feel like you're gonna need more than a day to knock it out. Bartek, over to you."
},
{
"time": "20:06:31",
"speaker": "Bartek Waresiak",
"text": "Yep, I will be stepping down as IS app DRI. Jacek will take the primary role, and Brindy will take on secondary role. So, yeah, if there is IS drama, if there are IS issues, if there are any urgent things. Go to them! And thank you very much."
},
{
"time": "20:06:57",
"speaker": "Jonathan Jackson",
"text": "All right. Thank you. An, you're next on the agenda."
},
{
"time": "20:07:08",
"speaker": "Anh Do",
"text": "Oh, that was quick. Yeah, so in OK, there have been a few projects that involve native changes required as part of the front-end-led projects. Um, so the background is that they, uh, want to contribute some PR, and, uh, um… AI assisted Pi, of course, and then what have been working for us lately is like depends on the size of the task like I would be the one to like either. Dri the change that they are they want to make, or like they prepare the Pi, and I do a thorough review of that. So and now we want to kind of do this more regularly. And so there was a need for some kind of like guidelines that we can give to contributor from outside the apple team. So I was just starting like a small task to basically collect ideas from people. And if you have anything that we already have somewhere, maybe I could get put in. And so. it becomes something that we can point other people to when they want to contribute to the Apple codebase to ensure our standard and make sure that, like, everything is being done the way that we want. So that's about it. Nice."
},
{
"time": "20:08:19",
"speaker": "Jonathan Jackson",
"text": "Cool, thank you. I just took a quick peek. I see you do mention the engineering expectations. I think that's a good source. We might also want to link… to the onboarding process. Not that they would need to follow all of it, but some of… that's basically our best source of, like, how to get set up with the codebase. So there's probably a little work to do to figure out how to have a slimmed down version of that that folks could follow. And I'm sure other people have other ideas as well. So thank you. Um… Luke, we have a non-Apple person lurking in our midst. Welcome. What can we do for you?"
},
{
"time": "20:08:54",
"speaker": "Luke Andrew",
"text": "Hello. Yes, thanks for having me. Luke from SRE, for people that I haven't met before. Um, this is just a plea for generic Apple help. I don't want to, sort of, get all of your attention to focus on this task. We basically have… a looping client that seems to be sending, uh, requests once a second to us, uh, that is Apple, but not DuckDuckGo Apple, based on the user agent, and doesn't seem to be Safari either. Um… And it's cumulatively across lots of different devices, lots of different queries, sending in the region of 3 million searches a day. Which is substantial, not sort of catastrophic, but substantial enough searches that it's something that we want to deal with. Umm. And I don't really know where to go next to try and understand where it might be coming from or how we might try and reproduce it. So I don't want to solve that in this call, but I just wanted to bring your attention to the task. And if there's anyone who thinks they might be able to help, I'd really appreciate. a second pair of eyes, and pointed out that it's not even worth, with what we have at the moment, that we can, like, escalate this to Apple, because we just don't have enough, uh, information to get any help from them. So yeah, that's it. If anyone has any questions immediately or async, just pop them on the task. Yeah, that's all I have."
},
{
"time": "20:10:18",
"speaker": "BA",
"text": "Quick one, Luke."
},
{
"time": "20:10:18",
"speaker": "Jonathan Jackson",
"text": "This is not from a single client, but from a particular app version, potentially, is that right?"
},
{
"time": "20:10:24",
"speaker": "Luke Andrew",
"text": "Yeah. Yeah."
},
{
"time": "20:10:24",
"speaker": "Jonathan Jackson",
"text": "Okay. You know, be scared that it was one client going crazy. Okay, um…"
},
{
"time": "20:10:30",
"speaker": "BA",
"text": "Yeah, I was going to ask, what's the — we eliminated bots from the equation. Are we happy that it's not bots?"
},
{
"time": "20:10:36",
"speaker": "Luke Andrew",
"text": "It doesn't look like bots. The queries all look human. The rate is really low compared with bots. The moment that I put in a block for it and it immediately stopped, like redirected away."
},
{
"time": "20:10:39",
"speaker": "BA",
"text": "Okay. Right."
},
{
"time": "20:10:52",
"speaker": "Luke Andrew",
"text": "It got, like, a 302 from deep, and then just immediately stopped, so that doesn't feel like… bossy behavior either. They normally persist a little bit and then give up. Whereas this was just immediately, it broke out of whatever loop it was in and stopped."
},
{
"time": "20:11:09",
"speaker": "Jonathan Jackson",
"text": "Interesting."
},
{
"time": "20:11:10",
"speaker": "Luke Andrew",
"text": "Uh, so don't all take a look, because that would be a waste of time, but if you think you can help, um, I'd appreciate a pair of eyes. I'm gonna drop off. Thank you all for having me."
},
{
"time": "20:11:19",
"speaker": "Jonathan Jackson",
"text": "Yeah, one last quick question. It sounds like you're treating this as something that definitely needs attention, but not an incident at this point. Is that correct?"
},
{
"time": "20:11:25",
"speaker": "Luke Andrew",
"text": "Yeah, that's correct. It's been going on for… Based on… um, how we categorize queries for, um, like, ads perspectives. These get classified as a separate category based on user agents, so we don't send them to Bing and say, these are definitely good queries. Um, it's been happening for about a month. So it's, at the moment, not urgent. I'm gonna raise it with SRE, maybe, and see if we think it should be an incident that we just let run, but at the moment, that's not how we'."
},
{
"time": "20:11:55",
"speaker": "Jonathan Jackson",
"text": "Okay. Great. Thank you for the clarity there. Uh, and yeah, if anybody thinks they can help Luke out and figure out what's going on there, feel free to hop into the task. Thanks for coming. Moving on. Alex, you're first in the regular topics list."
},
{
"time": "20:12:16",
"speaker": "Alex Martemyanov",
"text": "Yeah, hey. I have several topics for today, including the VS Code integration postmortem to run later. And the first one goes with a proposal. The proposal is pretty short. And kind of related to the, uh, recent incident with Mac OS 12 crash. that we are not. Testing for macOS 12 and 13, I guess, because we are missing the infrastructure on CI runners. And the suggestion is pretty simple to extract the macOS UI tests target from the main macOS Xcode project, leaving it as a separate macOS project inside the. uh, Xcode workspace. So it will be available the same way it is now, and, uh, runnable. So only, uh, the only issue I can see for those who use, uh, the actual macOS Xcode project instead of the workspace. they would have to switch to another project to run the tests. So, I just wanted to hear if there is any concerns or objectives against it."
},
{
"time": "20:13:39",
"speaker": "Dominik Kapusta",
"text": "I think some time ago, we… someone asked… who uses or doesn't use Workspace, and people who didn't use Workspace were in a… In a minority, anyway, like, very few of them, so… I guess… I could move to the workspace."
},
{
"time": "20:14:06",
"speaker": "Jonathan Jackson",
"text": "I think it'd be good to ask that question in that proposal, at least more explicitly, and just give people a chance to chime in if they feel like that would be a hurdle. Um… Other question for me is, is there… should we think about the iOS side of this as well, and to match… structure, or is this really a macOS only question?"
},
{
"time": "20:14:26",
"speaker": "Alex Martemyanov",
"text": "Okay. Maybe, I… Didn't think about it, actually. And the main concerns here is the compatibility. So we can reach macOS 12 compatibility, at least for some local runners that I'm going to present further. And the build times, so we have package fetching and building for every macOS runner that runs the UI tests and any of the dependencies. None of the dependencies are used during the runs, so it's a 10-second step for each runner that can be easily omitted, and so, yeah. And yeah, it's not related to the main browser targets, so there's no risks. Uh, and they're both, uh, U.S. Probably to think about it in the ER."
},
{
"time": "20:15:25",
"speaker": "Dominik Kapusta",
"text": "I think iOS is not…"
},
{
"time": "20:15:25",
"speaker": "Jonathan Jackson",
"text": "I mean, I don't have a strong… sorry, I don't have a strong feeling there, I just felt like if we're gonna make this change, like, if it's gonna end up with different structures depending on the app, we should think about whether we really want that to be the case, or if we should do the other."
},
{
"time": "20:15:37",
"speaker": "Alex Martemyanov",
"text": "No, it actually shouldn't change any structure, any file structure, just the project placement."
},
{
"time": "20:15:38",
"speaker": "Jonathan Jackson",
"text": "Screwed up. Yeah, yeah, yeah. Dominic, I interrupted you. I'm sorry."
},
{
"time": "20:15:44",
"speaker": "Dominik Kapusta",
"text": "Ah, no worries, I just wanted to say that iOS is not affected by this at all, because… iOS doesn't need testing on various macOS versions."
},
{
"time": "20:15:51",
"speaker": "Jonathan Jackson",
"text": "Alright. So the limita… this is about dealing with a limitation that comes from Mac OS 12 build, particularly."
},
{
"time": "20:15:59",
"speaker": "Dominik Kapusta",
"text": "Yes."
},
{
"time": "20:16:01",
"speaker": "Alex Martemyanov",
"text": "And bill times."
},
{
"time": "20:16:01",
"speaker": "Dominik Kapusta",
"text": "I'm Bill Times."
},
{
"time": "20:16:02",
"speaker": "Jonathan Jackson",
"text": "Got it. Okay. thanks for pointing it out. Uh, like I said, I think you might want to give people a little bit more time to respond to async if they have… particularly if they feel like the… Workspace thing is gonna be a hurdle, but my guess is it's not gonna be a big issue. Uh…"
},
{
"time": "20:16:22",
"speaker": "Alex Martemyanov",
"text": "Okay."
},
{
"time": "20:16:24",
"speaker": "Jonathan Jackson",
"text": "Next topic."
},
{
"time": "20:16:24",
"speaker": "Alex Martemyanov",
"text": "We can…"
},
{
"time": "20:16:26",
"speaker": "Jonathan Jackson",
"text": "From you, also."
},
{
"time": "20:16:26",
"speaker": "Alex Martemyanov",
"text": "Perfect. To the next topic then. Yeah, so, uh, this is another iteration of, uh, the Verfield project. I've been live coding for a while already. Uh, so this is the current state of things. It's changed a little bit, some of you may remember the first, uh, first demo. Uh, so the change is it's, uh, migrated to Go language, and, uh, now it runs on TART system that's used on, uh… We tried runners, I guess. And so the system is here to show you the available images, available runners and locations. So here you see I can have it. stored on the external SSD, because I have my internal 2TB ETH. up to completely, and I have the old MacBook Pro also managed from the same environment. And, uh, you can add other machines as well. Uh, so this is, uh, a wrapper around the TART system that manages, uh, Xcode installs, uh, SIP protection, and, uh, for virtual machine and real machines. Uh, if you use older hardware and, uh. It's, uh… basically providing MCP server for AI clients to. to run these UI tests. Mostly. on the older virtual machines. It can be not older virtual machines, but actual virtual machines. New refreshable machines as well, sir. Uh, for example, I don't update to macOS 27, because, uh… I expect some issues, but I use, uh, testing on macOS 27 using this, uh… a virtual machine system. And so basically the… Again, I have a question to the team in… In the light of a recent discussion of testing on order. macOS versions, for example, whether should I try to push it forward to, like, team-wide? So the idea… the idea is to be able, uh… again, we'll… And in the post-mortem. for the VS Code integration projects. So here you can see VS Code. Basically, it's running the Google browser. It can… run iOS browser as well, in simulator, and in addition, it can also run remote debugging, unlike Xcode, which had supported remote debugging. in a long time ago, but currently lacks the ability, so… Integrating these systems together allows, like, click one button. choose the virtual machine you want to run to test on, and it builds, deploys, and debugs in real time without any lags for library symbols transfer and other stuff. So it just works like you would do on your host machine, but in the virtual machine. So I wanted to hear opinions whether should be. try to adopt this team wide."
},
{
"time": "20:20:06",
"speaker": "Dominik Kapusta",
"text": "I can offer an opinion."
},
{
"time": "20:20:09",
"speaker": "Alex Martemyanov",
"text": "Nobody wants to."
},
{
"time": "20:20:09",
"speaker": "Dominik Kapusta",
"text": "uh… No, well, I mean… No one to be the only one commenting, but anyway. This will be the topic of, uh, of, uh, of the upcoming postmortem, uh, as well, that… The Apple engineering expectation of testing on older macOS version is essentially a dead low. We are supposed to test on older macOS versions, but we rarely do it. Perhaps for new features on macOS? I'm not sure. But certainly not for… Small… tasks. I don't think… well, I don't know, but I don't think we bother to test on all the ROS versions, every small version. Change to the UI, especially. And, uh… Because of that, if we had a way, and also we can't, we are unable to test in CI. So, if… I had a way to… Ask an agent to… run UI tests on a virtual machine. on an arbitrary OS version, that would be great. I would like to see the demo of that, actually. That would be awesome. And that is why we might be interested in adopting it. Perhaps."
},
{
"time": "20:21:41",
"speaker": "Alex Martemyanov",
"text": "Yeah, again, about the UI tests, correct point. So sometimes you want to run an agent reproducing an issue, for example, and it's not always convenient to upload it to CI, wait for the UI tests to be run. Look for the results, while if you run it locally on your machine, it will be blocked for 5 minutes, and do the stuff while you take a coffee. So this thing allows you to just run directly from the agent on the same machine in background and provide you screen recording with all this and the results."
},
{
"time": "20:22:22",
"speaker": "Jonathan Jackson",
"text": "Yeah, I mean, I think… You know, your point that our expectations are that we'd be testing on all versions that we support, but in practicality, I think almost nobody actually does that. And particularly with something like as old as Mac OS 12 where we don't have the hardware, we don't have like, most people don't have access to test it to your point, L. Um… I think I'd like to understand a little bit more about how the system would work, what kind of third-party dependencies there are, what it would look like to really set up and what it would cost. I think the idea of we would be able to test. On versions that we say we actually support is pretty appealing."
},
{
"time": "20:23:00",
"speaker": "Alex Martemyanov",
"text": "Okay, so probably the resolution here would be, um… So, first of all, I do use it as my self-made tooling, and uh… if… I can reach it to the point, I can make it to the point when you click a button, install the system, click a button, and it just runs. I think it would be worth. adopting at least as a selected auditory who can. have, uh, the means to testing, like, enough of RAM or some older hardware, uh, like, choose the early adopters and, uh, see how would we… expand it. And, uh, yeah, correct question by, uh, Federico about, uh, older ores. It's another topic that I wanted to raise during the post-mortem. During the incident, actually. Both for the incident, uh, that, uh, having… Maybe one dedicated machine, older machine, maybe somewhere that would run the UI test suite at least once per week for each release would be a great addition, even if it's like a physical machine somewhere. someone's office or home space."
},
{
"time": "20:24:28",
"speaker": "Jonathan Jackson",
"text": "Yeah, that's an interesting idea, too. I think… I guess I think that a proposal here that sort of lays out what a strategy for old testing would be that used this would be maybe a useful next step. Um, because then that would be a place that people could rally around, sort of solving that higher order problem of how do we actually make good on our promise of testing on the systems that we support. And it sounds like this would be one, but maybe not the only tool to consider, or maybe even as a combination. Does that make sense?"
},
{
"time": "20:25:00",
"speaker": "Alex Martemyanov",
"text": "Yep."
},
{
"time": "20:25:01",
"speaker": "Jonathan Jackson",
"text": "Cool. Okay, thank you. Interesting stuff. Sam, you're up next."
},
{
"time": "20:25:10",
"speaker": "SS",
"text": "Yeah, recently I have been chatting with some folks about being able to put Claude workflows in our CI. I talked about this with OT and they told us that they don't want Anthropic tokens being available in public repos. I've created a private repo to host the agents, uh, which is… Pretty bare bones right now. It lives here in the Apple Team Agents repo, it has CI set up, it has the Claude, uh, action set up. I have a workflow first for testing it, uh, just so we can make sure you can actually talk to Claude and back. Um, the only thing I'm waiting for is whether or not we should get a dedicated API key, because I've been told. Two different things from OT. So I'm just waiting to —. Get that sorted out. I think we should get a dedicated one. once we've done that, yeah, we can start doing things like an automation to clean up feature flags and such, like Fernando's, uh, proposed. So, uh, I'll post to Apple Diary once that's ready, but I think you'd be… if you do want to start building automations in this now, like, feel free, uh. As long as it's, you know, not super expensive. Pete, done."
},
{
"time": "20:26:19",
"speaker": "Pete Smith",
"text": "Yeah, thanks, Sam. This, this looks really cool. Just because I've seen, um, like, there's a few different conversations. There's a conversation with this, and there's the Bitrise, you know, running, um. uh… Agentic stuff on Bitrise as well. How does it all fit together? Like, I think I understand it, but, like, say I wanna… say we wanted to, you know, uh, build our feature overnight while we're in bed, um… How could we use this to do that? Or can we?"
},
{
"time": "20:26:43",
"speaker": "SS",
"text": "This is not that. This is definitely not that. This is not like the development environment thing. Yeah, these are not like the development machines. I really just expect these to be like GitHub Actions workflows that just do helpful things with Claude. Uh, and we just need a place to put those. Like, if it weren't for the API key limitation, this would live in the monorepo."
},
{
"time": "20:26:56",
"speaker": "Pete Smith",
"text": "Yep. Yeah, yeah, I guess, I guess what I'm wondering is, so, like, yeah, exactly, we can, we can hit Claude and, um, but, you know, Claude can't, well, build for us, so, like, well, build and check that it's actually working, so where would… say, say even, like, removing feature flag, where would that. On the PR, at the PR station."
},
{
"time": "20:27:17",
"speaker": "SS",
"text": "Yeah, this is something that Fernando and I was talking about, about doing some kind of coordination between these repos where the monorepo would talk back and forth, do the things that it needs to. This can create a branch. The monorepo can then do the actual testing. Yeah. Right now, I'm just using these for, like, dependability analysis kind of problems, or planning on anyway, which I have a demo for coming up soon."
},
{
"time": "20:27:33",
"speaker": "Pete Smith",
"text": "Okay. Yep. Cool. Yeah, cool. Thanks."
},
{
"time": "20:27:44",
"speaker": "SS",
"text": "Dominic."
},
{
"time": "20:27:46",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm, uh… one of the limitations here is that GitHub Actions workflows are limited to 6 hours of runtime. So…"
},
{
"time": "20:27:53",
"speaker": "SS",
"text": "Also that, yeah."
},
{
"time": "20:27:54",
"speaker": "Dominik Kapusta",
"text": "Yeah. And also, it's, of course, non-interactive. Um… Which is why we're currently trying to figure out if Bitrise… or Bitrise or not, but anyway, looking for some infrastructure provider for, uh… macOS machines that could run Agentic workflows and be… and offer. interaction with them, right? So, uh… Bitrise RDE remote. development environments is one of the options there. Um… That is in progress. For now. They also… it's also quite a fresh feature on their end, and they have some bugs there that we're trying to resolve right now. And we have a CloudOps team member on that as well. the side of… Connecting them to ClickHouse or Sentry. Yeah, so… We'll see in some time."
},
{
"time": "20:28:58",
"speaker": "SS",
"text": "Yeah, yeah, to Dominic's point, like, that problem is much bigger than what this repo is. This really is just, I want to be able to run Claude on an automation, like I currently do on my own machine, and I'm just sick of doing it on my machine. I just want to push that up to GitHub Actions. Have it run on its own, and… Show up with PRs and Asana tasks occasionally, so. Okay."
},
{
"time": "20:29:19",
"speaker": "Jonathan Jackson",
"text": "So the limitations here are that it can… It can inspect code, it can run as an agent, but it can't build and run, so it would… prospectively submit a pull request, and then CIA would tell you whether it did the thing or not."
},
{
"time": "20:29:32",
"speaker": "SS",
"text": "Yeah, the idea that I'm thinking here is that, yeah, like PRs would go over back to the monorepo. This thing would open PRs against the monorepo. And then CI would do its thing over there. Yeah."
},
{
"time": "20:29:38",
"speaker": "Jonathan Jackson",
"text": "Right. Yeah, and if we needed to inspect it from there, we could pull a branch and do whatever else we needed."
},
{
"time": "20:29:46",
"speaker": "SS",
"text": "Yeah."
},
{
"time": "20:29:47",
"speaker": "Jonathan Jackson",
"text": "Okay, cool. Definitely sounds like a good step, even if you're not trying to solve everything all at once, which is reasonable. You're the next topic as well, Sam."
},
{
"time": "20:30:00",
"speaker": "SS",
"text": "Oh, is this the demo? Probably should have just done this all at once. Yeah. So one of the things that I."
},
{
"time": "20:30:04",
"speaker": "Jonathan Jackson",
"text": "Oh, before you… sorry, if you're doing demos, before we get into demos real quick… Uh, we had a note here that we were gonna actually record demos. Um, but we haven't ever done that. Mostly people have opted out of wanting to be recorded, so I wanted to just check in since we have 3 demos here. do we want to record these? Should we rely on the… just the transcript summaries at this point, and whatever tasks people have written? I'm kind of okay either way. Um… I don't know. I don't know that we've ever recorded a demo."
},
{
"time": "20:30:35",
"speaker": "Pete Smith",
"text": "Alessandro. Alessandro is waiting for his Wednesday morning. Won't be the same if we don't record our demo."
},
{
"time": "20:30:39",
"speaker": "Jonathan Jackson",
"text": "Right. That's the question, right? I know, yeah, it's like this is sort of a hard way to do this. So, Sam, would you like me to record or not?"
},
{
"time": "20:30:51",
"speaker": "SS",
"text": "I mean, I've already shown this to Alessandro, so I don't think he cares. Yeah. Up to you. I'm good either way. I remember. Don't worry. This is a super quick one anyway, just to show the initial problem that I'm trying to solve with… with a repo like this. Let me share my screen. Um, so I have, for a while, wanted the other half of the flaky tests project. Right now, we have a flaky test project, which keeps track of, uh, you know, tests that are failing. Um… I have traditionally been more interested in the problem of what are the workflows that are failing, uh, and why, because these things were just, like… this stuff comes up a lot, like, during Xcode upgrades in particular, so… This is something that is being used by Claude to pull the monorepo, get the actions, go and look at the code, figure out what's causing a problem, and report back and give a little write-up about what's going on. Um, the idea being that eventually you could then move something into this ready-to-fix section, and the agent would then go and actually open the PR later. Um, you know, this is just moving a… moving an automation that I've had on my machine is like a daily, like, 10 AM workflow for a while. and just putting it remotely so I don't have to think about it anymore. Which is the ultimate goal. So yeah, this is the kind of thing that I'm trying to do with this repo. Um… As an aside, OT is kind of working on… something along this as well, which I learned about as I was setting up this repo. They are setting up this template, which lives on Dub, for what it's worth, for these kind of analyzing report workflows. Umm. So that might be interesting if you are needing like access from things within the system already. Uh, like, I think Lucas is currently looking at getting that thing to have sentry access and all this kind of stuff, so… Yeah. Go check that project out if you're interested. That's it."
},
{
"time": "20:32:48",
"speaker": "Jonathan Jackson",
"text": "Awesome. Thank you. Pete, you're next."
},
{
"time": "20:32:57",
"speaker": "Pete Smith",
"text": "Yeah, thanks. Yeah, this is in the demo section. It's not really a demo, I guess, but just wanted to share. I'll speak a little bit about, um. ASTAC, so I put a link in… a link into the chat there, so I'm sure people have heard… of… PSTAC, or maybe people have heard of PSTAC. I'm going to just share my screen. So if you haven't, um… Pstack is a plugin created by an engineer at Cursor or SpaceX. It's basically just a set of skills that this engineer found were very good. at, um, fixing bugs, implementing features. So they created the PSTACK plugin. What ASTACK is, is basically just a port of PSTACK. So PSTACK was. built for cursor. So it has a lot of built in you know, instructions in terms of cursor models and how they work so forth. So I just. Ported PSTAC, uh, over… To, uh, ASTAC, um… Basically replacing any of the cursor references with Cloud Code and Codex references. So what AStack is, is a plugin that you can use in Codex or Cloud Code. It's like it sounds very abstract. It's not. It's really just a. A set of skills, a set of playbooks, some defined principles. And they all work together to what I found to just to produce good output. um… So I'll just, I'll talk a little bit in a moment about how ASTAG works. So how it's set up at the moment, you can see on the left, I just have it there under my public, under my own public repo. But if anybody wants to try it out, I would encourage it. You can see like I didn't do a lot of work here. I really want to undersell this. asked an agent to port this over. So take PStack, port it, make sure it works with Cloud Code and Codex. The most work I did was creating that logo you see on the left of the screen, so that's where all my creativity went into. Um… But yeah, you can go here, you can grab the plugin, you can install it in Cloud Code. And you can try it out. I'd recommend trying it out for… for bug fixes, even like small features that are well defined. So, you know, the evidence, like any evidence I have is just anecdotal. I've just found these particular set of skills, these set of playbooks and the principles that are defined just produce very good output. Again, anecdotal. I haven't measured this. I also think it seems to do it at lower token usage. But again, I haven't measured it. So how it works, how ASTAC or PSTAC work is, you know, you install the plugin, it sets up a hook, so at the start of your sessions, the agents are aware that ASTAC is there. And if you say, hey, build this feature or fix this bug or whatever, you can explicitly say. Enter potato mode. But that's actually part of the hook. The agent will know, oh, if you give it a feature or a bug, it will enter potato mode. All that is like a top level skill, which is basically a router. And depending on the task that you give it, like fix this bug or implement this feature. You will go and find the right playbook and follow that playbook and in the playbook. That would reference what skills to use, et cetera. So. again, you know, there's nothing, like, there's nothing magical here. I mean, there's been other plugins that have been very popular. I was talking to Fernando earlier, and we talked about… was it the Superpowers one? I think was another popular plugin. So things like this will probably be, as I was speaking to Fernando about, they'll probably be, can, you know, eventually end up in the harness. Probably won't need plugins like this at some point. But at the moment, this is something I'm using daily. And I find it very beneficial. It just results in really good output. So I would encourage people to try it out. Like, what what, you know, we've seen probably saw the post from Sebastian, from OM. He's creating, like, auto, which is their version of pstack. He just took pstack. And ported that and kind of made it very specific to Duck AI. That's like the the OM version of Pete's group. So if ASTAC, if people find it useful, we could basically turn that into like the Apple version of PSTAC, Apple team version of PSTAC. and… that's something we could do. So yeah, I would just encourage people to try it out, if you're interested. There's an Asana task there that I posted, and you can give any feedback, and if people want to. People find it useful and want to contribute and make it better. We can do that. It's under AI enablement AOR. I spoke for a long time, if anybody has. Sorry, I shared that artifact. Sorry, key. I didn't go through all this artifact."
},
{
"time": "20:37:59",
"speaker": "Pete Smith",
"text": "It's linked in… The Apple Weekly Task, so you can go and look at that artifact, it explains at a very high level how it works. Again, it's not magic, it's just a skill, a ruler, lots of other skills. Sorry, my dog is barking. I don't know if you can hear my dog, but. He's over there barking at me. That's very low. That's it. If anybody has any questions, you can ask me questions, or you can ask me questions later. Jane, sorry, your hand up."
},
{
"time": "20:38:35",
"speaker": "JF",
"text": "Yeah, sorry if you said already and I missed it. What changes have you made over the original piece, Doug?"
},
{
"time": "20:38:42",
"speaker": "Pete Smith",
"text": "Yeah, so… Oh, I'm sorry, it looks like. Okay, dog went dead. Um, yeah, that's why I wanted to undersell it. Like, I didn't, I didn't, I didn't do anything. So, uh, I created that logo. What, what, what I did, or what the agent did, was just port it over, support Pstack over, um, for Cloud Code and Codex. Like, the original Pstack has references to Cursor, and how Cursor. Works. So I just ported it over, so it works in… Um, codecs and cloud code. I didn't add anything additional yet. Um… But the idea will be we can add things if we find them useful. We can add Apple-specific things. If we find them useful. So yeah, no changes really. Sorry, one more thing, James. Thanks for reminding me. I'm going to reshare. Sorry, everybody. Very annoying. I'm going to reshare. So a good question. Like, PStack is being continuously updated. So I have a scheduled task that runs every Monday, looks at the latest PStack, and consumes the latest changes, and, like, ports over the latest changes. So I keep it up to date. So I look at the upstream and keep. a stack up to date. But that's other than that, I just I just port it. I don't make any other changes. Like, you know, of course, there's a chance it's not ported well. It might not work properly, but the intention is it's just a direct port."
},
{
"time": "20:40:09",
"speaker": "Jonathan Jackson",
"text": "Cool. Thank you, Pete. Paul, I'm protesting."
},
{
"time": "20:40:16",
"speaker": "Pau Ballart",
"text": "Yes, thank you. I'm going to share my screen. This is pretty much. a demo that I owe you of the snapshot testing. So, quick reminder, this is already available on iOS, not yet on macOS, because we are waiting for macOS 27. runners on big drives on the CI. on, uh… Yeah, pretty much. It's a package that has a very nice README explaining of it, what I will show today. So you can read it or tell your favorite agent to read it. But it has like requirements, how to use it. A bunch of examples for both iOS and macOS, even though, as I said, macOS. is disabled. But let's do a bit of an example. if I find the Xcode that just crashed, apparently. Ah, it's here, yeah. So, uh, how does it work? We start with the bill. Maybe, or maybe not, you will have previews. That is the new, like, hashtag… preview macro but for a snapshot so I created this one you don't need to use previews but it's just if you use them it becomes handy so there is this new preview provider that's the system. protocol, then if you conform it like this, so pretty much. You configure the different states that you want to have in the view. In this example, it's this segmented control. So there are two previews, one for each tab, let's say. You configure it here. So that's the model or the state of the view. And then you configure it here. So it will render one of the previews for each tab in this case. That basically gives you the previews here, but what is nice about it is that then you have the snapshot test. becomes basically a one liner or yeah one four liner uh but yeah just one call because it reuses the same previews that you refine it and then uh this is just a unit test like. Any other that we have. that runs the test. And this. Basically, you can configure it in different ways, for example. Here, if you want, um… to have a preview, but you don't want to snapshot it, because it's not needed. You have different. uh parameters here in this um. Let me show you. In these configurations, so there is… a scope where you can say, I want just for previews, just for snapshots, or for all of them. And then, um… in the test, you can snapshot in a different set of, um, configurations. So, in these asset snapshots. But everything is here in this package. We have different things. We have the different strategies. If you want to snapshot, for example, iPhones, iPads, all the combinations, just a single screen or a custom. Uh, size? And then you have also. the different sizes of components that you can have in an app, right? Majority of things are the screen, but you can also test some intrinsic content size, bottom sheets, or just any big size that you want. So all of that has, like, default parameters. In this example, for example, it's just, you know, normal screen, and I want to judge a snapshot in that mode, because that screen doesn't have light mode. So, it would work like this. And this is a unit test, it runs super fast, and uh… It passes in less than a second. how it works when you change something so let's say remember we have this previous let's say now i change this uh. this view. No, there is a design change, so we have this title here. If I run the tests, now they will fail. I will show you how it looks like in Xcode. So pretty much, issue recording, blah blah blah, does not match reference. And then, you can go here in your tests. We see the test that failed, and if you double-click, there is this gallery. That basically is showing us the reference, the failure, and the difference. So you can preview it like this. That's the original one. And then the new one that got recorded is this one with hello."
},
{
"time": "20:45:21",
"speaker": "Pau Ballart",
"text": "So you can see a diff that it's generated. Basically, you see everything is moving down. Um… So here it can happen two things. It's a real failure and you need to fix your UI, or it's a design change that is… expected, and you want to re-record the test flight, because this is now the new correct design. To do it, you have different ways. Here, there is a record Boolean. You can pass it to true. But at the same time, instead of changing code. If you go to the folder of the test. In in in Git you can let me show you. in a… in another screen. You can just delete the reference image in the file system. So that's the submodule that we have. In the, um… With all the snapshots. So if you go there and delete the file, it will recreate it on top of it. Um, so yeah, basically you have these two options. If there is no original file in the file system, it will just create it right away. If there is an existing one, it will do the comparison and so on. So the easiest usually is, um, to just remove. the image and re-record it. But let's say that… This works, and you upload a PR, and it fails in the CI. So how does it look like? Pretty much the current PR checks that we have for iOS, we'll report them here with the faillet, and it generates an HTML report, which is this one. that, uh… creates the same thing that we see in Xcode, but in the CI. So if you see a PR failing, you don't need to download the artifacts and so on. You just have to open this, and it has, like, these drop-downs. with the same concept, like the reference, the failure, and the diff. Um, so that's… A bit what I wanted to show. Then, um… So the snapshots live in a submodule, as you probably know. So it's a different repo. It's these DuckDuckGo Apple browser snapshots. And it just contains the PNG files. So that is this. Orchestration, if you want to run when you create snapshots, you need to open, let's say, two PRs. But there is a script that handles everything. So what you would do is here when you record your new snapshots. Maybe I can do it really quick. Just a second. I will. Show you exactly what I mean. So we have the submodule. Snapshot references. I'm gonna remove… The, um… Tests for this one. which is the scan QR code test. So I remove it from the file system. Okay, from this folder. And then when I record it or when I run the test, it will record. So first time it fails, but now it says no reference found on disk, which is fine. And then second time it runs, it already has the references and it passes. Okay, so now we want to open the PR, uh, and we can see that the snapshot reference module has the changes. Again, old and new with a new title. So there is a script in the scripts folder. around doo doo doo scripts. called Open Snapshot Zoom Module PR. You just run this over there, runs it, and it will open the PR, so commit, push, open PR, and so on. Um, and then once in your main branch or main PR, there is a new label that you can tag. Uh, let me show you here. Merge the snapshots. So this will merge the snapshots PR and update the pointer and so on. So, it's these two extra steps. You can do it manually, but, uh, the easiest is once you record it, and you have the changes here in Git, you just run the OpenPR, uh… script, and then once your main PR is approved, you can, uh, just use this label to merge the… the snapshots PR. So you…"
},
{
"time": "20:50:21",
"speaker": "Pau Ballart",
"text": "It's a bit of extra work, but I try to minimize it and automate as much as possible, so… That's how we currently have it set up with these failures and so on. Any questions so far?"
},
{
"time": "20:50:37",
"speaker": "Dominik Kapusta",
"text": "Yes, this is amazing, and do we have a documentation for that in the Apple documentation project?"
},
{
"time": "20:50:44",
"speaker": "Pau Ballart",
"text": "For the CAI part, you mean?"
},
{
"time": "20:50:46",
"speaker": "Dominik Kapusta",
"text": "Yeah, for…"
},
{
"time": "20:50:47",
"speaker": "Pau Ballart",
"text": "Or in general."
},
{
"time": "20:50:48",
"speaker": "Dominik Kapusta",
"text": "In general. You've mentioned that there's a script that simplifies the work, and that would be great to have it as a task in the Apple Documentations project, if it's not there yet."
},
{
"time": "20:51:00",
"speaker": "Pau Ballart",
"text": "Okay, I will add it, yeah. Yeah, so the biggest documentation right now is the README, but I understand that it's not, uh…"
},
{
"time": "20:51:02",
"speaker": "Dominik Kapusta",
"text": "Awesome. Thank you so much."
},
{
"time": "20:51:09",
"speaker": "Pau Ballart",
"text": "in the best place. I mean, it's useful, but…"
},
{
"time": "20:51:10",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm."
},
{
"time": "20:51:12",
"speaker": "Pau Ballart",
"text": "Yeah, I will let it also in Asana."
},
{
"time": "20:51:16",
"speaker": "Dominik Kapusta",
"text": "Thanks so much."
},
{
"time": "20:51:16",
"speaker": "Jonathan Jackson",
"text": "Very cool, thank you, Pao."
},
{
"time": "20:51:20",
"speaker": "Pau Ballart",
"text": "I have one more thing to share, which is… So two things. Why is this useful, right? Like, because, okay, we can add a snapshot test and so on. There are three things that I see that are important. First one is PR reviews. Since now the two PRs are linked, it makes it easier to review changes, right? You read UI code of SwiftUI, for example, and you see paddings, frames, blah, blah, blah. Seeing a screenshot helps a lot, so now it would be easy to compare side by side, because you will have here, um… For example, this one. The… the file changes. Directly in the… well, it's not the… This one needs a rename. And you will have the file changes on GitHub to review side by side like this. So PR reviews are better than. I think it was already mentioned we can. think about our UI tests, and if we have UI tests that are asserting. Just how things look like. It's a good candidate to replace with. with the snapshots. Um, so… I will open a proposal at some point, but the idea is… Since UI tests are flaky and snapshots and units. are less flaky and run quite fast. We might look at opportunities to move some of these tests and with a good combination of unit and snapshots. Yes, we are still missing the navigation part of I tap this button and this other screen opens. But yeah, it's up for discussion, but I think you have already a good coverage of a feature, right? And the last thing is ship reviews, because here in this other repo, it's becoming basically like an S3 bucket of data. PNG files. So when you prepare your ship review, if you have used this, you don't need, uh… to regenerate the snapshots and so on. You would just even link it from here or pick them from here. And that's just a starting point. We can improve it with future ideas, like we were talking about different languages. So how we could snapshot test different languages, different dynamic sizes for accessibility, like a large text size and so on. Even, I don't know, when the snapshots PR is open. with some automation, check the original Figma design, and compare it, and there are, there are, um… ways to improve this. So this is just a starting point. And last thing I want to mention, it was part of the tech design to track adoption of this. So far, I'm the only one contributing, which is why I'm doing this demo as well. But I created with Claude an automation that every week checks the repo. It's very easy, because we can just go to the insides of this, um… of this repo and see contributors, but also just check, uh, the asset and snapshot, uh, usages. So this is a dashboard that I shared, uh, within DuckDuckGo. It's updated every week, and basically we can see how. how it grows over time. Um… So yeah, if you fancy, please use it. And if there are any issues, let me know. I'm like the unofficial or official DRI of this. Happy to be on top of it if it's causing issues as well."
},
{
"time": "20:54:59",
"speaker": "Jonathan Jackson",
"text": "It's really cool, Pat. Thank you for sharing. Yes."
},
{
"time": "20:54:59",
"speaker": "DR",
"text": "Good work, pal."
},
{
"time": "20:55:04",
"speaker": "Jonathan Jackson",
"text": "Very cool. We are now at 5 minutes to the top of the hour. Dominic and Alex, you both have postmortems on the list. Do you want to… run those now, understanding we'll go past time, and anybody who can stay is welcome to stay or not? Or would you rather find another time for those?"
},
{
"time": "20:55:24",
"speaker": "Dominik Kapusta",
"text": "I'm fine running it. It should also be short, but not sure about Alexa's one."
},
{
"time": "20:55:33",
"speaker": "Alex Martemyanov",
"text": "Probably can wait till the next Apple Weekly."
},
{
"time": "20:55:37",
"speaker": "Jonathan Jackson",
"text": "Okay."
},
{
"time": "20:55:37",
"speaker": "Alex Martemyanov",
"text": "I think it was waiting for a year and it didn't wait another week."
},
{
"time": "20:55:41",
"speaker": "Jonathan Jackson",
"text": "All right."
},
{
"time": "20:55:42",
"speaker": "Alex Martemyanov",
"text": "Thank you."
},
{
"time": "20:55:43",
"speaker": "Jonathan Jackson",
"text": "Thank you, Alex. Um, then, Dominic, why don't you go ahead and get started? Anybody who's not interested in Dominic's incident post-mortem, obviously, is welcome to drop. If we run a little bit late and you need to be somewhere else, that's also okay to drop. And Alex, I'll keep yours on the agenda for next week. Thank you."
},
{
"time": "20:56:01",
"speaker": "Dominik Kapusta",
"text": "Thanks. I've dropped the link in the agenda as well for the incident postmortem. What happened last Monday is we released the app that was crashing on macOS 12. And, uh, the app was out… well, uh, so the app was out for, like. 3 hours before we, uh, realized that there is a crashing scenario on macOS 12, and then that was handled real quick, uh, with app store rollout stopped. And, uh, Sparkle rollout stopped, uh, as well at some point, um, and the fix was released, actually… well, it… It. Well, almost immediately on DMG, and the next day on App Store, because of the review time. Um, but, uh, how it happened? So, it happened, uh, because we had a change to, um, the save credentials pop-up, which shows up every time you're offered to… you're being offered to save a password. Um… On macOS 12, um… And that change was due to dropping a storyboard, replacing a storyboard with a code-initialized view. So what didn't go as planned? This, uh, change was not tested on old OS versions before merging, and it was strictly macOS 12 issue. Uh, like I mentioned before in this call, we had that engineering expectation in place, but we're not really enforcing it for every change. There's no way of enforcing it, uh, and there's no way of. testing, um… all those versions in CI, so… that's why it happened. Really. Uh, the other thing is, uh, we didn't know about the crash, because, uh, I overlooked it in Sentry. I was the release DRA and I overlooked it in Sentry. There was a single crash on macOS 12 there. Uh, that I treated as noise, and I went ahead and released the app. The sentry summaries weren't generated on that day, because we had another… Whoopsie. Um, the week before, when we updated, uh. Well, some updated the model version and I reviewed it and approved it. and we merged that change, and we updated the model version, but we didn't update the SDK version, and the old SDK didn't… wasn't recognizing the new model, and it failed to… collaborate, so we didn't generate summaries. Um… So that's the other… the other thing. Uh, when the… but! When the summary was generated, uh, it clearly pointed out that there is a crashing scenario on Mac OS 12, which started the incident. A week of internal testing didn't catch a relatively easy-to-reproduce crash. It was a 100% crashing scenario, which wasn't caught. Because we don't have testers on macOS 12. Well, apparently we have one, because we got this one crash at some point. I don't know who it is. I'm…"
},
{
"time": "20:59:33",
"speaker": "Alex Martemyanov",
"text": "Yeah, and by the way, there was another kind of related issue about the crash on Intel machines. It's not directly related, but yeah, it was close."
},
{
"time": "20:59:41",
"speaker": "Dominik Kapusta",
"text": "Yes, another one, exactly. We also don't have testers, or many testers, on x86. architecture. The App Store review took 15 hours, which is rather long for an expedited review, but also there's nothing we can do about it. At least it got in the queue… I mean, it got in the review pretty quickly after requesting a completed review. What went well is that the sentry summary that was eventually generated, um… Clearly identified the crash, and suggested addressing it, and the fix was simple, quick to prepare and test, it was just assigning an initial frame to a view. And the hotfix release automation workflow less at this time. It's always important to point this out, because… We only talk about CI when it's not working correctly. Despite the long review time, we only had 37 crashes in total and only 9 affected users. That's all. for action items and DRIs, we actually, uh… there was an action item to update agent's instruction prefect… essentially update prefect to ensure that Claude agent SDK version is… compatible with used models. Uh, Sam has handled it, and, uh, well, there is a code command right now to, to update the SDK version whenever you update the model version. Um… The other topic that's not actually mentioned here is what to do about testing on older OS versions, but this is something we will be handling separately through Alex's work, mentioned earlier on the call. And… That's it. Finally, I created an incident task through the form. Asana forum, and marked the incident as high, because it's a crashing scenario, we need a hotfix, and an SRE person joined the call, and we talked a little bit, and he, um… Explain to me that if it's a one-person rollout. It's not a high severity incident, and we dropped it to medium, and they dropped the call. And that's it. And, um… That's something to keep in mind for later, for next incidents, when they are only starting rolling out, we may not need SRA help there. This is all I have."
},
{
"time": "21:02:09",
"speaker": "SS",
"text": "Regarding the action item, are you happy enough with just having the code comment now that reminds about the Claude SDK?"
},
{
"time": "21:02:15",
"speaker": "Dominik Kapusta",
"text": "I think so."
},
{
"time": "21:02:16",
"speaker": "SS",
"text": "you know, it's… it's not bulletproof, like, what I… what I wanted to do was to just ask the Claude SDK, what models do you support, and check that it's in the list, but it only includes… yeah, it doesn't include all the actual supported models."
},
{
"time": "21:02:18",
"speaker": "Dominik Kapusta",
"text": "I think, yeah. I saw that, yeah."
},
{
"time": "21:02:28",
"speaker": "SS",
"text": "Eh, maybe the comment's okay for now. I tried to make it very obvious what to do and how to confirm this."
},
{
"time": "21:02:32",
"speaker": "Dominik Kapusta",
"text": "Yeah, I mean, that's okay. Also, that comment would show up, because it's just very close to the line that is changing, it will show up in the GitHub UI when reviewing the code, so it should be fine."
},
{
"time": "21:02:37",
"speaker": "SS",
"text": "It's right there. Yeah, the only way I was considering extending this was to just have a GitHub Actions check that looks for model changes and adds a comment, GitHub Actions comments. But I would want to do this for all of Prefect. Whatever. I'll look at that."
},
{
"time": "21:02:56",
"speaker": "Dominik Kapusta",
"text": "Yeah, yeah. Should be fine. Okay."
},
{
"time": "21:02:58",
"speaker": "SS",
"text": "Okay."
},
{
"time": "21:03:00",
"speaker": "Dominik Kapusta",
"text": "Thank you. Thanks for handling that, Sam. Alex?"
},
{
"time": "21:03:05",
"speaker": "Alex Martemyanov",
"text": "Yeah, I got a proposal in… I got it related to post-mortem of the VS Code, but I think it more suits here. What about adding… updating our process to require adding UI tests in addition to renting some older Mac to run older OSs, but make a requirement to the process to cover any UI change. with a UI test. Even if it's a fix or a quick addition in the uncovered region, especially having all the Agentic workflows, it may be a quick and cheap option. I mean, cheap to add. maybe not to maintain. But it adds, of course, it adds extra cost for the runners. Or maybe we could have like a test suite number two that runs weekly, for example, and not daily."
},
{
"time": "21:04:11",
"speaker": "Dominik Kapusta",
"text": "I actually think it's… Some Windows team uses something similar. whenever they change UI, they add UI tests, and they have plenty of UI tests, and that's another problem. I believe, but… Yeah, we could… We could discuss it, I guess."
},
{
"time": "21:04:31",
"speaker": "Alex Martemyanov",
"text": "Yeah, because, uh…"
},
{
"time": "21:04:31",
"speaker": "Jonathan Jackson",
"text": "I think that's what we're considering. Sorry, go ahead."
},
{
"time": "21:04:35",
"speaker": "Alex Martemyanov",
"text": "Because obvious, like, obvious… thing that could fix it is, uh, like, QA, which we are missing, for… everybody knows for… for why, for what reasons, uh, but we have a lot of, uh, supported platforms, a lot of supported macOS versions, and, uh, it's, uh… Like, uh, it's impossible to… make the requirement as in the mentioned. Uh, process, like, to test all the supported macOS versions, because not everybody even have all these machines that, like, I have the older one, but it's not DuckDuckGo, it's my personal machine. And, uh, I can test it, but it takes time. Uh, and nobody… nobody does it, frankly. And we have no QA, and it's impossible to guarantee the quality in such conditions. So, maybe it's required. It should be a required condition to… to… raise the UI test coverage, the end-to-end coverage, so we can validate we are actually producing quality UI tests. Stuff."
},
{
"time": "21:05:50",
"speaker": "Jonathan Jackson",
"text": "Yeah, I think that's worth considering alongside the virtual machine testing stuff that you were talking about earlier, right? I mean, we've known for a long time that we clearly have testing gaps, especially on older versions and older hardware. And… To this point, I think we've just accepted that as the way it is and every now and then something like this goes wrong and we deal with it. um… But we should definitely think about whether there's a promise we're making to our users there that we're not able to fulfill properly. And I think certainly that's true right now. The question is, what does it take to do better at that promise? So I'd love to see some proposals around moving some of these pieces forward."
},
{
"time": "21:06:32",
"speaker": "Dominik Kapusta",
"text": "All right, that was all for me. Thank you very much."
},
{
"time": "21:06:38",
"speaker": "Jonathan Jackson",
"text": "Alright, and thank you. Um, so, Alex, we're gonna wait till next week for your other postmortem. Thank you for your flexibility there. And thank you all who stayed to finish that out. I appreciate it. And I look forward to seeing you again soon. Bye, everyone."
},
{
"time": "21:06:54",
"speaker": "Alex Martemyanov",
"text": "Thank you. Bye."
}
]
}
@@ -15,3 +15,137 @@ source: "https://us01mynotes.zoom.us/gBBa-iiUQLycw55WRV1tnw"
- **20:03:14 · Jonathan Jackson:** Hello, everyone. Let me go ahead and get started. Quick runs through our scheduled rotations as usual. This week, iOS triage is L, followed by Bartek, and then Brindy. Mac OS triage on is on this week by Jorge and then Rachel. Uh, for iOS release, Sam, you're on duty this week, followed by Bartosh, and then Mihao. And for macOS release, Dominic was last week, hasn't closed that task yet. Tom, you're on this week, followed by Juan, and then Joseph. You all may have also seen, I published our… Uh, release schedule changes around the winter holidays, uh, last week. Um, next step there is for me to look at out-of-office stuff and start trying to coordinate and… uh, coordinate swaps and coverage during that time when a lot of us are gonna be out, so keep an eye out for that soon, I'll get that. Um… I'm also using the Zoom transcript feature on top of Zoom summaries, and I'm gonna feed the transcript to Claude and see if we get a better summary that way than we have been out of Zoom's summarization AI. Uh, so… And I'll share maybe both, or I'll see what it comes up with, and I'll share an update after this meeting about what we ended up with there. Um, and one final reminder, next week, uh, is performance review week. The process starts with self-reviews happening on Monday. And then there's a few days of CAs writing reviews, and then a few more days of calibration after that. um… But because there's really only one day in that official schedule dedicated to self-eval writing, I suggest y'all think about starting this week. If you're anything like me, I usually need to write it, and then think about it, and then come back and edit it heavily, and then think about it, and then write it again. So I would suggest giving yourself the extra time if you need to do that. to get started early. Tom, what's up?
- **20:05:23 · Tom Strba:** Just a small note, I checked the macOS release rotations. Yes, there is not finished one rotation that's Dominic's, but this week is Diego. Right? Is that true?
- **20:05:36 · Jonathan Jackson:** Mm, got it.
- **20:05:37 · Tom Strba:** And I think I'm next week. Because I almost got a heart attack when you said that I am…
- **20:05:40 · Dominik Kapusta:** Yes, this week is Diego. And sorry for not closing my task.
- **20:05:41 · Jonathan Jackson:** Okay.
- **20:05:45 · Tom Strba:** that I am this week.
- **20:05:45 · Jonathan Jackson:** This week… Why is Diego… I don't see a task… this is a macOS release we're talking about, right?
- **20:05:52 · Tom Strba:** Yeah, I think Diego maybe marked it as complete in the beginning of the week, because there's just, like, triage…
- **20:05:57 · Jonathan Jackson:** Yes, you're right, Tom, your block is the 26th to the 30th, because that task is missing, I didn't see it, I wasn't looking at the dates, I was just reading the list.
- **20:06:04 · Tom Strba:** That's okay. Just wanted to be sure.
- **20:06:07 · Jonathan Jackson:** Okay. Diego is responsible for the release this week. It sounds like he's actually doing that. Is that right?
- **20:06:08 · Tom Strba:** Perfect.
- **20:06:14 · Jonathan Jackson:** He knows. Okay, cool. Thank you.
- **20:06:14 · Dominik Kapusta:** That's right.
- **20:06:18 · Jonathan Jackson:** Um, no problem. Okay. Anyway, think about starting your self reviews this week. If you feel like you're gonna need more than a day to knock it out. Bartek, over to you.
- **20:06:31 · Bartek Waresiak:** Yep, I will be stepping down as IS app DRI. Jacek will take the primary role, and Brindy will take on secondary role. So, yeah, if there is IS drama, if there are IS issues, if there are any urgent things. Go to them! And thank you very much.
- **20:06:57 · Jonathan Jackson:** All right. Thank you. An, you're next on the agenda.
- **20:07:08 · Anh Do:** Oh, that was quick. Yeah, so in OK, there have been a few projects that involve native changes required as part of the front-end-led projects. Um, so the background is that they, uh, want to contribute some PR, and, uh, um… AI assisted Pi, of course, and then what have been working for us lately is like depends on the size of the task like I would be the one to like either. Dri the change that they are they want to make, or like they prepare the Pi, and I do a thorough review of that. So and now we want to kind of do this more regularly. And so there was a need for some kind of like guidelines that we can give to contributor from outside the apple team. So I was just starting like a small task to basically collect ideas from people. And if you have anything that we already have somewhere, maybe I could get put in. And so. it becomes something that we can point other people to when they want to contribute to the Apple codebase to ensure our standard and make sure that, like, everything is being done the way that we want. So that's about it. Nice.
- **20:08:19 · Jonathan Jackson:** Cool, thank you. I just took a quick peek. I see you do mention the engineering expectations. I think that's a good source. We might also want to link… to the onboarding process. Not that they would need to follow all of it, but some of… that's basically our best source of, like, how to get set up with the codebase. So there's probably a little work to do to figure out how to have a slimmed down version of that that folks could follow. And I'm sure other people have other ideas as well. So thank you. Um… Luke, we have a non-Apple person lurking in our midst. Welcome. What can we do for you?
- **20:08:54 · Luke Andrew:** Hello. Yes, thanks for having me. Luke from SRE, for people that I haven't met before. Um, this is just a plea for generic Apple help. I don't want to, sort of, get all of your attention to focus on this task. We basically have… a looping client that seems to be sending, uh, requests once a second to us, uh, that is Apple, but not DuckDuckGo Apple, based on the user agent, and doesn't seem to be Safari either. Um… And it's cumulatively across lots of different devices, lots of different queries, sending in the region of 3 million searches a day. Which is substantial, not sort of catastrophic, but substantial enough searches that it's something that we want to deal with. Umm. And I don't really know where to go next to try and understand where it might be coming from or how we might try and reproduce it. So I don't want to solve that in this call, but I just wanted to bring your attention to the task. And if there's anyone who thinks they might be able to help, I'd really appreciate. a second pair of eyes, and pointed out that it's not even worth, with what we have at the moment, that we can, like, escalate this to Apple, because we just don't have enough, uh, information to get any help from them. So yeah, that's it. If anyone has any questions immediately or async, just pop them on the task. Yeah, that's all I have.
- **20:10:18 · BA:** Quick one, Luke.
- **20:10:18 · Jonathan Jackson:** This is not from a single client, but from a particular app version, potentially, is that right?
- **20:10:24 · Luke Andrew:** Yeah. Yeah.
- **20:10:24 · Jonathan Jackson:** Okay. You know, be scared that it was one client going crazy. Okay, um…
- **20:10:30 · BA:** Yeah, I was going to ask, what's the — we eliminated bots from the equation. Are we happy that it's not bots?
- **20:10:36 · Luke Andrew:** It doesn't look like bots. The queries all look human. The rate is really low compared with bots. The moment that I put in a block for it and it immediately stopped, like redirected away.
- **20:10:39 · BA:** Okay. Right.
- **20:10:52 · Luke Andrew:** It got, like, a 302 from deep, and then just immediately stopped, so that doesn't feel like… bossy behavior either. They normally persist a little bit and then give up. Whereas this was just immediately, it broke out of whatever loop it was in and stopped.
- **20:11:09 · Jonathan Jackson:** Interesting.
- **20:11:10 · Luke Andrew:** Uh, so don't all take a look, because that would be a waste of time, but if you think you can help, um, I'd appreciate a pair of eyes. I'm gonna drop off. Thank you all for having me.
- **20:11:19 · Jonathan Jackson:** Yeah, one last quick question. It sounds like you're treating this as something that definitely needs attention, but not an incident at this point. Is that correct?
- **20:11:25 · Luke Andrew:** Yeah, that's correct. It's been going on for… Based on… um, how we categorize queries for, um, like, ads perspectives. These get classified as a separate category based on user agents, so we don't send them to Bing and say, these are definitely good queries. Um, it's been happening for about a month. So it's, at the moment, not urgent. I'm gonna raise it with SRE, maybe, and see if we think it should be an incident that we just let run, but at the moment, that's not how we'.
- **20:11:55 · Jonathan Jackson:** Okay. Great. Thank you for the clarity there. Uh, and yeah, if anybody thinks they can help Luke out and figure out what's going on there, feel free to hop into the task. Thanks for coming. Moving on. Alex, you're first in the regular topics list.
- **20:12:16 · Alex Martemyanov:** Yeah, hey. I have several topics for today, including the VS Code integration postmortem to run later. And the first one goes with a proposal. The proposal is pretty short. And kind of related to the, uh, recent incident with Mac OS 12 crash. that we are not. Testing for macOS 12 and 13, I guess, because we are missing the infrastructure on CI runners. And the suggestion is pretty simple to extract the macOS UI tests target from the main macOS Xcode project, leaving it as a separate macOS project inside the. uh, Xcode workspace. So it will be available the same way it is now, and, uh, runnable. So only, uh, the only issue I can see for those who use, uh, the actual macOS Xcode project instead of the workspace. they would have to switch to another project to run the tests. So, I just wanted to hear if there is any concerns or objectives against it.
- **20:13:39 · Dominik Kapusta:** I think some time ago, we… someone asked… who uses or doesn't use Workspace, and people who didn't use Workspace were in a… In a minority, anyway, like, very few of them, so… I guess… I could move to the workspace.
- **20:14:06 · Jonathan Jackson:** I think it'd be good to ask that question in that proposal, at least more explicitly, and just give people a chance to chime in if they feel like that would be a hurdle. Um… Other question for me is, is there… should we think about the iOS side of this as well, and to match… structure, or is this really a macOS only question?
- **20:14:26 · Alex Martemyanov:** Okay. Maybe, I… Didn't think about it, actually. And the main concerns here is the compatibility. So we can reach macOS 12 compatibility, at least for some local runners that I'm going to present further. And the build times, so we have package fetching and building for every macOS runner that runs the UI tests and any of the dependencies. None of the dependencies are used during the runs, so it's a 10-second step for each runner that can be easily omitted, and so, yeah. And yeah, it's not related to the main browser targets, so there's no risks. Uh, and they're both, uh, U.S. Probably to think about it in the ER.
- **20:15:25 · Dominik Kapusta:** I think iOS is not…
- **20:15:25 · Jonathan Jackson:** I mean, I don't have a strong… sorry, I don't have a strong feeling there, I just felt like if we're gonna make this change, like, if it's gonna end up with different structures depending on the app, we should think about whether we really want that to be the case, or if we should do the other.
- **20:15:37 · Alex Martemyanov:** No, it actually shouldn't change any structure, any file structure, just the project placement.
- **20:15:38 · Jonathan Jackson:** Screwed up. Yeah, yeah, yeah. Dominic, I interrupted you. I'm sorry.
- **20:15:44 · Dominik Kapusta:** Ah, no worries, I just wanted to say that iOS is not affected by this at all, because… iOS doesn't need testing on various macOS versions.
- **20:15:51 · Jonathan Jackson:** Alright. So the limita… this is about dealing with a limitation that comes from Mac OS 12 build, particularly.
- **20:15:59 · Dominik Kapusta:** Yes.
- **20:16:01 · Alex Martemyanov:** And bill times.
- **20:16:01 · Dominik Kapusta:** I'm Bill Times.
- **20:16:02 · Jonathan Jackson:** Got it. Okay. thanks for pointing it out. Uh, like I said, I think you might want to give people a little bit more time to respond to async if they have… particularly if they feel like the… Workspace thing is gonna be a hurdle, but my guess is it's not gonna be a big issue. Uh…
- **20:16:22 · Alex Martemyanov:** Okay.
- **20:16:24 · Jonathan Jackson:** Next topic.
- **20:16:24 · Alex Martemyanov:** We can…
- **20:16:26 · Jonathan Jackson:** From you, also.
- **20:16:26 · Alex Martemyanov:** Perfect. To the next topic then. Yeah, so, uh, this is another iteration of, uh, the Verfield project. I've been live coding for a while already. Uh, so this is the current state of things. It's changed a little bit, some of you may remember the first, uh, first demo. Uh, so the change is it's, uh, migrated to Go language, and, uh, now it runs on TART system that's used on, uh… We tried runners, I guess. And so the system is here to show you the available images, available runners and locations. So here you see I can have it. stored on the external SSD, because I have my internal 2TB ETH. up to completely, and I have the old MacBook Pro also managed from the same environment. And, uh, you can add other machines as well. Uh, so this is, uh, a wrapper around the TART system that manages, uh, Xcode installs, uh, SIP protection, and, uh, for virtual machine and real machines. Uh, if you use older hardware and, uh. It's, uh… basically providing MCP server for AI clients to. to run these UI tests. Mostly. on the older virtual machines. It can be not older virtual machines, but actual virtual machines. New refreshable machines as well, sir. Uh, for example, I don't update to macOS 27, because, uh… I expect some issues, but I use, uh, testing on macOS 27 using this, uh… a virtual machine system. And so basically the… Again, I have a question to the team in… In the light of a recent discussion of testing on order. macOS versions, for example, whether should I try to push it forward to, like, team-wide? So the idea… the idea is to be able, uh… again, we'll… And in the post-mortem. for the VS Code integration projects. So here you can see VS Code. Basically, it's running the Google browser. It can… run iOS browser as well, in simulator, and in addition, it can also run remote debugging, unlike Xcode, which had supported remote debugging. in a long time ago, but currently lacks the ability, so… Integrating these systems together allows, like, click one button. choose the virtual machine you want to run to test on, and it builds, deploys, and debugs in real time without any lags for library symbols transfer and other stuff. So it just works like you would do on your host machine, but in the virtual machine. So I wanted to hear opinions whether should be. try to adopt this team wide.
- **20:20:06 · Dominik Kapusta:** I can offer an opinion.
- **20:20:09 · Alex Martemyanov:** Nobody wants to.
- **20:20:09 · Dominik Kapusta:** uh… No, well, I mean… No one to be the only one commenting, but anyway. This will be the topic of, uh, of, uh, of the upcoming postmortem, uh, as well, that… The Apple engineering expectation of testing on older macOS version is essentially a dead low. We are supposed to test on older macOS versions, but we rarely do it. Perhaps for new features on macOS? I'm not sure. But certainly not for… Small… tasks. I don't think… well, I don't know, but I don't think we bother to test on all the ROS versions, every small version. Change to the UI, especially. And, uh… Because of that, if we had a way, and also we can't, we are unable to test in CI. So, if… I had a way to… Ask an agent to… run UI tests on a virtual machine. on an arbitrary OS version, that would be great. I would like to see the demo of that, actually. That would be awesome. And that is why we might be interested in adopting it. Perhaps.
- **20:21:41 · Alex Martemyanov:** Yeah, again, about the UI tests, correct point. So sometimes you want to run an agent reproducing an issue, for example, and it's not always convenient to upload it to CI, wait for the UI tests to be run. Look for the results, while if you run it locally on your machine, it will be blocked for 5 minutes, and do the stuff while you take a coffee. So this thing allows you to just run directly from the agent on the same machine in background and provide you screen recording with all this and the results.
- **20:22:22 · Jonathan Jackson:** Yeah, I mean, I think… You know, your point that our expectations are that we'd be testing on all versions that we support, but in practicality, I think almost nobody actually does that. And particularly with something like as old as Mac OS 12 where we don't have the hardware, we don't have like, most people don't have access to test it to your point, L. Um… I think I'd like to understand a little bit more about how the system would work, what kind of third-party dependencies there are, what it would look like to really set up and what it would cost. I think the idea of we would be able to test. On versions that we say we actually support is pretty appealing.
- **20:23:00 · Alex Martemyanov:** Okay, so probably the resolution here would be, um… So, first of all, I do use it as my self-made tooling, and uh… if… I can reach it to the point, I can make it to the point when you click a button, install the system, click a button, and it just runs. I think it would be worth. adopting at least as a selected auditory who can. have, uh, the means to testing, like, enough of RAM or some older hardware, uh, like, choose the early adopters and, uh, see how would we… expand it. And, uh, yeah, correct question by, uh, Federico about, uh, older ores. It's another topic that I wanted to raise during the post-mortem. During the incident, actually. Both for the incident, uh, that, uh, having… Maybe one dedicated machine, older machine, maybe somewhere that would run the UI test suite at least once per week for each release would be a great addition, even if it's like a physical machine somewhere. someone's office or home space.
- **20:24:28 · Jonathan Jackson:** Yeah, that's an interesting idea, too. I think… I guess I think that a proposal here that sort of lays out what a strategy for old testing would be that used this would be maybe a useful next step. Um, because then that would be a place that people could rally around, sort of solving that higher order problem of how do we actually make good on our promise of testing on the systems that we support. And it sounds like this would be one, but maybe not the only tool to consider, or maybe even as a combination. Does that make sense?
- **20:25:00 · Alex Martemyanov:** Yep.
- **20:25:01 · Jonathan Jackson:** Cool. Okay, thank you. Interesting stuff. Sam, you're up next.
- **20:25:10 · SS:** Yeah, recently I have been chatting with some folks about being able to put Claude workflows in our CI. I talked about this with OT and they told us that they don't want Anthropic tokens being available in public repos. I've created a private repo to host the agents, uh, which is… Pretty bare bones right now. It lives here in the Apple Team Agents repo, it has CI set up, it has the Claude, uh, action set up. I have a workflow first for testing it, uh, just so we can make sure you can actually talk to Claude and back. Um, the only thing I'm waiting for is whether or not we should get a dedicated API key, because I've been told. Two different things from OT. So I'm just waiting to —. Get that sorted out. I think we should get a dedicated one. once we've done that, yeah, we can start doing things like an automation to clean up feature flags and such, like Fernando's, uh, proposed. So, uh, I'll post to Apple Diary once that's ready, but I think you'd be… if you do want to start building automations in this now, like, feel free, uh. As long as it's, you know, not super expensive. Pete, done.
- **20:26:19 · Pete Smith:** Yeah, thanks, Sam. This, this looks really cool. Just because I've seen, um, like, there's a few different conversations. There's a conversation with this, and there's the Bitrise, you know, running, um. uh… Agentic stuff on Bitrise as well. How does it all fit together? Like, I think I understand it, but, like, say I wanna… say we wanted to, you know, uh, build our feature overnight while we're in bed, um… How could we use this to do that? Or can we?
- **20:26:43 · SS:** This is not that. This is definitely not that. This is not like the development environment thing. Yeah, these are not like the development machines. I really just expect these to be like GitHub Actions workflows that just do helpful things with Claude. Uh, and we just need a place to put those. Like, if it weren't for the API key limitation, this would live in the monorepo.
- **20:26:56 · Pete Smith:** Yep. Yeah, yeah, I guess, I guess what I'm wondering is, so, like, yeah, exactly, we can, we can hit Claude and, um, but, you know, Claude can't, well, build for us, so, like, well, build and check that it's actually working, so where would… say, say even, like, removing feature flag, where would that. On the PR, at the PR station.
- **20:27:17 · SS:** Yeah, this is something that Fernando and I was talking about, about doing some kind of coordination between these repos where the monorepo would talk back and forth, do the things that it needs to. This can create a branch. The monorepo can then do the actual testing. Yeah. Right now, I'm just using these for, like, dependability analysis kind of problems, or planning on anyway, which I have a demo for coming up soon.
- **20:27:33 · Pete Smith:** Okay. Yep. Cool. Yeah, cool. Thanks.
- **20:27:44 · SS:** Dominic.
- **20:27:46 · Dominik Kapusta:** Mm-hmm, uh… one of the limitations here is that GitHub Actions workflows are limited to 6 hours of runtime. So…
- **20:27:53 · SS:** Also that, yeah.
- **20:27:54 · Dominik Kapusta:** Yeah. And also, it's, of course, non-interactive. Um… Which is why we're currently trying to figure out if Bitrise… or Bitrise or not, but anyway, looking for some infrastructure provider for, uh… macOS machines that could run Agentic workflows and be… and offer. interaction with them, right? So, uh… Bitrise RDE remote. development environments is one of the options there. Um… That is in progress. For now. They also… it's also quite a fresh feature on their end, and they have some bugs there that we're trying to resolve right now. And we have a CloudOps team member on that as well. the side of… Connecting them to ClickHouse or Sentry. Yeah, so… We'll see in some time.
- **20:28:58 · SS:** Yeah, yeah, to Dominic's point, like, that problem is much bigger than what this repo is. This really is just, I want to be able to run Claude on an automation, like I currently do on my own machine, and I'm just sick of doing it on my machine. I just want to push that up to GitHub Actions. Have it run on its own, and… Show up with PRs and Asana tasks occasionally, so. Okay.
- **20:29:19 · Jonathan Jackson:** So the limitations here are that it can… It can inspect code, it can run as an agent, but it can't build and run, so it would… prospectively submit a pull request, and then CIA would tell you whether it did the thing or not.
- **20:29:32 · SS:** Yeah, the idea that I'm thinking here is that, yeah, like PRs would go over back to the monorepo. This thing would open PRs against the monorepo. And then CI would do its thing over there. Yeah.
- **20:29:38 · Jonathan Jackson:** Right. Yeah, and if we needed to inspect it from there, we could pull a branch and do whatever else we needed.
- **20:29:46 · SS:** Yeah.
- **20:29:47 · Jonathan Jackson:** Okay, cool. Definitely sounds like a good step, even if you're not trying to solve everything all at once, which is reasonable. You're the next topic as well, Sam.
- **20:30:00 · SS:** Oh, is this the demo? Probably should have just done this all at once. Yeah. So one of the things that I.
- **20:30:04 · Jonathan Jackson:** Oh, before you… sorry, if you're doing demos, before we get into demos real quick… Uh, we had a note here that we were gonna actually record demos. Um, but we haven't ever done that. Mostly people have opted out of wanting to be recorded, so I wanted to just check in since we have 3 demos here. do we want to record these? Should we rely on the… just the transcript summaries at this point, and whatever tasks people have written? I'm kind of okay either way. Um… I don't know. I don't know that we've ever recorded a demo.
- **20:30:35 · Pete Smith:** Alessandro. Alessandro is waiting for his Wednesday morning. Won't be the same if we don't record our demo.
- **20:30:39 · Jonathan Jackson:** Right. That's the question, right? I know, yeah, it's like this is sort of a hard way to do this. So, Sam, would you like me to record or not?
- **20:30:51 · SS:** I mean, I've already shown this to Alessandro, so I don't think he cares. Yeah. Up to you. I'm good either way. I remember. Don't worry. This is a super quick one anyway, just to show the initial problem that I'm trying to solve with… with a repo like this. Let me share my screen. Um, so I have, for a while, wanted the other half of the flaky tests project. Right now, we have a flaky test project, which keeps track of, uh, you know, tests that are failing. Um… I have traditionally been more interested in the problem of what are the workflows that are failing, uh, and why, because these things were just, like… this stuff comes up a lot, like, during Xcode upgrades in particular, so… This is something that is being used by Claude to pull the monorepo, get the actions, go and look at the code, figure out what's causing a problem, and report back and give a little write-up about what's going on. Um, the idea being that eventually you could then move something into this ready-to-fix section, and the agent would then go and actually open the PR later. Um, you know, this is just moving a… moving an automation that I've had on my machine is like a daily, like, 10 AM workflow for a while. and just putting it remotely so I don't have to think about it anymore. Which is the ultimate goal. So yeah, this is the kind of thing that I'm trying to do with this repo. Um… As an aside, OT is kind of working on… something along this as well, which I learned about as I was setting up this repo. They are setting up this template, which lives on Dub, for what it's worth, for these kind of analyzing report workflows. Umm. So that might be interesting if you are needing like access from things within the system already. Uh, like, I think Lucas is currently looking at getting that thing to have sentry access and all this kind of stuff, so… Yeah. Go check that project out if you're interested. That's it.
- **20:32:48 · Jonathan Jackson:** Awesome. Thank you. Pete, you're next.
- **20:32:57 · Pete Smith:** Yeah, thanks. Yeah, this is in the demo section. It's not really a demo, I guess, but just wanted to share. I'll speak a little bit about, um. ASTAC, so I put a link in… a link into the chat there, so I'm sure people have heard… of… PSTAC, or maybe people have heard of PSTAC. I'm going to just share my screen. So if you haven't, um… Pstack is a plugin created by an engineer at Cursor or SpaceX. It's basically just a set of skills that this engineer found were very good. at, um, fixing bugs, implementing features. So they created the PSTACK plugin. What ASTACK is, is basically just a port of PSTACK. So PSTACK was. built for cursor. So it has a lot of built in you know, instructions in terms of cursor models and how they work so forth. So I just. Ported PSTAC, uh, over… To, uh, ASTAC, um… Basically replacing any of the cursor references with Cloud Code and Codex references. So what AStack is, is a plugin that you can use in Codex or Cloud Code. It's like it sounds very abstract. It's not. It's really just a. A set of skills, a set of playbooks, some defined principles. And they all work together to what I found to just to produce good output. um… So I'll just, I'll talk a little bit in a moment about how ASTAG works. So how it's set up at the moment, you can see on the left, I just have it there under my public, under my own public repo. But if anybody wants to try it out, I would encourage it. You can see like I didn't do a lot of work here. I really want to undersell this. asked an agent to port this over. So take PStack, port it, make sure it works with Cloud Code and Codex. The most work I did was creating that logo you see on the left of the screen, so that's where all my creativity went into. Um… But yeah, you can go here, you can grab the plugin, you can install it in Cloud Code. And you can try it out. I'd recommend trying it out for… for bug fixes, even like small features that are well defined. So, you know, the evidence, like any evidence I have is just anecdotal. I've just found these particular set of skills, these set of playbooks and the principles that are defined just produce very good output. Again, anecdotal. I haven't measured this. I also think it seems to do it at lower token usage. But again, I haven't measured it. So how it works, how ASTAC or PSTAC work is, you know, you install the plugin, it sets up a hook, so at the start of your sessions, the agents are aware that ASTAC is there. And if you say, hey, build this feature or fix this bug or whatever, you can explicitly say. Enter potato mode. But that's actually part of the hook. The agent will know, oh, if you give it a feature or a bug, it will enter potato mode. All that is like a top level skill, which is basically a router. And depending on the task that you give it, like fix this bug or implement this feature. You will go and find the right playbook and follow that playbook and in the playbook. That would reference what skills to use, et cetera. So. again, you know, there's nothing, like, there's nothing magical here. I mean, there's been other plugins that have been very popular. I was talking to Fernando earlier, and we talked about… was it the Superpowers one? I think was another popular plugin. So things like this will probably be, as I was speaking to Fernando about, they'll probably be, can, you know, eventually end up in the harness. Probably won't need plugins like this at some point. But at the moment, this is something I'm using daily. And I find it very beneficial. It just results in really good output. So I would encourage people to try it out. Like, what what, you know, we've seen probably saw the post from Sebastian, from OM. He's creating, like, auto, which is their version of pstack. He just took pstack. And ported that and kind of made it very specific to Duck AI. That's like the the OM version of Pete's group. So if ASTAC, if people find it useful, we could basically turn that into like the Apple version of PSTAC, Apple team version of PSTAC. and… that's something we could do. So yeah, I would just encourage people to try it out, if you're interested. There's an Asana task there that I posted, and you can give any feedback, and if people want to. People find it useful and want to contribute and make it better. We can do that. It's under AI enablement AOR. I spoke for a long time, if anybody has. Sorry, I shared that artifact. Sorry, key. I didn't go through all this artifact.
- **20:37:59 · Pete Smith:** It's linked in… The Apple Weekly Task, so you can go and look at that artifact, it explains at a very high level how it works. Again, it's not magic, it's just a skill, a ruler, lots of other skills. Sorry, my dog is barking. I don't know if you can hear my dog, but. He's over there barking at me. That's very low. That's it. If anybody has any questions, you can ask me questions, or you can ask me questions later. Jane, sorry, your hand up.
- **20:38:35 · JF:** Yeah, sorry if you said already and I missed it. What changes have you made over the original piece, Doug?
- **20:38:42 · Pete Smith:** Yeah, so… Oh, I'm sorry, it looks like. Okay, dog went dead. Um, yeah, that's why I wanted to undersell it. Like, I didn't, I didn't, I didn't do anything. So, uh, I created that logo. What, what, what I did, or what the agent did, was just port it over, support Pstack over, um, for Cloud Code and Codex. Like, the original Pstack has references to Cursor, and how Cursor. Works. So I just ported it over, so it works in… Um, codecs and cloud code. I didn't add anything additional yet. Um… But the idea will be we can add things if we find them useful. We can add Apple-specific things. If we find them useful. So yeah, no changes really. Sorry, one more thing, James. Thanks for reminding me. I'm going to reshare. Sorry, everybody. Very annoying. I'm going to reshare. So a good question. Like, PStack is being continuously updated. So I have a scheduled task that runs every Monday, looks at the latest PStack, and consumes the latest changes, and, like, ports over the latest changes. So I keep it up to date. So I look at the upstream and keep. a stack up to date. But that's other than that, I just I just port it. I don't make any other changes. Like, you know, of course, there's a chance it's not ported well. It might not work properly, but the intention is it's just a direct port.
- **20:40:09 · Jonathan Jackson:** Cool. Thank you, Pete. Paul, I'm protesting.
- **20:40:16 · Pau Ballart:** Yes, thank you. I'm going to share my screen. This is pretty much. a demo that I owe you of the snapshot testing. So, quick reminder, this is already available on iOS, not yet on macOS, because we are waiting for macOS 27. runners on big drives on the CI. on, uh… Yeah, pretty much. It's a package that has a very nice README explaining of it, what I will show today. So you can read it or tell your favorite agent to read it. But it has like requirements, how to use it. A bunch of examples for both iOS and macOS, even though, as I said, macOS. is disabled. But let's do a bit of an example. if I find the Xcode that just crashed, apparently. Ah, it's here, yeah. So, uh, how does it work? We start with the bill. Maybe, or maybe not, you will have previews. That is the new, like, hashtag… preview macro but for a snapshot so I created this one you don't need to use previews but it's just if you use them it becomes handy so there is this new preview provider that's the system. protocol, then if you conform it like this, so pretty much. You configure the different states that you want to have in the view. In this example, it's this segmented control. So there are two previews, one for each tab, let's say. You configure it here. So that's the model or the state of the view. And then you configure it here. So it will render one of the previews for each tab in this case. That basically gives you the previews here, but what is nice about it is that then you have the snapshot test. becomes basically a one liner or yeah one four liner uh but yeah just one call because it reuses the same previews that you refine it and then uh this is just a unit test like. Any other that we have. that runs the test. And this. Basically, you can configure it in different ways, for example. Here, if you want, um… to have a preview, but you don't want to snapshot it, because it's not needed. You have different. uh parameters here in this um. Let me show you. In these configurations, so there is… a scope where you can say, I want just for previews, just for snapshots, or for all of them. And then, um… in the test, you can snapshot in a different set of, um, configurations. So, in these asset snapshots. But everything is here in this package. We have different things. We have the different strategies. If you want to snapshot, for example, iPhones, iPads, all the combinations, just a single screen or a custom. Uh, size? And then you have also. the different sizes of components that you can have in an app, right? Majority of things are the screen, but you can also test some intrinsic content size, bottom sheets, or just any big size that you want. So all of that has, like, default parameters. In this example, for example, it's just, you know, normal screen, and I want to judge a snapshot in that mode, because that screen doesn't have light mode. So, it would work like this. And this is a unit test, it runs super fast, and uh… It passes in less than a second. how it works when you change something so let's say remember we have this previous let's say now i change this uh. this view. No, there is a design change, so we have this title here. If I run the tests, now they will fail. I will show you how it looks like in Xcode. So pretty much, issue recording, blah blah blah, does not match reference. And then, you can go here in your tests. We see the test that failed, and if you double-click, there is this gallery. That basically is showing us the reference, the failure, and the difference. So you can preview it like this. That's the original one. And then the new one that got recorded is this one with hello.
- **20:45:21 · Pau Ballart:** So you can see a diff that it's generated. Basically, you see everything is moving down. Um… So here it can happen two things. It's a real failure and you need to fix your UI, or it's a design change that is… expected, and you want to re-record the test flight, because this is now the new correct design. To do it, you have different ways. Here, there is a record Boolean. You can pass it to true. But at the same time, instead of changing code. If you go to the folder of the test. In in in Git you can let me show you. in a… in another screen. You can just delete the reference image in the file system. So that's the submodule that we have. In the, um… With all the snapshots. So if you go there and delete the file, it will recreate it on top of it. Um, so yeah, basically you have these two options. If there is no original file in the file system, it will just create it right away. If there is an existing one, it will do the comparison and so on. So the easiest usually is, um, to just remove. the image and re-record it. But let's say that… This works, and you upload a PR, and it fails in the CI. So how does it look like? Pretty much the current PR checks that we have for iOS, we'll report them here with the faillet, and it generates an HTML report, which is this one. that, uh… creates the same thing that we see in Xcode, but in the CI. So if you see a PR failing, you don't need to download the artifacts and so on. You just have to open this, and it has, like, these drop-downs. with the same concept, like the reference, the failure, and the diff. Um, so that's… A bit what I wanted to show. Then, um… So the snapshots live in a submodule, as you probably know. So it's a different repo. It's these DuckDuckGo Apple browser snapshots. And it just contains the PNG files. So that is this. Orchestration, if you want to run when you create snapshots, you need to open, let's say, two PRs. But there is a script that handles everything. So what you would do is here when you record your new snapshots. Maybe I can do it really quick. Just a second. I will. Show you exactly what I mean. So we have the submodule. Snapshot references. I'm gonna remove… The, um… Tests for this one. which is the scan QR code test. So I remove it from the file system. Okay, from this folder. And then when I record it or when I run the test, it will record. So first time it fails, but now it says no reference found on disk, which is fine. And then second time it runs, it already has the references and it passes. Okay, so now we want to open the PR, uh, and we can see that the snapshot reference module has the changes. Again, old and new with a new title. So there is a script in the scripts folder. around doo doo doo scripts. called Open Snapshot Zoom Module PR. You just run this over there, runs it, and it will open the PR, so commit, push, open PR, and so on. Um, and then once in your main branch or main PR, there is a new label that you can tag. Uh, let me show you here. Merge the snapshots. So this will merge the snapshots PR and update the pointer and so on. So, it's these two extra steps. You can do it manually, but, uh, the easiest is once you record it, and you have the changes here in Git, you just run the OpenPR, uh… script, and then once your main PR is approved, you can, uh, just use this label to merge the… the snapshots PR. So you…
- **20:50:21 · Pau Ballart:** It's a bit of extra work, but I try to minimize it and automate as much as possible, so… That's how we currently have it set up with these failures and so on. Any questions so far?
- **20:50:37 · Dominik Kapusta:** Yes, this is amazing, and do we have a documentation for that in the Apple documentation project?
- **20:50:44 · Pau Ballart:** For the CAI part, you mean?
- **20:50:46 · Dominik Kapusta:** Yeah, for…
- **20:50:47 · Pau Ballart:** Or in general.
- **20:50:48 · Dominik Kapusta:** In general. You've mentioned that there's a script that simplifies the work, and that would be great to have it as a task in the Apple Documentations project, if it's not there yet.
- **20:51:00 · Pau Ballart:** Okay, I will add it, yeah. Yeah, so the biggest documentation right now is the README, but I understand that it's not, uh…
- **20:51:02 · Dominik Kapusta:** Awesome. Thank you so much.
- **20:51:09 · Pau Ballart:** in the best place. I mean, it's useful, but…
- **20:51:10 · Dominik Kapusta:** Mm-hmm.
- **20:51:12 · Pau Ballart:** Yeah, I will let it also in Asana.
- **20:51:16 · Dominik Kapusta:** Thanks so much.
- **20:51:16 · Jonathan Jackson:** Very cool, thank you, Pao.
- **20:51:20 · Pau Ballart:** I have one more thing to share, which is… So two things. Why is this useful, right? Like, because, okay, we can add a snapshot test and so on. There are three things that I see that are important. First one is PR reviews. Since now the two PRs are linked, it makes it easier to review changes, right? You read UI code of SwiftUI, for example, and you see paddings, frames, blah, blah, blah. Seeing a screenshot helps a lot, so now it would be easy to compare side by side, because you will have here, um… For example, this one. The… the file changes. Directly in the… well, it's not the… This one needs a rename. And you will have the file changes on GitHub to review side by side like this. So PR reviews are better than. I think it was already mentioned we can. think about our UI tests, and if we have UI tests that are asserting. Just how things look like. It's a good candidate to replace with. with the snapshots. Um, so… I will open a proposal at some point, but the idea is… Since UI tests are flaky and snapshots and units. are less flaky and run quite fast. We might look at opportunities to move some of these tests and with a good combination of unit and snapshots. Yes, we are still missing the navigation part of I tap this button and this other screen opens. But yeah, it's up for discussion, but I think you have already a good coverage of a feature, right? And the last thing is ship reviews, because here in this other repo, it's becoming basically like an S3 bucket of data. PNG files. So when you prepare your ship review, if you have used this, you don't need, uh… to regenerate the snapshots and so on. You would just even link it from here or pick them from here. And that's just a starting point. We can improve it with future ideas, like we were talking about different languages. So how we could snapshot test different languages, different dynamic sizes for accessibility, like a large text size and so on. Even, I don't know, when the snapshots PR is open. with some automation, check the original Figma design, and compare it, and there are, there are, um… ways to improve this. So this is just a starting point. And last thing I want to mention, it was part of the tech design to track adoption of this. So far, I'm the only one contributing, which is why I'm doing this demo as well. But I created with Claude an automation that every week checks the repo. It's very easy, because we can just go to the insides of this, um… of this repo and see contributors, but also just check, uh, the asset and snapshot, uh, usages. So this is a dashboard that I shared, uh, within DuckDuckGo. It's updated every week, and basically we can see how. how it grows over time. Um… So yeah, if you fancy, please use it. And if there are any issues, let me know. I'm like the unofficial or official DRI of this. Happy to be on top of it if it's causing issues as well.
- **20:54:59 · Jonathan Jackson:** It's really cool, Pat. Thank you for sharing. Yes.
- **20:54:59 · DR:** Good work, pal.
- **20:55:04 · Jonathan Jackson:** Very cool. We are now at 5 minutes to the top of the hour. Dominic and Alex, you both have postmortems on the list. Do you want to… run those now, understanding we'll go past time, and anybody who can stay is welcome to stay or not? Or would you rather find another time for those?
- **20:55:24 · Dominik Kapusta:** I'm fine running it. It should also be short, but not sure about Alexa's one.
- **20:55:33 · Alex Martemyanov:** Probably can wait till the next Apple Weekly.
- **20:55:37 · Jonathan Jackson:** Okay.
- **20:55:37 · Alex Martemyanov:** I think it was waiting for a year and it didn't wait another week.
- **20:55:41 · Jonathan Jackson:** All right.
- **20:55:42 · Alex Martemyanov:** Thank you.
- **20:55:43 · Jonathan Jackson:** Thank you, Alex. Um, then, Dominic, why don't you go ahead and get started? Anybody who's not interested in Dominic's incident post-mortem, obviously, is welcome to drop. If we run a little bit late and you need to be somewhere else, that's also okay to drop. And Alex, I'll keep yours on the agenda for next week. Thank you.
- **20:56:01 · Dominik Kapusta:** Thanks. I've dropped the link in the agenda as well for the incident postmortem. What happened last Monday is we released the app that was crashing on macOS 12. And, uh, the app was out… well, uh, so the app was out for, like. 3 hours before we, uh, realized that there is a crashing scenario on macOS 12, and then that was handled real quick, uh, with app store rollout stopped. And, uh, Sparkle rollout stopped, uh, as well at some point, um, and the fix was released, actually… well, it… It. Well, almost immediately on DMG, and the next day on App Store, because of the review time. Um, but, uh, how it happened? So, it happened, uh, because we had a change to, um, the save credentials pop-up, which shows up every time you're offered to… you're being offered to save a password. Um… On macOS 12, um… And that change was due to dropping a storyboard, replacing a storyboard with a code-initialized view. So what didn't go as planned? This, uh, change was not tested on old OS versions before merging, and it was strictly macOS 12 issue. Uh, like I mentioned before in this call, we had that engineering expectation in place, but we're not really enforcing it for every change. There's no way of enforcing it, uh, and there's no way of. testing, um… all those versions in CI, so… that's why it happened. Really. Uh, the other thing is, uh, we didn't know about the crash, because, uh, I overlooked it in Sentry. I was the release DRA and I overlooked it in Sentry. There was a single crash on macOS 12 there. Uh, that I treated as noise, and I went ahead and released the app. The sentry summaries weren't generated on that day, because we had another… Whoopsie. Um, the week before, when we updated, uh. Well, some updated the model version and I reviewed it and approved it. and we merged that change, and we updated the model version, but we didn't update the SDK version, and the old SDK didn't… wasn't recognizing the new model, and it failed to… collaborate, so we didn't generate summaries. Um… So that's the other… the other thing. Uh, when the… but! When the summary was generated, uh, it clearly pointed out that there is a crashing scenario on Mac OS 12, which started the incident. A week of internal testing didn't catch a relatively easy-to-reproduce crash. It was a 100% crashing scenario, which wasn't caught. Because we don't have testers on macOS 12. Well, apparently we have one, because we got this one crash at some point. I don't know who it is. I'm…
- **20:59:33 · Alex Martemyanov:** Yeah, and by the way, there was another kind of related issue about the crash on Intel machines. It's not directly related, but yeah, it was close.
- **20:59:41 · Dominik Kapusta:** Yes, another one, exactly. We also don't have testers, or many testers, on x86. architecture. The App Store review took 15 hours, which is rather long for an expedited review, but also there's nothing we can do about it. At least it got in the queue… I mean, it got in the review pretty quickly after requesting a completed review. What went well is that the sentry summary that was eventually generated, um… Clearly identified the crash, and suggested addressing it, and the fix was simple, quick to prepare and test, it was just assigning an initial frame to a view. And the hotfix release automation workflow less at this time. It's always important to point this out, because… We only talk about CI when it's not working correctly. Despite the long review time, we only had 37 crashes in total and only 9 affected users. That's all. for action items and DRIs, we actually, uh… there was an action item to update agent's instruction prefect… essentially update prefect to ensure that Claude agent SDK version is… compatible with used models. Uh, Sam has handled it, and, uh, well, there is a code command right now to, to update the SDK version whenever you update the model version. Um… The other topic that's not actually mentioned here is what to do about testing on older OS versions, but this is something we will be handling separately through Alex's work, mentioned earlier on the call. And… That's it. Finally, I created an incident task through the form. Asana forum, and marked the incident as high, because it's a crashing scenario, we need a hotfix, and an SRE person joined the call, and we talked a little bit, and he, um… Explain to me that if it's a one-person rollout. It's not a high severity incident, and we dropped it to medium, and they dropped the call. And that's it. And, um… That's something to keep in mind for later, for next incidents, when they are only starting rolling out, we may not need SRA help there. This is all I have.
- **21:02:09 · SS:** Regarding the action item, are you happy enough with just having the code comment now that reminds about the Claude SDK?
- **21:02:15 · Dominik Kapusta:** I think so.
- **21:02:16 · SS:** you know, it's… it's not bulletproof, like, what I… what I wanted to do was to just ask the Claude SDK, what models do you support, and check that it's in the list, but it only includes… yeah, it doesn't include all the actual supported models.
- **21:02:18 · Dominik Kapusta:** I think, yeah. I saw that, yeah.
- **21:02:28 · SS:** Eh, maybe the comment's okay for now. I tried to make it very obvious what to do and how to confirm this.
- **21:02:32 · Dominik Kapusta:** Yeah, I mean, that's okay. Also, that comment would show up, because it's just very close to the line that is changing, it will show up in the GitHub UI when reviewing the code, so it should be fine.
- **21:02:37 · SS:** It's right there. Yeah, the only way I was considering extending this was to just have a GitHub Actions check that looks for model changes and adds a comment, GitHub Actions comments. But I would want to do this for all of Prefect. Whatever. I'll look at that.
- **21:02:56 · Dominik Kapusta:** Yeah, yeah. Should be fine. Okay.
- **21:02:58 · SS:** Okay.
- **21:03:00 · Dominik Kapusta:** Thank you. Thanks for handling that, Sam. Alex?
- **21:03:05 · Alex Martemyanov:** Yeah, I got a proposal in… I got it related to post-mortem of the VS Code, but I think it more suits here. What about adding… updating our process to require adding UI tests in addition to renting some older Mac to run older OSs, but make a requirement to the process to cover any UI change. with a UI test. Even if it's a fix or a quick addition in the uncovered region, especially having all the Agentic workflows, it may be a quick and cheap option. I mean, cheap to add. maybe not to maintain. But it adds, of course, it adds extra cost for the runners. Or maybe we could have like a test suite number two that runs weekly, for example, and not daily.
- **21:04:11 · Dominik Kapusta:** I actually think it's… Some Windows team uses something similar. whenever they change UI, they add UI tests, and they have plenty of UI tests, and that's another problem. I believe, but… Yeah, we could… We could discuss it, I guess.
- **21:04:31 · Alex Martemyanov:** Yeah, because, uh…
- **21:04:31 · Jonathan Jackson:** I think that's what we're considering. Sorry, go ahead.
- **21:04:35 · Alex Martemyanov:** Because obvious, like, obvious… thing that could fix it is, uh, like, QA, which we are missing, for… everybody knows for… for why, for what reasons, uh, but we have a lot of, uh, supported platforms, a lot of supported macOS versions, and, uh, it's, uh… Like, uh, it's impossible to… make the requirement as in the mentioned. Uh, process, like, to test all the supported macOS versions, because not everybody even have all these machines that, like, I have the older one, but it's not DuckDuckGo, it's my personal machine. And, uh, I can test it, but it takes time. Uh, and nobody… nobody does it, frankly. And we have no QA, and it's impossible to guarantee the quality in such conditions. So, maybe it's required. It should be a required condition to… to… raise the UI test coverage, the end-to-end coverage, so we can validate we are actually producing quality UI tests. Stuff.
- **21:05:50 · Jonathan Jackson:** Yeah, I think that's worth considering alongside the virtual machine testing stuff that you were talking about earlier, right? I mean, we've known for a long time that we clearly have testing gaps, especially on older versions and older hardware. And… To this point, I think we've just accepted that as the way it is and every now and then something like this goes wrong and we deal with it. um… But we should definitely think about whether there's a promise we're making to our users there that we're not able to fulfill properly. And I think certainly that's true right now. The question is, what does it take to do better at that promise? So I'd love to see some proposals around moving some of these pieces forward.
- **21:06:32 · Dominik Kapusta:** All right, that was all for me. Thank you very much.
- **21:06:38 · Jonathan Jackson:** Alright, and thank you. Um, so, Alex, we're gonna wait till next week for your other postmortem. Thank you for your flexibility there. And thank you all who stayed to finish that out. I appreciate it. And I look forward to seeing you again soon. Bye, everyone.
- **21:06:54 · Alex Martemyanov:** Thank you. Bye.
+6 -6
View File
@@ -50,8 +50,8 @@
"note_modified_at": "2026-10-06T15:22:23.633Z",
"source_url": "https://us01mynotes.zoom.us/gUhtLoqRTfSsTbZsann73A",
"folder": "2026-10-06 Jacek Łyp's Zoom Meeting 2026-10-06 20 44(GMT+6 00) gUhtLoqRTfSsTbZsann73A",
"sha256": "1e1ce06ac96ff369e42935ce13dc6a95ae5f32b1bffb53ed4570a7e14677cecf",
"cues": 3
"sha256": "2c6e9e71b22ba2bef88a916792118d81abbf20a08b790dc37e1735768bf102b4",
"cues": 305
},
"280BehgySpW8LynSS473nQ": {
"title": "Apple Weekly Team Meeting - Zoom ID 2026-10-06 20:01(GMT+6:00)",
@@ -158,8 +158,8 @@
"note_modified_at": "2026-11-10T10:01:44.278Z",
"source_url": "https://us01mynotes.zoom.us/p5FdcX9WT-afBpWjRgaW0w",
"folder": "undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w",
"sha256": "5d3aeb038b4212d9cdd785c7b1683d37ea04faf0816463ce4e37873af9bb8dbb",
"cues": 3
"sha256": "21d3c3d8f4c7fea11976f5cb54b98a121c895c7aabcb1b541c6d3f6f1167460a",
"cues": 130
},
"e5TYWRytRz2WwWSe68BSWQ": {
"title": "O-E 2026",
@@ -194,8 +194,8 @@
"note_modified_at": "2026-10-20T15:08:30.724Z",
"source_url": "https://us01mynotes.zoom.us/gBBa-iiUQLycw55WRV1tnw",
"folder": "2026-10-20 Apple Weekly Team Meeting - Zoom ID 2026-10-20 20 01(GMT+6 00) gBBa-iiUQLycw55WRV1tnw",
"sha256": "346d4bd302bfc92a437c43ddc0f16d64aa76fd67cdf88603598958c7c785ad2a",
"cues": 3
"sha256": "5757a175b493ba2bee769a1bcd33431e752ce73ed296d817ccf8946e60c6dbad",
"cues": 137
},
"7JZgnceAT1aZ2H75ok4dmA": {
"title": "Costas Brammer's Personal Meeting Room",
+1 -1
View File
@@ -1 +1 @@
{"observed_at":"2026-11-20T08:34:48.844Z","scanned":33,"imported":5,"skipped":28,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":88,"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":88,"gaps":[],"recovered_transcripts":2,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
{"observed_at":"2026-11-20T09:07:01.156Z","scanned":33,"imported":3,"skipped":30,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":88,"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":88,"gaps":[],"recovered_transcripts":1,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
@@ -23,6 +23,641 @@
"time": "16:02:10",
"speaker": "Dominik Kapusta",
"text": "Jest."
},
{
"time": "16:02:13",
"speaker": "Alex Martemyanov",
"text": "And basically no progress on other stuff yet."
},
{
"time": "16:02:19",
"speaker": "Alex Martemyanov",
"text": "I need to finish the priority cleanup. So basically last week we've discussed it during the OE that we should. Basically wrap up the project with the. No visible outcomes. There was a slight decline in the numbers and several genuine bugs fixed, but they were not representing the main feature breakage."
},
{
"time": "16:02:45",
"speaker": "Dominik Kapusta",
"text": "Nie. Drop, Ios."
},
{
"time": "16:02:50",
"speaker": "Alex Martemyanov",
"text": "I know."
},
{
"time": "16:02:57",
"speaker": "Dominik Kapusta",
"text": "Łazać."
},
{
"time": "16:03:00",
"speaker": "Alex Martemyanov",
"text": "There was some decline, maybe a third. So there was a decline in some part. of the numbers, but there is still around 40%. of the event sequence of the received events that so basically most of it is. The data we received for most of the breakage pixels represents just regular normal flow and nothing obviously."
},
{
"time": "16:03:34",
"speaker": "Dominik Kapusta",
"text": "Bardzo."
},
{
"time": "16:03:34",
"speaker": "Alex Martemyanov",
"text": "pointing to anything. So the discussion during the OE was to basically clean up the inefficient fixes that we've got. The feature flags for the features that are removed and some. Um, like the pinned tabs management fix, uh, that are, um, staying without the feature flag. And, uh… Yeah, clean up the data that's being collected, because we've collected enough of it, and, uh, implement some permanent data collection that stays there for, uh. for diagnostics for the future possible breakages. And try to add some in. inside of the extension, some metrics inside of the extension to, um, to track the loading progress, basically. Where we… where do we stop, and where the messaging."
},
{
"time": "16:04:23",
"speaker": "Dominik Kapusta",
"text": "Ok."
},
{
"time": "16:04:31",
"speaker": "Alex Martemyanov",
"text": "Stops. and try to reason about it from from that perspective."
},
{
"time": "16:04:37",
"speaker": "Dominik Kapusta",
"text": "Misji."
},
{
"time": "16:04:39",
"speaker": "Alex Martemyanov",
"text": "So, uh… So yeah, probably today I'm going to open the featured slugs and clean up PR. And. later this week will complete. So I've updated the project, moving on the post-mortem to the next week, since last week I had no time to. completed due to some circumstances. And, uh… That's mostly it. I still got some. PRs requiring my attention, like the crash reporting fix. So, yeah, no updates since last week. On it. So, basically, my concern about it is, uh, we may, uh, we may break the existing macOS collection while fixing iOS collection, so I need to… reproduce it, reproduce the crash and. this slowdown condition and normal conditions and see how it if it still works and nothing breaks and then I'll proceed with it."
},
{
"time": "16:05:49",
"speaker": "Dominik Kapusta",
"text": "Collection as in…"
},
{
"time": "16:05:52",
"speaker": "Alex Martemyanov",
"text": "The App Store reports."
},
{
"time": "16:05:53",
"speaker": "Dominik Kapusta",
"text": "Crosscode? Yeah, cross-collection, mhm."
},
{
"time": "16:05:57",
"speaker": "Alex Martemyanov",
"text": "Yeah, so matching against process identifier or by date."
},
{
"time": "16:06:02",
"speaker": "Dominik Kapusta",
"text": "Yeah. Yeah, yeah, yeah, yeah."
},
{
"time": "16:06:05",
"speaker": "Alex Martemyanov",
"text": "Mmm."
},
{
"time": "16:06:05",
"speaker": "Dominik Kapusta",
"text": "Oh. Right."
},
{
"time": "16:06:14",
"speaker": "Alex Martemyanov",
"text": "And… That is it, I guess, so… I'm. I'm not top performing for the last week. So just… Just completing the TP stuff."
},
{
"time": "16:06:35",
"speaker": "Dominik Kapusta",
"text": "Yeah, which is…"
},
{
"time": "16:06:36",
"speaker": "Alex Martemyanov",
"text": "And yeah, there was…"
},
{
"time": "16:06:38",
"speaker": "Dominik Kapusta",
"text": "Expected."
},
{
"time": "16:06:39",
"speaker": "Alex Martemyanov",
"text": "And there was the maintenance, the release maintenance. Luckily, it was growing weak."
},
{
"time": "16:06:46",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm."
},
{
"time": "16:06:47",
"speaker": "Alex Martemyanov",
"text": "So nothing else ended from it."
},
{
"time": "16:06:48",
"speaker": "Dominik Kapusta",
"text": "I saw that, yeah, that's good, that's good. All right. Nice. That's fine. So you're going to wrap up your project. Will you run the postmortem this week or next week?"
},
{
"time": "16:07:05",
"speaker": "Alex Martemyanov",
"text": "Next week, next week."
},
{
"time": "16:07:06",
"speaker": "Dominik Kapusta",
"text": "Next week. Mm-hmm. Okay."
},
{
"time": "16:07:07",
"speaker": "Alex Martemyanov",
"text": "So this week, I'm, uh… Completing the cleanup. And the next week is time for the postmortem."
},
{
"time": "16:07:18",
"speaker": "Dominik Kapusta",
"text": "Sounds good. Alright, and then… Do you have… Do you know anything about… You're next. Top priority?"
},
{
"time": "16:07:32",
"speaker": "Alex Martemyanov",
"text": "Uh, nope."
},
{
"time": "16:07:35",
"speaker": "Dominik Kapusta",
"text": "Yeah, because there won't be any follow-up… there won't be any follow-up in OE for…"
},
{
"time": "16:07:35",
"speaker": "Alex Martemyanov",
"text": "I guess I should make one."
},
{
"time": "16:07:41",
"speaker": "Dominik Kapusta",
"text": "For this. I mean…"
},
{
"time": "16:07:44",
"speaker": "Alex Martemyanov",
"text": "Well, I guess not, at least for the moment."
},
{
"time": "16:07:45",
"speaker": "Dominik Kapusta",
"text": "Immediate follow up at least. Yeah, yeah, yeah."
},
{
"time": "16:07:49",
"speaker": "Alex Martemyanov",
"text": "And, uh… So if we are shifting the diagnostics into the JavaScript part, it's probably… due to some someone else to. Keep up with it."
},
{
"time": "16:08:05",
"speaker": "Dominik Kapusta",
"text": "No."
},
{
"time": "16:08:05",
"speaker": "Alex Martemyanov",
"text": "So maybe there will be a follow-up task to perform the data analysis next week."
},
{
"time": "16:08:12",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm."
},
{
"time": "16:08:12",
"speaker": "Alex Martemyanov",
"text": "So just one, one cloud shot. To fetch the data, to perform the analysis, to see the trends, and if… Anything new is highlighted from it. So I could person. Wrap up up a date. And that's it. And it goes after."
},
{
"time": "16:08:29",
"speaker": "Dominik Kapusta",
"text": "Yeah, yeah."
},
{
"time": "16:08:31",
"speaker": "Alex Martemyanov",
"text": "Two weeks from now, I guess, when the release is out."
},
{
"time": "16:08:39",
"speaker": "Dominik Kapusta",
"text": "All right, fine, we'll need to learn what's next for you. When would you be opening? When would you be opening a top priority, Fred?"
},
{
"time": "16:08:47",
"speaker": "Alex Martemyanov",
"text": "Gosh. Probably now."
},
{
"time": "16:08:53",
"speaker": "Dominik Kapusta",
"text": "Yep."
},
{
"time": "16:08:55",
"speaker": "Alex Martemyanov",
"text": "It's really, it's a good time."
},
{
"time": "16:08:55",
"speaker": "Dominik Kapusta",
"text": "Okay. Okay, this is interesting then. There will be some work. shaping up in OB. If you're up for it, that may be interesting. I'm not sure how much native support they need, but… It is… considered a big problem these days, and that's the fact that all the JavaScript code injected into our websites causes performance issues. And side breakage. But… Yeah, well, both of them, essentially. And I'm, like I said, I'm not sure… If… A native engineer would be needed immediately. But if so, then… that… That would be very important. So this is very important. And… Let me see… So the assessment is this Thursday. And the projects… Okay. Let's see. Let's see. I see there is a… So this is the assessment task. And there is a subtask for the… staffing for the Apple team, so it sounds like they will need… they will need someone from the Apple team. This is not finalized yet, but… But, uh… Should probably be… should probably be… filled out today, I hope. I'll have the proposed critical path and Gantt chart ready for review on Tuesday. I'm proposing OB focus on performance this cycle, specifically the cost of the JS and config we inject into every frame."
},
{
"time": "16:11:21",
"speaker": "Alex Martemyanov",
"text": "Thank you."
},
{
"time": "16:11:21",
"speaker": "Dominik Kapusta",
"text": "They may at least need someone on the native side to, I don't know, implement some. measurements. I suppose. If this is something that… would be of interest to you, then that's great, because if not, I think you will still be mentioned there. What do you think?"
},
{
"time": "16:11:58",
"speaker": "Alex Martemyanov",
"text": "Visibility. What is this discussion? That you mentioned."
},
{
"time": "16:12:04",
"speaker": "Dominik Kapusta",
"text": "I was just reading the last comment in the thread."
},
{
"time": "16:12:07",
"speaker": "Alex Martemyanov",
"text": "Okay."
},
{
"time": "16:12:08",
"speaker": "Dominik Kapusta",
"text": "From Dave."
},
{
"time": "16:12:22",
"speaker": "Alex Martemyanov",
"text": "Mmm… Well, looking at my current TP, if it can be reproduced, it would be more of a… something that I would be interested in, if… And if it's something like we got some breakage to fix it. Not so exciting, I'd say."
},
{
"time": "16:12:52",
"speaker": "Dominik Kapusta",
"text": "Yeah, yeah, yeah, I can tell. I can tell. This, however, should be easier. On the functional side, on the technical side, it should be easier. at least from…"
},
{
"time": "16:13:10",
"speaker": "Alex Martemyanov",
"text": "Yeah, at least if there is exact cases reported on or some exact websites."
},
{
"time": "16:13:13",
"speaker": "Dominik Kapusta",
"text": "Yeah, I know. Uh, it may be… it may be about… it may be about just measuring things."
},
{
"time": "16:13:17",
"speaker": "Alex Martemyanov",
"text": "It should be easier."
},
{
"time": "16:13:22",
"speaker": "Dominik Kapusta",
"text": "So that front-end engineers can… Do changes, make changes. But I don't know. I don't know the details. Let's see. Trim the Apple Cs. Bundle and isolated world."
},
{
"time": "16:13:37",
"speaker": "Alex Martemyanov",
"text": "Okay, I'm fine to get mentioned on the thread, and so for the next TP, I'll probably open it on Thursday, I guess."
},
{
"time": "16:13:38",
"speaker": "Dominik Kapusta",
"text": "Interesting. Mmhm."
},
{
"time": "16:13:47",
"speaker": "Alex Martemyanov",
"text": "Makes sense."
},
{
"time": "16:13:49",
"speaker": "Dominik Kapusta",
"text": "Yeah, probably. I think it makes a lot of sense. I will be AFK for the rest of the week. Um, Bob…"
},
{
"time": "16:13:57",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "16:13:59",
"speaker": "Dominik Kapusta",
"text": "It's not a problem, of course. Um… I will try to… Try to reach out to Jonathan to ask. If he knows anything about OB plans for a pool. Or if he knows anything about anything else. Any other objective that might need Apple people and I'll let you know. Do you want to talk about your performance review?"
},
{
"time": "16:14:31",
"speaker": "Alex Martemyanov",
"text": "Uh, yes, I guess so."
},
{
"time": "16:14:35",
"speaker": "Dominik Kapusta",
"text": "Why not? Right. All right. I linked it in the agenda, updated the link to the latest review. So, congrats on the promotion!"
},
{
"time": "16:14:52",
"speaker": "Alex Martemyanov",
"text": "Thanks."
},
{
"time": "16:14:52",
"speaker": "Dominik Kapusta",
"text": "Amazing, you made it."
},
{
"time": "16:14:53",
"speaker": "Alex Martemyanov",
"text": "I guess it was a lot of your efforts."
},
{
"time": "16:14:55",
"speaker": "Dominik Kapusta",
"text": "uh…"
},
{
"time": "16:15:00",
"speaker": "Alex Martemyanov",
"text": "Involved to make it go through."
},
{
"time": "16:15:06",
"speaker": "Dominik Kapusta",
"text": "Just a bit, really. It's, you know, this… this performance review time is overall great. I mean, I like it. I like… I like working on it, because it's, uh…"
},
{
"time": "16:15:17",
"speaker": "Alex Martemyanov",
"text": "Bye."
},
{
"time": "16:15:19",
"speaker": "Dominik Kapusta",
"text": "Um… okay. It's a great time. When you can appreciate people you work with and be able to do something for them. uh… make them… make their efforts visible and recognized. So, if that works, then that's great. This time it worked, so that's amazing. Uh, but… At the end of the day, it's just your work. put into the project. Uh, and, uh, and that got you… a bump in project management, which is amazing, which is… it's essentially hard facts, especially this year. If you look at the… if you look at the review… Format. It's… Like, dry facts. Nothing else, no pros, no…"
},
{
"time": "16:16:13",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "16:16:15",
"speaker": "Dominik Kapusta",
"text": "Did a great job! everyone likes you, and so on and so on, like it used to be in the previous years. This time, it's, like, super, super concrete. With dates, with complexity assessments, with… The amount of direction needed."
},
{
"time": "16:16:32",
"speaker": "Alex Martemyanov",
"text": "Mmhm."
},
{
"time": "16:16:33",
"speaker": "Dominik Kapusta",
"text": "with clear impact stated in each bullet point. So it's just your work. distilled into a few sentences. So… Yeah, great job and keep doing that. I have to say… I have to say, I didn't ask for a promotion, because… I learned that these are the rules. The rules are, you have to have a star in all… in 4 out of 5 dimensions. So you would have to have a star in project management, and in… Team leadership. So I was like, okay, I would like to bump Alexa's project management. But I'm keeping the level at D, because… That's what the rules are, and the rules are in Asana. Um… These are the rules. Alex. There is a task about it. So I read through that task to be 100% sure that I'm doing the right thing, and I said. We have four stars in total, but not… in four dimensions, so it remains D. And everyone agreed with me. And then the calibration committee visited the review just on… it's actually last Friday afternoon. And they said, well, we decided to promote Alex based on that, because… Because we… that's what they thought would be the right thing, and also they are working on updating these rules here. to allow promotions in more, like, spiky profiles, when you have two stars somewhere, and no stars elsewhere. Uh, so…"
},
{
"time": "16:18:26",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm. No, I see."
},
{
"time": "16:18:31",
"speaker": "Dominik Kapusta",
"text": "Yeah, that… that happened. Oh, actually…"
},
{
"time": "16:18:31",
"speaker": "Alex Martemyanov",
"text": "Thank you."
},
{
"time": "16:18:35",
"speaker": "Dominik Kapusta",
"text": "Oh, actually, there is a change in that. If you see… The latest edit in that task. there is a sentence added. In exceptional cases, someone may have spiky dimensions performing more than one level above the next level. these can balance out dimensions that are not yet at the next level and will be reviewed case by case. So, in your case, that warranted a promotion, so that's great. Um…"
},
{
"time": "16:19:00",
"speaker": "Alex Martemyanov",
"text": "I see."
},
{
"time": "16:19:01",
"speaker": "Dominik Kapusta",
"text": "All right, so we have this. Um, and… Well, you proved that you're… operating on the D-star level when it comes to project management. Um, and uh… Where is your review again? Yes. So we have this, we… I didn't have the… evidence to… ask… bump Team Leadership to the star, but this is something we should… focus on… In the coming year."
},
{
"time": "16:19:48",
"speaker": "Alex Martemyanov",
"text": "Okay."
},
{
"time": "16:19:48",
"speaker": "Dominik Kapusta",
"text": "And it will be… Tricky. Because you're not a project advisor. And it will be… Even trickier, because you may… In your current… Work. setting. It may be tricky for you to become a project advisor, but… Let's do whatever we can to try and push that. So, in short, to become a project advisor, you should probably be able to stay in a single objective for some time. On a positive side, we have 12 months. Or six months, let's say, until you're able to operate. to work as a project advisor and make impact, right? And also, I wanted to… Clarify that it's not required. It's not required that you grow to D-star in team leadership by next cycle. It would just be great, it would be the right thing. It's just what's missing in the distal level, so… So we should focus on that specifically. Uh, team leadership… is… Essentially about accelerating the work that is being done. And it's a quote from the Professional Levels PDF. Organizational leadership is accelerating how we work. overall, like, overall, and team leadership is accelerating the work that is currently being done. So, organizational leadership is figuring out new processes, or improving existing processes, and team leadership is finding people that. Struggle at a given time and helping them move forward."
},
{
"time": "16:21:49",
"speaker": "Alex Martemyanov",
"text": "Mmhm."
},
{
"time": "16:21:51",
"speaker": "Dominik Kapusta",
"text": "And, uh… the project advisor role fits here very, very well. So it's very easy, if you're a project advisor, if you're advising projects, then you can just help move projects forward. If you're not a project advisor, you can still do it. You can still do it, but it requires you to proactively go. Go through projects and see if there's something you can help somewhere. And I imagine… It can be very hard if… You're just starting out on that? So… and I'm also… You know, we have plenty of time. But, uh, it would be great to have. Some evidence of you doing things like that. In a year from now."
},
{
"time": "16:22:44",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "16:22:47",
"speaker": "Dominik Kapusta",
"text": "Let's see, I'll try to… I'll be trying to… let you know about opportunities to do that."
},
{
"time": "16:22:58",
"speaker": "Alex Martemyanov",
"text": "Okay, so…"
},
{
"time": "16:22:58",
"speaker": "Dominik Kapusta",
"text": "You could also, if you have… Yeah, you could also, like… Look at some projects here and there. OL seems… straightforward, the most straightforward here. However, OL these days is about web extensions, mostly. And we seem to be covered there, but if there's anything… coming up in OL that I think would benefit from your help. Then the easiest is to just add yourself to the project and keep following whatever is happening there. Look at the subtasks. I don't know, help? help the DRI essentially move forward, um… And let's see how it goes. We'll… We will revisit growth areas, and also… Try to formulate something that… Not really, like, describes… What needs to happen? So that's team leadership, and that should be the main focus for next cycle. Uh, apart from that, just keep up your project management, and also getting to this start in project management, showing that you can… run projects smoothly and keep stakeholders up to date and essentially. yeah, do a good job as a… as a project DRI is… is something that will help you become a project advisor, I believe, uh, I'm sure. But the process… the process is that the ODRI selects new project advisors, and this is the main blocker now."
},
{
"time": "16:24:36",
"speaker": "Alex Martemyanov",
"text": "Okay, yeah."
},
{
"time": "16:24:44",
"speaker": "Dominik Kapusta",
"text": "So, just to end my speech… Even if you're… bored with… Uh, analyzing site breakage, or various types of breakage. Maybe if it's something that you have actually… Uh, you have a lot of experience in… maybe it would be… easier, helpful to… To stay in this area. If that's possible, if… You know, if staffing allows for that. Uh, and gain a little bit more depth. which would allow you to grow others, perhaps advise projects at some point. But let's see. For now… Take it easy. Take it easy. It's not that you have to start smashing it first week after the review. So yeah, wrap up your project. Let's see what comes next. If the next thing for you is OB, then I think it will be good. If not, we'll rearrange things and see how can we grow in."
},
{
"time": "16:25:55",
"speaker": "Alex Martemyanov",
"text": "Mm-hmm."
},
{
"time": "16:26:03",
"speaker": "Dominik Kapusta",
"text": "In a different setting, but yeah. That's what I wanted to say overall. What do you think about it?"
},
{
"time": "16:26:10",
"speaker": "Alex Martemyanov",
"text": "Yeah, sounds wise, uh… I guess so. There is. some… opportunities to be looked for in the tech designs and. Some other projects that are ongoing, related to my expertise, and uh…"
},
{
"time": "16:26:28",
"speaker": "Dominik Kapusta",
"text": "Yeah, totally."
},
{
"time": "16:26:31",
"speaker": "Alex Martemyanov",
"text": "And… Yeah, let's look for… for the OB, uh… Next project."
},
{
"time": "16:26:39",
"speaker": "Dominik Kapusta",
"text": "Mmhm."
},
{
"time": "16:26:40",
"speaker": "Alex Martemyanov",
"text": "Maybe there's something that could be done."
},
{
"time": "16:26:46",
"speaker": "Dominik Kapusta",
"text": "Cool. Cool, cool, cool. That's, that sounds good. All right, and with that, like I said, for now, let's just see what happens. Let's see where you land next next week. Mmhm. And I think that's all I had. Can I help you with anything? Is there anything you wanted to… Raise. talk about."
},
{
"time": "16:27:22",
"speaker": "Alex Martemyanov",
"text": "Okay. I… I don't know. Not really, not anything. In this tech, um…"
},
{
"time": "16:27:48",
"speaker": "Dominik Kapusta",
"text": "That's fine. That's fine."
},
{
"time": "16:27:52",
"speaker": "Alex Martemyanov",
"text": "So, yeah, there was, uh, some work, like, kinda planned for, uh, the UI test runners and, uh, all this stuff, but, uh… I'm… At the moment, I'm not doing anything related to it, just completing the TPM."
},
{
"time": "16:28:09",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm."
},
{
"time": "16:28:10",
"speaker": "Alex Martemyanov",
"text": "Um, the open… They opened, they already closed pull requests that I need to complete and. That's… that's all that's on my plate. At the moment, so I'm planning to move forward with this."
},
{
"time": "16:28:28",
"speaker": "Dominik Kapusta",
"text": "Mmhm."
},
{
"time": "16:28:28",
"speaker": "Alex Martemyanov",
"text": "organizational leadership stuff."
},
{
"time": "16:28:32",
"speaker": "Dominik Kapusta",
"text": "Okay."
},
{
"time": "16:28:32",
"speaker": "Alex Martemyanov",
"text": "But not… not right now."
},
{
"time": "16:28:37",
"speaker": "Dominik Kapusta",
"text": "Sure, sure. I mean, that's fine. Totally fine to… Like I said, to take it easy for now. Um, alright, uh…"
},
{
"time": "16:28:52",
"speaker": "Alex Martemyanov",
"text": "I mean, for sure, I… I will need to, uh, sync up with you, and… On that area, when I get my hands on it."
},
{
"time": "16:29:00",
"speaker": "Dominik Kapusta",
"text": "Mm-hmm. Yeah, yeah, we can do it next."
},
{
"time": "16:29:03",
"speaker": "Alex Martemyanov",
"text": "But yeah, just not ready."
},
{
"time": "16:29:05",
"speaker": "Dominik Kapusta",
"text": "next week, um… Later. Should be fine. All right, all right."
},
{
"time": "16:29:15",
"speaker": "Alex Martemyanov",
"text": "Thank you."
},
{
"time": "16:29:20",
"speaker": "Dominik Kapusta",
"text": "Good. So if nothing else, we can wrap it up here. I don't have any other announcements, any other important info. I'm also… deep down in my project, trying to open a ship review today, so let's see. And then I'm taking 3 days off, finally. So I'll be back next week."
},
{
"time": "16:29:43",
"speaker": "Alex Martemyanov",
"text": "Okay."
},
{
"time": "16:29:43",
"speaker": "Dominik Kapusta",
"text": "But we'll see each other weekly. If I know anything from Jonathan, I'll let you know. Because I'm curious myself. So let's see. Good. If that's it, we can wrap it up here. Congrats again. You're doing a great job. It's a pleasure to be working with you, and yeah, we'll keep smashing it, hopefully, starting next week."
},
{
"time": "16:30:05",
"speaker": "Alex Martemyanov",
"text": "Thanks."
},
{
"time": "16:30:12",
"speaker": "Dominik Kapusta",
"text": "Awesome."
},
{
"time": "16:30:13",
"speaker": "Alex Martemyanov",
"text": "Okay."
},
{
"time": "16:30:14",
"speaker": "Dominik Kapusta",
"text": "Thank you. Thanks and have a great rest of the day. See ya."
}
]
}
@@ -15,3 +15,130 @@ source: "https://us01mynotes.zoom.us/p5FdcX9WT-afBpWjRgaW0w"
- **16:01:44 · Dominik Kapusta:** Is it going.
- **16:01:46 · Alex Martemyanov:** And then… I'm pretty good. Thank you. After you… after last week's, uh… I was… So all this RKAFK, so I'm… Wrapping up the top priority project. Mostly, mostly it finally merged the link tooltip thing from the Hug days.
- **16:02:10 · Dominik Kapusta:** Jest.
- **16:02:13 · Alex Martemyanov:** And basically no progress on other stuff yet.
- **16:02:19 · Alex Martemyanov:** I need to finish the priority cleanup. So basically last week we've discussed it during the OE that we should. Basically wrap up the project with the. No visible outcomes. There was a slight decline in the numbers and several genuine bugs fixed, but they were not representing the main feature breakage.
- **16:02:45 · Dominik Kapusta:** Nie. Drop, Ios.
- **16:02:50 · Alex Martemyanov:** I know.
- **16:02:57 · Dominik Kapusta:** Łazać.
- **16:03:00 · Alex Martemyanov:** There was some decline, maybe a third. So there was a decline in some part. of the numbers, but there is still around 40%. of the event sequence of the received events that so basically most of it is. The data we received for most of the breakage pixels represents just regular normal flow and nothing obviously.
- **16:03:34 · Dominik Kapusta:** Bardzo.
- **16:03:34 · Alex Martemyanov:** pointing to anything. So the discussion during the OE was to basically clean up the inefficient fixes that we've got. The feature flags for the features that are removed and some. Um, like the pinned tabs management fix, uh, that are, um, staying without the feature flag. And, uh… Yeah, clean up the data that's being collected, because we've collected enough of it, and, uh, implement some permanent data collection that stays there for, uh. for diagnostics for the future possible breakages. And try to add some in. inside of the extension, some metrics inside of the extension to, um, to track the loading progress, basically. Where we… where do we stop, and where the messaging.
- **16:04:23 · Dominik Kapusta:** Ok.
- **16:04:31 · Alex Martemyanov:** Stops. and try to reason about it from from that perspective.
- **16:04:37 · Dominik Kapusta:** Misji.
- **16:04:39 · Alex Martemyanov:** So, uh… So yeah, probably today I'm going to open the featured slugs and clean up PR. And. later this week will complete. So I've updated the project, moving on the post-mortem to the next week, since last week I had no time to. completed due to some circumstances. And, uh… That's mostly it. I still got some. PRs requiring my attention, like the crash reporting fix. So, yeah, no updates since last week. On it. So, basically, my concern about it is, uh, we may, uh, we may break the existing macOS collection while fixing iOS collection, so I need to… reproduce it, reproduce the crash and. this slowdown condition and normal conditions and see how it if it still works and nothing breaks and then I'll proceed with it.
- **16:05:49 · Dominik Kapusta:** Collection as in…
- **16:05:52 · Alex Martemyanov:** The App Store reports.
- **16:05:53 · Dominik Kapusta:** Crosscode? Yeah, cross-collection, mhm.
- **16:05:57 · Alex Martemyanov:** Yeah, so matching against process identifier or by date.
- **16:06:02 · Dominik Kapusta:** Yeah. Yeah, yeah, yeah, yeah.
- **16:06:05 · Alex Martemyanov:** Mmm.
- **16:06:05 · Dominik Kapusta:** Oh. Right.
- **16:06:14 · Alex Martemyanov:** And… That is it, I guess, so… I'm. I'm not top performing for the last week. So just… Just completing the TP stuff.
- **16:06:35 · Dominik Kapusta:** Yeah, which is…
- **16:06:36 · Alex Martemyanov:** And yeah, there was…
- **16:06:38 · Dominik Kapusta:** Expected.
- **16:06:39 · Alex Martemyanov:** And there was the maintenance, the release maintenance. Luckily, it was growing weak.
- **16:06:46 · Dominik Kapusta:** Mm-hmm.
- **16:06:47 · Alex Martemyanov:** So nothing else ended from it.
- **16:06:48 · Dominik Kapusta:** I saw that, yeah, that's good, that's good. All right. Nice. That's fine. So you're going to wrap up your project. Will you run the postmortem this week or next week?
- **16:07:05 · Alex Martemyanov:** Next week, next week.
- **16:07:06 · Dominik Kapusta:** Next week. Mm-hmm. Okay.
- **16:07:07 · Alex Martemyanov:** So this week, I'm, uh… Completing the cleanup. And the next week is time for the postmortem.
- **16:07:18 · Dominik Kapusta:** Sounds good. Alright, and then… Do you have… Do you know anything about… You're next. Top priority?
- **16:07:32 · Alex Martemyanov:** Uh, nope.
- **16:07:35 · Dominik Kapusta:** Yeah, because there won't be any follow-up… there won't be any follow-up in OE for…
- **16:07:35 · Alex Martemyanov:** I guess I should make one.
- **16:07:41 · Dominik Kapusta:** For this. I mean…
- **16:07:44 · Alex Martemyanov:** Well, I guess not, at least for the moment.
- **16:07:45 · Dominik Kapusta:** Immediate follow up at least. Yeah, yeah, yeah.
- **16:07:49 · Alex Martemyanov:** And, uh… So if we are shifting the diagnostics into the JavaScript part, it's probably… due to some someone else to. Keep up with it.
- **16:08:05 · Dominik Kapusta:** No.
- **16:08:05 · Alex Martemyanov:** So maybe there will be a follow-up task to perform the data analysis next week.
- **16:08:12 · Dominik Kapusta:** Mm-hmm.
- **16:08:12 · Alex Martemyanov:** So just one, one cloud shot. To fetch the data, to perform the analysis, to see the trends, and if… Anything new is highlighted from it. So I could person. Wrap up up a date. And that's it. And it goes after.
- **16:08:29 · Dominik Kapusta:** Yeah, yeah.
- **16:08:31 · Alex Martemyanov:** Two weeks from now, I guess, when the release is out.
- **16:08:39 · Dominik Kapusta:** All right, fine, we'll need to learn what's next for you. When would you be opening? When would you be opening a top priority, Fred?
- **16:08:47 · Alex Martemyanov:** Gosh. Probably now.
- **16:08:53 · Dominik Kapusta:** Yep.
- **16:08:55 · Alex Martemyanov:** It's really, it's a good time.
- **16:08:55 · Dominik Kapusta:** Okay. Okay, this is interesting then. There will be some work. shaping up in OB. If you're up for it, that may be interesting. I'm not sure how much native support they need, but… It is… considered a big problem these days, and that's the fact that all the JavaScript code injected into our websites causes performance issues. And side breakage. But… Yeah, well, both of them, essentially. And I'm, like I said, I'm not sure… If… A native engineer would be needed immediately. But if so, then… that… That would be very important. So this is very important. And… Let me see… So the assessment is this Thursday. And the projects… Okay. Let's see. Let's see. I see there is a… So this is the assessment task. And there is a subtask for the… staffing for the Apple team, so it sounds like they will need… they will need someone from the Apple team. This is not finalized yet, but… But, uh… Should probably be… should probably be… filled out today, I hope. I'll have the proposed critical path and Gantt chart ready for review on Tuesday. I'm proposing OB focus on performance this cycle, specifically the cost of the JS and config we inject into every frame.
- **16:11:21 · Alex Martemyanov:** Thank you.
- **16:11:21 · Dominik Kapusta:** They may at least need someone on the native side to, I don't know, implement some. measurements. I suppose. If this is something that… would be of interest to you, then that's great, because if not, I think you will still be mentioned there. What do you think?
- **16:11:58 · Alex Martemyanov:** Visibility. What is this discussion? That you mentioned.
- **16:12:04 · Dominik Kapusta:** I was just reading the last comment in the thread.
- **16:12:07 · Alex Martemyanov:** Okay.
- **16:12:08 · Dominik Kapusta:** From Dave.
- **16:12:22 · Alex Martemyanov:** Mmm… Well, looking at my current TP, if it can be reproduced, it would be more of a… something that I would be interested in, if… And if it's something like we got some breakage to fix it. Not so exciting, I'd say.
- **16:12:52 · Dominik Kapusta:** Yeah, yeah, yeah, I can tell. I can tell. This, however, should be easier. On the functional side, on the technical side, it should be easier. at least from…
- **16:13:10 · Alex Martemyanov:** Yeah, at least if there is exact cases reported on or some exact websites.
- **16:13:13 · Dominik Kapusta:** Yeah, I know. Uh, it may be… it may be about… it may be about just measuring things.
- **16:13:17 · Alex Martemyanov:** It should be easier.
- **16:13:22 · Dominik Kapusta:** So that front-end engineers can… Do changes, make changes. But I don't know. I don't know the details. Let's see. Trim the Apple Cs. Bundle and isolated world.
- **16:13:37 · Alex Martemyanov:** Okay, I'm fine to get mentioned on the thread, and so for the next TP, I'll probably open it on Thursday, I guess.
- **16:13:38 · Dominik Kapusta:** Interesting. Mmhm.
- **16:13:47 · Alex Martemyanov:** Makes sense.
- **16:13:49 · Dominik Kapusta:** Yeah, probably. I think it makes a lot of sense. I will be AFK for the rest of the week. Um, Bob…
- **16:13:57 · Alex Martemyanov:** Mm-hmm.
- **16:13:59 · Dominik Kapusta:** It's not a problem, of course. Um… I will try to… Try to reach out to Jonathan to ask. If he knows anything about OB plans for a pool. Or if he knows anything about anything else. Any other objective that might need Apple people and I'll let you know. Do you want to talk about your performance review?
- **16:14:31 · Alex Martemyanov:** Uh, yes, I guess so.
- **16:14:35 · Dominik Kapusta:** Why not? Right. All right. I linked it in the agenda, updated the link to the latest review. So, congrats on the promotion!
- **16:14:52 · Alex Martemyanov:** Thanks.
- **16:14:52 · Dominik Kapusta:** Amazing, you made it.
- **16:14:53 · Alex Martemyanov:** I guess it was a lot of your efforts.
- **16:14:55 · Dominik Kapusta:** uh…
- **16:15:00 · Alex Martemyanov:** Involved to make it go through.
- **16:15:06 · Dominik Kapusta:** Just a bit, really. It's, you know, this… this performance review time is overall great. I mean, I like it. I like… I like working on it, because it's, uh…
- **16:15:17 · Alex Martemyanov:** Bye.
- **16:15:19 · Dominik Kapusta:** Um… okay. It's a great time. When you can appreciate people you work with and be able to do something for them. uh… make them… make their efforts visible and recognized. So, if that works, then that's great. This time it worked, so that's amazing. Uh, but… At the end of the day, it's just your work. put into the project. Uh, and, uh, and that got you… a bump in project management, which is amazing, which is… it's essentially hard facts, especially this year. If you look at the… if you look at the review… Format. It's… Like, dry facts. Nothing else, no pros, no…
- **16:16:13 · Alex Martemyanov:** Mm-hmm.
- **16:16:15 · Dominik Kapusta:** Did a great job! everyone likes you, and so on and so on, like it used to be in the previous years. This time, it's, like, super, super concrete. With dates, with complexity assessments, with… The amount of direction needed.
- **16:16:32 · Alex Martemyanov:** Mmhm.
- **16:16:33 · Dominik Kapusta:** with clear impact stated in each bullet point. So it's just your work. distilled into a few sentences. So… Yeah, great job and keep doing that. I have to say… I have to say, I didn't ask for a promotion, because… I learned that these are the rules. The rules are, you have to have a star in all… in 4 out of 5 dimensions. So you would have to have a star in project management, and in… Team leadership. So I was like, okay, I would like to bump Alexa's project management. But I'm keeping the level at D, because… That's what the rules are, and the rules are in Asana. Um… These are the rules. Alex. There is a task about it. So I read through that task to be 100% sure that I'm doing the right thing, and I said. We have four stars in total, but not… in four dimensions, so it remains D. And everyone agreed with me. And then the calibration committee visited the review just on… it's actually last Friday afternoon. And they said, well, we decided to promote Alex based on that, because… Because we… that's what they thought would be the right thing, and also they are working on updating these rules here. to allow promotions in more, like, spiky profiles, when you have two stars somewhere, and no stars elsewhere. Uh, so…
- **16:18:26 · Alex Martemyanov:** Mm-hmm. No, I see.
- **16:18:31 · Dominik Kapusta:** Yeah, that… that happened. Oh, actually…
- **16:18:31 · Alex Martemyanov:** Thank you.
- **16:18:35 · Dominik Kapusta:** Oh, actually, there is a change in that. If you see… The latest edit in that task. there is a sentence added. In exceptional cases, someone may have spiky dimensions performing more than one level above the next level. these can balance out dimensions that are not yet at the next level and will be reviewed case by case. So, in your case, that warranted a promotion, so that's great. Um…
- **16:19:00 · Alex Martemyanov:** I see.
- **16:19:01 · Dominik Kapusta:** All right, so we have this. Um, and… Well, you proved that you're… operating on the D-star level when it comes to project management. Um, and uh… Where is your review again? Yes. So we have this, we… I didn't have the… evidence to… ask… bump Team Leadership to the star, but this is something we should… focus on… In the coming year.
- **16:19:48 · Alex Martemyanov:** Okay.
- **16:19:48 · Dominik Kapusta:** And it will be… Tricky. Because you're not a project advisor. And it will be… Even trickier, because you may… In your current… Work. setting. It may be tricky for you to become a project advisor, but… Let's do whatever we can to try and push that. So, in short, to become a project advisor, you should probably be able to stay in a single objective for some time. On a positive side, we have 12 months. Or six months, let's say, until you're able to operate. to work as a project advisor and make impact, right? And also, I wanted to… Clarify that it's not required. It's not required that you grow to D-star in team leadership by next cycle. It would just be great, it would be the right thing. It's just what's missing in the distal level, so… So we should focus on that specifically. Uh, team leadership… is… Essentially about accelerating the work that is being done. And it's a quote from the Professional Levels PDF. Organizational leadership is accelerating how we work. overall, like, overall, and team leadership is accelerating the work that is currently being done. So, organizational leadership is figuring out new processes, or improving existing processes, and team leadership is finding people that. Struggle at a given time and helping them move forward.
- **16:21:49 · Alex Martemyanov:** Mmhm.
- **16:21:51 · Dominik Kapusta:** And, uh… the project advisor role fits here very, very well. So it's very easy, if you're a project advisor, if you're advising projects, then you can just help move projects forward. If you're not a project advisor, you can still do it. You can still do it, but it requires you to proactively go. Go through projects and see if there's something you can help somewhere. And I imagine… It can be very hard if… You're just starting out on that? So… and I'm also… You know, we have plenty of time. But, uh, it would be great to have. Some evidence of you doing things like that. In a year from now.
- **16:22:44 · Alex Martemyanov:** Mm-hmm.
- **16:22:47 · Dominik Kapusta:** Let's see, I'll try to… I'll be trying to… let you know about opportunities to do that.
- **16:22:58 · Alex Martemyanov:** Okay, so…
- **16:22:58 · Dominik Kapusta:** You could also, if you have… Yeah, you could also, like… Look at some projects here and there. OL seems… straightforward, the most straightforward here. However, OL these days is about web extensions, mostly. And we seem to be covered there, but if there's anything… coming up in OL that I think would benefit from your help. Then the easiest is to just add yourself to the project and keep following whatever is happening there. Look at the subtasks. I don't know, help? help the DRI essentially move forward, um… And let's see how it goes. We'll… We will revisit growth areas, and also… Try to formulate something that… Not really, like, describes… What needs to happen? So that's team leadership, and that should be the main focus for next cycle. Uh, apart from that, just keep up your project management, and also getting to this start in project management, showing that you can… run projects smoothly and keep stakeholders up to date and essentially. yeah, do a good job as a… as a project DRI is… is something that will help you become a project advisor, I believe, uh, I'm sure. But the process… the process is that the ODRI selects new project advisors, and this is the main blocker now.
- **16:24:36 · Alex Martemyanov:** Okay, yeah.
- **16:24:44 · Dominik Kapusta:** So, just to end my speech… Even if you're… bored with… Uh, analyzing site breakage, or various types of breakage. Maybe if it's something that you have actually… Uh, you have a lot of experience in… maybe it would be… easier, helpful to… To stay in this area. If that's possible, if… You know, if staffing allows for that. Uh, and gain a little bit more depth. which would allow you to grow others, perhaps advise projects at some point. But let's see. For now… Take it easy. Take it easy. It's not that you have to start smashing it first week after the review. So yeah, wrap up your project. Let's see what comes next. If the next thing for you is OB, then I think it will be good. If not, we'll rearrange things and see how can we grow in.
- **16:25:55 · Alex Martemyanov:** Mm-hmm.
- **16:26:03 · Dominik Kapusta:** In a different setting, but yeah. That's what I wanted to say overall. What do you think about it?
- **16:26:10 · Alex Martemyanov:** Yeah, sounds wise, uh… I guess so. There is. some… opportunities to be looked for in the tech designs and. Some other projects that are ongoing, related to my expertise, and uh…
- **16:26:28 · Dominik Kapusta:** Yeah, totally.
- **16:26:31 · Alex Martemyanov:** And… Yeah, let's look for… for the OB, uh… Next project.
- **16:26:39 · Dominik Kapusta:** Mmhm.
- **16:26:40 · Alex Martemyanov:** Maybe there's something that could be done.
- **16:26:46 · Dominik Kapusta:** Cool. Cool, cool, cool. That's, that sounds good. All right, and with that, like I said, for now, let's just see what happens. Let's see where you land next next week. Mmhm. And I think that's all I had. Can I help you with anything? Is there anything you wanted to… Raise. talk about.
- **16:27:22 · Alex Martemyanov:** Okay. I… I don't know. Not really, not anything. In this tech, um…
- **16:27:48 · Dominik Kapusta:** That's fine. That's fine.
- **16:27:52 · Alex Martemyanov:** So, yeah, there was, uh, some work, like, kinda planned for, uh, the UI test runners and, uh, all this stuff, but, uh… I'm… At the moment, I'm not doing anything related to it, just completing the TPM.
- **16:28:09 · Dominik Kapusta:** Mm-hmm.
- **16:28:10 · Alex Martemyanov:** Um, the open… They opened, they already closed pull requests that I need to complete and. That's… that's all that's on my plate. At the moment, so I'm planning to move forward with this.
- **16:28:28 · Dominik Kapusta:** Mmhm.
- **16:28:28 · Alex Martemyanov:** organizational leadership stuff.
- **16:28:32 · Dominik Kapusta:** Okay.
- **16:28:32 · Alex Martemyanov:** But not… not right now.
- **16:28:37 · Dominik Kapusta:** Sure, sure. I mean, that's fine. Totally fine to… Like I said, to take it easy for now. Um, alright, uh…
- **16:28:52 · Alex Martemyanov:** I mean, for sure, I… I will need to, uh, sync up with you, and… On that area, when I get my hands on it.
- **16:29:00 · Dominik Kapusta:** Mm-hmm. Yeah, yeah, we can do it next.
- **16:29:03 · Alex Martemyanov:** But yeah, just not ready.
- **16:29:05 · Dominik Kapusta:** next week, um… Later. Should be fine. All right, all right.
- **16:29:15 · Alex Martemyanov:** Thank you.
- **16:29:20 · Dominik Kapusta:** Good. So if nothing else, we can wrap it up here. I don't have any other announcements, any other important info. I'm also… deep down in my project, trying to open a ship review today, so let's see. And then I'm taking 3 days off, finally. So I'll be back next week.
- **16:29:43 · Alex Martemyanov:** Okay.
- **16:29:43 · Dominik Kapusta:** But we'll see each other weekly. If I know anything from Jonathan, I'll let you know. Because I'm curious myself. So let's see. Good. If that's it, we can wrap it up here. Congrats again. You're doing a great job. It's a pleasure to be working with you, and yeah, we'll keep smashing it, hopefully, starting next week.
- **16:30:05 · Alex Martemyanov:** Thanks.
- **16:30:12 · Dominik Kapusta:** Awesome.
- **16:30:13 · Alex Martemyanov:** Okay.
- **16:30:14 · Dominik Kapusta:** Thank you. Thanks and have a great rest of the day. See ya.