This is the Fuego status and roadmap boff, so I apologize, I'm going to go kind of quick here and if you're not familiar with Fuego, a lot of this stuff might fly past kind of too quick to understand. I'm going to have the obligatory flames. But I'm going to give a little micro introduction to Fuego in case you're not familiar with it and then we'll jump into the boff and I want to leave plenty of time for discussion at the end.  This is the architecture diagram.  Your device under test is connected to the host usually via SSH but we're adding some new transports. The vision, super, super high level vision is we want to do for testing what open source has done for coding. If you look around the industry, you see that there are significant parts of the testing process at companies that is still all internal, the QA methodology, the tests themselves. That's not to say that there aren't open source frameworks like Jenkins or Autotest or Lava and there are test programs like LTP but there's still significant pieces of the whole testing QA process that are unshared. And so the intention of Fuego is to address some of this. We want to promote the sharing of test methods and test results the way that code is shared now. Make it easy to create, share, discover tests, make test results easy to share and evaluate. So that's the super high level vision. The goals for this, we want to allow really quick and easy setup, support a wide variety of boards, transport types, distributions, eventually send the data to a centralized repository and make it possible to join a decentralized test network. So people are building board farms with things like Kernel CI but there's a lot of overhead in building up an entire board farm. Basically I want a board farm to consist of a developer who's on his development sheet and a single board that's right there, have it be easy for that developer to join a decentralized network, share tests, share results with other developers. So the status really quickly, there are three main forks, which is bad. We have what I'm calling, this is new terminology, the Sony fork, the Toshiba fork and the AGL fork. And I just want to talk about what features each one has, kind of where they're at. So the Sony fork, I'm the maintainer of that. This stuff, most of the stuff I've been working on is in the next branch. I've got a command line tool that's working pretty well. A lot of reason this is in the next branch is it's kind of prototype code. So some of this stuff is not really ready to be released to the public yet but it's pretty close. It shows proof of concept. I have a test package system. I've introduced a test package format in YAML, of course, why not? Well, I'll talk about why not later but anyway. There's a client side of a test server system so I can issue test requests, send test run data back to the server. I can do packaging of the tests, of target information and the run information. I have, there are some new transports that were added recently, serial transport. So if all you have between your host and a box is a serial connection, you can run Fuego on that. And then TTC, which is a Sony internal tool. I don't expect a lot of people are interested in that too much but if you happen to be running TTC it's pretty cool. Some of the work in progress is a new test dependency system and I'll talk about that more later. So in the Toshiba fork which is being worked on by Daniel Sangreen is a refactored Jenkins integration. This has been a big issue that we have a static version of Jenkins that's baked in right now. And so this one uses minimal Jenkins plugins to make it easy to use the latest Jenkins version and it actually does run on the latest Jenkins. It also refactored the directories somewhat. There was kind of a, there was a whole lot of sim links around there. It puts the Fuego core directory outside of the container and then volume, volume mounts it in. And so that's actually much easier for development. That means you can work on your, for us developers that's really handy for just users. It's probably not that big of a deal. And then there was some work on, with the outputting results to Excel files. The AGL fork, I'll call it, has been really focused on lava integration. And they are also using the latest Jenkins, my understanding, or relatively recent one. Not the super old one that, that my repository has. I thought I saw some stuff on the mailing list go by about test categories. Oh, okay. Okay, so there's four. Okay. Well, good. You should have as many forks as possible. And then I thought you guys had also done some stuff with reporting features. Okay, also in the old one. Okay. So, I'm going to go over the feature list, kind of where we are with different things and talk about kind of what the current status is, what we've got prototyped and kind of looking and these are some of just the major feature areas. So the Jenkins integration, the Toshiba fork simplifies the integration greatly. And I think we should just adopt that. We are going to lose some things in that though. We're going to lose the dynamic parameters. And so I don't know if that's a big deal or not. Is AGL using dynamic parameters?  Are they all triggered automatically? Okay, so you don't care about the dynamic parameters. Dynamic parameters is a feature in Jenkins where you're allowed to specify some parameters before the job runs when you launch it from the interface. What about your situation? Okay. So you just have to alter the job configuration. Okay. For me, this is not a big deal, but I would kind of later on I'll talk about, oh, well, on this slide, no, right now. So it's definite that we want to use the latest Jenkins. I think AGL raised some issues with security issues with older versions. We're using a simple text template now in Daniel's scripts, but there's been discussion on the mailing list about using Jenkins job builder. As long as we can hide that complexity from the end users, so they never have to see any of that, I don't really care which method we use. It sounds like Jenkins job builder, I looked at it, it's kind of complicated. So I don't want any of our end users to have to learn that themselves, but if we use it, if we have like Fuego install target or something, and it's using Jenkins job builder under the hood, that's fine. So I think we should probably look at that. And then I want to take the Fuego install tools that you've written and integrate them into FTC, which is my kind of, I'd like that to be the central command tool. I talked on the list about renaming that, but anyway, that's not that important. I'm going to skip over this. This is the overview of the test framework landscape. You can look at this, kind of the differences between the different systems. I don't care. So let's go to containerization. So the Docker container builds okay, except, of course, the guy showed up on the mailing list this week and said, oh, my container didn't build. So one of the things I want to do, one of the things I want to do is actually just have a Docker container available. Someone can just download. It's a big download.  So that would avoid the build issues. The Docker container is really useful. I think it's critical since we're doing actual test program building to have a reproducible environment for that. But I did consider running Fuego outside of the Docker container. If you're not doing a build step, then you don't need all that huge overhead because you're just going to connect to the board with SSH or maybe over lava. So I don't know if that's worth putting a whole lot of effort into though. Are people, anyone finding the Docker thing too heavy or too cumbersome? Would be nice? Okay. I kind of thought that's kind of, it's nice to have, it's kind of lower on my priority list because we've got a lot of other stuff to work on. But I think it would be nice because that would make it really lightweight because the script system itself is only a couple hundred K. And if you can avoid having to do the whole Docker thing, that would be nice. But there are a lot of, especially since I added the server support, there's a lot of Python module dependencies, YAML, JSON, and Python requests. So the overlay generation, I did some simplification and I think the way that Daniel's doing it in history is actually using plan differently than it was intended by the cogent guys. And I think that's the way we should adopt, which is a plan is just a list of the tests you want to run with whatever variant you want for those tests. The spec, I think we should leave alone, they're in JSON, which is kind of overkill I think because most of them are just declaring some shell variables, but it's okay. It looks like we're going to end up with JSON in the system. I want to avoid, if possible, having too many languages for someone to have to learn to learn the system. Now we've got shell scripts, Python, JSON, and YAML, and it's like, that's too many. That's too much junk to throw at someone when they're just learning a system. One interesting effect of this, the overlay generator that you may not know about is that we can actually do inheritance on our base scripts. So you can define a board really simply by inheriting from another board. It's a lot like the Lava device type feature where you can have a device type that declares most of the parameters and then you just declare a couple of custom ones. So we actually have that capability, but I don't think anyone's using it. I don't think it's documented very well. Anyway, that's just FYI. The script system seems okay. Overlays actually, I have this nagging feeling that we could actually accomplish what we're doing with overlays just with shell sourcing. So we may be kind of have too much complexity there. But it's not the type of complexity that the end user has to worry about, right? It just happens under the hood. So unless you're actually a Fuego developer, this is not that big of a deal. I have been working on simplifying the specs and plans. So you now do not need to specify a test plan default, which was a ridiculous test plan anyway, because all it did was specify to use the spec default. So that I think is actually pretty good. That's particularly useful for packaging. On the transports, the serial port, support for the serial port is about 80% there. You can run most of the tests now. There are a couple that have timeout issues because it takes a lot longer to transfer large files over the serial port and then reboot has issues. But I think we're going to get a two for one here because if we do the lava integration the way I think we should, which is to add an OV transport connect and an OV transport disconnect instead of using the hook that's in there now. I think it'll kind of be much more official layer of the transport layer, and then we'll be able to put the commands in there. And that's what we need to get the serial port to handle reboot as well. I don't know, is that clear or is that, any questions on that? Let's see, then I added support for TTC. Still really want ADB. I think we're really close. I don't think it'd be very much work to add ADB support. The biggest issue I ran into when I was trying to add it is that Docker, when you're using ADB, as you reboot the target USB nodes come and go. And Docker, that freaks Docker out. So you have to create a different, yeah, okay. Well, what about like the actual USB device nodes though? I'm not familiar with ADB mon, is that something that? Right. Okay, you're saying put the demon inside the container. Okay, okay, sorry, I'm going to. So will that work though, will the USB nodes show up inside? Well, okay, so I'll look into that. That's, thank you for that suggestion. Okay, so yeah, okay, that's good information. This is why we have buffs. And then I think we have, in terms of transports, that's where the, that's where you put the lava integration, is it the transport layer, right? And then there, okay, it's it, yeah, yeah, yeah, because we don't have these connect and disconnect, right? So you put it in pretest, right? Okay, yeah, it'd be good to have, well, yeah. So I think once we, we put it in the transport because there are a couple places you want to call it. You want to call it on reboot as well, possibly. I don't know, I'm still trying to process your presentation from yesterday. Yeah, reboot is tricky. The test collection, okay, yeah, yeah, okay. Yeah, that's actually really cool. Is that what you used for the Docker target? Okay, yeah, that's actually super handy because then you don't even have, in order to play around with the system, you don't have to have a board or anything. You can just, and I don't know, there might be, well, that's inside the, well, yours is inside the Docker container, or is it running on the host outside? Because theoretically, if you didn't mind all the disturbance that running Fuego causes, you know, you could use Fuego on the host itself. So, yeah, yeah, we should be able to, as long as there's a transport, the command tool could do it, then it would be pretty lightweight. You wouldn't have all this Java running and Docker running and stuff. So, is there another question? No, no, it's, as was discussed in earlier sessions, Fuego is pretty dumb about the boot loader layer. It kind of assumes that there's something else that gets the board up, and that it successfully comes up to the point where you have a network or serial console. So, and not handling that was a conscious decision on my part, because I knew that Lava 2 had all that junk in it. So, that may be a mistake. We don't necessarily want to have a requirement on that if people don't want to do Lava 2, but we had other stuff to worry about in the short term. The test collection, I think this is one of the most important things, is to actually have a whole bunch of tests that people can run. And it's shocking to me, how many years have we had Linux? It's like 25 years, and there's not a collection of tests. Well, there are, but it's all, there's onesies all over the place, like cyclic tests is over here, and IO zone, and Bonnie is over here. There's nothing organized for how to get, well, what is the new thing? The new shizzle in file system testing is, oh, Ted shows thing. I can't remember. Anyway, but anyway, we have not many new tests in Fuego itself. Currently, I would say of the 50 tests we have, about 20 of them are actually useful, but they're still general purpose. I would like hundreds of tests. I would like tests of all kinds of different things in the system. The reason that I haven't really dug in and started, started fleshing out the list of tests is because I want to get this infrastructure first, right? I want to know what the package format is. Before I make 100 test packages, I want to get the package format right, or at least close enough that it's not a huge burden if we change something. But it's really important not to delay too long actually making some tests. That's like the whole point of the tool is to test stuff and so we need actual tests. So I see that as a phase we need to do. This is the 50 we've got now. Roughly in the area of functional benchmark and stress tests. Results parsing and post-processing. So we have kind of three things. Well, not including the Jenkins stuff, but we have log compare. We have the parser.py thing, which is only used for benchmarks right now. To extract from the log file the values, the metrics that you're going to use for your benchmark comparisons. And there's a couple of extra little files for how you do the compare and whether it needs to be higher or lower than a certain number. And then we have the float charts, which is the graphing. We also have this thing in there, I don't know if you've noticed it, which is the functional LTP pause neg. So that's for when you have these huge tests that run a thousand things. Instead of, this allows you to say well of those 1200 things that LTP runs, if like 1150 of them succeed, I'll call that success. It's kind of a cop-out. There's actually a feature in there that's not utilized, which is a diff against a reference log. But Cogent never provided, well I don't know if the tools are in there. But they had some ox scripts that would allow you to catch the output and use that as a reference log and you could diff against those. And basically it would say if you saw any differences, that was a failure, but it needs a little bit smarter diff because there are things that you end up with like timestamps and date and stuff that you have to filter out before you do the diff. But that's super, super handy for finding what actually failed. Right now we just use these counts, which is pretty coarse. It's much nicer to be able to say well this is what failed and in the log this is the delta. This is the difference in the message in the log for what failed. And we need to do more here. We can talk about a unified output format. The command line, this is what the command line supports right now. And it supports doing these operations on the local machine as well as on the server. I've tried to have kind of a verb object format for all the things, so it's not too hard to figure out. It seems like a whole lot of things, but once you get into it you can list the targets on your machine, you can query a target, see what its settings are, you can get and set in values for that. And then you can list the requests out on the server for the boxes, you can make your own request and then you can run a request off the server. And the same thing with tests, you can package a test. So if you have developed a test on your machine, something really simple that just has some shell script stuff, you can very easily write the ammo file, turn that into a package, put it up on the server and now anyone in the world can go grab that and run it on their machine. And if they trust you, the idea is that you can put it up on the server and say, I'd like this to run on all Beagle Bones in the world. And so the people that have said, well, I'm willing to run stuff off the server from unknown, well not unknown parties, but certified parties would run that and give you results back. So there's a couple more command line options I want to do. I want to do the install target, which is basically your stuff and the install test, I want to extend to support your tools. Then I want to do some query things. Let's see, when does this thing go to? Cause I'm going to run out of time. Just talking up here. One o'clock? Okay, I got another 23 minutes. So the Fuego server, the idea here is that it could be a distributed test coordinator. The code here is really, really slapped together quickly. In fact, I did most of it in just the last week. But it does actually do this stuff, right? It holds, you can go browse the tests that are up on the server and that are available. You can see what the description string is, see if you want to download it. You can download the test, you can install it on your target. And you can make a request that's stored on the server, run that request on your local nodes. I even did some stuff with wild carding so you can, there's limited query functionality. The vision here is that I want a test store just like an app store, that you can, that there's all these tests that people have developed and you can go look at the description. I don't know if we're going to do like a rating system. Five stars on the block test. So make it easy for people to share the tests themselves. There's an awful lot of tests that, like a developer will sit at his desk. Well, one that I saw that go by was on the kernel mailing list, someone just runs DD on his block device every night. And every, on the kernel next tree. And he just happened to notice one time when it regressed, right, he said, I don't know what happened, but between yesterday and today, the block layer had some issue on my device and he was able to catch it fast. Let's see, let's go. Okay, that was super quick and I'm sorry I'm going so fast. So let's talk about the projects that I think are currently in flight. We have the Foygo command line tools currently in flight. We have the Jenkins integration refactoring, the directory and the link cleanup, test packaging system, test dependency system, although it's not in code anymore. That's just, that's one of my projects that I'm working on the side. So you can't see it yet, although I could write the spec up for how I think it's, how I'm planning on developing it. I've got some of the, some of the code is written, but again, it's not suitable to put in a repository, public repository yet. And then the lava integration. And that seems like enough work just to get those all production grade would be great. There are some other things that people have requested that is actually kind of driving these at a higher level. Siemens last year said they really wanted to use Foygo with something besides Jenkins as a front end. And so that's been kind of driving a lot of the emphasis on working on the command line tool. We want, people wanted to make development or release management easier and that's kind of been driving the Jenkins integration refactoring. There are a couple of bugs have come up that we've been able to fix. And, oh, the execute individual test phases. I think that could possibly help a lot with the timeout issue on lava. And yeah, yeah, you can, well, I have an idea. And for some tests, like particularly if you're building a static binary, you could have the build results and it wouldn't matter what the, you know, as long, you would need to know the platform like ARM, but you could build a static ARM binary and have that available. So there's no build. Nobody never needs to build that tool. And that would simplify things a lot. Well, it just, it's not that it, it makes the architecture more complicated, but it makes the end user experience more robust, right? Because then if you can avoid, any step you can avoid is just avoiding, you know, yeah, yeah. Okay. Yeah, that's basically, I want to treat it like a binary cache. And it would only work, I think, if you had things you could do static because one of the big reasons to rebuild is you got to match up where the dynamic libraries are for all these different targets. Let me jot that down, though. Well, that's true. That's true. It's a test for the SDK. Sorry, just second rank source. Be available. Okay. The other thing I don't, oh, okay, this is the big one. Kevin Hillman, who couldn't be here today, he said, create and submit Lava v2 jobs and post-process the results. Actually, I think we're like really close to this. Yeah, because it would be super cool to be able to provide a, and I don't know if there's anything in Lava we need to change, but it'd be super cool if every Lava lab, or every Kernel CI lab was instantly Fuego capable, right? So then, we can just keep encouraging them to build out more labs and then it gives us a place to run our tests as well. So I think that's really cool. That's kind of high on my list, is to finish that up and make it work. The other thing with test scheduling is the server doesn't, well, and this had to do with yours, but right now, Fuego itself doesn't do board reservation. Jenkins does, but when I run something from the command line, I just have to know that the board's not busy and that's kind of lame. That's one of those features that needs to be finished up on the FTC. Okay, so now I'm on to this massive list I got from Daniel yesterday. Some of these I've already gone through so we may not need to discuss them, but we'll kind of go through this list real quick and see what we have left. So clean up unneeded stuff, overrides. The pre-test should be able to automatically select overrides, so I'm not sure I understand that one. Can you, I may have mangled the wording when I put it in the, oh, oh, okay. Oh, I'm all over this one. I agree, I totally agree. I, as part of the test dependency thing, and maybe I'll just go to that slide real quick. So the test dependency, the reason, one of the reasons for the test dependency is to find out which tests will apply to your machine. If we're gonna have, I'm already trying to address the scalability of the system. If we have hundreds or thousands of tests, some of those are not gonna have anything to do with yours, like if you're testing wireless and you don't have wireless on your board or you're testing ethernet, you don't have ethernet, or if you, there's specific hardware required or specific buses, you know, you're doing a CAN bus test or something. So one of the ideas of this is that we specify in the base script a bunch of the dependencies in a declarative form. So you have these need variables that say, what do you need? And then the board can provide some items and it says, well, I have ethetool, I have wireless, I have, you know, a CAN bus or whatever. But I think it's really important that you don't require humans to go populate this board data, because that's gonna make it just too hard. You should never ask during installation a question that the user doesn't know the answer to. And that's the problem with a lot of this stuff, is like, wow, you know, it's like, do I have a GPIO 7 that controls an LED? I don't know. Some of this stuff you can't probe for, but to the degree that we can, I'd like to make probe tests that can go populate the board file automatically. So I actually have some stuff in the tool for getting and setting variables in the board file during the test run. So probe test could go say, oh yeah, this guy's got this cake and fig, or this board uses this cake and fig, it has ethernet, it's got the proc file system, it's got sysfs here, it's got usb. It can put those automatically in your board file so the end user doesn't have to do that. And then the test, you know, can know ahead of time. And then you could, also the end user can use that to filter what tests are appropriate. So that's the idea. But we probably should discuss this more on the mailing list to see if it matches what people wanna do. Okay, okay, how many Daniel screens are there? There's actually, there's actually, I stopped at five, you notice I stopped, okay, keep it simple, I agree. I think we wanna keep it super simple. And so anytime we can reduce the complexity, reduce the number of steps, I think that's really important. One of the things I've wanted to do is make an automatic board detector, or like a board wizard. So you could say, you know, oh, I see you have a serial port. I just ran some commands over it. It looks like it's running Debian. So should I set up a Debian board for you? Board definition, same thing with SSH. SSH only runs on a couple of things. And there's some things you could probe on the host. I don't know if people would be game for that or not, but it'd be an opt-in type of thing where you'd say, well yeah, go ahead and probe my system, see if you can find what my target is. And if you already have some other system installed, such as TTC or Lava, you could hopefully just find those out directly without having to do any setup on the Fuego side. Provide deploy and boot as in Lava. I agree. Although for me, this is a lower priority. I don't know where it is on your priority list. Okay. Well, this would be Fuego putting support for this stuff in. But if you're already on top of Lava too, right, then we don't really need to, right? We don't need to add that complexity to Lava or to Fuego. So I think it would be good eventually, but it's kind of low on my priority list. The transports, I think ADB is real critical just to kind of finish out the common transports. There may be some other target agents, but I think that we'll do. I need to finish the serial support actually anyway. And then updating deploying the OS. That's kind of in the same category as the first one, right? Okay. Common output format. Okay, so we had some great discussions on this in like November, December, but we didn't kind of come to a conclusion. I think it would be great. I actually think that maybe we should look at what Avocado is doing because they seem to have done this pretty well. Yeah. Well, I think what they do, I'm not sure, but I think what they do is they actually go to some their own common format and then you can specify as an output parameter, which one to go to. And they also support like HTML, right? So you can dump out a page of just HTML that then just plops into a browser. So the way they've done it, I think is good. And I don't know if we want to use Avocado itself, but we should at least look at how they're doing it. Let's see, parallel testing on same device types. I think your idea was that you could do this with Jenkins labels. So this is Macy. Okay. Let's see, multi-node tests. Yes, we should support that, but we have kind of, it's kind of lower priority at the moment. I know you may have some stuff for CIP that an external node, right? Right, well, that's what we're doing with the existing Ethernet tests is we have the host as one endpoint. And that's pretty easy to do with our current system. To do non-host, you know, other nodes that participate in the test requires some thinking about the APIs that we want to use for that. Let's see, ability to run tests already on the target. We're almost there. We've got, I don't know if you saw my is on target stuff, but there's something that we'll probe, look on the target and find the path. And then the next step was to, you don't have to cache it, but sometimes the operation to find it takes a while if it's not in one of the normal places. So I wanted to add some support for caching that. Then auto, let's see, I'll automatically prepare TFDP, NBD route before testing. Oh, okay. Okay. Yeah, I think this is, I think that's what the Mitsubishi guys did. They had a presentation at ELC Europe where they were talking about how they were doing their kernel testing. So support of matrix of board tests is something Avocado does pretty well. Smart support command line Fuego tool. I think we're pretty close with FTC, creating an interface to download and install new tests. Actually, FTC does it at a very gross level, except I did use tar balls. So, okay. Well, I don't mind making that an option, but I do want people to have a discrete ball that they can just say, here's this thing. You don't need to talk to me anymore. You don't need to connect to the internet to get it. So, we could talk about that one offline. How are we doing on time? I'm gonna bisects kernel CI integration. Okay. Okay. Well, yeah, I agree that it's valuable. It's also like really hard. What? Yeah, I kind of wonder. Well, one thing is, I mean, you could use FTC as part of a bisect as long as FTC, like the command line tool, returns appropriate error messages or error codes. FTC, yeah, yeah. Kernel CI integration. I think that's, okay. So, is that talking about using our stuff with the kernel CI front end? Right. Well, yeah. Yeah. At the place where you were integrating greater jobs for the building. Right. Well, yeah, I looked at the kernel CI API and it's pretty simple. Basically, it's like four different JSON transfers for the different types of objects. So, the only issue, I think, is there's a little bit of a, currently an impedance mismatch between our run information and the run information they have. There's this very specific for booting and they have some kind of funky weird fields in there I need to ask Kevin about. But I think it would be good. If we're gonna run tests on their system, I think they need to, they'll probably have to adapt to running a non-build boot test. Yeah, hopefully we could. Yeah, it would be the latter. Yeah, yeah. Yeah, they've got, one of the things that it's important to keep in mind is I'm going like totally off. This is a really random thought. But the reason kernel CI is successful is they're catching bugs right when they have the developer's attention, which is that time of patch submission. Right? And a lot of these automated systems, the problem is they're running some tests in the background and no developer's actually looking at the results. Or they're not tied in to give the results back fast enough to the developer so they can take action when they're interested. And so that actually is reflected in kind of the design of how the request and the architecture of the system move stuff through the system is that you wanna get results back when a developer is interested in them. That's when they're most likely to actually do something with them and make a change in the code based on the test results. Let's see. Yes, quick to run.  Oh, LTP? Yeah, LTP is a disaster. Well, on that note, I really think that we should have specs for every test for a quick, and I don't know if you wanna call a long one, but there should definitely be a quick variation of every test that runs in under a minute. And... Right, right. Well, I would like to see LTP, even if you're using LTP, I'd like to see it broken up so that you're not just running one huge blob. If you wanna run the huge blob, you should be able to, but... Yeah, dash dash all or something, but if you just wanna, what are the semaphores doing? What are this set of syscalls doing? Or what are these tools doing? Okay, so I have one minute left. I'm gonna, I'm sorry, but I'm gonna kind of scoot through these. Oh, we're almost done. I think this is, okay. I already covered the vision. So the roadmap. So I think we have some process issues. I wanna talk about what technology level, what are the priorities, and we'll probably have to take this offline. But in terms of process efforts, we gotta unmerge, or we gotta merge the forks. We gotta unfork the forks. And I think your, my understanding was the main AGL requirement was get off of stinky old Jenkins. So I think if we, if Daniel and I can get our trees together on the latest Jenkins, that'll go a long ways towards making you happy. So, and I don't think we're that far apart. I mean, you did that big refactoring, which I have to do, but I think, so I think the first priority should be for me and Daniel to get our stuff together and then come back to you guys and see if we can get that lava stuff in. I think we'll be in really good shape. So my, I think we need more real-time communication. I'm proposing a monthly conference call and I'm actually proposing that we piggyback on your guys' call. Is that okay? So I'm not gonna come every week because you guys have AGL stuff to talk about.  I don't know, is that okay? When it, the call is at 5 a.m. in the U.S., which is a little bit challenging, but it's not that bad. Seven, yeah. Well, there you go. No, no, no, I'm fine. I actually, I can make 5 a.m. work.  Oh, 10 p.m. for you? Okay. It's really tough to get something that works all around the globe. And that's, you know, that's a reasonable time. Oh, okay. And then I think we should do a FOIGO mini-conference. So we did that thing in Japan. I thought it was actually pretty good. It'd be good when we get kind of the stuff merged together called a V2 or something like that and roll out the features, explain them to people. I don't know if we wanna do something at LinuxCon Japan, or that's not the name anymore. Open Source Con Japan, well, I don't know what it's called. May 31st. Yeah, May 31st. I'll be there, so, but I don't know how, do we wanna have some kind of official FOIGO conference or should we take that one offline? Okay. I think super high priority is lava integration. I think that'll get us a lot of interest. If we could actually be running FOIGO tests in kernel CI board farms, I think they'd be happy. I think we'd be happy. I think everybody'd be happy. So that, I think that is, after we get through with the merging, I think that's our highest priority is to get that done. Okay, here's some repositories that I know about. I'm sorry, I didn't know. I kind of trailed off because I ran out of time making the slides, but your repository, I think was in your slides. So, and I don't remember if you had posted your repository location, but anyway. Yeah, so, see Jansmone's slides for the other repository locations. FOIGO, it's hot. Grab some candy on the way out. I'll feel bad if nobody eats it. It doesn't matter though, you don't have to. I know it's hot, anyway. So that's it.


