 Hey, we're recording. It's August 26th, 2021. This is the DevSync for the micro-built team. Okay, so we're going to kick it off with Derek. We're working on a little promo video and we're putting together, well, we're actually taking a look at the state of the software as it pertains to getting some good footage of the Mark II in action for the video. Yeah, so that is to shoot with the latest, but most of the skills actually had some stuff that wasn't in the latest yet, so Chris helped me get mine up to date via Git. So I've got all the, you know, not latest, but most recent contributions on it. And so that's what you see in the video. And I went through all, I went through our demo script that we typically have been doing in the past and filmed that it's up on YouTube. That is private for the time being. In fact, I don't think we can even make it public for the community, unfortunately, because at least with that demo, when we did Pandora, we use a copyright song. So I could do one in the future that doesn't do Pandora, and we could share that publicly. But well, if you ended the video with and now music and you launched Pandora and then faded the black, that would be fine. Yeah, I mean, I could edit the Pandora part out, but I just can't, like as is YouTube won't let us, they'll flag it for copyright infringement. Yeah, I didn't do any editing, I just threw it up there. So anyway, yeah, take a look. I think we all saw the things that stood out to us. I mean, there's some kind of funky GUI interactions where some of the GUIs are kind of persistent when they should be cleared. But this is all stuff we kind of knew about. It was going to be addressed in the sprint. The thing that I think concerns me the most is the stop behavior. And I don't think we can just say necessarily that it's specifically to like, I was seeing a lot of news, but then I saw Pandora, you know, Giz mentioned it could actually be present in, you know, a lot of other skills too. It's just maybe coincidence that I'm seeing it, you know, in some cases. But I think that's the biggest thing that sticks out to me. Otherwise, I'm pretty happy with the progress. So yeah, and then, you know, the thing we're talking about is, you know, the person we're partnering with create these promo videos is it would be an ongoing partnership. So there's definitely some parts missing. You know, there's not GUIs ready to play the common play stuff. We can send him a device, and he can film some of that stuff again when we get it in place. But the other stuff is just me getting a Mark II that's going to be photograph ready. So that's actually, honestly, the more time consuming part. But that's what I'm going to do. But yeah, I like this process now that we've got a place, you know, we should just keep this going where we create this video every week and upload it. Okay, cool. Did you want to keep doing that, you know, outside of the DevSync? Just do like a... Yeah. Okay. Yeah, I think it would be good. It would be good if everybody, you know, if we did this like every Thursday, you know, and I try and get it uploaded like at least an hour before the DevSync and everybody takes time. I mean, that's going to be five to 10 minutes. You know, everybody takes time to watch it before the DevSync. That would be great. So I can commit to that. That sounds great. Did you come up with a list of bugs that you need fixed for building purposes? I think I can work around everything at this point. The stop stuff doesn't... It's inconsistent. It's not every time. So we can work around it. And then, you know, I guess he was going to try and get the news gooey in there if I wanted it. But like Chris mentioned, it's going to be inconsistent because Pandora is just not going to happen. So, yeah, I mean, if it's not a lot of effort, you may throw it in there for me. But... Well, remember, you don't have to say play Pandora. You can subscribe to a channel and just say play the channel name or just play in general something. And then nobody would know what you were actually using to play in your video. Oh, yeah. But I think I was just talking about the fact that we're not going to have any gooey for music playback, although we could for news playback because it's, you know, there's kind of some work already been done there that could quickly be... Right. Okay. But that's a nice to have. Nice to have when we get the news gooey. But I think at this point, that's the only thing I'm going to need. Right. Okay. Well, I'll leave that between you and get us to figure out if you want to get the latest and greatest news gooey up there. Oh, the other thing, Chris was going to add the latest home screen changes that he's been working on that would just add the weather icon, the current weather. And after I set an alarm in the demo, the alarm icon will pop up on the home screen. Cool. It might also... I don't know this, but it may clean up some of those weird gooey interactions that you're having too. Because now it won't... Well, that's because during the demo, I stack things pretty quickly. So like I'm doing the skills right after each other. Sure. You know, stuff... You know, we have this thing where, you know, the gooey is persistent for 30 seconds, you know, unless otherwise, you know, like time or something where you've explicitly stopped it. So something's happening there where the things are getting stacked up. Of course, when we shoot the video, I don't have to do it that way, right? You know, I can... Yeah. I can work on tricks or whatever. But so, you know, you'll see it like so, you'll see it in the demo, but if you keep watching, like it goes back to one of the weather forecasts, it should clear out. Okay. That sounds like that's a bug report on a gooey stacking up like that, because you should be able to interrupt a gooey and, you know, interrupt the audio. Why can't we interrupt the gooey and have it replaced with a new screen? Well, it does get replaced. It's just when that interaction ends, it goes back to the... Right. Which is a bug. Yeah. Well, yeah. It was put in there intentionally. But the way that it... The way that it is appearing at the moment is a bug, but like... But the functionality of stacking screens is a feature. Yeah. I mean, it should only return to a previously interrupted skill if that skill is like a persistent skill, right? Like, so if you interrupt the music to do something, sure, overlay your new screen on top of it. And then when you're done, you go back to the music. The music keeps playing, the gooey comes back. You know, that kind of makes sense. We'll get into that in the next screen. Yeah. Yeah. I thought this was going to get resolved in the gooey interaction, or the skills interaction. Yeah. Yeah. Okay. Well, that's fine then. Okay, great. So you're going to get a little bit more help to put some other updates on there, but it looks like you're pretty good to go. Yeah. I'll meet with Chris again tomorrow to get the... You know, should go real quick to get his home screen stuff on there. Okay. Great. And then I'll just be back in the shop, painting up the Mark II and getting it looking good. Cool. Do you literally paint it? What are you painting it with? Just spray paint. Okay. Yeah. I mean, you know, you do it, you're careful and, you know, do light coats. It looks pretty good. All right. So we spent a good chunk of yesterday going over miscellaneous important agenda items. So I want to get back to going through the status of the sprint and the skills but before we do that, a couple, just a quick update, I think. Let's see. Nope. No, I don't have anything. Okay. Yeah. We can just go through the sprint status. Throw it up here. My name is October 20th to 30th, cast in stone yet because Sarah asked me to hold off, but longer I hold off, the more chance it's going to be, I'm not going to be able to get my booking. Oh, contact her about that because I think she was booking plane tickets a couple of days ago. She was what? She was booking plane tickets a couple of days ago. Well, yeah, it wasn't plane tickets but it was about accommodations because I'm going to pay first and then you guys will reimburse me a certain amount each day that I was out there because, you know, I'm not going to an Airbnb and I'm going to, you know, be in something a little more expensive and I'll cover the overage. But somehow that turned into, well, I'll just do it and then they'll reimburse me, which is fine, but she said hold off until I have, you know, the exact dates and I thought it was definitely the 20th to the 30th. When was that? That was yesterday. Well, I'm confused because if they're booking plane tickets, we have to know the dates. Yeah. Yeah. So, all right, I'll follow up. Yeah. And CC me on it, please. Okay. Thanks. Okay, so I'm going to show a window over there. Okay. So here is our Sprint 21 status board. How are we doing on the home screen? Chris, you're muted. All right. We're getting there. There's ancillary PRs and other skills that have been submitted. The home screen skill itself still needs a little bit of work. Not much though. And I did not work on it today pretty much at all because I was dealing with PRs for other things and helping Derrick out. So today was not a very productive day as far as home screen skill goes. But I will probably spend some time on it this afternoon. Still have to get it done tomorrow, but nothing else comes up. And now you're muted, Michael. That's clever. So, okay. So on the timer skill, this is a known issue. We need to get Marketplace Approval. I've been doing the testing for 20.2.1. Okay. I just got the parker off to go. And then, so I should be able to release that today. Yeah. That's the blocker, really. Once that's out, we can move forward with getting the Dr. Container ready and getting some desktrum. Yeah. So once I release, then Chris is going to update the Docker stuff and then we should be able to merge the skill. Great. That's awesome. Okay. Due to due, we moved that into the next sprints, future sprints. So really, we're down to just two things now. That's great. Okay. Well, we can stop looking at this time. Chris, have you had a look at the new skill, Payaya? I have not. I was hoping to get my own screen skill done first, but again, I'm not spending time on it today. So I will look at it. Cool. It's a bigger PR. So that's why I'm kind of putting it off until I have time to really sink my teeth into it. Oh, yeah. Yeah. I skipped the news improperly. I was looking at the future sprint for the GUI, not the audio. Okay. Well, so for the GUI, there's all the blank cells that we haven't looked at yet. Yeah. That's this upcoming sprint. For the next sprint. Yeah. Yeah. So anything that's blank is basically for the next sprint. Yeah. Okay. Yeah. Those notes must be there for some other reason because we had, I don't know, maybe we had a different status in there at some point and I replaced it with that. Anyway. Oh, well, I think the music skills, they're going to have to wait for the music sprint. Right. Yeah. So that's the future sprint. They're not in the GUI sprint. Right. Same as, and the news too, because they'll write the news and music are all going to use common play. So yeah. Yeah. Date, time and home screen are also kind of bundled together. Once the home screen's done, there's going to be a, have to be a small effort. Well, I'm not small, but there's going to be an effort to, you know, move skills around a little bit to make the time scale work and the old date time scale network, at least on the Mark II. Gotcha. But we're not like deleting the date time skill from the marketplace. No, but we do need to, we do need to have a think about how we make sure that it's not, that we don't have the date skill, the time skill and the date time skill all on the same device. We should, we should probably deprecate the date times our market has deprecated somehow. Yeah. There's really no reason to have all three of them on the marketplace, but yeah, you should probably say maybe, maybe 2202, it'll go away or something like that. Yeah. Okay. Let me write that down. All right. Well, let's go around the room and get any other status updates you want to share. Yes. Do I get you while you're yawning? Yes. Yeah. So I've been doing testing for the core release. Got a new stable image out for the Mark II, which resolves the, the, the, the boot issue that we had with secure boot. The one thing I noticed the other day, yesterday, maybe, is that Panicor are making some progress on support for the 510 kernel. So that will be very, that is something that would be very great for us. So I'm reaching out to them to, to have a chat about when we might be able to make that jump because that adds things like GPU support, which we currently don't have on the Mark II image. And so that causes problems when you're trying to do like video at higher resolution and things like that. So, yes, that'll be awesome. So just thought I'd throw that out there. All right. Well, that's cool. Let's see. All right. Well, let's go to Chris. Yeah. So as I mentioned earlier, I spent most of my day doing things other than I was supposed to Chris made, guys only made a good comment on a change I made to the Mark II skill that is probably not implemented, clearly wanted to. So I've been looking, I spent some time today looking into that. It happens to work for the home screen skill because the only thing that home screen skill does is do an idle screen. But yeah, it could potentially break further things. So I'm looking into that because that is going to be a prerequisite. One of the prerequisites to having the home screen skill done. Either that, I just renamed the QML files, which I could do as well. I just, you know, the hard coding in the Mark II skills was bugging me. And yeah, worked with, you know, spend some time looking at all the different skills and what state they were in so I could help Derek with his getting his device set up with the right, whatever the most recent SAR. So just a little bit of this, a little bit of that today. All right. Sounds good. Ken. So I refactored the Cal Confidence routine. But the issue really is, and I guess this is a guess question. I've got a bunch of words embedded in here that I use to extract the topic. They're basically like pronouns and verbs. Um, where do I store those outside of the common query framework so they will be translated? It's not a skill. It's in the common query framework. And so the question is in core, when we have words that need to be translated, where do they live? Okay. No, no, no, no, it's not that that's what was in the duck duck going wikis. And that's going to happen because of triple nested loop. But I've chosen to, since I'm just looking for word count frequency matches, I've converted the lists to sets and subtract them. And part of the reason for that is touching upon the next topic, which is I also wanted to understand why it takes so long. Right. As you guys saw yesterday, it takes between five and six seconds for the common query framework to finally resolve when it's gotten a response who to dish it off to before something actually starts playing. And I know why a portion of that is, and it has to do with going through every skill in the active skills array that's in there. And it could be volumous because they tend to linger. So that serialized right call his converse wait for a response call his converse in a loop. I can't do anything about that with this architecture. But what I can do is I can take the calculation query that is being done in common query, and I can optimize that. And so that's what I was doing with sets. And then the other thing is I'll also, I started looking at trying to fix the common query time out. And that that's a known bug that it's mistaken a value that it thinks is in seconds, but really is in milliseconds. So once I find that again, I've already fixed that once before. So once I find that again, I'll fix that and commit that as well, which is why it keeps timing out, even when it gets responses. And it's been given the true flag that they're being worked on. So that I'll get around to as well. I have. I have. Yeah. Again, I suspect the lion's share of the slowness is in serialized converse invocations. And I can't do anything about that. And then, yeah, I don't know, I have mixed emotions. I looked at it for the use cases these targeting, I think it's fine. It's not clear to me, it's not going to be problematic in other use cases, but I haven't had a chance to actually flesh those out beyond just thinking from a high level, how's that going to work? So I haven't gotten into that yet. I will try. There was also a boot issue that my mark two hit, which Michael believes might be due to Google speech to text. But I don't think it's that because once it boots speech to text is working, I believe something has changed down in the Google connection code during startup to determine whether we have Wi-Fi or not. But I don't know that. And that's what I worked on today. I'm only working on tomorrow. Okay. So you're going to be continuing to work on optimizing and the common query stuff. Yeah, the only thing that's really holding me up because I got it all refactored and working is I just needed to know where to put those words because they really need to be in a file somewhere. So that we have a half a chance of people translating them. And then now that I know where to put them, I'll go ahead and put in the code to bring them in as a list and parsing it instantiation so it doesn't get done every time. That could also be a little bit slow because it goes through them and everything every time. So I'll get all that. But I should have this all wrapped up by tomorrow. Okay, great. Let's see. Well, I guess that's it, right? Derek, you have to say. Hi, I don't have anything to do.