 All right, welcome. This is December 18th. This is the Minecraft DevSync and I'll start off by saying that yes, we know that there's a problem with Selene. We're fixing it right now Obviously this message is way too late for you But that explains why Chris may or may not be fully in attendance for the rest of this call So let's go ahead and get started with Josh first name. I saw on the list I Submitted all the stuff for the update All the firmware update stuff has been submitted and the purchase Pull request is done And the investor update it didn't go out yesterday, but it's it's I need to look at one more thing and then it goes out So that's really the two big things and then we talked a little bit about the lawsuit and I found an artist for the I Found and selected an artist for the children's book excellent All right, well, yeah, we'll look forward to sharing more about that with the community soon and Yes Hey, I did some Mostly the Wi-Fi stuff. Yes, actually so we're designing some Pulling the screens that used to exist The previously the so I haven't had a lot of sleep as well The Wi-Fi setup screens used to be static images and so they were portrait mode because that's the original orientation so I've been porting those over to QML QT and and making them Dynamically created in code so that you know rather than just using it one static image So it will work on any future device as well The side product of that is that our Connected screen was like, you know a giant green green screen with a big tick and and the word connected underneath it and That is now Generic enough that we can use it as like a status screen for for any number of things So, you know change the background of red change the icon to an X. You've got an error screen, you know and I had a high inner circle and changing the blue you've got an info screen like all that sort of stuff and Yeah, you dropped out there for a minute. Oh Right after you said something about info screens Don't worry. It's just nice nice to do visual development every now and again Yeah, the slingy stuff. I'll let Chris talk through and I think the Wi-Fi screens was there's the main thing Oh, the panoramic image obviously is going well. We all just came from a meeting from that So we've got another meeting on Monday to Look at that and I'm gonna take a couple of days off next week Which kind of means that I won't be around the whole week because of how America Australia times and works and But can and Derek will be available for Pantacore and and people can just keep an eye on the The chat and stuff in case there's any more Issues that would be useful, but hopefully we get all this fixed up today and Going to Christmas with a nice working system Yeah, so not to Underplay where we are with the Pantacore stuff But my understanding is that everything is working if we hadn't worked up Salini then We would have been doing a demo today Is that right? Okay, that is yeah. Yeah, so there's obviously still tweaks and stuff, but the you know they worked with Ken a lot in particular and got all the hardware working and audio in and out and and And Theoretically all the button stuff should work. They didn't have the device there with them to check but Yeah, it seems like all good, so there's lots of tweaks that we still need to do and then and then look at So once this is up and running, it's all you know user experience improvements and things like that well for the month main part Yeah, yeah All right, great So, okay, not to Delay this any further. Let's go to Chris and see what's going on with Salini. I'm having a bad day So last night I Deployed all the changes I made to Salini. It was a Very large update to Salini. There's a lot of stuff going on the upgrade to Angular 10 Which meant upgrading some of the code and in Salini UI Lots of wakeboard stuff and lots of new database stuff to support the tagger. So there was a lot in there And I went to bed around 2 a.m. Thinking everything was fine After converting some tests and woke up this morning and found out they weren't so The there was initially an issue with adding With adding a device with the pairing code that issue is resolved It was an issue with those wake words Indirectly and I don't know if we want to talk about this right now or not, but the there's a sub select that Picked the wake word From the table so we can put a reference on the device table That sub select was returning multiple rows because there's a hay mycroft Pocket Sphinx and a hay mycroft precise I Think in the last iteration there was just a might mycroft precise so that returned one row and everything was fine So the regression test didn't catch it because There is no regression test for multiple wake words being returned to that sub select The regression just did did pass So My hack was to make sure that that sub select in SQL I just did some hard coding to make sure that subs like would return one row all the time That's why it works now But I did want to have a discussion Maybe after this or something about what the longer-term solution is to that because I think You could certainly have an issue where you know we support multiple wake word engines And I think you there's certainly a viable thing that you could have multiple The same wake word with multiple engines and right now we couldn't handle that the way The code is written. He's been lucky so far that it hasn't been this So how does that affect a pairing So so after you pair then All the information you enter on the pairing screen one of which is the wake word Gets populated on the device so So I was trying to insert the device table Basically, I'm adding a row to the device table when I do a pair and Device table has a reference to the what what wake where it's using Gotcha, so that was failing so then there were a I saw a bunch of Just trying to use log in and use the the interface the web interface for logging in and doing account management stuff Yeah, logging in is fixed that was That was a typo Basically I had there's a GitHub in a in a Facebook Key we used to do to do those logins with them and they were inverse So I want to nurse them and everything work fine Okay, I want to go all the time does I don't skewer But that is fixed now already in production and I just The compile for the add device where you hit add device. You don't even get a screen. That is now fixed as well That bill just finished So that was a that was an angular 10 upgrade issue with view child that the the tool I used to upgrade angular 10 did not catch so That was just a one-line change and that is done So I think that's everything I think as was going to run through and try to do with a brand new account Create an account and add a device and make sure everything is working now, but I believe I've addressed them all Okay So then we need to have a discussion about Not here not now, but you know, what are we going to do about this in the future? You know, how do we miss these things for what can we add to our regression test suite to make sure this stuff doesn't happen again in the future? that sort of thing and And then also, you know, Josh requested we take a look at our notification system because as he I think rightly pointed out We don't want to be learning about this from our users. We should be getting you know errors and and alerts Directly from the system somehow if things start to fail, so We don't have any UI tests, I think that's part of the problem right now, so Then that will definitely be a topic for discussion. All right, so yeah So I haven't really worked on the wake word stuff today. I'm pretty much trying to find my day doing bug fixes So I'll get back to that on Monday. Okay. Yeah if you could spend just, you know run through again, you know, I know you've been beating your head against it for for all of today, but You know try to exercise all the paths just in case for logging in and pairing and stuff Because you'll know better than anybody, you know, what the different options are that sort of thing, so Okay, great. Thanks. I think if everyone if everyone can go in so Everyone could go in creating your account and like or or just pair it three pair of device when you're existing account I think that would also help because You know, I know It's it's so easy as the person who designed who has implemented the system and has gone through it many times yourself You often just like do the exact same thing each time Because you like it's just how your brain is wired up to work Well, I know Josh is good at breaking things. So, yeah Yeah, I don't I don't I don't well. I don't have a device as my challenge. So that's the challenge Well, wait, we can fix that. Can't we Well, the pantograph needs a R4 device No, it doesn't not to pair not to it doesn't you don't you don't need audio to pair I can send you the link to the pantocore build. I've been testing the Wi-Fi on our R3, you know You know all through parent everything. So yeah, okay. I mean, I'm happy to run the run it on the R3 I've just been waiting to mess with the software until I had a piece of hardware that would work Yeah, I mean after parent it's not going to do anything You can at least pair it Actually, well actually it does it does do audio out, but you just can't talk to it Oh I'll schedule the postmortem for Monday we can have more detailed discussion about Oh, yeah, okay. Yeah All right, thanks Chris Ken, how are you doing? Ken's hurling wait. No I've reconfigured my office and my laptop is right in front of my monitor And until I get it situated it's cutting off like the centerpiece of the monitor I'm good. I continue to work on the integration of the new URLs into the existing continuous training process and Putting together a schema for that for trial for training runs so that I know What the counts were the last time I ran And I can do my threshold tests based upon that and all that good stuff Uh, and then I got to the point where I you know needed data. So I started stubborn out The back end and that's where I was at when the shit at the fan an hour ago It's kind of helping some customers Okay Um, all right, so you're gonna be working on that for the next little while. All right Derek Hey, all right, so this uh today. I was basically going through our documentation and the bomb and Creating um as much details I can for johnny so that uh, he can Uh inventory all the stuff and kind of understand it all the a little biter. So Michael did a great job of setting the standard with the fan spec document not everything will be that detailed but um, we'll be creating a spec document for All the parts so that you know, you know what they look like and Know a little bit more about what can fit or you know, more about them than can fit in the spreadsheet Um, so I began that process and I gave everything part of actual part number for my cross now um So I talked to johnny a little bit about that. So, you know, I I'm imagining that's going to happen Um, probably I told him probably January 4th. We'd start Getting these things organized and shipped started starting to ship to joe based on timelines But we should review that um And then I was also going back. So I've been talking a guess a little bit about the wi-fi setup stuff yesterday and uh updated all out, you know starting yesterday updating all those screens But then today also has been a good amount of time just going through um, all the all the mock-up designs and figma uh for a lot of the skills and updating them to The horizontal screen and any other changes that have happened in the meantime that would require updates Uh, so that when you know pants of course stuff's up and going and we have the time to focus back on skills We will have um, some of those updates to to review and and focus on Um, I think the big decision out of that is we we do have to think about Uh, those of you that were on the pants core call There's an opportunity to support both the wi-fi setups and If we want to do that we have to create a design that that kind of prompts the user to select Which one they want to use And guess came up with a few ideas on how to do that. Uh, so I think we need to mock that up and and have A look at it to see if we want to support that Derek was that the issue? I thought the issue was that their process wasn't getting the message bus messages was the only issue I didn't think there was anything like that Well, no, this is uh this This is just something we discussed do we want to support? Um being able to Choose between doing the ap mode versus the onboard Screen mode do you mean a particular device? right? No, no Now that they've got the access point networking working They're like, well, we don't really need the soft keyboard anymore And I'm like, why? And then someone's saying, well, there might be a need to select one or the other. But I haven't tested this bill, but I'm assuming the way it would come up, there'd be a Wi-Fi connect on the soft keyboard. And then if I wanted to go to the access point, I could. And maybe it could be the dialogue could even say at that point, if you'd prefer, you can go to blah to put in your password or select your network. But other than that, I thought the main issue was simply that they didn't have the messages plugged in. So when you were going through their Wi-Fi setup, you weren't seeing the proper screens. Yeah, no, it's two separate things. Yes. They don't have the prompts. It's kind of on us to do that. The guest is kind of working on that. So that's like the screen is just telling the user what to do. And the audio prompts telling the user, hey, this Wi-Fi AP thing is going to be spun up, and you should go look for it. So yeah, all that's going to happen on the screen if we do the AP route. But they are willing to help us build a system that would support both, presenting both to the user, and they choose. Do they choose to use a soft keyboard to set up, or do they choose to use the AP mode to set up? And so they can support that if we want to do it. So I think the choice for us is. You're confusing me, though. That's where you confuse me. So first of all, I thought that's already how it's working. And second of all, why would the user have to choose? I mean, they wouldn't have to say any choose. We wouldn't have to ask them to choose. They could just either use the keyboard or go to the access point. Why is there a concept of they have to choose? Well, because as it is now, it'll be very confusing, because there's nothing that really tells them. They both have this AP mode being spun up. And maybe as we had previously designed it, there's all these audio prompts and these screens telling them to go to an access point and connect. Meanwhile, there's also a keyboard showing up on screen. We just have to think about this and present it better to the user if we want to give it a choice. Because open source and Linux, we like choice, but it can be confusing to have multiple options being thrown at you at the same time. So we just have a good spec on the user experience. Well, this is... Derek is working on, or is Gez working on that? We should work on it together, but Gez is off next week. So I guess I'll take a stab at it. Yeah, I mean, I like having technologically both options, but Ken is right. This needs to be dead simple for the user. And since we have an on-screen keyboard, we should use it. I want somebody's grandma who remembers her password to be able to get this device up and running with no trouble. But there was something brought up in the PantoCorp medium, which I believe is an issue that causes the bug that I see that they are dealing with in a bit more of a direct way than the blue systems guys are dealing with it. Yeah, but they said they could fix that. They just needed to work with it. Yeah. I mean, you're absolutely right, Derek. What he said was that they go directly to network manager. Blue systems go through an intervening layer, and they're not stateful. So they may... Yeah, but the point is, they're getting there explicitly as a fix for that bug. Right. Okay. So the status says Derek is going to outline an actual user experience workflow, and we're going to get down with it. Okay. This is all... We're not making it an either or decision. I just, you know, to me it was like, yeah, both. Right. The technical issues seem like they've been resolved. It's just right now I think it would be confusing for the user as to what to do. Okay. So it's all about props and visuals. All right, so anything... Okay, so that was work on the bomb, the Wi-Fi setup, UX, anything else going on? We should probably check in next week, early next week on ordering stuff. I would suggest we do that. I'll set something up with Chris and Johnny. Okay. Yeah, let's do that. Okay, who haven't I talked to yet? I think I hit everybody. Great. I haven't been around much today. I had a bunch of stuff to do with the kids and doctors. So nothing really to report on my end. Still work in progress on prototypes of the fans and things like that. PCBA stuff continues to move along. Getting new quotes in every day. So hopefully that will wrap up early next week. Any other topics people want to discuss? Yes, just FYI, you created the incident report. It wasn't available to the public. I just, okay, just flag it. I just shared it with everybody. So it is now out there for the world to see. Thank you. Thanks. Okay. Great. So I think Chris and I are gonna have a follow-up after our next meeting about responding to this stuff. Anybody else who wants to jump in on that is welcome too. But for now, I guess that'll be it. Thanks for listening. Have a great weekend.