Alright, watch this, it's the level one. AHHHHHH! DAMN IT! How's it going everybody? Dott, today we're back with some more Dragon Ball fighters, right? Madges, this time playing the suggested team of Videl, Goku Black, and Piccolo. I don't think there was any suggested theme behind this team. I just asked you guys for teams and the very first comment under mine was just these characters names, no other context. But look, we got the costume on and everything. Me and Great Sam and still don't know who's under the mask. We for sure got this. Oh, I did not know Videl had a line against Broly like that. And if I was Videl, I would probably not talk to Broly like that. But that is just me. You would not catch me alive talking to Broly like that. And if you did, I'd be, oh, dodge that. Oh, yeah, I'm kind of a Videl player 24. Well, never mind. I was feeling myself. The dodges were looking real crisp. For one solid second. All right, I'll take that. Honestly, not the worst trade. God, Broly is just Broly. Is it what is this met? No, no, no, no.   There was so much pressure there that, of course, you would command grab.   Okay, at least I got to the ground. I'm a guard cancel here. Let's just get out. No, the keyblast assist. Wow, those come out fast. Super ready to waste no time. He just shows up and shoots you. All right. All right. That's fine. That's fine. Oh, no, I'm getting, I'm getting bodied. Oh man. That was kind of sick. Okay, I didn't predict it.  He just be shmoving. I can't stop him. There we go. We got him, boys. We got him. That one should have worked. That one should have worked. I thought that would work. Wow. Get a combo as well. Yeah. Makes sense. Don't even try it. Don't even try it. I keep thinking that I can get a Super Dash after that and that is just my bad. Ah, man. Sorry. I'm not, I was, I was ever a Goku Black player before the, I'm still not a Goku Black player, but after the buffs, I just, I've started dive kicking a lot more and it feels good, dude. It feels good. Even if I don't totally understand when I can connect my Super Dash. I'm just dive kicking, dude. All I know is dive kick. This is just dive kick, but with like anime aesthetics. Now we take this. I'm actually just going to vanish so that I can get this corner back. No blocks. Wow. A block would have been crazy there. Nah, no, nah. Nope. Bam can dodge it. Oh, that's it. No, I didn't. I'm so bad at timing. Oh, damn. Oh, that sucked. I was really going for that grab. All right. We still have Sparking. He doesn't have Spark. We got a, we got a pretty big advantage when it comes to Sparking. Ah, it's a little faster now, huh? It's a little faster. You got to be afraid. It's also a beam. It's also a beam. It's two things. It's a command grab plus a beam. And it's a little faster now. So we all got a respect. He's going to go behind. Really? I can't believe he didn't go behind. I knew it, dude. He was going to press his luck trying to catch me on the back. But it ain't happening. I forgot this is instant now. Goku Black is a new beast. I kind of forgot. I kind of forgot that Goku Black is a beast these days. All right. How do I get out of here in the coolest way Papa reads? All right. We just switched. We just switched. We just switched. I could have maybe ended the game there. No block. Oh, that was dumb. Okay, but we still have sparking. I'm feeling pretty good about our chances. If we lose, I'll just say it off the top. I say this all the time when I'm in situations like this. Losing here would have been an accomplishment on my opponent and a great collapse for me. But we do get the win. They didn't even have to bust out the sparking. Give me my tape. I want my weights back on. I actually feel weird without the weights on. Wow. Blame your own fate. Blame your fate that brought you to me. That was a great game. Actually, that felt pretty intense the whole time. I didn't even know if I was talking all the way through it. I feel like there was parts where I was focused, especially when I was trying to do dive kicks with Goku Black. But we out here. We got the first W. I'm happy enough, dude. And we got a couple of dodges. You know, that was kind of doing work as well. Do I try to dodge on round start? Hmm.  Oh, that was so simple. I can't believe I just, I fell into the grasp of that play. Dodge. Dodge. Oh, come on. That was sick. Even you got to admit. That was so sick. That did good damage, too. Oh, no, no, no. Oh, I'm bad at the game. But when was I was bad at the video game? I didn't know. I never would have done this if I knew if I was bad at the video game. Guard cancel. Are we beat those?  Getting a bit of, getting a bit of lag. But I was born in 19 frames. I don't even notice it. Don't even notice it. Can I combo off that? No. Well, you know, I'm going to keep checking. That's too high, right? Yeah, it's too high. Oh, I don't think he meant to do that. And the fact it worked is crazy. Oh, no, don't do it. Ah, he did it.  Probably should have went for a Key Blast there. Two bars. Is that going to be enough to kill? He's going to go for it. No, no, he's not going all the way for it, though. Never all the way for it.  Wait, wait, did that counter actually work? Or what was that?  No, Piccolo. All right, get Piccolo out. We need his assist. Uh-oh. Uh-oh is right. Uh-oh is right. I don't know why I did it. I don't know why I did it. I just felt the need to save. Lag saved us. Lag made us who we are. The lag really saved us here. Really and truthfully. I'm just going to go for it. I'm going to go for it. Ah, we're dead. Ah, he's not going to give me the chance to go for it. No! I was going to wake up super with Gohan.  Should not have done that. I tried to just 2H. See if he would have went for anything. It was bad. Hit is fast. Hit do be fast. I don't know what he's trying to do with Videl there. Just at a range. No dude, we're making all the mistakes. All the neutral mistakes. No patience. No confidence. Oh no, poor little Piccolo is alive. Did not expect to be staying alive after that. I was in the middle of getting ready to say we have to do something drastic and get to do all right. I'm just going to let me calm down. Let me play some essential Dragon Ball fighters. Let me give you just the essential. I tried to do the exact same thing I got blown up for doing the first thing. I tried to do 2H. Wait, homie drop one more time for the homies. Dude, one more try. One more try for the homies. Yo, he probably knows I was calling for a homie drop. Appreciate it. But I am going to have to take you out now. Stop that. Guess some help. Nope. I hope this kills. I'm in limit break. All right, get good. This guy gave me a homie drop. This guy's the real homie. I appreciate it. But sadly, that was lucky. Got caught jumping. Damn. That sucked. That was actually, I mean, he did give me a homie drop. We were dead. We were dead a long time ago. We can't, we can't be sad that we didn't get the, we didn't get the homie drop and back. But now, damn, I got to pay back the homie drop. If I'm in, damn, he's created an economy, dude. Now I have to pay him back. If we start winning this next match, he's smart. All right. I see your devious little plan. I'm just going to run up to him. Oh, come on, Videl's, Videl tried her best. Give it to her. Just because she doesn't have protagonists. Let me dodge that real quick. Cheeky little bit of damage. God, if I knew the Videl combos right now, I might have been mashing. Oh, so close and yet so far. I may have been mashing. I may have been mashing. We'll talk about it in the future. Nice. These long legs, dude. Dude, how long the Goku's legs go on for? I'm just going to drop the level one on him. Give him the holy grenade. Boom. All right. Just get him out of here. All right. All right. Come on. I got to get a lead so that I can give him a homie drop. I will pay him back. I always let it be known that I always repay my debts, dude. What is he doing? I didn't expect that. I'm not homie dropping Broly. Technique of a God. All right. Nice. I didn't have to use three bars. I thought I was going to have to use more. Woo. Super baby two. I hope you're ready to be homie drop. You paid me in kindness and I will do the same for you, friend. Oh, try to step up. I am just flailing around, though. I am just I am just outside of a car dealership, waving these wacky inflatable arms right now. This is just not a good look for me, honestly. Thank you. That was, ah, thank you. Oh, damn. I wasted everything, dude. Everything I was gifted, I wasted. Damn.  I'm so sad I couldn't do more off of that. Dragon ball. Let's go. You can't dodge. I can't draw a dragon rush. That was that was my bad. My be my be. And I got to I got to kill him so that I can homie drop him. Otherwise, I can't pay back my debt. Hey, I'm just I'm just mashing because I want to get a hit. It did. Oh, what? What just happened? Okay. I just let me homie drop you, dude. Just go easy, dude. He knew it. He knew I was going to Super Dash. Damn. That was genius. That was genius. I have to admit it was genius. Damn. Damn. I'm so focused on the ending. I can't play the game for the game. Play the game for the game. Me play the game for the game. Oh my God. He's fast as. All right. You're now in homie drop territory. All right. Here it is. Here's my homie drop. Don't ever say I don't repay my debts. He didn't get hit. Damn. I regret nothing. I had to do what I had to do. I had to pay him back. Had a bit of robbery, but let's go. Take the win. Don't ever say I don't repay my debts. All right. I repay my debt. Oh God. That got really intense. Oh, geez. I hope. What if like he let me live by accident and he didn't give me a homie drop and now he's just like he was toying with me. I hope that's not the case. Good games to that guy. We are moving on, dude. Oh my God. Oh, I hope he knows it was a sign of respect and not a sign of that. All right. We are back with the next match against Kepler's beauty. We played against her a ton of times on the channel. And now we will do it again. The mirror match of mirror. Well, I don't know. I said mirror match because I don't think we have a single character in common. We don't. I'm not going to dodge right away. Yeah. I feel like I've played against Kepler's beauty enough that oh no. Oh no. No double Sunday. We take those. We will definitely take those. Down on my luck, though. I'm just not playing well. After, dude, sometime in that second game I lost the ability to move well. I don't know when it happened. Maybe, I mean, I never had it, but maybe I lost a little bit I had. I'm dead. One, two from Kepler. Oh, yikes. Didn't even get a hit with Vidal. That was just... Oh, no, there's a little stutter there. Game was mourning Vidal's loss. That's fine. Do you see this? That's annoying. That was supposed to be a reflect. Oh, no, not a Keyblast hold back, dude. All right. We got pretty lucky there. Not going to lie. Another big bit of lag. Let's go. That wasn't... You were not supposed to get hit by that. I will say that right now. But I don't keep the pressure up, dude. Nice. All right. Feel good. Felt pretty good about that one. It's, you know, the basics. Sometimes you got to rely on the old basics to get you to where you need to be. We're pretty much back in the game at that point. We got a few confirms that we didn't... Oh, I can't believe my jumping light didn't win. We got to win those air dairs. We're piccolo. We're born to win air dairs. Back dash. Yeah. Yeah. Okay. Okay. You called my panic vanish out. Is that... I mean, you didn't have to do that to me, but you did. You did. All right. All right. All right.  Okay. Understandable. Our good tonight. The reeds are good tonight, and they're not on my side. I'm in the library getting checked out. She has my Dewey Decimal System number, bro. What am I supposed to do? Oh, no. I got to at least hit spark. At least I got to hit the right buttons to use spark. I'm just mashing. Am I going to get red again? Because we all know I'm mashing spark at this point. Oh my God. They try, they try to do. I didn't level three there because I forgot we were on this patch and I didn't want to waste my sparking.    I'm both of those things.  I should have just popped a level three. I should have popped a level three.    All right. All right. It's fine. We're still alive on. We still have a chance to win. I don't want to see anybody giving up. We don't have any people giving up, do we? Because I have not given up. I'll let you know when I give up. I'll let you know when I give up because it's not happening anytime soon. Again, I don't know what actually happens. So I'm just getting lucky right now. Level one should kill here, right? Right. Correct. Correct. Correct. All right. Correct. Let's go. Let's go. I told you I didn't give up yet. I told you I was going to tactfully reset my way to victory. I told you these things. Oh, that was a good choice to cancel it. All right. Watch this. It's the level one. I swear, dude, I, if we went back and looked at the inputs for that game, you will see if we slowed it down that I did input the super. I was just a frame too slow. I was a frame too slow. I don't even know why I wanted to do it. I could have gotten vanished on pretty easily, but I just, I wanted to, it would have looked so cool. Damn. All right. Well, that was a big loss. That was a big loss. I'm not going to. Oh, I forgot. Vidal was on the team. I didn't do anything with her last time. So that's probably why. Oh, you can't superdash to that. Oh, I'll take it. I'll take it. I will take that. That is big. Kind of got out of there eventually. I'm just kind of playing peacefully right now. And I keep trying to do that. I'm just, we're playing kind of peacefully right now. There's not a lot to say. I'm going to dodge spark because obviously they're going to spark. Why do I go for these things? Why do I try to be the person I am? It would have been so cool though. Admit it. Why did I spark? You pick a low assist. God, don't do it. I'm just, I'm begging for that to hit at this point. Okay. Okay. Okay. We kind of throw away the lead we had. I mean, we still have the health lead. I didn't even know that put them behind me. I was very confused. Oh, Goku why? Goku, wait, wait, wait. We might be living question mark. Nope. Sometimes I like to add a little drama to the scripts. Damn, why did I spark? Sometimes I just spark out of emotion. The spark just comes in a desire for a knee. You know, spicy. That was good. All right. Just take him to the corner. Aject her button. I did hit. I did try to hit reflect. I am that guy. I am that guy. I am that guy. I thought you were going for the six H. All right. Life is pain. Life is brutal. Level one. We just down tech here. Down tech to H. No, no, no, no, no. You don't down tech to H. That was my mistake. Oh, you hate to see it. Pretty nice combo though. And now we just let Piccolo do cleanup boys. I did not mean to do you. I go through like that. I figured they would jump in again. Why am I mashing reflect like an idiot? Okay. Okay. We're all the lag. I was born in 90 frames. My hometown has come to save me. We out here. We are out here. The hometown is back. Oh, homie drop. A lot of homie drops going on. That was never a homie drop. Well, I feel I feel good calling it there. We got blown out in that last set. But the first set was a good example of friendship.  If you did, if you have any more teams to suggest, let me know down below in the comment section while you're down there. Make sure to like button and subscribe to the channel if you want to see more videos like this. And check out some of the other videos that should be on your screen right now if they catch your eye. Other than that, I've been Dr. Do it and I will see you in the next one. Man, I'm playing UI Goku. I feel like playing UI Goku next.


