I would say, let's start with a little boff. I intentionally didn't take that seat, but it's because it's a boff, not a talk. So I would like to make sure that we get to have a topic we want to, and so I want to have a very fair share of spring capability. I also will send long minutes afterwards to the Debian WannaBuild mailing list. So I have now two main topics on my topic list, which one is, I should say, what we have achieved within the last year or last month and a half years, so you get everyone up to speed. And second one is individual topics, which means pepperon's bike shafts integration. So this question that's already started is used for S-Build and WannaBuild for cross-building. So first I would like to get our topics complete, and then we can go into the individual thing. So any more topics right now, maybe we can always add topics later. So any more things you think we should talk about here right now? I don't know, this is a camera spot, but we can start. Yes, good topic. Okay, I hope you all should speak about new volunteer from this round here for WannaBuild, because I saw many people, I should be able to answer that. So more topics right now? Otherwise, I think we should now start with looking back on what we have achieved, I think. All that has more things to say than I do. So if you want. You want to see the DDA made or? Just what are things which we're not sure anyone in this room knows about already. Which is, I think, it's the before declaration that we had done. Presently we have to just summarize the, you may be thinking about the announcement. Okay. I think it's probably the... You said it, I don't know, I think it's probably good. I saw an announcement out there, right? Yeah, I think it's probably good. I saw it in the week. Ah, yes, I was with the Portsman, obviously. No, no, no, no, it depends on the announcement. Yes, it depends. I need to admit that I missed it and also some main list, Ash has missed it, so. Not nice? It depends on the announcement. There were a couple of things on there that it said we might get these done by the week, and whether any of those actually happened. Ah, okay, I'm so busy. Yeah. So just pointing out the points, that's the arch all packages, the Portsman, the Merge, the ROMNs, the Asynbase appels from the BuildDemons, the Algebra is upgraded to Chessi. Yeah. Can you remember? Yeah. New people have volunteered to do it. Thank you. Yeah. So basically. So, I mean, we're now almost at the end of depth comp however. So, I think we really should move on to what are we going to go. The further topics that we had, discussion about this S-build and one-up build for cross-building, already more or less start before the boss starts, so I think we should probably call to you with that one first. Yeah. So, I think you wanted something, so you should explain what you want. You know, maybe it's in support for not just the further two things we already said. Okay, so this came from a discussion with Matthias Schloser, the GCC maintainer. And we'd like to get more coverage of an idea of what the state of the archive is in terms of cross-building. So, I did some, like, one-shot cross-builds of 1,000 packages. I do plan on doing a further one-shot build of, like, 3,000 packages. But it would be much better if we had, like, real-time results in terms of what packages do support cross-building and which don't. So, the idea that we had was, like, would it be possible to integrate this in one build in some way to add another build demon running on AMD64, which is supposed to be Chi, and which is, like, having a host architecture, like, ArmHF, which is well supported for cross-building in principle, and have it, like, throw away all the binaries so not to occupy space or save them if you prefer. But in particular, publish logs in some place that is accessible to be included in Tracker Debian Arch, maybe. So, the question is, is this something that's doable within the wanna-build setup of Tracker Debian, or should we use the setup outside, and how can we integrate that in a way that it can pull source packages that are uploaded to Unstable automatically, and build them immediately? It's possible to do this in one build, because, basically, it's, the fact you throw away the binaries is more on the buildy side, but it's going to be difficult to integrate with the current wanna-build, because it means two architectures with the same name. What you could do, you could use another name for the architecture, and do on the buildy side, and map it with an architecture name, and build architecture. So, I mean, we have a lot of things that we're not using currently to make an architecture in the mapping. We used to have that in place for other things, but yeah. That's already not that nice. But you even could do it, if you really do it well in a way, so that, I mean, when wanna-build gets called, it actually sends back a YAML file to the author to build the, and says, what do I want to have? So you could, even there, and say, but in reality, it's still 864. The thing is, that's the wanna-build internally.  One of the cases to check if the packaging is still or not to... Yeah, it doesn't really check. I mean, that's part of the material to bring in the architecture, and I'm just thinking, maybe I said something wrong, because the installability check is probably different when you're cross-building, and when you... It is. So yeah, basically what we would need to do is, as it seems more like what we do for the port script, is that we don't have it in the normal Debian. Basically, there are different trigger runs, depending which arch it is. Basically, we need to do that part really fresh, to say, well, yeah, you actually have a different, and I think that also needs a very few places patched, which are allowed of this installability check. Wouldn't it be possible to add another suite, virtual suite to one of those that you say, this is a cross-stream starter than architecture? So it's not the same architecture, but... Yeah, that's the question, but there are still the items at the beginning, at the problem of all the installability checks everywhere you go. So the installation check has to be right written differently. Let me give you an answer. Stop, stop, stop, stop. I heard in the discussion, thanks. Well, someone who was slicing his hands quite nice for some time, and so I simply should give him a chance to say something, just as a person with a bigger outer. Yeah? Just a question. What's the purpose of this? What do we do with the cross-stream batteries, or what's the purpose of these bills? To get an idea of structural problems with cross-bulling. So until doing the initial, like, 1,000 package cross-bull, I was unaware that Debian's CMake cross-bull support was currently completely absent. The idea is to figure out this problem. It's not completely absent. It's been fixed once. It may not work very well. It's pending. Whatever. Whatever. So currently we are facing structural problems with cross-bulling already, and it would also help if maintainers could, like, figure out whether their package is cross-bulled or not and have that in the tracker. Like an additional information, your package cross-bulled successfully, and your package does not maybe want to investigate. So as to give maintainers an idea of whether that works. Okay. So the question, actually, is it worth trying to integrate into one bill if you probably require some changes in work or should we just use one of the various one-shot things running once a week, which is easier, probably. This is a separate... Technically, any bills that we have, because there is even more to for new bills, could put as a bill to the configuration to ask more than one bill. So that would work. However, in that case, you should have different suite names. Yeah, and those billchecks. I mean, those billchecks support stats, but you have to feed it with the right information. Yeah, so I mean... It might be... I mean, I have done the work for the ACOL support, and I think it's not trivial. There are plenty of places where it's used. So, yes. I mean, what are we both going to worry about? If you're just doing... There is some work to do. Yeah. If you're just doing one-run bills, you don't need to worry about the damaged part. Yeah, and that makes part of your, you know, formal convenience agreement. Yes. Exactly. One bill is the continuous flavour. Right. All our other bill, these... Except for PiBit, which will take triggers. All the others, you give a list. Right. So then I've seen that you were holding your head for so long. I think what I wanted to say about installability has been taken for all already. So, go. Okay. From what I understood, your need is just to have the packages as soon as they are uploaded, so you get a chance to upload them on your browser. Yes. And have the results as soon as possible. Well, that's the... Like, with a normal delay, like six hours or a day. Yeah, sure. Because if that's the initial need, what can we possibly do is to ask a particular master to do some push on another machine, saying, hey, there are some new packages being uploaded, so we can get them uploaded on it. And it doesn't have to be linked to one of them. Yeah, sure. I'm asking whether that's the point to integrate that. I don't know if that's going to... Well, I think... We have access to files that were included in the upload. Waiting until publishing is not an issue. I think it also makes sense to integrate this into one of those because that makes it the same thing we're using everywhere. Otherwise, you've got this for cross-bonding and this for that architecture, and then somebody else comes up with something else. I think that wouldn't bother you. The other argument is that people want to do bills of stuff for all sorts of reasons. And a lot of those people don't really need want to build. Because they don't need to continue us. They actually want to do a mattery bill, for example, or they just want to build their package for more than two architectures every so often, or every time there's a check-in. So there is a need for other sorts of building. So it's not... But I think in the long term you're right doing it the same way everything else and maybe it's a good question to see if it would be useful possible, whatever, to add one-shot bills to... We already have a package for doing a set of cross-bills in the long term. Sure, it's called X-Builder. My question is would it be useful, possible, whatever to add support to one of those to say I want everything that's in the archive currently to be rebuilt with this set of our options, please, at a temporary suite for that to your database and build things. I don't know, maybe that could be a good way forward and you have that feature and still everything is integrated. I don't know the code of one-shot bills well enough to know whether that's a feasible way forward but maybe it could be. So the reason I was wondering whether this should be integrated into one-shot bills is that having cross-bills support in one-shot bills has a benefit in its own if we ever want to use to do like architectures which are being cross-billed possibly 32-bit architectures or something about that. So that was my reason to approach this with a question what we can do out of archive as well just which is the right place. I guess we should have a look at what's missing at the moment. For a separate instance where we don't have the architecture name flash it's hard. It's hard? Well, I think there is an idea. And just the fact that it's slightly non-trivial. Just to change the code I guess there is two-three days to figure out where to to put the integrated in the archive as a flavor so there's like this architecture is crossed but it's the same thing as that's probably more work because we'll have to figure out the database. The thing that you currently don't have really any information in the tables cross building means you have two architectures together, both architecture and architecture and right now we don't have the information. Is that a problem really though? We have a suite that says part of it is the architecture and part of it is the architecture or the thing you're building for you have a suite it's confusing. We have a suite saying an MB64 cross meaning I built this on a new system. Does it have to be specific to cross building? I guess the Kling issue is the same. The suite is client built that's a different build essential and lots of content. We have the same goal of saying we just want to build. We don't necessarily have a repeat archive build. It's probably different than saying we want to cross build architecture because if you want at some point to say this architecture is cross build there are some more implications there like if you keep the binaries you run the test tubes because you can have the archive completely building but if you have a problem you can get nothing working. Maybe just the concept of a shadow architecture this is the same as same-host architecture we already have but a different build and it's not the real one that would cover a C-Lang rebuild and GCC5 rebuilds and cross rebuilds. What I'm thinking about which would be a larger change but I think more worse in the future would be to basically add or give the chance to have an option for architectures where default is just the empty option and then we could more easily add multiple architectures different small different things so we have only architecture but something like architectures slash architecture or colon architecture or an additional value in the in the yaml that is transmitted but it's definitely a very large change that we have already discussed before and I'm not sure if it's a reversal that's the first part of the work I think it's the way to go but we have to we have to do the code and rewrite probably part of one ability because there are things to change I mean even without that I think there are part of one ability that has to be redone already so if you want to do this kind of things there is probably some kind of it's probably the way to do there is still a bunch of brokerages what about there is still a bunch of brokerages yeah there is of course a brokerage and there is still the triggers are external I mean there are plenty of things to probably change there and mostly if you look we are talking about one ability but the service on bili.demo.org is actually one ability on one side there is the web interface the Python code that gets that part of the log and then you are in the SQL database I mean it's like 5 6 different pieces that some of them have their own configuration files so when you add an architecture you have to add them 4 or 5 different places so yeah it needs it's getting improved over time but it's still working on the other side ok so it's been a while since so I think you are holding up quite some time that you was an eye can you briefly summarize the initial steps of getting crossbow support to want to move what it needs to initially well I have to go into details in the code for me it's if you really want to do that you have to add a new column in the database and this is my architecture, my host architecture then you should replace everywhere in the code when both is a course and there is probably a way we have to redo also probably the trigger part because then when you start to pull external I mean other architecture more than one architecture it's difficult to know which package file to use which file to use right now and it means for integrating the trigger code inside basically so if you want to have I would prefer to call them flavors now because it's not personal honestly because what you really need to do is to make sense the database because we have currently we have two things which are which are holding is package or is architecture and then for each of those packages the individual version so we need to make we have two architecture in suite we need to extend architecture flavor in suite this needs to go all the database then there is if that's done then there is we only have one of the channels to be able to do it then there needs to be whatever I mean I could imagine that we have a different set of Zickers for such a case that would be fine with you or we extend the current Zickers Zickers are Zickers are code which is really you need to be quite careful we're touching it because it's very much standard independent so I think we currently run Zickers for something like 8 to 9 minutes or 15 minutes so I mean every 15 minutes there is a part of the key master and it definitely be much or enough short as in the whole cycle as we're going to miss some of those what does the triggers do when you understand that part it just imports a new package a source file you can put them in oracle updates one of those databases yes the changes in the outside yes the package and the source files and then it's mangled them a bit to keep on the latest version because when you are building an experimental you have unstable as a base so there is camera it's depending on the future you are building if you have been back for security for those updates the code is slightly different and you are basically it's merging these files but differently depending on where is the code where is the code where is the code Zickers is something something is coming Zickers is coming yes and if that's done then you need to take care of the code of one upgrade which could handle packages so that a big people could say I am interested in packages for unstable and for A364 please give me the gross packages if that's done so you need to just build a bit and then mostly should be working but then you still don't see the logs because the logs will just be eaten or that's a good case the bad case is logs are not eaten in just as bad for the normal unstable which will even get worse the point is that you have to modify the code passing the logs to take that into account and I think you don't have as it's written some code information in the mail or something but we should at that point also start to include a version of S build in the log file so that we could detect oh something so this is a newer log so yeah now becomes enthusiastic just a quick one I like the idea about flavors because it also enables us to do profiles like default profiles for certain suites in the future without much further work should be also note that if we are doing cross builds we need to pass the cross build profile like those builds the actual build it promotes the idea that we could collect like clang builds cross builds things under the common term flavors the easiest thing which is just to say we do an architecture MD minus cross but then we would have the same with the next architecture coming up not as easy but I think the better thing in general is to say we have architecture which could have more than one flavor so we have to do also this is next and as for code only once we can use it later on MD 64 C line cross multiple flavors is one type but anyways that's also something I'm a bit worried is that if we use the one build the official one build for that currently I don't really know any architecture we have we probably have 20 more architecture but then I'm afraid the code won't scale anymore yeah I want to have too many flavors either we have to get bigger machines that's another thing that probably will help us to scale a bit more probably we'll have to write some part of the code so it's more efficient most of these are like priority things as well we don't really want to take away from our normal build time finding out how well C lang and crossing works on one of its side already that's just a build you can easily prioritize one suite or one architect one suite or another today already you can just say build unstable first and if you find them then build expert careful so I do that today but that's not the scaling you should already know what's talking about right so I think that who don't just in a chance to speak I'm speaking as well Helmut, what's the archive coverage for a crossbeam so I think we have about 20,000 those packages of them about 3,000 are trust satisfiable so those are the ones that don't end up being uninstallable and of those I trust build 1,000 and about half of them not correctly all of them some succeeded despite reducing coverage do you think it makes sense to have some trigger from a separated instance and get better coverage in the archive and once if there's more coverage then it makes sense to have a perfect architecture cross m68k for example then we can really rethink on the code of one of these and maybe re-backdoor and adapt one of these for the newer times I was asking whether one of those places do do that I want to have the feature somewhere maybe that place is one of those maybe not for me, I think it makes sense to do it at the moment, externally and maybe in the future it would be nice to get it integrated but not with current one of these it's quite old code and it needs a lot of changes actually, one way to do it would be that we try to write a new one of these from scratch that's been used for that also as a desk time when it works we use that for if someone can do the work that would be great I'm happy with anyone who's leading up on that build however I really don't think the issue is that I think yes, if someone wants to do the mana build it would be totally ok for me of corp biology it would always be less than the real build I think that's and the other thing is I just want to add if you speak about flavors flavors are not flexed you could combine but it's just a string which could be an empty string for a normal archive or a string but it's not said it's a yeah, I could combine different flavors because it would be ingeservable to the database design ok, also as a set I would like to stop this topic for the per person bike sheds and for the aspect maintenance I think we need some time for that so for the pbs per person bike sheds any yeah for pbs pba or whatever I think it's kind of the same issue the current code is not very flexible to add new skills like architecture with suits I think it's kind of the same issue than important thing what are you not flexible I mean sorry I was thinking about making a special suit like sit pbs and helping the packages but it wouldn't be better to just have very many flavors which just automatically starts with pbs minus whatever they are of sit if you can't get back of the set way the thing is that you are the same installer if you want to check so it takes I think 3-4 minutes for suit and for architecture of course you can read that in parallel if you have multiple CPUs but if you have 500 pba you need 2,000 minutes of CPU to test run that I'm not sure it's that bad because we have a very short time to run it's very short of a few packages no it's you need to take the whole if you have 5 packages because then time is more or less it doesn't shorten it so much the other thing is we don't need to run it for another 15 minutes we would run it much more soon yeah I agree but still it's probably a scalability issue so I don't quite understand the scalability you should get is it that most of the run time is being used by running those built up check but partly I would say to sort of the definitely most so Johannes Rauer has been working on those built up check for doing the reboot strap thingy I already asked him whether he could pre-process source packages or source lists and binary package lists some does internal format and then have those work from those so since you were checking multiple packages it could cost the parsing step which is really the step that takes most time and does pure steps so parsing takes most of the time and parsing takes most of the time so parsing and representation in the internal format so indeed so if you use the same check on the same background this could save however we are changing the background a bit so because we run it again let's say unstable but then we have a certain set of overlay packages which are different from time to time is it that bad? so basically you can say I keep what I produced once before memory and just merge it to a new group with only 5 additional packages so yes I think they can be done but it's not just the same group with different things but there is a large core which should stay the same then we just add some other packages so that should be doing the same like doing the parsing of the unstable background set once as a pre-parse thing to do could be a significant time saver okay get me to touch on the show I've been working on that yeah that's the meaning well then there is still also internal to one of it maybe that can be improbable but you also when I've been internally you have to parse all the package file source file and look in the SQL database the status and the data status but in that part you only go via the packages and source files which are for this a pbs so it just contains 5 source files I was talking more in the cross building case it's a cross building case the cross building case of course takes the same amount of time as normal the pbs is really Barnaby is just Barnaby is more or less just directly proportional to the number of packages which are which in the suite are to be built so those parts it looks to me like as it's currently very proportional about the number of packages which are available as build dependencies which is of course in the pbs is a very larger number why do we have a monolithic design with one build no matter how many suites we have and not just one database or you know but it can't make more sense to split it up into individual tasks that do this job for each suite separately oh but that's what we do it's running by a monolithic not everything but not even running by a monolithic so everything can run in parallel as long as it's not the same suite is affected so for example for debian for the 50 minutes from debian to parallel for this port we can see this back off because it's running parallel it's the only thing you can't run in parallel it's an import into one suite and architecture at the same time to do something else on that part so it's running parallel we are actually using 4 cores we can go more if we get a faster machine so it's a good course but I think we on you thought it was close we do plenty of new architecture or ppa it's a lot more than what you can get by scaling the number of suites so there isn't just one database it's one database but the database is not super admission and you don't see the database in selfies the database is not basically there are two reasons about the topic of database on this side it used to be that this is one of the database but it was perc.db files it's now a database it's way back as perc.db files I'm not claiming that all suites are called as a perfect one however we profile all of the bad ones so I mean of course if somebody with a really good database engineer could go on it then the design probably will come to something better but it's not that bad so maybe another stupid question do we run those build-app checks for each source package that we try to build or do we pass multiple source packages we pass all of them what we basically do is we make a fake we have ten minutes left so we make a fake packages list which says package build, source, minus, minus, minus name with runtime dependencies on it then we have these packages and say for all packages it's this package list same as the installable and you can take all those packages list for checking out installability that's what we currently do and those lists contain for example if we build an unstable contains a list which for incoming or plus from unstable if it's instrumental from unstable incoming from instrumental instrumental incoming so the list of packages you could build against is very large but it has two different separate lists otherwise it would be just incredible slow slightly crazy question if one was considering the possibility of rewriting would we in fact want to use something like OBS and then use a real use somebody else's system who wouldn't have to maintain it all I have this horrible so it's one build I don't know whether on balance maintaining that horrible must in one place might be a reasonable plan I wonder if it works for us now it's difficult to make it evolve but porting OBS to there's also some fairly hard builders build in things that we may only not agree with we would have to make some significant changes but that would be easier than a whole rewriting no actually if I look at one of the specifics we have basically what does one of the build contain there's something which makes sure that basically to find out which packages each source package has a cycle about the state change we want to put like to allow them so we have a state machine included and well yes that's a state machine nothing special on it that used to have lots of ugly pearl code and it's gotten more and more to use it's now more than it's a state machine not as lots of pearl codes as if and then statements which is better then we have this interface to say give me the package and transfer some information on it and we have the dependency checkup and that's mostly it all of it yeah my point is that there is one of it other part as we talked before they communicate through real weights for example when I build some mails to them in advance so it's kind of complicated sometimes the builder gets on my mail and I'm all for writing the thing in full right of when I build from scratch taking into account all of that trying to use only one communication channel secure if possible the problem there is that when we want to write something in Debian if you don't have the manpower for some period of time you will end up doing nothing yeah and people have started rewriting it several times in the past but I think it's the way to go if possible I don't think it's possible right now where do you want to comment on that for example what I would prefer if someone has a bit of rewriting time currently the build demon forks a spilt away and just basically wait until it's done what I would also prefer if S builds and we still check other 5 million say am I still supposed to build suspension or if not up or because then we come together with one build channel made to S build so that's what we're doing improvements on I want to say when I build it's also probably been decided I mean rewrites the way they communicate to each other trying to get as much as possible as taking S build demons in the sense that imagine you the build demon ask when I build okay what I should do without knowing which suite is supposed to build or whatever just when I build answer all there is an unstable on wheezy this package to build the build demon should build the package if possible send the log continuously when it's getting built so when the build is finished it uploads the binaries and then there is no states to right now we have to keep the logs are still kept on the build demon then there is a separate process it has to keep the states to upload the binaries and basically if you start your job and when it's finished you say okay I can forget about everything I have done I release some logs the package and so on that will help a lot and that will make also as a result if they crash or they will boot there is no problem anymore like now we have to clean that manually sometimes yeah but how for example for that I mean for a lot of these things there are very cold parts in place so if someone says oh yeah I want to take out on this I'm happy about it so for example I'm for the log I'm not sure just use syslog for for it syslog for build logs I don't syslog is not made for the kind of stuff syslog will hopefully throw things away syslog besides it's too much coming in syslog is also not made for communicating state of a configuration management system however I know at least one would be okay but anyways 5 minutes left and I think I would if under something so that topic I would like to use in the last minutes on the expert maintenance if that's okay I'm just saying I think it's a bad idea to use syslog for that I have the best ideas I know it yeah so yeah okay it's an expert maintenance I think we brought it up well I was just wondering I think there was a bot which I wasn't able to go to so I don't know whether that decided that the maintainer has retired officially or we have a lot of things we're interested I was thinking the idea there is that the maintainer for sroot he still wants to be a streamer so there are going to be some persons going to take care of the part and on sroot there were some people interested but we have to try to say that to follow the build elements the developments to make sure that the stretching release we can say oh install the ice build from stretching and devos we have to get some communication between the actual code running the people running after code on the build elements and the people doing their build elements okay so I'm just now wondering what I should put into the maintenance of our set part I guess we'll be happy there's enough people actually doing work that it will carry on like this as a sort of team maintenance so there's somebody to be the maintainer so I've seen someone who has fancy heads which I always prefer so you want to show us a bit of work on your school then apply some different patches to experiment a little and I think you would like to know whom to get in touch with who's running that and whom to communicate can you maybe write that for the meeting minutes is Roger actually still happy to be able to talk to us about it because he left him a half with the system yeah he's still communicating and I have a code right who's that? Roger Lee he's maintaining his school I didn't bring his NMU so that we had a version in Jesse which had a reasonable amount of important fixes in and the other two people have finally moved off their fork from like 10 years ago so we put a load of their stuff back in so they're using the S-Build in order to build now suddenly everybody's in the same page which is good we just need to not let it rot it's basically I would say the most maintenance for S-Build when it comes to the S-Build on their abilities is the standard ourselves yeah but same the feature for the build demands in S-Build people want more features for running them on the desktop or the government machine so we have to just keep that in mind so we are probably to get a team which take care about adding this feature for the and other people looking at the build demands and trying to make these particular what I wanted to say to you was basically the team which is trying to make sure the things that work on the build demands can do it better than the build demands however I'm not sure if there's the right person to do it on their desktops and we have one minute left so I think that's the last remark you previously just did that by forking a version right well we are forking the right now we are forking the GC version but it's we tried, well it's a fork but all the patch are in master anyway so we just have like 5 patch left something like that we are trying to get them done down but anyways for the spit art type I mean people are also at the spit art type so if there's some need there are like 10 or 20 person and I think this guitar part is it's always at the body it is well maintained, you shouldn't need to be maintaining a fork, right? no there are specific patches in it like for example something like the don't want to build even to start if this conflict is not set okay so that's a specific patch the point also is that the build demands are running the stable version of the gun, that's one of the reasons why we are forking, we are just forking and trying to keep the important patch on both sides now we might want to get to run the unstable version of S build on the build demands but at some point there were some features that are needed on the shoot side there are some dependencies between the two we probably don't want to have to back both also the shoot and boost and so on if there are any features and as a topping I think that's not the mark because we should not end with the both for example there are times when we want to add features to run a build like we just discussed before we need to add patches to build but we can't do that basically we want to add features to build these that we can't put into a stable point like this because it's really a new code but we just need it and we need to basically throw it out the same amount of build on the run a build otherwise the little thing time is over so thank you for your participation both I will try to finish writing up some minutes of the last things that we discussed and I will also discuss the writing minutes and then I will send some out to the dev and run a build list so thank you very much all for joining and yeah I think that was one of the almost last DEBConf events for all of us so thank you for joining DEBConf and have a good and safe trip home and I hope to see you again thanks


