 Hi Israel, can you hear me now? Hello Peter. I don't know what else is coming because it did not respond on Discord. Oh Sandy, it's coming, okay. Good. I'll just wait for him there. And I think Takuma is also coming. I believe so. I'm sorry to rate this, I'm mistaken. I log in on the usual meeting room, yeah, sorry. Hey Takuma, no problem. We're still waiting for Sandy as well. Hey everyone. Hi Sandy. Before we get started, does anyone have any discussion items? No, I don't have any. My personal notification exists, yeah. Okay. Can you hear me? Yeah. Okay, so I'm sorry that I'm next week I moved to UK. I live in UK. So it is difficult for me to join this time slot, but it is no problem. So Israel will attend this time slot, yeah. So please continue this usual meeting but I will not attend. You can join on 3am. If you wish. Of course, if I wish, I will attend. So in UK so that this is, this time maybe midnight. If my potential exists, I will attend. Yeah, thank you. Well, have fun in the UK. Yeah. Yeah, enjoy in London. And maybe so one or two years I stay in UK here. Okay. Yeah, sorry to lose you here in San Francisco but. Yeah, yeah, yeah. Here's where it is. Yeah, yeah, yeah, yeah. San Francisco and so the California is very good place but as for my work, my work so that I will move to UK. Sounds good. Sounds good. Other than that, do we have any targets and do we have anything to discuss today? For me, nothing. Yeah, I don't have anything from me. Okay, no maybe I'll just do one thing. I'll do a screen share and I show how to do the setup of the branch protection rules so that certainly CI jobs are mandatory. I'll do a quick screen share. So if you are here on the main page, then you click settings. Then you go branches. Then there's this branch protection rules, which there could be multiple but we only have protection for the main branch. And then there's this list of settings here and ultimately. There's this status checks are required. And then you can just search for things. And I'll just search for what Sandy gave me. So there's all three of them you do you want all three of them. Yes. Okay. Only an admin can do this right. We don't have permissions to do this. I honestly don't know. The reason why I figured it's a good idea to show you because then you can go and check if if you can actually do it. Okay, I actually tried it. So there was no and they didn't let you. Yeah. Oh, that's not good. Yeah, we should fix that. Oh, because I don't want to be the only admin. Because then the. Okay. What. Jesus. What is happening. Well this went south fast. Yeah, and every all the change I just made disappeared. Give me one second I need to get my phone. Okay on the phone the the app is asking for a number, but there is no number anymore. Oh, Jesus. Okay, I haven't seen this one before. Then let me why don't I just try the other thing, which is if I go to hyper literate self. Teams. And then there should be. Probably still called cactus. Yes. Security administration. Contributors. Maybe the maintainers don't have admin team discussions. I don't care about that. Members that I'm trying to find out what permissions this has. Because one of these teams is this one security administration. But where does it show what are the permissions. Click on the members. But you're also a maintainer. Oh, this just takes me to. Something real quick. If I just add you here now. Oh, no. It's not going to work. Okay. Oh, maybe now there we go. The app popped up the question 50 on approve. Yes, okay. I don't I still don't know why don't you have to maintain or label. Oh, maybe I, maybe I also need to add you. No, you're in there. So then where do I get this? Where to get that label from? Not sure. Well, either way, can you can you please check real quick if you have permission to add jobs? Okay, let me check. Yeah, now I can see all those options. Okay. Yeah. Just add. Everyone to this security administration group. I don't know why. Or how this came to be that the maintainers are not admin. It's just a security thing. But it wasn't your own. She was around. That's the discord. Yeah. Yeah. You got it. Okay, great. Yeah. We are. I joined the security. Yeah. Okay, I sent it to Israel as well. So then Peter, Jack, please send it. Okay. It should be good. Okay, well then that's all I had. For the meeting. Does anyone have anything else? Nothing from me. So there's just one thing I, so I said on the slide. Sorry, the score, right? Two of the workflows were failing and the errors are like completely random every time. Maybe if we have some time, check it sometime. Yeah, I'll open bugs right now. It's a, it's another thing. I think it's happening after I added something about. Yeah. Build jet thing. Has its own problems. Nothing. Yeah, the, the only real solution will be. I think if you just cut down on the bloat and the CI by not executing tests that don't need to run because we haven't changed the code that they're testing. Okay. I guess we can do that by adding the path. And the criteria to run. Something like that, but it's going to be more complicated. Okay. I opened the issue for it. And I'm going to ask, I already asked Jack to work on it. It's just one that it's a one put the link in the chat. Sorry. So I opened this issue. And I want to get this done as soon as possible because we are not going fast enough because of the CI, which is super annoying. It should run. Maximum health an hour and then it should be done. So I'm going to have to fix this quick because it's great to have good test coverage, but if it then just slows us down to health and it's pointless. Yeah. For the issues. So the failures that you saw. If you could save the logs of it. That would be great. Okay. I can, I can show you how. I'll share my screen again. Because there's a specific way that works better than others. Give me one second. Yeah. So if you have a job. Like the CI job. And then it failed like this one. And then something failed. I don't know what happened here, but anyway. Okay. So there's some crash with some random stuff. And the best way to do it is to click on this gear and the same view or logs or the one that says download log archive. These two. And then because if you just. So if you just save this link. It will actually expire in about a week and then this link goes dead and it doesn't have the logs anymore. So that's why it's recommended that you actually back up the entire log as a text file or as a zip on your machine. And then you put that as an attachment. To the issue itself. When you open it. Okay. Okay, probably did the same thing here. Yeah. This is how you should do it. If you look at this issue. This one, then you see that. I have a little excerpts, but then I also have the full attached. Okay. Yeah, that's it. Oh, and then the other thing. I don't know if you've seen this or not. Sorry, I just have things that come up as I try to stop talking. So if you have something in this giant cactus. Oh, God, they're force pushing every two minutes triggering a new run. So yeah, first of all, it's efficient to cancel these if you see this someone like Sharrell for example, just sent in five commits on the same PR then you can just go and cancel the old ones because those are not they're just going to waste time by running. So I did something to automatically cancel these right. Yeah, but I'm not sure if it works or not. Okay. Because these should have been canceled then. Yeah, true. But they were. So yeah, you can do that, but then also. If something specific failed just a single job then. I recommend instead of free running the entire thing just rerun failed jobs and then it gives you a list of just the ones that are going to go again. This was originally the reason why I had all these jobs like 40 or 50 jobs or maybe even more in the same YAML file just so that we can easily use this rerun failed jobs thing. Because it's easier to manage it that way. But it also has its downsides it's like pros and cons. But anyway, I really I will really stop talking now. That's all I had. And if no one else has anything here then thanks everyone for joining and I'll talk to you next time. Thank you. Thank you. Bye.