Hello, welcome to Haidiyuan. My name is Kei. I'm marketing. Hello. Hello, I'm Debbie. I'm product manager. And this is your contact right here. Yeah. So, Haidiyun, what is this? What are you showing here? This is our product, the POS. So this is the POS with a lot of connectors. A lot of things happening here is for the store, the sales. And this one? Another machine. A restaurant or the machine. So people can just order. Yes. And then do you have some smartwatch connected also? Yes. Oh, there. So then it vibrates when there's an order. At table one there's an order. People click and all the waiters can just come and say, okay, I'll take it. Then this guy will take it. And then we'll bring the chocolate cake directly. Maybe the waiters can get one cup of the coffee for the customer. All right. And this is PCB? Yeah, it's PCB. So what is the CPU? It's 328. 3128. Right here. 1GB RAM? Yeah, 1GB RAM and 8GB flash. All right. Can you show how it looks? You can actually disconnect. And then the customer can use it nicely like this. What kind of price are we talking about? 100 and 5 dollars. So it's a good display. It's a high quality display. So the pictures look good. And then all these can do a vibration in here. All right. Let's try here. This order. Okay, submit order. Okay, pay. There. Okay, cool. And this is for the waiters included. This included the price 105 including $10 extra. Big vibration in here. And this is a team making this product? Yeah, it's a team in the car. All right. Hello. Hi. What does this guy do? He's a technology manager. And some of these guys are here. Hello. What is he doing? The software. Yeah, software. This is the software to connect, make a custom menu and system right here. Yeah, also all this. And it's included the software, the price 105 including software. Hello. Hello. This is Android. Android. Is this Android? Yeah. Android. Android software right here. UI engineer. All right. So I can do all these things and they work very good. Hello. Hello. Hello. So this connect. What is this? A system. It's called a table. Yeah. And a table number. And everyone have a customer on the table may get the number. So the device will restart the signal. Is it Wi-Fi? Yeah, Wi-Fi. It's a Wi-Fi in a restaurant, right? Yeah. All right. Hello. Hello. So testing. Yes. Doing some testing right here. It's possible to show the printer how it works. So through the UI can go and then it will just go. Print all three at the same time. Cool. So Heidi Yoon is POS and restaurant owner. And in the future will be more market, different one. Yeah. Considered to do more and more POS style special tablet. Right now our POS device about one month under 10K. 10K order already. Yeah. And the restaurant business is new. There is a new product for us. Because this restaurant order only for the restaurant market. So at least we only get the 2K order. And is it for Chinese restaurant or outside China also? Right now we only for Chinese restaurant. But this restaurant is the famous restaurant in China. In China. It's very easy to translate and work for other languages. You can go to Spain and France and Germany. No problem. For the restaurant order... Oh, it's sweet. I'll show you another... It's different UI. Different video systems. No. This is the logo of Heidi Yoon. For this device, when the customer orders the food, then the service can be played for the advertising. How do you say advertising? Pay for it. This can be advertising. It's advertising. You have an advertising solution in there. Right. Right. Cool. Okay, so that's cool. That was cool to see some restaurant ordering solution right here.