By not only listening to them and validating their concerns, we give women a voice here on the show by being open about ourselves, because we represent everyday women as every way women.


Atom Homescreen has a concept almost as old as the original iPhone. In fact, Atom Homescreen was introduced in February 2008 with iPhone OS 1.1.3. Today, more than 10 years later, Atom Homescreen has come a long way, and what started as a mere bookmark has now turned into a PWA superpower. My name is Tom and as you've guessed, today I want to talk about Atom Homescreen. Let's get going! Chrome first introduced Atom Homescreen banners in Chrome 42. We're talking May 2015. We've heard from developers like Alibaba that users re-engage four times more often with their app at Atom Homescreen. So in the early days, it seemed like getting users to install a PWA was an immediate recipe for success. In consequence, we tuned the heuristics for Atom Homescreen to prompt users sooner, which yielded to 48% more installs. In hindsight, this alone wasn't directly correlated with other app success metrics that you as an app developer would care about, such as conversions. We introduced an improved variant of the feature in Chrome Beta 57 with better integration into Android, so apps were no longer just bookmarks. Other new features included the ability to change the app icon and app name by changing the values in the web app manifest, and also to register a scope of URLs where the app would be launched directly. But we've heard one thing loud and clear. Developers want more control as to when their apps show the banner. For example, if you're an airline and you have a PWA for storing boarding passes, of course, it only makes sense to ask people to install it after they've actually bought a ticket. If you're a new site and your users are all logged in, it might make sense to show the prompt immediately. And in some cases, even if you have a fully qualifying PWA, you might not even want to show the prompt at all. But most probably, you would want to define your own criteria in your app to determine who is a loyal enough user to show the banner to. Let's see how we can do that in our good old friend AffiliCats that we've introduced in our last two episodes. It simulates a comparison site where you can get great deals for cats. AffiliCats makes money when someone clicks through to one of the deals. The app meets the PWA installability quality bar in Lighthouse, but we're going to hold back the prompt until someone has actually viewed at least two deals. Should the user come back to the app, which hopefully they do, we can then show them a customized button that will trigger the browser's prompt. We're in full control. Add to the home screen as a superpower that, if used wisely, can indeed have a massive impact on how users use your PWA. And if they perceive it as a real app worth a precious space on their home screen. Thanks for watching and see you next time. If you like this series and want to see more, let us know in the comments.


