 Good afternoon evening morning. It is the Yeah, look my watch and I forgot to get it is the November 18th Devsync or Minecraft AI on the eve of the lunar blood moon eclipse that's going on in Me in the States and some other places if you don't mind being up at three o'clock in the morning Hello everybody Derek what's going on? all right, well as I alluded to yesterday continuing my cat and journey and getting the mark to ready for DFM and production With the new orientation of the the ports out the back so yesterday. I was working my way through the audio chamber and Mostly done with that and starting to tackle Some things on the the body the main Kind of solid part of it detail-wise got the ports cut all out and all that good stuff and Got some work to do on how the audio chamber mounts into it as that's changed slightly Still using Those soft grommets to to basically dampen it from dampen the audio chamber from the rest of the housing to prevent vibrations up to the mic But because we've switched the orientation of how it assembles Chris if you remember we assembled the back last Well now you're going to assemble the front last and so that changes how How the things screw so that body itself the back is now going to be part of it. So it's going to simplify the parts So yeah, so the tricky part then is to get it assembled from the front. So that's what I've been working on Very good, and that's it for me You know probably continue on that journey tomorrow. Although I got a couple marketing tasks That I need to address tomorrow Moving to the upper left corner of my screen, mr. Smith. Yes, I've been working on the startup sequence Wi-Fi detect with Pantacore And it appears they agree with me that there's indeed a bug in the AW connect container So they are addressing that issue. However, I am working on a solution That will work just in case they don't get their bug fixed in the near future. So That's what I've been working on and we'll continue to work on and hopefully we'll have done by tomorrow Very good. Mr. Gazzling With the fresh new clothes Yes, I'm getting my house in order was what we were discussing just before the recording started I I Caught a bug Well, I caught half a bug and then a detail Also noticed another part of it, which I hadn't realized So we we fixed that up. There's a PR in core That needs needs Review and approval so we can merge it in Basically, it was the when we updated the WebSocket client Updated so that there's a new API for the WebSocket client very slight modification and But change the signatures of some of the some of the functions to it to accommodate that but the the GUI bus actually uses a different Doesn't use the WebSocket client for the bus it has its own tornado and Queue WebSocket or something Connection on the on the GUI side So the change signatures broke that But only in only in very certain circumstances like when the when the GUI was closing it wouldn't it wouldn't shut down cleanly and And for touch events where messages were coming back from from the GUI So that's why we didn't notice it super quickly because That code's not on the mark to yet, so we wouldn't have picked it up there and and Yeah, I don't do a lot of touching the screen on the on on desktop so Anyway Well, you can you can also just like click or like and you know remotes and and that sort of stuff things that big screen do so Yeah, so I can see how they they picked it up Anyway, so pretty small change In the end, but took a bit of digging into understanding Why it was you know happening and and what the real root cause was and all that sort of stuff I Also did some work on that the V2 More from alpha API Through Selene I've been having some trouble there, so I was hoping to catch you Chris and see if we can work out what's going on And Yeah, community general community stuff and Oh, I also pushed the V 21.2.1 To the mark twos so that will update today Or tonight in your time zones And that'll come out. Yeah, so by morning you'll you should see a new update if you're running latest and Just be aware that like the the Configuration locations a little bit moved so hmm So that's just stuff that was in dev but not in the mark two branch, right? Yes, it's actually Up to current master so I haven't I haven't Gone the full dev I thought since we weren't even at the at the latest point release that I thought we'd get there and you know verify that's all working correctly and then and then Yeah, push rebase off the latest dev So I've been using it for the last week and I haven't I haven't hit anything but you know, it's so easy for one person to to Not find something because they're just not using the different pathways that different people use so Yeah, just wanted to get it into everyone's hands Before we push forward further awesome Cool that means me So today I spent a little bit of time applying a couple changes to the spec for the Service initialization Stuff I've been working on based on some comments from Michael I think we're at a good place so Michael and anybody else wants to take a second look at that. There's just been some tweaks I've also specced out how I'm planning to change the The skill service bring up sequence Basically, I listed everything that it does The issues with how it do why doesn't what things the way it does and how I'm gonna change it around most of it has to do with, you know the assumption of no internet connectivity and And moving some of the things that really don't belong in a skills startup And probably that mostly the how So that spec is out there and ready for Review, it's right underneath the stuff Did you guys read the other day? So if you want to take a look at that too? That would be awesome And I've been in the code as well trying to break my assumptions about things that I've written in in the document so I'll cut that from the video but Is um, is that spec something we can share out as well because I feel like it could be good to Because yeah, that's that's part of what we've been trying to talk about right? Yeah. Yeah is information So it's part of that whole part to boot sequence document We started in Hawaii So I don't know if it's worth separating those things out or just getting that document to a point where it's clean enough It's shareable So well to the extent that it's a it's a discreet chunk of work I Think it's worth just cutting pasting it into its own document and link it from the other one So, you know, we retain, you know coherence. We don't start duplicating work and stuff Okay, we'll probably do that then because the as long as Michael if you take another look at the Service initialization section Let me know if Kind of meets what we were talking about then yeah, I'll go ahead and share that part And we can I can write many specs as I go a little pieces that we ingest instead of one big piece Maybe I'd be better anyway So readings Michael we've all given our status updates as a go cool It's going fine, it's going fine I had a had a whole morning off to just sit down and crank out some work and it just evaporated I got no What I consider work done which is Looking at the technology and the code and the and the The to-dos and stuff, you know Yeah, it was all just administrative. So Yeah, so that's me Awesome Since we have Michael today, do we want to anything we need to talk about? And it's only got is not even like 445. Good job gentlemen. Yeah, I joined late So I haven't had a chance to derail the meeting but here I go watch this So I was in Jira. I woke I woke up at five this morning and I had some ideas And so I've created a whole bunch of tickets Actually, no, I just created one ticket It's got a whole bunch of line items that need to be turned into other tickets Relating to logs and the reason that this is important. It's not necessarily urgent At this moment, but it's it is important it's because it ties in with the activity system and having a coherent view of the basically the state of the my cropped system as a whole and in a given point in time and and So the concept is that I want to start to transition from log files, you know, which are Useful as far as they go then we'll probably continue to be useful in some way going forward into something that's more like a State monitor something that's keeping track of all of the stuff that's happening in the system So our first pass at that would be Once we get the well, actually, maybe it doesn't matter the order the first pass of that would be a system that listens to the message bus and Just records a list of all the things that have started and then ended and just has an active list of all the ongoing activities, right? Sounds like a supervisor service in a way I mean, it's maybe maybe a supervisor, but it's more of a the start of It's it's the it's the tiniest little seed of a system which will eventually could eventually be Something that is aware of the history in the context of what has happened in the system and Can start to reason about oh well the person said this and they said that other thing five minutes ago So they're probably related, you know and start to build in, you know The the ability to actually have that data around to to make decisions about Obviously, that's a little bit down the road But I think it's be a super useful tool even in its most basic incarnation just for debugging purposes of knowing What's happening right now? What skill got triggered? What was the intent that triggered it? What were the cascading list of things that happened, you know because of that? And you can see how they're interacting So So I think that that would be a really useful tool, you know, even in a very primitive implementation and Would probably give us a lot of what we're looking for when we're like crawling through the log files trying to figure out Okay, well, what's the state at which this thing went bonkers, you know So anyway, so, you know got a while here this morning and wrote a bunch about that and started throwing things into an epic about log files So then the other thought I had was Thinking about, you know, I think I think it was guess who pointed out that, you know We're using JIRA in a way that it's not intended to be used. We're not really doing We're not really doing agile development per se, right and so I've been thinking more about the idea of Assigning Things to epics whether they be tasks or bugs or whatever. I'm actually sure about bugs definitely tasks though and Assigning those to epics and then just having a sprint be a defined period of time So rather than it being however long it takes to get all this stuff done You know, it's just two weeks and we try to get better at estimating how much time we're going to spend on things so that one, you know my Thoughts are one about creating a sense of urgency about some of these things and focus on, you know, maybe smaller bites of tasks and And also start to develop as we're going to be bringing on more people a way of Measuring our pace so that we can start to estimate how long it's going to take us to do things in the future Not so much to be like cracking the weapons and do it faster, but just like, you know We can make a wild ass gas about it's going to take us, you know a month to fix this Feature or re-implement this thing, but you know, if it takes us three, we currently don't really have a way of tracking that, you know so Just a couple of thoughts So I look like a thumbs up from 10 Yeah, cool. All right, no one can get us to yeah, okay. Well then get one more thing to do So I Was actually thinking there's some food for thought that the log file epic Might be a good thing to assign to our incoming employee Because it touches everything because like one of the first tasks is implement the started ended messages around every activity, right? So it'll end up touching every part of the code, right? and and then just having a routine sort of the The thing that gathers all of the status together would be, you know, a pretty straightforward thing to build But then having a way to communicate that out in a useful way like maybe either Through a skill or something like that would then be another way to familiarize him with the system as a whole, you know, so Because it would touch all the parts. It would touch the do you would touch the you know the skill system and Interactions and stuff. So just a just a thought I thought Put out there with the team. So you can think about that. We've got some time Um, hey while you've been talking, which you've been clearly doing too much thinking but I Was also wondering where we're at with the The skills interaction spec that we wanted to share out because it feels like it's it's basically done and Just needs to to get pushed out. Is that yeah at the very least the Yeah, the part that Chris has has taken on a crack at right Yeah, that part for sure and I think that'd be a good thing to get out. I mean just do it now, right? and And get some feedback and that'll give people some time to wrap their head around that concept and Give some feedback on that and then we can you know further that discussion with different ideas about You know the whether it's My hair brains you know about handling at a low level or Ken's hair brains you know about handling at the top high level You know, we can at least throw out some different proposals there But But yeah, I think that that system on its own is going to be useful Yeah, it's probably good to stare at that first because some of the ideas from that document trickle into the Startup sequence stuff that you've been talking about and so okay. Yeah So what is so I will I'm happy to do that. I'll take one last pass. I didn't make sure there's nothing stupid in there What does that just a sharing in the depth channel or general? I reckon I reckon it might be good to put it in the forums because that just gives us a you know a Single thread that you know we can go back and reference and stuff and then point people to that forum thread from Chat and different places Okay, so just a form post that includes a link to the document kind of thing Yeah, I'd try and do a like a brief intro as to like You know that you might even grab I can't remember what the what the intro of the document is But you know, yeah often whatever the intro there is you can copy and paste that and to give the context of what you're talking about and Yeah, what do you want people to do with that, you know Trying to link or post to each other because like for like I said this Bootup sequence stuff kind of follows on from that Yeah, absolutely. Yeah as well. Okay. Yeah, any time you provide a link Anytime you put a link to a to a forum post or a Or a forum thread It'll create this, you know, large rich tech rich preview of it. So, um, yeah, it's good like that All right, I'll do some sharing then awesome Cool, well, I don't have any Additional more work for you But I've thought of my last day So we're almost done then Yeah, yeah, basically It's still in the 825 that wasn't nearly derailing enough for Well, I guess it's just a good day sometimes you get lucky