Everybody Matt here for late in sports cards ripping six boxes of 2122 tops tier one Bundesliga soccer These are for Danny G. Good luck Danny As I mentioned earlier, I'm not a soccer guy, so I will mispronounce some names But hopefully still pull you some big hits here. This is dual patches to 25 Nicholas Dorsch. Nice patches Rookie Otto to 25 armel Bella coach out Coach out and Otto to 50 Matthias Genter Those of you that know hot or not no soccer. We'll have to tell me how I'm doing on the pronunciations here All right next up That is Jersey to 127 Jamie Luelling rookie and Otto to 100 Andre Chromaric this is Otto nine of ten Lucas Hernandez low number of Otto there There you go, Danny. All right box three this is rookie patch to 127 Marco John and Jumbo patch Otto 405 Christian Gunter or Gunter. Sorry low number jumbo patch Otto Five on that one and Otto to 106 Timo horn three boxes to go Not a very long queue after this just about a half dozen boxes So grab up your boxes get in line and you won't be waiting too terribly long To get your box ripped. This is dual patches to 25 Takuma Asano 25 there This is Otto to 75 Ride on Baku. I'm sure the correct pronunciation doesn't end with an upswing like a question, but Hopefully I'm close on that one and Otto to 106 Willie Orban two boxes to go. This is rookie Jersey to 127 Gabriel Vidovic and Jersey to 127 Mark. Oof This is Otto to 25 Maximilian Agastine and Otto to 50 Florianne new house Last box. Good luck. Let's finish off with a nice one-on-one for you here, Danny This is Jersey to 127 Shereldo becker and Jersey to 127 Jordan Toronto Toronto Torano Riga Torano Riga, this is Otto To 25 Musa Diabe And on the back Otto to 100 Sebastian Polter. All right, that'll do it for your break Danny Thank you for the purchase appreciate that and we'll get these right out to you