Of all the profound minds born of Zeno's thought, the one who most influenced the Stoic philosophy was, without question, Chrysippus, for if Chrysippus had not existed, neither would the Stoic. His thought is so ubiquitous in Stoic doctrine that many place him alongside Zeno as honorary co-founder of the academy. He was born in 280 BCE on the southern coast of what is now Turkey in a city known as Soli. While still a youth, he journeyed to Athens and began training to become a long-distance runner. This proved to be short-lived as he would soon discover philosophy and begin his ascent to the peak of that Hellenistic age. The then head of the Stoic academy, Clanthys, would adopt him as his pupil and school him in the metaphysics, ethics, logic, ontology, and epistemology of the Stoic philosophy. A few years would pass and Chrysippus would choose to venture away from the porch and teach Stoicism elsewhere, though he would eventually return in around 230 BCE following the death of his master would become the third man to lead the Stoic. He was such a prolific writer that perhaps even the mighty Voltaire would stand reverent at the sheer scale of his works. Which other philosophic figure could match his 705 book library or his daily 500 line quota? An unusual death seemed to be a fashion among the Stoic leaders and in the year 207 BCE, Chrysippus would certainly perpetuate it. If Diogety's laertious is to be taken at his word, Chrysippus apparently laughed himself to the Aleutian Fields. How might you ask? Well, after witnessing a donkey eating some figs at the 143rd Olympiad, he would add to the situation a comical comment, after which he burst into a fit of laughter ultimately culminating in his death, this or he simply just drank too much undiluted wine. His philosophy defended a materialistic ontology and offered its readers an alternative to the Aristotelian and Platonic metaphysics that had up until that point dominated antiquity. His cosmos was a deterministic one and he maintained that human felicity was achieved through living in accordance with nature and in striving to synchronize one's life with virtue. He was perhaps best known by his extensive work in the field of logic and for this reason I would like to begin here in exploring his contributions to the Stoic philosophy. The propositional logic developed by Chrysippus is, without a question, most responsible for the logic associated with the Stoics. What would place him apart from not only his predecessors Xeno and Clanthys, but also from the immensely influential system of logic developed by Aristotle? Well, Aristotelian logic concerns itself with the interrelations of terms such as when we examine the terms car and wheel in the Syllagism, if all cars have wheels, and I drive a car, then my car has wheels. Stoic logic, on the other hand, was concerned rather with the interrelations of propositions. Take the proposition it is day and apply the logic of Chrysippus in this manner. If it is day, it is light. But it is day, so it is light. Along with his work on propositional logic, he was also said to have completed 12 works on the Lyre paradox, 7 on amphibole, and another 9 on various other logical quandaries. Clement of Alexandria would even name him Master of Logicians, and Diogenes later she has said if gods used dialectic, they would use none other than that of Chrysippus. Unfortunately, with the new Platonist preference to Aristotle, his form of logic would fall out of style until the modern propositional calculus proved what the Stoics already knew, that Chrysippus had achieved something momentous. Let us move on to his ethics. If you are familiar with Stoicism, then without question you are familiar with the ethics of Chrysippus, one where the goal of life is to live in complete accordance with nature. The difficulty arises when one is confronted with the task of how to achieve this vague ideal. It seems to Chrysippus that the man who lives in accordance with reason lives in accordance with virtue, and virtue is to live in accordance with one's experience of the things which come about by nature. So in short, to achieve this Stoic ideal, we must place virtue above all else. Any disruptive emotion should be cast aside as they are contrary to nature and considered an enemy to right judgment. Freedom is in fact obtainable, but only after one has liberated themselves from irrational desires, and to achieve this your emotions must be subjected to uncompromising reason. So let us then establish a sound epistemological foundation. For Chrysippus, the soul is like that of a blank sheet of paper, prepared at any time to have any number of impressions written upon it. This differs from Xeno and Clanthes in that they believe the soul only capable of receiving one impression at a time. Upon receiving an impression, we are at once aware of not only its existence, but also the cause of its existence. This makes up what we perceive to be reality. Some impressions lack a corresponding impressor or an underlying real object, and in order to distinguish between those impressions that are true and those that are false, Chrysippus believed that we use a combination of memory, classification, and comparison. With this theory of knowledge, Chrysippus places heavy emphasis on the proper function of one's cognitive abilities and begins the transition from the theoretical into the empirical. Without question, Chrysippus stands among not only the most influential Stoics, but also among the most influential philosophers of the Hellenistic Age. And while we covered much of his philosophy here in this video, there's even more that I wasn't able to get to. With 705 books, it seems that with Chrysippus I bit off more than I could chew. Though I hope you were able to glean the essence of his teachings from what I did cover. If you want to learn more about Eastern and Western philosophy, consider subscribing to the channel. And as always, thank you for talking philosophy with me. Until next time.


