 It's a failure in Travis and my bot will notice it and add a comment that says like the tests are failing in Travis Please look into it. And then this usually helps to contribute to figure out sometimes. It's very yeah, like an extra space or something Yeah And also for for easy blocks and framework. We're getting stricter in terms of code style It has to pass the pep 8 standard Python stand. Yeah code-style thing Maintainers 10 including myself. So there's 10 people who have merged access to each of the repositories Most of them are in Europe with the video is in the u.s. Bart is in Canada and they grew up in central in Singapore which helps because you're basically There's somebody always around if they have time looking at pull requests For well for the well the maintainers can can look at the or whenever they have time Yeah, whenever they are free, it's up to them We have a maintainer of the week system where we ask one of the maintainers to pay closer attention To like try and reserve one hour per day per working day To look at contributions and that just an agenda that we plan. We ask people when you have time It well, it doesn't have to be Doesn't have to be working days Yeah But it's some maintainers do a better job or Some maintainers just think they will have time that week and then it turns out differently. That's fine It's good to have some some degree of People paying attention to what's coming in. This is only easy complex this one I Have the same data for framework and easy blocks and actually the the the policy is That whoever opens a PR even a maintainer doesn't merge their own PR So that means if I open most of the PR's somebody else will have to merge it I'm not merging my own PR and this does skew this a little bit because a big part of the light green is my own PR Which I'm not supposed to But they're also looking at PR from other contributors and yeah, it's still increasing. So I'm happy Yeah, not having a group of maintainers today would be impossible. There's too much coming in Okay, I have a small demo here. I have this easy conflict file This is just a copy of an existing one. So if I See if the network works if I do preview PR on this one. It should show me an empty diff now in the background Okay, hold on check out master and try that again It's a bit more verbose than it should be so this will pull in the develop branch from easy conflicts and Diff this easy conflict with the ones that exist already So it has found an easy conflict that looks very similar to what I'm giving it And there's actually no diff because it's an exact copy of what's already there now if I Go in and change the version and I was checking earlier. It's a good example because So apparently these still find a matching final pie easy conflict and show the diff Which hopefully only has the version Has a little bit more because it compared with a bunch of other easy conflict So this is the multi diff thing for one of the four that it compared to had this version the other hand this version had this version and the new one which is different from all four has the new version and then of course because It's pulling in older versions as well the checksums are also different or one of them the tool chain is different and so on So it has an algorithm to try and figure out the closest match to what it has and Here it's actually failing a bit Could could do a better job with only Showing Intel tool chains and not false for example If I undo So now I've only changed the version the checksum will definitely have changed so I can do inject checksums to fix the checksum Should do it like this Because inject checksums takes an argument with the type of checksum It found existing checksums in the easy comfy files with telling me you have to force me to do it Because I'm not blasting away the existing checksums without you telling me now it did it what it does it it does the Checksum replacement in place, but it does save me a backup So I can dip with the backup and Show you that only the checksum has changed and now well I'm supposed to test the easy comfy file first or I can just open a political request and assume it will be okay Or let's see make it full useful There's a bunch of dependencies, so I would have to update these dependencies if I change the tool chain Let me just show you if I do new PR No, so you check github first This should be all Okay, hopefully This is checking whether my configuration is okay Configured easy build that this is my github account. This is my token It's checking the versions it checking whether I have push access to my fork on github, which takes a little while But it should be all okay Hopefully Ran into an issue here, which is a warning that is misspelled Okay, but it seems to be okay, so it should be able to do new PR and One of the nice things about new PR if you're not fully certain You can make it a dry run, so it will show you what it will do without actually doing it So now it is pulling in the easy conflicts repository and the temporary directory So it can do the branch on top of current develop. It's pulling in develop Copying easy conflict files in the right place Getting all the metadata preparing a branch with a suitable name and giving all the information targeting develop this is the Title for the pull request with a new version in it and It's only one easy company file. So this looks of case if I'm just now Remove the dry run. It will actually go and open the pull request for me disabled cleanup temp there And you can actually go in and look at the git diff. Oh creates You you actually don't have to Do that manual Let me show you so now actually has a pull request if I click it I Will get exactly a pull request with this version of follow pie It has it here in the right location To the develop branch using this branch that it pushed and so on it doesn't get easier than this Okay, it's saying here disconnected I Showed you dry run Where it gives an overview what it will do We have two tabs of driver normal driver and extended driver You do extended driver. It will show you the diff So you don't have to do that manually and So extended driver will also do with dry run not actually do the PR But it will show you a full kit diff of what it looks like like this And actually it should be doing it in color. I'm not sure why you doing it in color, but the diff here Yeah, it's a new easy config. So it's a diff that shows you everything If you change the existing easy company will see a proper diff Some PRs can be very long. Yeah, you can imagine if you're writing easy country files all the time. This is a very nice feature and Lots of people when you just look at the list of pull requests like if you if they follow this format Most likely they were opened by a new PR So it helps us a lot just visually looking into what's coming in like this one is not opened with new PR Actually this but maybe Sam took over He took over the pull request title for some reason It's really helpful any questions on that Good question. Yes. So when you do new PR Let's say this easy config file needs a patch Like follow by one fourteen two six typo not patch So Assuming this patch is used in here. It will take in the patch It will figure out for which easy config the patch matches because they have to go in the same directory And it will do the right thing will move the patch in the right location and all that much That's also something we only added later, but it does the right job. You can actually do this So for an existing PR So you have pull request number you forgot to add the patch which happens like an attachment in an email Happens all the time you can do this and it will figure out for All the easy config files that are touched in this pull request for which one is these PR relevant And it will put it in the right place. Yes It will look at the easy config files that were touched and this pull request for For extensions it doesn't work Yeah, for extensions we have to fix it and another nice thing of update PR is it doesn't matter how the PR was opened Even if it was done manually later, you can do update PR doesn't really care how it was This just saves a ton of time To do the get dance. Yeah, okay, I think we're done Tomorrow we're starting a bit earlier nine So if you're diving into Belgian beers tonight, just be aware So Gregory will start with the talk on the VT Adrian not sure if Adrian is around yet. We'll talk on open HPC and then Victor on reframe The tomorrow is mostly talks, but there will be some time in between for hands-on stuff as well I know brewery visits tomorrow. Okay. Thanks