D um and be the same kind of thing sooner we do it the sooner it's in place for the rest of this fiscal year so we can't let it wait too long but we also don't have enough knowledge to know that'll probably be some time in October once you have the strategic plans at your priorities shortly thereafter we have a conversation with you about next year's budget the FY 25 budget on what how you see those priorities moving forward and what your thoughts are what parameters you might want to put on as far as budget limits or tax rates or whatever because then we will be starting in November with our own staff presentation to give you your budget in December so going to be a lot of uh thought processes coming up in October so just enjoy your September and when you're not looking at assessments on the board of civil authority still as we're talking about budgets are we still on track to have a fiscal 2023 I believe so for the next meeting which would be just one meeting later than normal yes thank you okay come check in with the boss back yes yep she's nodding and then one other thing I didn't want to add it to tonight because we just discovered this so late but um you may recall it right after the flood you issued me some authority to take actions with flood related and that actually expired on august 23rd so we might need to re-up that so um you won't probably don't need a million dollars now but it would be but there are still some FEMA related things it would only be those kind of things to move along so we might ask you to do a call-in meeting sometime just to re-up that maybe only agenda on the item for some more period of time at a lower level so great because we've been kind of operating as though we're still in place so I missed that is that it that's it okay so we can adjourn at 9 22 p.m thank you all thank you