Dance is an outpouring of human exuberance. In India, all our gods, all the gods who were worshipped are all dancing gods. Dance is a test of your balance in many ways. I'm not just saying physical balance, your inner balance also is determined. I am just very grateful to have the opportunity to ask you a question today. My question for you, Sadguru, is do you in the Indian culture have a dance that is also considered a medicine dance? Or do you guys consider dance to be something that can have healing properties to it? So, thank you so much and have a safe journey. Namaskaram, Michelle. Wonderful to be talking to you, the dancer. I must tell you this, my daughter who is thirty now, just turned thirty, she is a classical Indian classical dancer. It's a very intricate and sophisticated form of dance, which largely at one time evolved in the temples of India as a form of worship, as a form of offering, but today it is also being done on stage. So, are Indian dances in some way connected to our spirituality, are Indian dances in some way healing or signify something more than just entertainment, one hundred percent? Because all the dancers, the classical dancers in India do not treat dance as an entertainment process. It is treated as a sacred duty and a sacred process. Well, it's very different from what you have here, but very, very sophisticated way of movements and offerings and very complex stories being depicted through the dance.  Having said that, I want you to know this, that in India all our gods, all the gods who are worshipped are all dancing gods. If they cannot dance, we do not consider them gods. How's that for you? Because dance is about the exuberance of your physical form. If your life energies, if your body is in an exuberant way, it will naturally dance. What kind of dance may be cultural, but essentially dance is an outpouring of human exuberance, where there is no outpouring of life. How can you be… how can such an entity qualify as god? So, all our gods are dancing gods, so it is very much deeply embedded in our culture. But when we say India, it is not like one thing. India is a vast country. It had over nineteen-thousand languages at one time. Every few kilometers you drive, you will see people look different, eat different, dance different, their culture is different, their music and dance is different. We… we are also struggling as to how to preserve all these things, because it's too complex and too elaborate. But today quite a few forms are very well, you know, very much in practice, lot of youth taking to it. And it is on stage, it is being attended by people, people even pay to watch these dances. So, there is a whole revival of that in this generation. It's very important to understand that if your body refuses to dance, it's not about whether you can dance or not, it simply is a question of do you have life energy spilling out of you or no? Are you an overflow of life energies or are you a depleted life? So, bringing this dimension that we call as dance into… you know, at a very early age can be very wonderful to bring balance to children as they grow up, because whatever talents, whatever competences we have, competencies we have and whatever genius that is there in every human being can unfold only if there is balance and dance is a test of your balance in many ways. I'm not just saying physical balance, your inner balance also is determined when you're not balanced, you cannot dance. So, this is very important for every culture, it must be brought back and it's great that you're bringing back the Native American dances and I just saw a small video of yours. I wish we had met, sometime you must come here to our center in Tennessee and perform. It'll be wonderful to see you dancing. I saw with all those heavy bells, it must be quite an effort to do that, but you're doing great. Congratulations and my blessings to you. Let this culture live.


