 All right welcome to the DevSeq. Goodbye Derek. Yes hello and goodbye. I've got a run. See you. Yeah I'll catch you all there. See you. It is Wednesday the 29th of September if I'm not mistaken. Who wants to go first? Yeah cool. I just have to I had to do math minus one is really complicated at this time of the morning. My mark two I brought it up on my on my hot spot again but it has come up with a build date of 929 so did they change anything that makes it worthwhile for me to try to reconnect my local net no nothing's changed on the on the Wi-Fi on the Wi-Fi front yeah did you gotten back to you did you get have you had more files okay where how long ago was that yes the wrong files but I think he was a junior guy but I sent him what he really needs as well as what he asked for was that Julian or Sebastian maybe anyway how long ago was that though if because if it's been too long then I'll I'll give him a nudge well you can give them a nudge but like it's Julian Hartmer hmm anyway so that's that's one thing on that just just feel free to like if they're not if they haven't responded in a few days or something like just feel free to nudge them and say hey you know any progress any progress and you know they're busy like all of us so yeah I helped out in the wake word channel there was a fella that was having a cold and that's a lot I was getting at he's running us on a ps3 right so we're on all kinds of devices but anyway he was having trouble with the wake words tried to help him out with that a bit I don't think I made that much of a difference but at least you got some attention I attended the metrics meeting yesterday it was interesting and I got bogged down working on converting this this runner into a module I had a friend try to install it on Debian and it didn't and I'm very sensitive about it being cross compatible across all working environments so you know I'm a little skeptical about just releasing a runner module that only works on Ubuntu and doesn't work on Debian or Mac OS X or anything else so it's kind of where I'm at and yeah that's that's it pretty much for me I'm working on that cool is it in the repo already or no okay um yeah if you want if you want another tester let me know I will thank you since I'm already talking we did do some updates to the to the mark to yesterday and so the Wi-Fi connect skill just got moved from the build recipe over to the micro skills repo so that it's being loaded in the same way as everything else I think that was the last the last skill that was being installed by the build recipe so we now have that you know single list of this is what's on the device I reactivated the daily builds now that they're succeeding and Ken's clearly on the on the latest and that's all working well and Chris do you want to talk about the other changes that you pushed yeah I've been mucking with the resting screen so now there's you got the skill update from yesterday now you should have to date two timestamps on your screen right now if you're running in dev mode the build timestamps which is always that there's always been there and now the last time we updated mark to branch of my cross skills repo which should be on a daily basis or no no more frequent than a daily basis I guess there could be days that we don't have anything that the push so yes it's day I spent time I've spent a PR with that logic in it guys reviewed it I've addressed your concerns guys so you want to look that again today cool we can get that pushed just so you guys know that basically I I'm looking at the skills that Jason file to find out when the last time a skill was was updated or installed is that gets updated by MSM whenever it runs so and there was an install time and an update time in there and basically I look for it both and figure out whatever the most recent time is for any skill in that in that file which actually made it easy because it was an existing file that had that information I needed I just needed to read it and pass it so and I'm spending today or I spent a good part of my day-to-day I'm trying to understand the resting screen architecture and the mark to skill now there's some of the mark-to's tools come in the my crock-based skill class and there's some stuff in the in the GUI enclosure stuff so I'm bouncing around trying to figure out everything you know works together and the reason I'm doing that is because I'm trying to there's two tickets right now in the sprint that actually we should should today should be the last day we work on it I guess we can talk to Michael about that tomorrow when we see him two tickets where if you reload the home screen which I've done a lot of recently that the screen goes blank so you know making sure that the right things get happen with the resting screen handler when that skill gets reloaded also something I noticed is that there's a ticket I'm working on related to this because if there's an error in the home screen for any resting screen for that matter that might would be my guess whatever is handling the resting screen continues to try to load it up over and over again and that error my device gets stuck in a loop or keeps telling me that I've got this error with my home screen not something that should be a problem for our production device because they shouldn't be having that problem but something that should be fixed well we'll talk about that when you're done well yeah and there's like you know people can make their own resting screens home screens as well so yeah you know it's not just our own that we've got to worry about yeah and I think it's tripping me up a little bit is there's a lot of comments in this code that says it should be part of the half it should be part of the hell I'm like who you know how much of this do I want to touch yeah the house come but anyway I'm still learning those comments in there I wonder was that you or me I have three questions that are some of them are related the first is are we sure that our bus still runs on Debian by the way yes bus the client I run Debian on machines because we rely on version yeah because we rely on version 54 of web socket client because of the dot app of the app last but Debian doesn't go all the way up to 54 I believe that's about to jump to one point one point something as well so what's that the web socket client that Python module is about to jump to one version one point something I'm just wondering if it's been tested on Debian since we've modified the client didn't we just modify the client not that long ago it hasn't it's still running the old version at the moment on micro of core but there on the mark to on the mark to it is still the old one yeah okay so that was the first question I had the second question so we know that it runs on Debian that's good the second question I have is something that Chris V brought up which is skill load order and interskill dependencies did I understand his comment correctly that we cannot control the order of skill load we could we don't right now and if we did not right now that's that's very interesting well there's sort of is well at the moment there is a priority skills list so like you can say this this needs to be loaded first or these this set need to be loaded first and then everything else loads but I don't know what order within those two sets that things load there's not much in the party only like two or three skills in the priority skills that parents well how do you how do you make sure that the pairing skill runs after the Wi-Fi skill they're both in the those are two of the skills in a priority list because they have to be there and is the priority list a ordered list they don't they don't they don't actually have to load in order okay I think I've heard enough and then the third question I had was this mark to the with this bill I noticed that what I do my mark to is I rename start my craft so that it doesn't automatically restart are you with me on that does that make sense yes because you're in a start my cross script so that when when the things that try to restart my cross call that it just yeah okay up until a recent build that was just fine but sometime between the last build and two Thursdays ago's build which I believe was dated 819 or 829 or something something changed so now when I do that it will automatically reboot after a certain period of time if my craft is not detected to be running that surprises me that were you aware of yeah it surprised me too because it's a change in behavior it was what we were discussing last week regarding a static image versus an unstatic image in all the different moving parts one of which is the panticore underlying code so you're saying if I if I jump on a mark to now if you go to your mark you and you rename start my craft sh2 foo dot sh and you stop my craft and let your mark to sit there it will magically reboot in about 10 or 15 minutes and they didn't used to do that anyway that's just the three questions I had because some things I was working on yeah I can't think of what would be doing that like the hmm yeah I mean I was trying to get something deployed that actually relied on that message bus and it didn't work on Debbie and that was what learned me that it was blown up on a couple of different well so this is a like a fully raw Debian images that yeah I don't in puts in different locations and so you know there's not everything you expect to be in your current virtual environment some of it's at the global level and yada yada yada and then when it's at the global level and then your your local you know virtual environment calls out for the new one it gets confused as which one to load and all that good stuff so that's well why I was kind of why why is everything not loaded into the micro virtual environment well it's a different question and that's a different problem space and so that appears to be right in other words if you do that then there's dependencies that I guess are sub dependencies that are not being met by installing the module that have already been met by installed my craft and that's kind of cheating so I just wanted to understand why that was that that's where I was at okay and in fact I will I'll probably pull an old kivy image out and or maybe I'll just burn a new Debian and try it with my craft installed first and then cool okay well those are the questions I had we also there's a question we need to be asking ourselves at every one of these meetings for a while and that is do we have any skill updates to push today good cause that's going to be a manual process yeah that you guys are I gonna do and there's also release notes in kind of influence that I want to keep up to date so that we can look back at and say oh this is why this is getting this way nice this is why it's broken or whatever yeah um so that is my getting the home screen skill today with I don't have any you don't have any okay well I think the home screen skills you know what I have to update right now and that's just from code review remarks from Gez the timestamp on the home screen right now is in UTC which doesn't make a lot of sense considering well yeah so yeah that's now but the build dates in UTC so I was following that pattern but it does make more sense for the skill update to be in local time so that is yeah that's now in local time now cool cool yeah so build day will be in UTC so we get like everyone can say the same thing but the skills one is constantly changing anyway so that's local cool well I should only change once a day but well actually you know what I wonder if it should be local because isn't part of the reason we put it there so everybody can say this is the last so we can all match time is on it yeah maybe you might want to keep it in UTC because we have that that's the reason I put it there it was that so we could all say oh what what skill date are you gonna make enough we don't hopefully all come up with the same answer yeah I think it's I think you're right but it won't be it won't be the same answer anyway well it should be close it should be within an hour in other words that's what I'm getting at at least you have a chance looks like this one went off at 147 heaven knows when it's everyone's date should be the same let's put it that way unless yeah that's all I was getting at is that if you use UTC for both then they're gonna be within hours of each other worst case and so that'll make sense yeah that's that's not I think about it I think I might revert that change yeah maybe what we're doing this process once once we switch back to just like you know pushing stuff whenever then I feel like the local time makes more sense but I get what you're saying yeah well once I do with finished in this process I may get rid of this field it's all together out of the scale I don't know may not be even necessary the reason it's there so we can all sync up and say oh is a version I'm running hmm well it is it is you can hide it that development device flag or whatever yeah that's true stop all right I'm gonna revert that change before I so I mean I did not push anything out today from skills because I was that was the only thing I was all your other changes yes from the code review or non-functional so they were just yeah yeah I think so yeah oh I don't touch the home screen today then from the world cool so yeah no no build changes today okay guys I might go out to you tomorrow to ask you to try the new loadable module what I get a repository yeah great cool yeah all you have to do is change a config value and then reboot yeah and well you might want to do like a pip install first yeah at least working in a environment that has Minecraft previously installed that's probably really just the goal I guess I was just trying to you know say well this would be nice it could run on you know non mark two environments but I don't know if that's a priority today worst case they could always switch it back to precise and get the old binary it sounds like the Airbus crew have been working on the same type of thing too like they maybe they you know we're seeing the limitations of running everything in the in the full runner and they've been working towards the same kind of a thing is that right no so they yeah so Jarvis created module for the you know precise light runner I actually have that running on this mark too so this is running OVOs whatever it's called precise white or I forget so yeah he's already got that working the problem is that brings in a load of stuff from OVOs mm-hmm all its dependencies right so yeah I mean I'm pretty sure when I give you this module tomorrow it'll work cool on a mark to theirs did what I haven't tried is to pull theirs into a non-microft environment and see if it blows up in Debian as well you know again I'm just going above and beyond right now I'll focus on the mark to that all right I don't think there was anything else that I really needed to say and yeah I'm just gonna be working away at the the high priority sprint today I did start working on the the automated pushes from Minecraft core to the to the mark to build system initially I was doing it from GitLab you know to pull from from Minecraft core but realized that we have this perfect trigger scenario so now it'll be basically any time anytime you push to the to the mark to feature branch of Minecraft core it'll it'll trigger a new build of the mark to that's the intention it's not working yet but there's just a little bit of you know it's a little bit different to where we've done it like where I did it in the DAP for example because that that was all within GitHub so it was all using the GitHub API and whereas this is yeah across from GitHub to to GitLab so it's a little bit different unfortunately but hopefully that I think that's awesome could you also add the capability sending out an email when somebody commits to the branch and it breaks so because that's what we used to get all places I've been at is a nice email hmm well yeah it will it will run the well and so that that all exists on our on our mainline branch the problem is that we've been working on this feature branch and we haven't set up the same stuff for the feature branch so is that right if I push to feature mark to and it breaks the build I'll get an email no no like if you push to dev and it breaks the build then you will get an email and so we need to add the same stuff to feature mark to I was kind of you know like because feature mark to is just this sort of quick rapid blah blah blah we didn't we didn't add that stuff when we really should have like you know back at the start and we are gonna merge the feature mark to branch into dev so I don't want to like spend too much time you know building out CA infrastructure for something that's not going to exist in a couple of months time but given we're gonna do all the skills interaction stuff and you know kind of make sense but yeah so the very like the the unit s really easy and then we'll see about the the void cump tests cool anyway that is everything from me let's be a wrap let's wrap it all right thank you guys talk to you tomorrow