Today he brought along a friend up in New York who's a former minister and still a manager. This is excellent. As far as introductory books, that's a very helpful book. Is that about divorce? Yes. And it's real introductory. I mean, he actually will give stories and then the quote from the course. And he doesn't quite get too deep. I mean, it's real helpful. But it will be the place to start. It is. Yes. And we have 70 some tapes available, some of which are at an introductory level. And some we call beyond the basics and some that are going much deeper. And with tapes, you can play them in the car. And some of them you have to play over and over because these ideas are so fundamental. And yet when the mind is resistant to them, it takes repetition just like any kind of course you would take. And most of us have found tapes very helpful. I'm not listening to what I know or anything worn out because of this. In the workbook, Jesus makes this statement that everything you believe is rooted in time. So again, when I see a tape like that, here I am questioning beliefs and root. You know, root seems to be real, the bottom and basic. If everything that I believe or everything that's part of the ego belief system is rooted in time, then that's what it only comes down to this questioning, this linear view of time. That's what I'm coming to see. In some places, they talk about time as being simultaneous instead of linear. Well, initially I can be like, well, that sounds interesting. What's simultaneous? Yeah, what happened? But here's a little description that is from Absence of Felicity, where Jesus gives this graphic kind of description of time. And sometimes if you're kind of visual oriented, it's helpful to have a graphic. See, there's not a whole lot of graphics you can think of when you think of time. He says in the course of the sentence, when correction is completed, time is eternal. But here's the description. Time is like a downward spiral that seems to travel down from a long, unbroken line along another plane, but which in no way breaks the line and appears with its smooth continuousness. Along the spiral, it seems as if the line must have been broken. But at the line, its wholeness is apparent. You can kind of think of a spiral and a thinking from maybe a position inside the spiral of looking and seeing all these steps like the spiral staircase and seeing all these separate things. When you look up or down. Right at the line, if you were like on the line, just blowing on the line would seem very smooth and continuous without any sequencing of events. Everything seen from the spiral is misperceived. But as you approach the line, you realize that it was not affected by the drop into another plane at all. But from this plane, the line seems discontinuous. This is by an error in perception which can easily be corrected in the mind although the body's eyes will see no change. So that's the stuff we were talking about the other night about. The correction of misperception would be a quick judging to let go of all the boxes and just take forgiveness as your only box. The body's eyes would still see a world. But if there was no judging and category surprising going on in the mind then it's kind of like being right there with the Holy Spirit at the line and just watching the events. There wouldn't be any separate events, just watching the images go by. The eyes see many things, the mind corrects and you respond not to the eyes illusions but to the mind's corrections. You see the line is broken and as you shift different aspects of the spiral the line looks different. Yet in your mind is one who knows it is unbroken and forever chases. To me that's been real helpful to think of it in the graphic kind of sense. Come back to the line. Where's the line? Are you talking about the line of the spiral itself? That would be analogous to the Holy Spirit. Some of you might have read some of it when they talked about out of body experiences or so on and so forth. Here in some literature the silver cord. Everyone seems to have a silver cord that goes back. Attaches them? Yeah. They feel like they can use their mind to go beyond, beyond, beyond. But they're always attached to the silver cord. Like the silver cord is their connection to... Like a safety line. Yeah. And there's just a lot of different things. I've used the analogy too of just thinking of... Instead of having all these separate situations and events. Like I wake up in the morning. I go out at breakfast. I brush my teeth. I make my bed. I go to work. I go to lunch. All these separate situations and events you can imagine a cord like for a necklace or a bracelet that would just connect them all together. That would be like a golden cord that would be in the middle. Pretty much analogous, I think, to this line that he's talking about. It's a perspective. It's a way that if you were right there on the cord then you wouldn't be... It feels like a blow instead of all these broken-up isolated... Like I start, you know, driving to work by getting in my car. I drive for a while. And then I stop driving by getting out of my...  And it breaks up. And they're separate events. And when I'm in that place everything seems like a struggle. That's your concept. And I really wait to get to the next thing that I'm...  Constantly readjusting which causes stress. And the key thing we could look at too is like when Ram is saying about that person out there on the screen, that's the person that seems to be part of these sequence events. In other words, when you think about even your own personal history, there seems to be all these events that this person went through. And there all seems to be these events that looks like this person is going to go through, just coming up. And the way to transcend that would again be to come above the battleground, so to speak, or to really start to be identified as mine. Instead of being the person on the screen to be the mind that's watching the screen, or the dreamer of the dream, the court calls it. And that's where the flow comes back to mind versus body senses. Then, in essence, you seem to be on the screen, but it's not your perception.  It's your piece, you're at peace. So you're flowing on the screen like Ram is saying, it's a flow. There's no separate frame. There's no readjustment to every box. No stress. Tell them here in time how you surround stress. When you're told part of that, how does that work? Yeah. See, that's the thing about... I know. See, that's the thing. Well, we're going to go into it. Every time I've attempted to be peaceful and in linear time, in other words, I say, well, I'm dealing with people like this and this and this, so I have to meet them where they're at, or I have to... You see, you get out on the screen again. It really has to be questioned, because it's that whole thing of the old Bible quote about being in the world but not of it. I mean, how do you do that? Well, in the end, you have to get to such a detachment. It's no identify with mine that you don't perceive yourself as in it, even though it seems, Jesus certainly seemed to be walking around in it, but it was a real detachment like he was... But he wasn't going. Well, guys, I have an appointment at 12 o'clock with this other gathering over on Mount Olive. So, you know, we have to kind of cut it. He stayed as long as they were willing to listen, and then went to the next mount, but that's how his life was afloat.  It's like, when I'm getting caught up in what's going on in here, the thing to remember is, oh... Because when I'm caught up out here, I'm one of the fears of the dream. I'm no longer the dreamer right in there. So then you adjust by trying to fit in and distract yourself from this with the stuff out on the screen. And it's not wanting that distraction anymore. And when that happens, the screen's a distraction, and you pull back, this is all you want. You don't want to be in linear time. Linear time doesn't work real effectively. There's a trick. What's the trick? Well, I think, Sid, you're asking a good question because when you start to really follow this in, the world, as you know it, starts to seem to crumble or not make sense. And many people, there was a woman that married me. Yes. There's a woman that married me who, you know, she was asking around and talking about jobs and the woman came to you and she said, this isn't making sense anymore. And she started going to the courts deeper and deeper and she started listening to, I guess, which is a real high level of, you know, not trying to reconcile truth and illusion and trying to make it work. And she just said, I'm going to step out because it's not making sense anymore. She was stepping out of her job. That's what she can particularly what she was referring to, right? Working this job doesn't make sense anymore. And I have found that. I have just graduated with a master's degree in health education. And I'm trying to figure out, well, what job would fit into this goal of peace of mind? What job isn't going to be a distraction? I'm a nurse. If my goal is taking care of people and giving medicine and all that kind of stuff, then I really must believe in sickness. If I take it away and don't believe in sickness and it's just healing, then can I just work with every patient at their level to help to heal their mind and work with my mind, you know, because it's ultimately my lesson. At the pace that's necessary, am I going to be on a doctor's pace, a hospital's pace, a nursing registry's pace? How can I have peace of mind working at a pace the world wants me to work in? Well, you know, that doesn't seem to work. You know, so for me, there's been something coming in my meditation for many years now. And it says there is a job out there for you, but you're not prepared for it yet. And I've kept that in mind. So I got the degree for some reason because that opened up of how that's going to look. I had no idea. And there isn't a job that I can go that I can find in the paper that's going to give me peace of mind and hold on to this purpose that I desire. It's so strong. And are you getting an inkling of what this other job might be? Oh, I'm getting an inkling. Yeah. Yeah, I am. It'll never show up in the paper. No, I won't. I won't. Oh, I'm getting an inkling. I think it's good too. Lynette brought up the point of finding it again today. And I would say, again, you have to start where you perceive you are. You know, this is a direction. I think we're starting to unveil a lot of things and talk about it because as you sit around and talk, I mean, even when Rhonda would come and we would go into things and you had a job in a formal sense and it seems to be a process of elucining where you just take the next step that becomes apparent. You know, you feel it real strong. And a lot of times, when you even feel a strong idea of what the next step is to be, you go, we'll kick right in with all this screeching and everything. But, but, but. Right. And when you hang with it though, it just, this persistent guidance is called to awaken. It just doesn't go away. And you hang with it where you are in linear time. You don't bolt out of it because now you came to, of course, a miracle screw and it seems like that's what you do. The part of the listing too is when the mind's in its decease state, it perceives itself as splinter between many levels.  And it seems to have a lot of needs. And you can see if the mind's deceiving it believes it has all these levels and all these needs that to yank out of a job situation. Well, what's, what's good is that going to do? I still perceive I have needs. Now how am I going to get the income to meet such needs? So to me that's why it's very important like Mary said, to question the beliefs. And for me it's been a process more and more of like unifying the needs. It's kind of gotten simpler and simpler to the point where I've seen that healing is my one healing of my mind. Initially it certainly didn't seem that way. I had student loans to pay off and, you know, very specific things that is like, well you can say healing, but the government doesn't particularly see it that way. You've signed a note for, you know, to pay back a student loan.  Then it was even the choice of job. It was really interacting with the people I could do.