Hey y'all welcome back to the fire and water cooking channel and happy 2019 It's New Year's Day, and I'm gonna start something that's gonna be a rather long video by the time you see this It's gonna be two months ago. So Happy new year. It's probably gonna be sometime in February when this video or February or March when this video airs But I'm gonna do some dry aging. So come right back and check it out Morning's coming now All right guys if you're not familiar With the dry aging beef it's Actually pretty easy and there's a company out there that makes these special bags and they're called umai bags They're my dry is the name of the company and What they do is they make these bags that they're similar to a vacuum bag But they are a breathable membrane that makes it easy to dry age your own beef without any Issues so all you really need is your own refrigerator or you can have another refrigerator out in the garage like a lot of us do Which is what I do. It's what I'm gonna do and That's all you need something where you can keep it in the refrigerator You know at the regular refrigerator temperatures of you know under 40 degrees And keep it for you know 30 60 75 days sometimes a hundred days to dry age it so It's best to dry age a Primal a full primal and what I'm gonna do is actually a lot of people will do full rabbi or full strip loins But I'm gonna do a packer brisket a prime packer brisket that I picked up at Costco 299 a pound for a prime brisket And if you're familiar with any of the other Cooking channels like sous vide anything or everything or Guga foods Guga actually did one not too long ago He did a 60-day Choice brisket that he dry aged and it turned out rather well, which intrigued me so I'm not really gonna copy him I'm gonna actually do something a little bit different with this brisket. This is a prime grade So it's a little bit higher grade than what he used, but I'm only gonna do it for 45 days. I'm not gonna do 60 I'm hoping since it's a prime grade 45 days will be get similar results of what he got and I'll go ahead and link to his video up here because It was really opened my eyes to what you can do with a brisket when you dry age it so Like I said this I'm going to go ahead and dry age for 45 days I'm gonna stick it in that refrigerator and not touch it. So I'm gonna go ahead and also I have a beef top loin top sirloin Without the cap on so I picked this up at Costco also, but this is a choice grade So I'm also gonna dry age this as well and cut some sirloin steaks from it So we're gonna do these both for 45 days. I'm gonna put them both in today So I'm gonna go ahead and get this prepped and we'll be right back I guess first of all when I want to go through is These my dry bags you can get them on Amazon. You can find them at their own website umaidry.com But I happen to pick these up on their website because Amazon was out of the brisket size They come in different size bags So just make sure that you get the right size bag for what you're wanting to do They have some that are roast size bags. So if you're doing a smaller roast, you can do those They have some for the strip loins, which is a little bit more narrow They have these bigger bags that you can use for brisket. They're also for like your bone-in primals like your bone-in prime ribeye primal so just make sure you get the right bags for what you're trying to To age there's some instructions on here and pretty much everything in the kit tells you exactly what to do You're gonna need a vacuum sealer first of all There's no getting around it because these are bags that need to be vacuum sealed Like I said, even though they are different than a vacuum bag They're a membrane where these bags let air out, but they don't let air come back in So what happens is as this sits in the refrigerator moisture will leave the meat and kind of dry out But you won't let any more moisture back into the bag. So it lets it kind of breathe out, but not breathe in So that's what keeps a lot of the bacteria and all the bad stuff that happens when meat starts to rot out And one of the things you have to do when you're doing these transferring the meat into the bag is You don't want to take the meat out of the bag.  So that we don't get any other contamination inside the my bag so that's one of the most important things and that's what I'm going to do right now and We'll get this started.  Maybe a little bit less Just so that I don't have so much extra in the space in there So I still want this to be you know Is air tight as I can get it so I'm just going to trim maybe about this much off of the bag So that we can not have as much extra So I'm going to do that and then I'm going to go ahead and wash up the Sirloin and get it in the bag. All right guys I'm going to show you how we're going to start this out One of the first things you want to do is make sure you wash the outside of the cryo pack of your meat Really well with soap and hot water make sure you also before you do that Make sure you wash your sink out really well because what we're trying to avoid here is cross contamination You don't want any any kind of germs or anything getting inside the umai bag So that's why you wash the outside of the cryo pack We're going to cut the top off the cryo pack and we're going to slide the bag Right into the umai bag because we don't want to have any contamination We're going to pull the cryo pack out while leaving the meat totally in the umai bag Now that we've got the meat inside the cryo inside the umai bag We're going to go ahead and seal about 75% of the top Since the bag is much wider than the vacuum sealer We're going to have to seal a good portion of the top before we can vacuum seal this So umai recommends you actually sealing this about two to three times So you take about 75% of the opening and you get it inside the vacuum bag and just seal it two or three times And once we got that done, we're going to open it up And we're going to take our vac mouse fabric that comes with the umai bags And we're going to make sure we clean the opening off really good first We're going to stick that vac mouse in there We're going to make sure we got that inside the vacuum sealer really good And then we're going to go ahead and make sure we push any of the excess plastic up against the meat As much as we can and then we're going to go ahead and seal it We're going to make sure we do it on a moist seal on this particular one So that we can give it a nice tight seal And again, we're going to make sure that we seal this Two to three times after it's done Vacuum sealing just to keep make sure that the seal is nice and tight And like I said, we're going to have as much of the plastic touching the meat as possible You need at least 75 to 80 percent of the plastic touching the meat by what umai bag says And that's all there is to it guys once you make sure you have it all sealed up And you have as much of the meat touching the bag as possible You're going to put it on top of a rack on top of a cookie sheet or any other type of pan You want to make sure that this has some good air flow around it And you want to make sure when you put it on the rack that you make sure that's all the plastic is tight as possible around the meat We're going to stick this in a refrigerator regular refrigerator I'm going to stick it in my garage refrigerator, which sits at around 37 degrees fahrenheit That's what you want to have you want it around that temperature And then I'm going to do the top sirloin for 35 days And then we're going to do a video when we take that out and do some cook Cook some of the steaks up for that and I'm going to let the brisket go for 45 days And then I'll do a separate video when that comes out So I hope you guys got something out of this. This is a basic video on how to use the umai dry age bags I think this is going to be something I'm going to do it on a regular basis going forward That's really simple. Just make sure you follow the steps exactly the way they have them and you shouldn't have any issues With turning out some really great product Make sure you like us on facebook Follow us on our facebook group Make sure you follow us on instagram twitter Like this video subscribe and i'll see you guys on the next video. Hopefully with some really great aged beef Thanks again. Thanks for watching


