 Let's get things moving and try and wrap up quick today. I also have Pac on today, so. Woo. OK. Well, I can go first. I had promised a demo, but I haven't actually gotten to it yet. I do have a device on latest. And I haven't actually checked to make sure it's not through all its updates. I got it set up about an hour ago. So I will get that demo done and uploaded. We can talk about more tomorrow. Really, my goal is just sounds like the news was the only one I should expect any changes on. So I'll I'll throw some some extra utterances at the news and see what we see. Everything else. Just do one real basic. Kind of one utterance demo because not really expecting much to change there. Um. But other than that, I'm just like based on the decision we talked about yesterday to change the orientation of pie to all ports towards the back. That's just been my main priority to get that done. So Kevin can actually get prototype out before he leaves next week. So almost there really. I think I'll be able to get it to him later in the morning tomorrow. I'm actually pretty stoked about it. I think it's going to be cleaner, nicer all together. It's got to find a way to keep the USB in place. I've been thinking about that too. That's it for me. Can we write up a like, I know we're going to get to it anyway, but while it's on your mind, fresh on your mind, it'd be good to write up the reasoning behind that because that'll go in the next Mock 2 update, I'm assuming. Yeah, I don't know. It's kind of one of these things where I like to see Kevin get the board layout and stuff a little bit. Make it a little bit more real before we go talk about it too much. OK, just in case he wants to make it. So it's a decision that we're going to try and do it, not the way I'm doing it. Well, we are doing it. It is almost no reason it's not going to work. But again, still, I like to. But I'll work on it next week. How about that? Because by then, we should have at least something back from Kevin. Yeah, yeah. Well, and the updates doesn't go into the 15th or something like that. It was more like, if you're already thinking about why we're making this decision and what the, you're in that handspace, and I thought it might be good to do it now. I think it's almost done, I'm sure. Yeah. If you're done and I'm talking, I did some upstream fixes for the packages that were broken. So we merged some patched versions. Well, we changed the requirements file to point to patched versions so that they'll start working. If you care about their details, go and check the PR. But it looks like the official versions will get updated pretty quickly. So that'll be good. Everything is humming along pretty well except for one time of skill VK test. But it's only failing maybe like 25% of the time or less. So it's meant that I've been able to get a whole bunch of stuff passing and stuff, which has been good. And I think I know that it's not a priority for us, but the XDG, the next XDG PR, I have to do a final pass through it. But I think that the only remaining question there is if we're happy with the new file location for where skills are installed. I thought there was still some, is it still the data directory? Because I'm not a big fan of that. Sorry, I said that again. It's still the data directory? It's the, yes, I think so. OK. So I think I know there's some discussion at the yard about moving it away from the data directory. It doesn't really make a lot of sense. Yeah, so I think that's where that is, is the final question. So I think if anyone has opinions about that, or is going to care, then we should nut that out. If you don't care, it doesn't look like you care. So I'm going to assume that we don't need to check in with you again. And I'm assuming that Michael doesn't care, or Derek. Cool. I mean, the only thing I care about is I tend to agree with Chris V that it doesn't belong to data directories, kind of weird putting code in the data directory. But other than that, I don't have much of an opinion. Cool, cool. All right. I don't think I have anything too exciting other than that. Ken, did you want to go? Can everybody hear me OK? Yeah, so I updated the dev team channel with the alarm skill problems. It appears that the alarm skill that Derek is running, since I was told it was the 2102 branch, is extremely old. All of those bugs were fixed about three months ago. The code's languishing somewhere. And now it needs to be merged, because there's been point releases, and changes, and all sorts of stuff. So I don't want to commit another PR, because I don't know why the original one was not merged. And so I can commit a PR for what I have, which is far different than what we're currently pulling, and it'll have to be merged. But there's a lot of work there. There's a lot of stuff pulled out, or just not even put in there. There's heuristics, and all sorts of stuff that's just not available. So I don't know what happened to the alarm skill. I don't know why it never got merged. But he's running a very old version, and the code I have now will not work. So somebody's got some merge work to do, I assume, if they decide they want to take the new alarm skill. So do you have the code that you're talking about running on your device at the moment? I do. Can you either put that into a branch, or just send me a zip file, or something? Yeah. I can send you over a zip file. Cool, cool, cool. All right, do that, and I'll take a look. Yeah, so there's a lot of stuff changed. There was a lot of files added. There was a lot of voked file changes. There was a lot of code changes. So I will send you a zip file, and you can have at it. After that, it's been about half a day doing that. The other half of the day, I was unraveling this mess that is the precise binary, because I'm trying to run a version of TensorFlow Lite runtime on the mark, too. And that's difficult. I can run the model using the precise binary and the upgraded TensorFlow, but that's not the goal. So anyway, that's what I was working on. So today, I was unraveling the alarm skill and unraveling the precise executable stuff. It might be worth posting something about that in the precise channel, too, because I don't know if anyone else has worked on that already. They might have some pointers. You're muted, Ken. You are still muted. Yeah, it looks like the PR was primarily to get TensorFlow, the environment, upgraded to 2.2. Somebody gave me a TensorFlow Lite model, but I haven't really seen a TensorFlow Lite runner. That's what I was kind of building. Because the code that they gave me that was on OVOS is using TensorFlow 2.2 to run the TensorFlow Lite model, which kind of defeats the purpose. I do have a zip file that I will email you, by the way, right now, to see you now. Chris Fair. So I finished going through every applicant I could find. It has submitted a coding test, and I reviewed them. And my comments and ratings are in reading. And I finished work on what's going to be a PR, which basically I don't know if anyone else besides me had maybe seen this, but it's OK. Committed for a BK testing, a criteria matcher, or a criteria waiter class. Well, I extended that to do some weight for, well, I didn't extend it. There's three classes now. One is just waiting for events. One waits for dialogues, and the other one is basically what OK had originally. And this will replace a bunch of the code that is already in that file, and some other code that I think is probably redundant with this. So I'll create a PR for that. I can't run final tests on it, because I don't have an interconnection, and because I don't have an interconnection, I'm kind of limited in what I can do. So I may just submit the PR, see how the test runs on the PR. This was done to fix timer skill, expired timer test source, were sporadically failing. OK, submitted, there's been a PR merge that addressed some of the problems, but right now we're getting some false positives. They're passing when they shouldn't. There's like, for example, the stop skill only handles four different variations of the word stop, but this VK test looks for eight or 10. So they shouldn't be passing, but they are. And this fixes that. And I also put an X fail on the ones that wouldn't pass, because they're going to require an update to the stop skill for them to work, not to the timer skill. That all makes sense. So there's a timer skill PR and a PR to core with some void comp testing tools that kind of go together that will paint a true picture for these timer events and will hopefully provide some reusable code that people can use whenever they want to test for dialogues or events or anything, or criteria or anything like that all in one place. So I don't know what I'm going to do this afternoon or tomorrow. I'm supposed to get my internet fixed tomorrow afternoon. I will see if I can find some things that are required on my internet that I'll probably eliminate in a little while. Are you not able to use your phone to tether? I can tether, which means I can do stuff with people, but that doesn't work out my devices. So I can't run tests on my devices, because they can't connect to my phone. You're an Apple guy, aren't you? Sorry. That's why I have my little mic. That's why I keep my MiFi device, because this is what I do for a living. So if ever I lose my internet, I just pop up my LTE device, and then I can have 12 devices connect to it. So I connect the mark twos to it, connect the laptop in the TVs, and we're good to go. Sounds like you'll be having it fixed pretty soon, right? Every day should be fixed tomorrow, so it's just a day. But I'll just try to find things that don't require me using my devices today. There's always reviewing PRs. Yay. Yeah, that's what you said. Cool. Michael, did you have anything? No. And you're sick, so if you don't want to talk, that is OK. Yeah, I don't have COVID. But everyone in my house is sick. There's something going around. My daughter's sick, and all her friends are sick. I don't think I'm going to have something going around. There's lots going around. All right. Get a call around. Well, then let's leave it there. I'm going to be at Picon all weekend, including today. So I'll be getting some stuff done in between things. But yeah.