Do you have anything to be delighted with the spirit show mother allowed tonight? Twice coming from behind to get a point against the unbeaten league leaders? Yeah, obviously very pleased. Confidence levels had been knocked after the last two defeats. It was a tough challenge for us tonight and we met it head on. We attacked at every opportunity, carried a threat. Probably had the better chances of the two teams on the night. Had setbacks in the game, responded really well.  And showed that belief in their own ability. It was growing as the game got longer because we've got some good players coming here tonight. All the talk about Bristol City and how good all their players were. Well, I think a few people might be speaking about our players on the way on tonight. And talking of setbacks, certainly the timings of their goals were blows. Obviously early in the first half, late on in the second half. It makes it, I suppose, all the more commendable the fact that we've come back and got the point. Yeah, I felt we started the game really well. And the goal was soft, flinted 6-4-5. But that was normally as great as those situations.  We played some great football and switched the player at every opportunity. And really hurt them in wide areas. Got the goal. I thought we took off the gas for a period. It was almost like we needed a breather. Second half, they started quicker the two teams. But as a half, we're on. And I thought we carried more of a threat going the other way. And had some good opportunities. A point away from home is always a good thing. But this one in particular, as we said, they weren't beaten. I think this is only the second time in the drop point at home all season. It's twice coming from behind. There's a heck of a lot of positives to come into that. Yeah, it was a championship level game. Watching from a similar quality of the football from both sides was excellent. They're a good side. They've got a lot of threat going forward. They scored a lot of goals. They're very cavalier in the way they play. But I think the game kind of panned out as we thought it would. Their attack pushed the two wing backs on the gamble. But on the counterattack, they lead themselves open. And there was plenty of moments where we did look at the threat on the counterattack. Didn't always pick the right pass, but generally carried a threat and created a number of good chances.