It's always been a dream of mine to go to university, but growing up where I came from and what I've experienced, it just seemed like it was going to be very, very difficult. My childhood was very turbulent and dysfunctional. There was kind of no stability. We were always running away from something. Applying myself to school was difficult because I always felt different from the other children. There's a lot of bullying related to poverty. I was sent to school with no food. Every time we moved somewhere new, I had to start a new school. That was very nerve-wracking for me. I remember having panic attacks from a very young age, about six years old, which is quite abnormal. I now learn. I had very bad anxiety. Despite that, I really liked learning. I'm kind of fascinated with the concept of lived experience practitioners. I've seen people myself and you just don't gel with them if you feel like they don't understand you. So, I wanted to use my experience and what I've experienced and gone through to help other people that were like me. I made the decision during high school that I did want to go to university. So, I applied for the Newstab program at the University of Newcastle and successfully completed it. I'll never forget when they sent me out the little package with all the information in it. I was very, very nervous, but I thought, just give it a go. I think I was really ready to start pursuing something seriously. I heard about the scholarship program and I thought, nah, that's not for me. Like, there's people that need it more, but then I checked out the requirements and I was like, oh, okay, well, this is exactly for people like me. So, I applied and that's when things really started to change with my studies and myself. The Shapings Future Scholarship has allowed me to access psychological support. The scholarship has helped me afford things like textbooks, computer, one of the main things that I used my scholarship money for was actually to pay my rent at my rental property, which I've been living in for, it'll be going on for years now, and I think that's the longest I've ever lived in a house. When I achieved the stability and I knew that, okay, well, I'm not going to get kicked out, I'm not going to have to leave in the middle of the night. It alleviated a lot of the worry and I could really, for the first time, apply myself. It was kind of always a fear in the back of my mind that my life might go back to what it was and that fear is very diminished. Knowing that there's a group of people out there, strangers, who believe in me and think that I can go on to achieve great things has helped me start to believe that myself. I would say to people who donate to scholarships that you're doing an excellent service to society. I cannot thank my donors enough. You're really creating a new society and allowing people that don't have a chance to have a chance. My name's Nikela, I'm studying a Bachelor of Psychological Science at the University of Newcastle.


