 So, hello everyone. So, today is July 20th and it's, let's see, so today it's a meeting for GitLab plug-in modernization for Jenkins, GSOC. And we have, let's see, let's make sure my screen first. So, okay, can you see? Yep. Okay, so do you want to report what you have been able to achieve over the last two weeks? So, maybe Ajay. Yeah, so, yeah, so I was working on the milestone tool and now it's successfully working interactively except one problem that I was having with it, like the merge request was not working because like the merge request state enum was not matching with the older state enum in the GitLab plug-in. So, instead of using the updated and reopened enum, either I'll be using the opened enum or the all enum. So, we'll have to decide more about it a bit more. Other than that, everything is working fine. And I've also added the document, like not the documentation, but the ordered checklist of what to test interactively on the GitHub channel. Maybe I'll also add it in the modernize the GitLab plug-in modernization meeting notes so that the mentors can test it interactively and find if there is something wrong with it and inform me so that I can fix it. I'll be also debugging the code, the milestone tool code now in the meeting just so that it could be used as a reference for the review, for the reviewer that is Basil and Chris and Mark so that they can know what's wrong and what's right and can be sure that it's working properly. So, other than this, I am the problem that I am facing currently is more on the test part, like one issue that I had was the GitLab SSL test was not working on the Windows, but it on the Windows operating system, but it was working on the Linux environment. So, like, I don't have any clue why it's happening, to be honest. And I think I'll need some help on that. And on the other tests, like the tests in the milestone, one will be disabled because I decided as per Basil's suggestion that the test will be, the PR for the test will be in the milestone three. So, I'll be, I'll be disabling the milestone one test. And I'll be also making a normal PR for the second milestone by like a new PR, not the draft one with all those changes. First, the milestone one full request will be merged this week most probably like, sorry, the next week most probably, and the milestone two PR will be merged after that if the interactive testing is working properly and Basil gives a positive review on that. Okay, so that's what happened. Other than this, the test could be a block, could be a potential blocker for me, because I still don't know why it's not working properly, but the connection tests are fixed, but not the JSON API responses that I'm getting from GitLab are differing, and I have to fix it, but there are still some differences which I'm not able to figure out why it's not working the way I want it to work. So I think tests will require a bit more work on my side, which will be in the milestone three. So yeah, I'm hoping for two merges back to back, I guess, next week. Other than this, there are also some other pull requests in the GitLab plugin, which I want to be merged after the second milestone, like next to next week, so yeah, don't merge it right now. After the milestone two code is merged into the GSOC project branch, then it can be merged into the master branch. Okay. Other than this, the milestone four will be for the proxy, and the milestone five will be all about the documentation changes that we want to have. There is a documentation PR by Mark, and a PR will be also be made by Chris and by me. So we'll have a lot of documentation to add and at the last part of the modernization project. Yeah, looks good. So far so good except for the tasks we need to work on a bit. Yeah, we need to work on them because the problem with the tests is I'm not getting the response from the merge request. For some reason, I am quite feeling that if I try to make the test work after the milestone two tests, actually, I'm trying to make them work together, maybe that will work better. But I just have an intuition for it, but just let me try. First, I want those two milestone pull requests to get merged, and after that, I'll start working on the test extensively. It should not be that bad to be honest, but it can be bad because the sample events, not the events, the sample hooks that were created, it was a very different approach that the author took, and we have to create the corresponding events for that and then simultaneously match it. And it's a lot of matching matching things that I have to do. And it's a lot of manual labor that I'm currently doing, trying to match them all. Okay. Yeah, sounds good. Okay, so let me check like for the look somewhere, maybe if I'm last week and see if I've missed anything. So Mark will be out just for this week and you're back next week, so we can talk to him about like what he wants, like what he thinks about the plans we have next week. So I think we cover everything so far, yeah. So can we post it about the tasks? Like what? Can we post it about the tasks? So is like if you encounter like any like if you get stuck for too long or yeah, you can find a solution together. Yeah, I think we should be discussing it to be honest, because like, there are a lot of things that I'm doing like I'm also I'm managing both the tests like the milestone one test and the milestone two test simultaneously right now. So I'll try a bit more if I'm not able to get it working then of course I'll ask for a bit a bit for help because like I cannot be stuck on it for a long amount of time. And the connection tests are already fixed, which means that the connection is proper. There is something wrong with the JSON responses that we are getting because I'm not able to maybe match them properly. And maybe I'm not able to find which is the HTTP version, which is using like I was having an error of 17.0.5 while in the GitHub like the CI, it was actually 18.0 something so I don't know how to match them. So yeah, these trivial issues can be fixed. Okay, sounds good. So I think we'll meet again next Friday night, IST. Yeah, yeah, I think that's that's okay. So should I like a debug it live like the second milestone to code so that you can have proper guidance while reviewing the pull request right now? Yeah, if I No, not today because like maybe later, so we're kind of have a separate meeting maybe on Saturday afternoon. Yeah, no worries. Yeah, it's okay. I wanted Basil to like see the debugging because so that he could be sure that it's working properly. And because I changed the execute method quite a lot like I actually destroyed to be destroyed it to be honest, like the webhook action that I was getting from all the all the processes that I was getting it from behind. I stopped getting the webhook action. I made all the methods to be void. And then I executed it directly instead of receiving the webhook action in the getDynamic method. So I changed it quite a bit and I tested like tested it using my debugger quite a bit. So yeah, that was the major thing that happened in the milestone to make it work because it was not working. And it was give it was throwing me a lot of 404. So I fixed it somehow. But yeah, it was a big change. So yeah, that's why I wanted to show him like how the debugger is working so that he could be sure that yeah, it's working properly. I have a sense that maybe when Mark is away, he won't be here, but we can try like after Mark's here. So we should like paint Mark first and ask like if he knows if he can ask for requesting Basil's reasons next week. Yeah, in the draft pull request, I actually want to request Basil to review the draft pull request right now see if the code changes are proper or not because he reviews things in three stages, right? So at least the first stage I get it. Yeah, okay. Yeah, true. Have you tried painting him? No, I haven't really tried it yet. Yeah, try painting on the issue. Oh, PR, no issue. Okay. Yeah. So I'll try to reach out to him too, if I can. So I think that's that's what happened this week. And previous weeks, of course, I was having blocker in the milestone too. So it's, it's now finished. I can have a blocker in the test, but I don't think so that will be, it will be that major because of course, it's just mapping the API responses. Okay, sounds good. Yeah, keep up guys. Yep, that's it for today. Thank you. Bye.