the scientific method is largely an empirical method it's based on observation and when we observe nature what we are observing is the behavior of nature when we see a billard ball hit another that's a behavior of matter and what science then does it analyzes these observations and tries to extract the patterns and regularities of the behavior of physical nature as it presents itself on the screen of perception conscious perception so at the end we end up with predictive models of nature's behavior we know that if we put things together this and that way we will get this and that effect and these predictive models are the heart of technology we use these models to develop technology because we know how nature behaves and then we can put that behavior to use to our advantage and and because of the success of technology science has acquired enormous cachet in our culture as the enabler of the technologies that extend and improve our lives and this is all fair enough but science says nothing about the intrinsic nature of the physical it only analyzes behavior in differential terms in terms of patterns of differences bear differences for instance what is a positive electric charge it is that which is not a negative electric charge because it behaves in a symmetrical opposite way that's all science does but what is a charge intrinsically what is the nature of a charge science has nothing to say about it it's fundamentally outside the scope of the scientific method the intrinsic nature of being of existence is a question of ontology a question of philosophy which has a broader less precise but a broader method that's not based only on perceptual observation it's based on logic also based on empirical consistency it's based on certain values like parsimony you try to make sense of things with the least number of postulates and it requires a certain way of thinking and a basic level of acquaintance with the literature that lots of scientists don't have some do have but lots of them especially the very vocal ones on the media a lot of them don't have they don't even they're not even aware of this fundamental distinction so they ended they end up thinking that science itself is a philosophy why it has nothing to say about the intrinsic nature of things and then they spill out nonsense bullshit if you forgive my english some of this gentleman we just saw on that video are guilty of this of being very ignorant of the issues of philosophy and then doing pseudo pseudo philosophy