All right, I don't know how to make what I'm making right now Which is the holder uppers for these things big things flap out and then I need sticks to hold them in place now I got Pipes that fit into each other. Well, this one fits into that one pretty snug, but like loose enough to easily move So I've got telescoping pipes How do I attach them at the bottom and at the top and have them just connectable? and all I know so far is If I have two pieces of pipe that are each one meter long that should give me a decent range of Things so I'm just gonna start by cutting these Into two one meter long pieces and see if I can make one of these things One meter meter. Wow look I'm making progress No idea where I'm going yet Making some kind of progress. All right, this seems like a pretty straightforward thing Just some sticks to hold up some panels Of course things always get more complicated once you start putting in Reality and there's all these factors like you got to put them in places where they're not going to be in the way People tripping on them and kicking them and it doesn't get in the way of loading and unloading stuff from the boat And these have to be able to close Both of them All right, what do we got? That telescope is quite nicely. Ooh This is a one inch schedule 40 and this is a one and a quarter inch schedule 40. They fit very nicely I'm kind of thinking these can be permanently attached to the bottom but pivotable So when these come down they can somehow attach to this I can put my pin in to set it to the right height up there or down there And then when those close detach it at whatever way and then this can attach to here And stay pivoted there and then it's basically out of the way Let's have to position them in places where they will really be out of the way And then I'll just have to make some little easy to connect the disconnecting here So I want these just flopping around All right, so I just need to pivot at the bottom. All right, that's pretty sweet I got a little sheet of stainless steel here. I think I can do something with that. Okay, take this Wrap it around and fold out some tabs I just need two cuts there and I drew a line at an angle because this is not going on something flat Okay, there's my two cuts. This is gonna go that way because the slope is there those will fold in and Those will fold away All right, you fold those away before I do anything else That's about right I think I can get away with this on the top panels the bottom ones I'm gonna have to do something lower profile on there pretty good I think I can just leave that up there. I can make this a little shorter, too So it doesn't stick out much. I'll have to paint it since it'll be in the sun Wherever it needs to stay I think that top pipe can just stay up there And the bottom one, I don't know, I can hook into this maybe. I guess I could just sit right there It's pretty stable. See if that is in the way of my head Right. Oh nice shade. I can definitely pedal like this. Yeah, just enough headroom I haven't put the pins in to hold this at different positions yet I had to figure out what to what pins to put in first I'm gonna hold it Horizontal and up And then down here. I'll probably just have three positions. I think? I don't know. I mean I can make it as many positions as I want It's just drilling more holes So I've got this side all done. Now I need to do the other side The other side is trickier On this side, I could leave these attached Because all this is on top. It doesn't matter But the flap that's under this Whatever I do there needs to be low-profile enough to fit under this one So there's not a lot of space. So I'll probably have to have these things Stay with these and somehow click into the Think about it. This side is great though Super easy to put in and out Yeah I like it. This back panel is supported in a little bit from the end. That seems to work really well There isn't much bowing in here at the front I just put it right at the front Because that was the most convenient place to put it down here You know if I put it over here somewhere it kind of be in the way of walking through and then the front panel is Supported all The way at the front and then all the way at the back so that the cargo loading area can be totally open So it's not the best. However, I'm thinking On the far edge of this I might put a flap that kind of goes down or you can even go up I know something to just make that more rigid When it's open all the way it doesn't sag much but it does does bow a little bit Or you know, maybe I'll just shut up and leave it the way it is And see if it's a problem. Otherwise, I'll be fixing things that are not problems for no reason Over to the other side of the boat These go up. So whatever I do to that panel there Needs to fit under here and a ton of space These definitely won't fit obviously I guess I'm gonna go consult my brains and see if I have any ideas in there


