 And we're alive Michael will be joining us in visual form shortly Welcome to the September 15th Dev sync It is Wednesday or Thursday if you live in Australia. Thank you In in our typical fashion Derek, do you want to give you your update first? Yeah, sure So yeah, Chris and I met today and talked a little bit about where the GUI was at and a couple of the skills common Q&A and The pairing and Wi-Fi and talk a little bit about install although that doesn't have anything yet The pairing and Wi-Fi is very close So I was trying to wrap that up real quick so it can be in the queue and Really, I think the Wikipedia side of common Q&A is it's good for my standpoint as well So yeah, I just wanted to get those in a good place so that you know Somebody if Chris or someone else ends up taking those on and they're good to go and then We had all these these mark two dev kits arriving more and so I could go up and help a little bit today to Get some organization in place put some shelves together and stuff to Store or help get that stuff working. You may see And then tomorrow I'm gonna try and shift some more focus over on to help the marketing team with star engine So that's a yeah, that's kind of a map. All right, Mr. Smith. I am preparing a I Integration okay, awesome. I love the short and the sweet. Yes I Want to talk to Derek because I've also been asked to do some start engine stuff and so I want to make sure that way We are cross what we're doing By the other team Yesterday not the most productive day I got a new mark two And that took a while to put together so apologies to Chris for me previously questioning your Your speed at putting them together because yeah for some reason the new plastics are Well the plastics from these kids are way harder than the Way more junked up than the plastics from the last kits that I got so Sorry that anyone in the community got one of these ones too But it does get together beautifully you just have to like Clear everything out nicely first and have a utility knife on hand and blah blah blah Yeah, so not really a lot to to report a Depending on what happens with the start engine stuff other than that I want to get jump back to To take a hopefully a final look at the wiki skill Because I think that's the last thing That and the home screen slash Alarm slash Whatever changes that need to be merged in I think that's the last bit from sprint 22 and then we can finally like box that up and put it to bed and and Be only working on one spread at a time like you kind of meant to Yeah, so My other priority and actually it is a higher priority is getting back to Following up from the meeting on Tuesday that Chris and Michael came to So yeah that's me and Michael everyone else has gone already. We were too quick for you. Sorry, but I've recorded it Very much. Oh, I thought yeah, I don't remember what Chris said So I had a little more interesting day last night So I submitted to PR to core both of them were going through the CI process and the weather Intense whether vk tests were all failing, which I thought was strange It looked like the same problem we had before but I knew that we had upgraded our subscription So I was a little concerned about that took me a lot of figure it out, but I found an obscure bug in salini That was causing the problem When you do when salini authenticates the user it pulls the user information from the database and It one of the things it pulls is the last time that account was active And if that account activity timestamp fell on a Zeroes for a microsecond value Microsecond value wasn't in the timestamp, which was wreaking havoc with a Parsing routine that took that just that string of the date and tried to you know, add microseconds to it Or try to parse microseconds out of it I looked and there's only five accounts in the database that have this particular problem So I'm not surprised it hasn't come up but One of them was the DevOps account, which is the account that runs all all of our VK tests so I put a little fix in there to check for a date string that didn't have microseconds in it and And I just I emergency patched production so that we could So that these tests would fit would run and they did run after they made that fix so I will do a proper PR and all that good stuff with this fix in it But I didn't want to hold up VK tests forever because it's something silly like that And so so I did do that last night Mine I don't know. I don't look and see which ones they were. I just searched for the timestamps But I'm saying was you said that there were five accounts affected by this was one of the accounts mine. I don't know Sounds like it would be fixed now I'll run the query again, but I doubt it because your problem is not the manifesting itself in the same way So I think it's a that's a different problem There's some documentation. I've been in So one of the tasks I had from a couple days ago was to write tickets for all of the GUIs that we don't have yet I did that I assigned the ones that haven't still need some Figma work to Derek And the ones that just need me to do the coding work to me Those are those are all out there And I was in confluence we've been doing a lot of talking about Procedure so I've been in confluence updating some of that documentation and Oh, and I did some work on the home screen scale When I brought my My mark two up the other day after having unplugged for a couple of days I didn't have a Background on my home screen so I debugged that and fixed it And now I do but that'll be So it'll be a commit for that PR Going in to address that So that's that's me All right, I just a quick follow-up was that bug in the home screen or somewhere else It was well, I actually actually I think it was xdg related Because well the bug was actually in the settings of the setting that says use this Use this picture for my background and I had removed The old default to put in the new default that we kind of I think it's just it's kind of the same image But just gonna move around a little bit And I had actually named the old the new one to not be default and in my settings on Salini it was The value is default so And I had a hard time finding What the problem was because I didn't know what that we had merged xdg into the mark two branch So I had so that's I'm confused. It looked like it looked like we had Because when I was looking at the code I checked out the mark two branch and there was much xdg stuff in there But so I was looking in the wrong place initially for my settings That was a bit of a problem too, but Yeah, it's So it was it was a settings problem was what it really was Okay, well that speaks to this process that we were discussing yesterday and So it's interesting. I can edit follow-up question for you as well. I Take it your mark two is still not working. That is a true statement. However If I boot it tomorrow and it's not fixed and then I'll go around the corner and pick up another USB drive and burn the latest test image and start from there and Actually, that's fine because I'm I've got the PR just about ready for the TensorFlow light runner so what I can do is take our latest and Create a new branch and then when I get into my mark to just change to that branch and test and it should be Latest and good test environment and yeah, so that's it's not I'm not blocked by it, but no, it's not working Got it. Thanks, Ken Do you I'm gonna send you some spare USB drives. I don't have your new address. You said it to me Sure. Yeah, I've got a ton You send me a couple do that and I only got one spare. It's nice to have a few extra All right, I don't have much of an update. I was working on the business stuff last night And Yeah, so I Guess I will mention that I'm I do intend to be spending more of my time on the business side That you know as soon as possible so I'm Trying to work with with all of you guys to I want to get to a place where we have a solid roadmap that we're all in agreement about and That you know, my hope is that I can sort of put things on autopilot for a little while. I Expect I'll still do the check-ins but I would like to try to Be able to take more of my attention to other things at least for a little while so Yeah, so Yeah, yeah, there sure is and Yeah, so, you know the the top-line goals for me are to get the You know get the roadmap squared away get us all in agreement with that make sure that that's shared out with the community So they understand, you know, where we're going and and then some You know at least get the plan in place for the the necessary internal reforms Regarding process so that we can make a little progress make progress more steadily and And get the the build system also. I think probably simplified so that we can you know expose that progress to our community More regularly as well So Move on guess wasn't here yesterday. So for here is his edification When I was wrong on my mark, too. Oh, it is Not able to connect to the back end And it's trying to hit the API and entry point what's going on Chris believes the DNS issue I believe it to be a cert issue because You know unsurprisingly at the time it's failing to connect to the back end on port 443. It's also still reading the date as January 1st, so as a result It does not believe that it has a valid cert because the cert probably isn't valid by now If that makes sense and that's the same problem we had in the connect routine with the Google HTTPS, so Yeah, this isn't a problem. Yeah, I suspect it's just surfacing a little bit later when we try to connect to the back end with that particular build for whatever reason and It's probably a timing issue Okay, well short and sweet. That's the way to do it so I Guess that's it for today. We'll check in again tomorrow