 I'm recording. So good evening, good afternoon, good morning, good night everybody around the world listening to this Google Summer of Code office hour of 4th of August. And Dirage looks tired on the video, but I didn't want to bother you with that. So welcome everybody. We have Adrian, Raj, Chris and Vian around the table here. So I have no special announcement to do right now. So let's go straight into the matter. I think that in India the new university semester starts so a lot of people are busy. Work is going on. So Dirages, your camera is on. You're the first one to give us an idea. What's happening? Where you are? Do you have any impediments? Yes, thank you. So what's happening is we just merged our PR of this week, which talks about, I mean, which makes it possible to schedule the times we read the update center. So with that in place, you would be able to configure it however the way we want the update center to be read once a day, once a month, twice a day, anything. And after that, I also, I was also a bit confused this week because I did not clear the difference between the terms that scheduling and batch updates. So then my mentor helped me to understand the difference this of a weekly meeting that happened. So that was a big help because I was looking in the wrong direction to solve an issue. So that was a big help. And after that, today I also reviewed the PR related to probe engine, which has been opened by my mentor Adrian. So that was very, very helpful to me to see how we have an idea and how do you write a code for it. So that and actually the tests that he wrote. So even I read them, it made sense to me how testing is done. So that is also one very important thing that I learned this week. And so for now, I don't have any impediments. And if I share with you what we will be working next is I see there's an issue that Adrian has created where we would need to document the probes that we have applied till now on the plugins. I would need to get discuss it more with him. But this is something we need to work on. It's like a documentation enhancement kind of issue so that any outsider who does not work with our project can also see what we're working on right now. So it's just like provide the bigger picture or current status of the project. And there are a few more two, three more issues for me. So I will, I cleared the priority on how should I work on them with my mentor in the weekly meeting. So I'll be working on them this week, like tomorrow, there's one in progress. And I did read few things about it. So if I still don't understand how to do that, I will reach out to my mentors like 13 hours from now, not 13, yes, 13 hours from now. That's the plan. Okay, that sounds great. There are two important words I remember and noted from your presentation. It's first, you learned a lot of things, which is great testing in these kind of thing. And you're working very well together with your mentor, Adrian. So thank you, Adrian, also for your help. Adrian, something you would like to help or to add or before we move on? No, no, no, really. I appreciate what George and the work he has done and the research he has done. So when he has, he's not waiting, he's not asking question and I wait for me to give him the answer. He's looking on his own. And that's very, that's a very nice thing to see. So I don't have anything more to say. The Irish is doing great, great work. And we have, even though it might not be on the first, what we add in mind at first, we still have many things for the Irish to do and things on which he will learn new things, which is really the important part for the project. Really like to hear that. So very good. Thank you for both, for doing all that, looking forward to see. The next one in the row is Vihan. Do you hear us? Are you in the state to answer us? Go ahead, Vihan. Hello everyone. So in the past two weeks, I've spent most of my time researching about ways I can break down the ASCII law. So there's been a lot of trial and error. And I've tried some approaches, failed in some and thought that some are good. And also in the process found some anomalies in the documentation generator that are present. So to start with, I found that a lot of documentation on the five steps is repeated. So for example, the class that SCM is present in six different places, and it on itself might carry around a thousand lines of ASCII. So that is 5000 lines of redundant data that we don't want. And this is a proof for every other SCM provided. So there is, I could comfortably say there are more than 100,000 lines of ASCII. Which are repeated in the five steps reference. So my goal would be to divert them onto a single new location, a new page so that I can link that page to every location where we want to see it. So this is the way I want to abstract that particular piece of documentation. And to do that, that breakdown, the breakdown thing, I've tried some approaches. So the first one was to basically alter the two ASCII dog generation process itself. So from the Java man that we have, we generate the ASCII dogs. And in that in between are the functions where we enumerate the nested choice of objects. I tried to detect the number of parameters nested within and then try to set a threshold for them so that we can alter the configuration to maybe send and put a new page. But that was not very straightforward. Like I tried a lot, tried some algorithms also, tried to find the depth of the tree. I tried to visualize a tree and try to find a depth. But the thing is, both the functions are recursively calling each other. And it's becoming very hard to keep track. So mind blowing. So the approach that I think will work now is to add a processing layer to the existing ASCII dogs that are generated from the two ASCII dogs. So that is to not trouble the two ASCII dog at all. And once we have the list of ASCII dogs in that folder, I will create another layer on top of that, which will process them and will result in actually filtering out the part that we want. So basically, we are now changing our field of study from working with Java objects to basically a string array of the lines of each file. So working with it, with it is much easier. Although it does not make sense because the repetition is still happening in the first go and we're removing it in the processing layer. But I think for now it is the easiest way for me to implement it. And it's easier to make changes in configuration as well if you're just working with strings compared to Java object. So that is something that I have to start working on. This looks like an interesting puzzle to solve for. Okay. Thank you for the update, Vian. And well, good luck in your exploration, although I'm convinced that you and your mentor are going to solve that. Okay, the next one is Yiming. Hello, Yiming. Do you hear us? Hi, I can hear you. Great. How are things going? Okay, I like to share my words recently. So firstly, I keep supporting multiple languages demo by making users choose based images in the action parameters. So there are some issues previously, but I know I fixed it because Abel Adaya suggested that previous parameters cannot support the alpine image compilation. So I added some new features on it. Now this request has been merged yet. So users can use them. And secondly, I submit the changes in JFR for for a new core and the plugins. This is important. And as I haven't made the thirdly, I haven't made the project plan for the second phase. I also make the project plan accordingly. And finally, I also try to support the runtime type actions for Windows runners based on our weekly meetings. So this, this poor request is under review now. Yeah, that's my work recently. Hey, that sounds really interesting. And yeah, a good, good thing. And congratulations because you have upstream pull requests being merged. So there's also a very good you mean, so well done. Oh, thank you. Good. Chris, do you want to add something to Yamings project or I think we will need to work on the bit more documentation later, but over as the power has been good. And that's the impression I have to so well done. Really impressed by the good work doing. I see that you all progressing well and learning. Well, I hope you're enjoying it. Also, although it's hard work, but it really looks good and impressive scene from from my side here. Does somebody want to add something or see the message from from beyond? Okay, great. He just said that he enjoyed doing all this. So if somebody I let the mic open now, if somebody wants to add either a question or a comment or tell us something, he can speak now. Three, two, one. So I wish you then, oh, congratulations. Well done. Looking forward to next week's update and see how things are going. So we have a nice rest of the day and a nice week, everybody. Thanks. Bye everybody. Bye. Bye everyone.