Hi, my name is Anne Keita. I'm the Executive Director for Sister Care. Sister Care is an agency offering support to those unfortunately been victimized by intimate partner violence. We service everyone throughout the Midlands. We are that best friend to a survivor and we want to secure to them that it's not their fault and that they can live a life of free independence from violence. Sister Care has a 24-hour service line. That number is<PHONE_NUMBER>. Please check out Sister Care's website. It's sistercare.org. It's an opportunity for you to see all of the type of services that we offer. A great way to say that I want to volunteer and we also have that donate button. A little bit does go a long way and we are very appreciative of our volunteers and our donors and we really want to make sure we're staying focused on freeing families from violence.


This is stock number 11013A, we are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used truck headquarters. Today we are checking out this super clean 2017 Chevy Silverado 1500 Crew Cab Short Box LT2 with the Z71 package and the All-Star package. This truck has a 5.3 liter V8 motor, it has been fully safety to end inspected by our service shop. It has a fresh oil and filter change, all the fluids have been checked and topped off. This truck is 100% ready to go. Black clear coat is the color, we shoot all of our videos in 1080p 60 frames per second so if you have HD capabilities on your computer tablet or smartphone device turn them on right now because it is definitely your best way to check out the quality and condition of the truck before seeing it in person. If you want to check out all the photos on this truck, the upper right hand part of your screen is a link to our website. This one comes with the 18 inch painted alloy rims, excellent shape on there, no scuffs or scrapes. On this truck we have brand new Goodyear Wrangler Fortitude 26565 R18 tires on here. They are brand new. We put those on in our safety inspection, so four brand new tires all the way around. No dents or dings on that front fender. This one does come with the HID headlamps, the LED running lights, and the LED fog lamps which will turn those on when we start the truck up here. They are super bright. Front bumper is in really nice shape, I didn't see any major dents or dings on that. The hood is in really nice shape as well. And the grille is all blacked out too. Passenger side front fender, no dents or dings on that. And the passenger side rim, no scuffs or scrapes. That tire is brand new as well. And as you go down this side of the truck, take note of how clean the body is, how reflective and mirror like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down but you're still interested in purchasing the vehicle, you can see the truck, hear the truck, and have confidence in the vehicle that you're looking at before you even get here. So that when you do get here, there's absolutely no surprises. You can make a smart buying decision from the comfort of your own home. And that is why we offer the Summit Auto Fastpass option in the upper right hand part of your screen. A link right to our website where you can apply for financing, get pre-approved, see a payment quote, even appraise the trade all from the comfort of your own home. So when you get here, all you got to do is drive the truck, love it, and you'll be all set to go. Four-wheel disc brakes, that back rim is in excellent shape, back tires are brand new as well. You can see the frame and underbody is in really nice shape, especially the body there. The frame looks good, has all the original factory exhaust, has some nice rough country painted step bars, and the lower rockers are in nice shape as well. The rear brake rail covers on there, Z71 stickers. As we come around to the back, the rear bumper is in great condition as well. I didn't see any major dents or dings on that. It does have the rear bumper steps. Full towing package, which includes a receiver hitch four pin and seven pin wiring. Locking tailgate has the shock down assist tailgate, so it's never going to slam down on you. And it does have a very nice spray and bed liner. Now I'm not sure if this is a factory one, but it looks really good, beds in nice shape, and that tailgate is in nice condition as well. Down the driver's side, just as clean as a passenger side. No dents or dings on that box. Full disclosure, this back rim, excellent shape as well. No scuffs or scrapes, and that tire is new too. Down the rest of this side, looks really good. It does have the capitalist fuel fill, which is a really nice feature. Never get gas on your hands. I think they started that in 17 on Chevy's. Doors look really good, no dents, no dings on there. The step bars look pretty good on this side. It does come with power mirrors, driver's side blind spot mirror.  No rips or tears on these seats. Both these front seats are heated. Power driver's seat, for sure, I think it might have power passenger. All-weather formats, auto headlamps, turned out four-wheel drive. It does have the tilt and telescopic steering wheel. Power windows, power locks, and power mirrors. And as we hop inside here, we'll turn the ignition on so you can see miles and everything. 29,933 miles on this truck. The instrument cluster is very nice and clean. You get the Z71 background on the instrument cluster there. Comes with the leather-wrapped steering wheel. That's in nice shape, no scuffs or scrapes on that. Bluetooth and information center controls on the right, cruise controls on the left. This one has the six-speed automatic transmission, the Chevy MyLink system, AM-FM, and Sirius XM radio capabilities. This also has a CD player, and you can do projection here. So if you have a navigation system on your cell phone, you can project it to the screen through Waze or Google Maps through Apple CarPlay and Android Auto. And if you have an aftermarket navigation system like Waze or Google Maps, you can project it to the screen, and then it's like you have navigation on your screen. This is also where your backup camera shows up. We'll show you that in just a second.  That's your cargo lamps. Downhill assist control. You've got two USBs, two 12-volt power points, and then a 110-volt, 150-watt plug-in. Aftermarket brake controller, passenger side, floor mat, and seat are in excellent condition. No rips or tears on that. The headliner is in nice shape as well. You do get the map lights up there, on-star capabilities in that rear view mirror, and you do get the wireless cell phone charge pad on this particular truck. We'll take a quick look at the back seats, and then we'll start it up and check out under the hood. Back seats are in excellent condition as well.  Rear window defroster, that's part of the All-Star Group. No rips or tears on the seats. Smells clean inside this truck. All-Weather floor mats back here as well. And we'll start it up. Take a look under the hood. Show you that backup camera there. It's a nice feature. Take a quick look under the hood. Then we'll check out those HID headlamps. And I would personally like to thank you for checking out the video today. And hopefully from this HD video you will have been able to tell just how clean this truck is. All the way around inside now, under the hood we have the 5.3-liter V8 motor. Engine-based, very clean, runs very smooth. This truck has been fully safety and inspected by our service shop, has a fresh oil and filter change. All the fluids have been tracked and topped off, and this truck is 100% ready to go. HID headlamps and LED running lights and LED fog lamps. And to see more pictures of this truck, or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, halftones, recorder-tons, one-tons, you name it, we got it. Go to our website, www.SummitAuto.com. Full pictures and descriptions of every single vehicle from two locations, all at SummitAuto.com. And if you'd like to check out more HD videos, you can go to youtube.com slash SummitAuto. Remember to like, subscribe, and share on this video and all the videos that you see there. In fact, in a second, you will see a link to subscribe to our YouTube channel on your left. A link to more Chevy halftone truck videos like this one on your right, if you have not been to our website on the bottom, a link to this vehicle on our website. Click those, check us out, and we really look forward to helping you with this super clean 2017 Chevy Silverado 1500 Crew Cab Short Box LT2 Z71 All-Star with brand new tires and black clear coat. Thanks again.