Chapter number 34 of Billy Bunny and Uncle Bullfrog. This is a LibriVox recording. All LibriVox recordings are in the public domain. For more information or to volunteer, please visit LibriVox.org. Recording by Lola Janie. Billy Bunny and Uncle Bullfrog by David Corey. Chapter 34 Billy Bunny and Jenny Muskrat. Well I played pinocchio with Uncle Lucky Left Hindfoot last evening and it was so late when I got home that I overslept myself this morning. And maybe I'd have slept all day if Robbie Redbreast hadn't come to my window and told me that Billy Bunny was reading a letter which I told you about in yesterday's story and that every time he turned a page he laughed harder than ever. Well I was so curious to know what he was laughing at that I told Robbie Redbreast to fly back to him and look over his shoulder and see what was in the letter while I hurried and dressed as fast as I could. And when I was all ready to go into the friendly forest where the little rabbit was I saw him coming towards me with the letter in his hand and the little Robin perched upon his knapsack. Good morning he said and handed me the letter and now you shall hear what was written to Mr. William Bunny, Briar Patch, Old Snake Fence Corner, USA, care of Uncle Sam. My dear Billy Bunny, just a few lines from your old friend the circus elephant to tell you that he is coming to see you as soon as he gets over the measles. If you've never had the measles dear Billy Bunny, don't get them for they are dreadful things for there's so many of them. Please give my love to Mr. Lucky left hind foot and tell him as soon as I'm well I'll be back in his circus your friend Ellie and as soon as I read the letter the little rabbit put it in his pocket and hopped away and by and by he came to a little stone house by a river and before I go any further I'll just whisper to you how I know all this. You see the little Robin told me all about it for he and I are great friends and his nest is in the old apple tree just under my window. Well pretty soon after looking all around Billy Bunny knocked on the door of the little stone house and in a few minutes it was opened by a nice lady muskrat whose name was Jenny Ava. How do you do little rabbit? She said and then she invited him in and gave him a cookie made out of carrot seeds and pumpkin flour and after that he showed her the letter from his friend the circus elephant and just then all of a sudden the front door flew open and in came the miller's dog and oh dear me Mrs. Jenny Ava muskrat forgot all about her society manners and ran down the back stairs into the river and the little rabbit forgot to say goodbye and hid himself in a big hat box where she kept her last year's Easter bonnet and then what do you suppose the miller's dog did? Why? He began to sing. Old Mrs. Muskrat jumped into the river splashity splashity splash and little boy rabbit jumped into the box that held her best bonnet and trampled upon it. Mashity mashity mash.  End of chapter 34. Chapter number 35 of Billy Bunny and Uncle Bullfrog. This LibriVox recording is in the public domain. Recorded by Lola Janie. Billy Bunny and Uncle Bullfrog by David Corey. Chapter number 35 Billy Bunny and the Millers Dog. After the miller's dog stopped singing as I told you in the story before this he poked his nose into the hat box where Billy Bunny had hidden himself and said in a deep growly voice come out of there or I will growl and bite the bonnet that Mrs. Muskrat wears for best and the purple flowers on it and then she'll think it's you who did this dreadful unkind deed and never speak to you again or you with cookies feed. Goodness me but you are a very poor sort of a poet said the little rabbit peeping out of the hat box your poetry is dreadful and this made the miller's dog so ashamed of himself that he couldn't wag his tail or even bark no sir he couldn't do a thing but slink out of the door and close it so softly that it didn't pinch his tail hardly at all laughed the little rabbit did you ever see such a silly dog and neither did I and neither did you I know well after a little while Mrs. Jenny Ava Muskrat came up the back stairs from the river where she had gone in the last story you remember and wasn't she glad that nothing more had happened if you had jumped into the other hat box she said you would have spilt my next year's Easter bonnet and that would have been too dreadful for anything and wasn't the little rabbit glad well I guess he was twice over and maybe three times and after that he said goodbye and hopped away and after he had traveled for a long long ways he came to the field where his old friend the scarecrow lived have you ever been asked the little rabbit and he took a lollipop out of his knapsack and offered it to the scarecrow but he didn't want it haven't you got a cigar he asked I haven't smoked forever so long I'm sorry said Billy buddy I don't think I have any really and truly cigars here's a chocolate one if that will do and he handed it to his friend the old clothesman but the old clothesman couldn't smoke it at all although he tried the very best he could and pretty soon it began to rain and the chocolate became soft and sticky and the little bunny all wet so he said I guess I'll crawl into a hollow stump if I can find one and it didn't take him long for he hopped away to the woods nearby and the first thing he saw was an old stump so he hopped inside and no sooner was he safely out of the ring than a voice said what are you doing in my hollow stump who are you anyway why didn't you knock on this old wood block if you really want to stay and in the next story I'll tell you who it was that said this end of chapter 35 chapter number 36 of Billy Bunny and Uncle Bullfrog this LibriVox recording is in the public domain recording by Lola Janey Billy Bunny and Uncle Bullfrog by David Corey chapter number 36 Billy Bunny and the wood chuck you remember in the last story that just as Billy Bunny hopped into the hollow stump a voice said what are you doing in here I came in to get out of the wet answered the little rabbit and then the voice replied what is it raining I want you an umbrella and an old woodchuck opened a little door in the side of the stump and winked at Billy Bunny that's very kind of you said the little rabbit and he opened his knapsack and gave the woodchuck a nice lollipop and after that the woodchuck said I think you'd better stay here with me until the rain is over don't you think so and Billy Bunny said yes for the woodchuck was very nice and had such good manners that the little rabbit felt quite at home but oh dear me it began to rain so hard right then and there that the water just poured into the old hollow stump and pretty soon it was very uncomfortable so the woodchuck said now don't you ever tell anybody where I'm going to take you for it's my very own house and I never let anybody know just where I do live you see so many people are after me some with guns and some with sharp teeth and claws that I have to be very careful so the little rabbit promised and then he followed the woodchuck through the little door and down a long passage until they came to a nice large comfortable room now this is where I live said the woodchuck and he went over to the cupboard and took out a carrot candy gumdrop and gave it to Billy Bunny and then he lighted a big cigar and sat down in his old armchair and smoked and all the time they could hear the rain pattering on the grass overhead for it's wonderful how you can hear all sorts of sounds when you're underground and have big ears like a rabbit you know now I'll tell you a story said the old woodchuck after he had blown some lovely round rings of smoke into the air once upon a time not so very long ago a band of tiny fairies lived in the woodland near and often I would hear them singing soft and low when all was dark and quiet and the moon shone bright and clear so one evening I stole softly out of the hollow stump and found them dancing merrily with tiny skip and jump and just as I was going to say how do you do the fairy queen began to scream and then away she flew and then her tiny subjects took fright and ran off too and now I never see them more I dancing near my old stunk door that's too bad said the little rabbit for he was so interested in what the old woodchuck was saying that he had forgotten all about his lollipop and had dropped it on the floor and in the next story he'll pick up his lollipop and eat it because I hate to have him lose it don't you end of chapter 36 chapter number 37 of Billy Bunny and Uncle Bull Frog this LibriVox recording is in the public domain recording by Lola Janie Billy Bunny and Uncle Bull Frog by David Corey chapter number 37 Billy Bunny and Little Peony let me stop for a moment and think where I left off last oh now I remember Billy Bunny was in the old woodchuck hollow stump and it was raining oh my yes cats and dogs as they say in grown-ups stories so we'll say kittens and puppies well after a while the rain stopped and the little rabbit said goodbye and hopped away and pretty soon not very long a little bird began to sing down the shady forest trail over the hill and through the veil Billy Bunny hops along with a whistle and a song and if you have never heard a rabbit whistle like a bird you must ask each little rabbit if he has the whistling habit who's singing asked Billy Bunny and he took his silver policemen's whistle out of his knapsack and blew on it so hard that the little bird began to cry oh dear oh dear will you whistle my ear off and then of course the little rabbit stopped for he didn't want to hurt that little dear bird no sorry ma'am who are you he asked and the little bird replied I'm pee-wee the littlest bird in the whole friendly forest what do you look like said the little rabbit curiously gazing here and there and everywhere and behind a tree and under a stone I've never seen a pee-wee and then that little bird flew down from a tree and Billy Bunny saw the tiniest little bird he had ever seen why it wasn't much larger than a butterfly goodness but you're small said Billy Bunny are you so small that you don't like lollipops of course the little bird said no and so would you no matter how small you were but when she tried to fly away with the lollipop she couldn't no sorry ma'am wasn't that too bad so the little rabbit gave her some sweet cracker crumbs instead and after that he hopped away looking for another adventure and it wasn't long before he had one for just as he was hopping across a fallen log that made a narrow bridge over a brook a little fish swam up to the top of the water and said here's a letter from your friend the whale and he held up in his mouth a blue envelope I guess it was made of some kind of waterproof paper for it wasn't the least bit damp and when Billy Bunny opened it he found a small coral ring inside and in the letter it said this ring is for you Billy Bunny the pretty mermaid asked me to send it to you so here it is please tell little fish that you have received it and that it fits you perfectly and then the whale signed himself your great big hearted friend the whale end of chapter 37 chapter 38 of Billy Bunny and Uncle Bolfrog this is a LibriVox recording all LibriVox recordings are in the public domain for more information or to volunteer please visit LibriVox.org recording by Larry Wilson Billy Bunny and Uncle Bolfrog by David Corey Billy Bunny and Old Mother Magpie Uncle Bolfrog sings a song that is never very long all he says is chunker chunk and he splashes in Kerplunk and the little fishes swim oh so fast away from him if they didn't don't you think he would eat him in a wink now who do you suppose was singing this song why a little tadpole named Tattie Legs and it made Uncle Bolfrog quite cross for he didn't like tadpoles anyway and Tattie Legs wasn't very polite as you can see now swim away said the old gentleman frog and he looked angrily at Tattie Legs now swim away or I'll swallow you and maybe your cousin and your aunt if they're around so the little tadpole swam away and after a while Old Uncle Bolfrog saw Billy Bunny not very far away he was talking to Mrs. Cow about the clover patch you see Mrs. Cow was very fond of clover and so was the little rabbit and he knew that Mrs. Cow could eat maybe 347 times as much clover as he could and so he was afraid she might eat up the whole patch and leave nothing for anybody else please don't eat all the clover tops mother wants to preserve some for the winter don't you worry replied Mrs. Cow as she whisked a big forcefly off her side with her long tail don't you worry and don't you fret there'll be some clover blossoms yet so the little rabbit felt ever so much better and hopped away and by and by came across Old Mother Magpie and he wasn't a bit pleased or she was always finding fault with him and everybody else for that matter yes Old Mother Magpie made lots of trouble and Billy Bunny had never liked her but he couldn't get away without her seeing him although he tried his best good morning Billy Bunny said the old lady Magpie and she raised her bonnet so she could see him better for the brim was half over her left eye good morning replied the little rabbit I'm sorry but I'm in a dreadful hurry and he hopped away so fast that he left his shadow a mile behind him gracious me exclaimed Old Mother Magpie that Bunny doesn't like me very much I guess yes you don't have to guess again cried a voice and parson crow cod and hod and this made the old lady magpie so angry that she flew away to tell Barney Owl that she was a very much abused person but here we are at the end of this book and so we shall have to jump to the next which I will call Billy Bunny and Uncle Lucky Left Hindfoot end of chapter 38 end of Billy Bunny and Uncle Bullfrog by David Corey


Hi, everyone. Thank you for joining today's by itself stock. So first of all, I'd like to thank the chance to come back initiative for finding all NFCO events. And as always, the talk will be recorded and shared on our YouTube platform and shared on Slack as well. So if you're not able to catch all of it now, you can catch it up later in those spaces. And today we're glad to have Phil, who is up information at Sylap Lab in Sweden, and also the author of MultiQC who will be presenting on troubleshooting fill by plane NFCO by plane. And it's going to be roughly a 15 minute talk and then we'll have more of a Q&A session and discussion at the end. So feel free to use the chat box or unmute yourself and post any question or comment at the end. Over to you Phil. Thank you very much. Thanks for the introduction. It's nice to be back, giving another size talk. It's been a few months since I've done one. And quite a nice topic today, I think. I'm hoping that this will be quite a good resource for especially new people to NFCore who are just trying to pick up running next to running and NFCore pipelines and might be running into trouble. The idea today is to just run through some of the common questions and queries that we see on Slack and people will try and run pipelines and hit difficulties and kind of walk you through my personal typical kind of steps of what I do when something goes wrong. I'd like to point out that this talk is aimed at kind of end users, so people running pipelines. I'm not going to go into kind of originally the title was debugging a failed pipeline but it's not really debugging. I'm not going to go into how to look. I'm not going to go into the code of the pipelines themselves. I think that would be a good to follow on talk. And also like I say, like many of these talks really is kind of this is my personal take on it. I'm looking forward to hearing what everyone says in in the chat in the discussion afterwards like think about what kind of things you do if you're a bit more experienced and if you have any suggestions. And hopefully that part of this today's talk will be as good as my slides. Right, so I'll kick off. Let's see if I can get some working. Yes, because at some point things will go wrong.  And so here this is kind of your your lifelines to take a step back take a deep breath try not to send your keyboard through your computer monitor and and we'll walk you through how to how to get things up and running again. I've broken the talk up into five sections is the kind of steps I take. And so the simple one is start small, start simple start small. And we kind of say this over and over again but it is never you can't repeat it too many times really. We use this minus profile test, we use that for all of our automated testing and basically that should always work pretty much. So, if you are starting to use next low or you're running a new pipeline for the first time is always a good idea to run this first with a profile test, keep everything as small and minimal as possible and check but it works, because it should work because it should be passing on the automated tests. And so if it doesn't then it means there's something wrong at your end basically with the way you're running next flow with the config with something that's outside of the pipeline itself. And that translates where the problem is coming from which is what this is all about. So start small start don't use up some massive data set that's going to take days just checking that the pipeline runs as you expect with a minimal test data set. And also if you've hit a problem just check the basics. You don't have to go far in the slack history to see that lots and lots of people's problems have been resolved by updating next low. They come out fairly frequently. And within NF call we tend to use many of the latest features of next way. Many of the nice features features of next flow come as a result of us requesting them so it's not really a surprise. So, the first thing I always do if something goes wrong is I just check that I'm running the latest next low stable release. If you're running the latest edge version and that's also interesting and maybe try with the stable version and because that could be important for the pipeline developers to know. Then there's all the other like really simple stuff like have you got enough disk space like pipelines will fail in weird and unpredictable ways if you run out of this space. If you're using Docker, do you have a Docker demon running in the background. Did you remember to start it. Just kind of run through these basic things and often that will that will get you up and running. And wherever we see common things coming up within NF call we try and add it to the website on the troubleshooting documentation page. So if you haven't already just have a scan through that and see if see if what's happening to you as mentioned there. Okay, most people will do that stuff without really thinking about it but next just to categorize what kind of error it is that you're seeing. So, just because next flow fails on a certain step of a pipe pipeline doesn't necessarily mean that it was that step that it was that software tool which was responsible for the failure. Different types of failures happen at different times in the execution pipeline. So we're going to we're going to go through that now. Errors can happen basically before the first process kicks off so right when you first run next play. They could happen during that first process so when it next to tries to run run something it fails. It could happen somewhere somewhere else during the run and something wrong at the very end. So these are kind of different steps and one of the most common is before the first process so you try and run next flow and it just kills that is immediately. All of these examples, and I have mostly taken either from myself or from searching the slack history so apologies in advance if you see one of your queries on slack coming up as an example I'm not picking on anyone.  So, so here this is a very obvious one. Unknown config attribute project there. So next flow is found something in a conflict which it doesn't recognize. And the reason is that this particular attributes is only available in more recent versions of the next way. You can see at the top that this is running 0.27.3 which is years old now. So not very surprising. So next flow is an up to date using your version, you should work. This is very obvious this happens right away you've only got a couple of lines of output here. But it's not always that obvious you could be running the RNA pipeline like here, you get tons of output all looks good it's nice and colored everything's fancy but you got a kind of really obscure error spat out, but just take a step back, go back up to the top. This version is not very out of date but a little bit out of date. And that's enough in this case to make the pipeline fail. So next version always check that first. And remember, if you're new to next one and of course, you need to tell next flow how to handle software dependencies out of the box if you just run a pipeline without any arguments. Next we will expect all of that software to be installed on your machine which is almost certainly not going to be happening. So you need to tell it, I want to use condor I want to use Docker I want to use singularity, or as about eight different types of kind of engines, which we can use to handle software dependencies automatically for you, but you need to tell next which one to use. And typically we do this with a config profile so here I've got test common Docker, I'm saying run the test profile and use Docker to do it. And of course you might want to use a different tool here or you might have your own config, which defines the which software tool to use here. So it might be the name of your institutional config here or something. But you don't have any spaces. If you have a space there, then it will just run profile tests and ignore the Docker, and your pipeline won't have any software to use. So, small thing catches a lot of people out including myself I've done it lots of times. Okay, so what very often you'll get when you something goes wrong, especially if the pipeline fails within the first process or within the actual execution of a pipeline is a lot of output. And this can be quite intimidating. Next flow really tries to help you with with figuring out what's gone wrong. And to do that it tells you everything it possibly knows about the step that was going on when it failed. And this isn't all of it here. But let's try and kind of take a pause and try and work through it and once you get used to looking at these kinds of areas and break down the different sections that they're quite quick to skim through and what we're really going for here is always finding the relevant part of the log which bit is telling me what's wrong. Here you can see the bit that pops out to me when I see this is command not found. This was a step in a pipeline the first step. But it's, and it looks like maybe it's something that was wrong with our Sam here from your pipeline. But when you look at this I say command not founds this is almost certainly a software packaging problem. So this has been run without Docker. Next flow doesn't know where to find the tool that's trying to run. And so it exits with an error saying the command is not found. Add minus profile Docker or something similar. And this will fix itself. Other kind of typical ones within this first process could be something to do with actually submitting the job to your computer environment. So here I'm trying to, or someone was trying to submit a job to a SLAM HPC cluster using S batch. And here it said the area is the top course by fail to submit process to grid to schedule if execution. So there's an S batch error. And in fact, so you can see under the command output actually tells you what was wrong. So again, this is not a problem to do with the pipeline. This is a problem to do with your config. Okay. So I kind of touched on this already but let's break down that log and try and get used to what it's telling us because there's a lot of text to look at here. The structure is always the same. So we have at the top information about where you were in a pipeline and what kind of error there was. So the top line says, okay, this is the process every pipeline is built up by lots of different processes that run in order. This is the name of the process that went wrong and in brackets you've got the tag which in this case is the name of the file where it broke. And it says caused by and that's kind of a summary headline of what went wrong. So here next flow was expecting some output and it didn't get it. So it's expecting a zip file and it wasn't wasn't generated. And then it says, okay, this is what I was running. This is the exact actual bash command, which to be honest for NFCorn for us is rarely interesting. Most of the time you can sort of trust this but that's like the resolved command that was run. And then you've got the exit status which is the status that was generated by the command when it finished. Usually not on zero. It means error and zero means success but in this case, we got zero even though it was an error. Next up in the log we have the actual output from that tool. So command line tools can generate two types of output in a terminal, you can have standard out and standard error. But for the purposes of this talk basically one and the same thing. So this is just telling us so two different types of output that we got from from fast QC in this point. So there wasn't anything on the command that standard out, but the standard error gives us a big blob of text. And if you run fast QC yourself manually, in a terminal if you run fast QC, this is what would be printed out basically. Okay, so there's a bit of a misleading, like red herring at the top that warning message is actually not related to the error in this case. And for bit, if you keep reading, it looks interesting as here. Okay fast QC is telling us what went wrong. It's just kind of buried. It's saying your file is probably truncated. So this error is almost certainly due to a corrupted file that downloaded didn't finish. This again is very common. And you just kind of need to work your way through the log file and the output to figure this out and try and spot that little nugget of interesting information in here. This is another example. This is running some tools. And again, same thing. Here it is buried in there some tools sorts truncated file. These are all examples I pulled out of slack. If, if you need to dig into this a bit more though, you can you don't have to look this is just the main output from next low running in the terminal when you run the pipeline. But you can start to dig into this specific process a bit more. And that's where the next bit of log is useful. Here it tells you where that process was running. So, every process generates multiple tasks each task runs in a work directory and an isolated file system. And so here this is the path to that work directory and we can go in there and we can start to dig around in those files and see if we can spot anything that wasn't immediately obvious in in the summary log output we have here. So what's the what's in a typical work directory and that's me the work directory. You have over the input files and any output files that were generated by the task, but you'll normally have a core set of files which next flow itself generates. You have a bunch of files which just capture the output from the tool. So I've mentioned this already that you've got standard out and standard error and you have a file for each. And then command log captures both into one file, which might be useful if you want to know what order different stuff came out in. So I have files which next flow uses to to kind of track and run the job itself. The exit code file just captures about zero or non zero value. I've got the trace you've got the command dot begin which to be honest I'm not sure I've ever looked at. And then what's usually the stuff that's most interesting after the output from at all is the command run and command dot sh. The final one is the bash script and that's just the resolved command which is run, and you can try running that yourself on on on the command line if but that won't use any of the software stuff like Docker and things. The command run is what next load itself actually launches and that will use Docker and everything and that should give you an identical error message. So it's useful to look at if you're using s batch or, you know, an HPC job scheduler, because at the top of that file you'll have the requests that were actually given to the cluster. So if your if your cluster is rejecting your jobs because of weird memory or CPU requirements you can check in a look at the headers and then manually debug that. Okay, you've looked through all this stuff you, you still don't really know what's going on. Maybe you found a little nugget of text which you think is the smoking gun. You don't really understand what it means. Now is the time to kind of start searching and the first place I always start is slack and of course slack. And we've been using it for a few years we have two and a half thousand users. There are, I don't know how many 10s or hundreds of thousands of messages in slack. There's a pretty decent chance that someone has come across this before and asked for help. So if you've, the key is to search for the right thing but once you've got that little nugget, stick that into the slack search bar and have a look. Many tools and errors will span multiple different pipelines, and you're probably not a member of every single pipeline channel. So it's really worth searching ever because maybe you hit the samtool sort error in. I don't know, I don't know seek and maybe someone is hit the same thing in the site pipeline. So searching all the slack is really, really powerful. And then of course there's also Google and you can ask finally ask for help. So this is just a few screenshots here you can see that that truncated file error if I stick that into into NF course slack. You can see there's this stuff, people talking about it and I don't know seek and Sarah in viral So having a dig through that might be helpful. And of course, search and Google once you have the correct bit of text is obviously helpful. Okay, you're still stuck. Now it's time to ask for help. There's good ways and bad ways to do this so what I'm going to take you through is the kind of like what I as someone responding to help request is kind of what makes my life easy, which gives you the best chance of getting a quick and useful Firstly, if you can pick the correct slack channel to post in we have lots of slack channels. If your pipeline is specific to if your question is specific to a given pipeline please ask in the channel for that pipeline, because the people in there will know the most about that pipeline. If you think it's to do with the config posting configs and so on and so on. If in doubt, you can always post in a help or and someone will either answer you there or redirect you provide straight away as much information as you can. This is really important and more experienced people tend to be used to this but especially if you're new to the community or new to buy informatics, you can kind of post the bit that you think might be wrong, but really out of context it's almost impossible to help. So as a minimum, usually we'll need the full command that you use to launch a pipeline and any next flow conflicts you use, because that ties together to tell us what environment your era came from. Sometimes this can be quite a lot of output. And so if in doubt post a short question or summary and then you can create a thread and slack and then you can kind of dump these outputs into there and it doesn't float and flood the whole slack channel. Use markdown code blocks don't just paste in your text from the terminal, because then you want to use those triple markdown triple back ticks to do a markdown code block. This is just purely code formatting, but it makes it much easier to read your message for anyone reading slack very easy to do once you're used to it. And try to narrow down the issue as much as possible before you ask so go through these steps we've talked to and come up with the best kind of question as you can, and tell other people how they can get reproduced error, because that's how bug fixing works. The first thing I do if I have an error reported to me which I think comes from a pipeline, so I go and see if I can get the same error. And once I can then I can work on it and dig into it and make sure I fixed it. But if I can't reproduce the error on my end is very, very difficult to actually fix anything. These are some of the things if you if you fall foul of these requests you might start to see these things come up. And these are things where we've written the same thing a lot of time so now, now we have little helpers within slack and so every now and then I'll type more info, and you'll get a little slack bot message which says basically what I've just been saying, please tell us a bit more about how you run next please don't feel offended if you get this, I send it to everyone. It's just a little reminder like we're probably going to need more information to be able to help you. I'm also about posting in the correct channel. And if you, if you don't format your code blocks nicely then there's a risk that me or someone else might ask for for for kind of better formatted ones in the future. I'm not really complaining it's just trying to help you out saying, I don't know how to do this. Here are a couple of help pages.  Now is the time to move away from slack and actually make an issue on the pipeline repository on GitHub. And this is where we track kind of problems feature requests and bug reports, so they don't get lost because it's quite easy to lose things in the slack and, you know, they just kind of disappear out of sight when you're a maintainer and you forget about it. If you make an issue on the repository it's there and it keeps all about discussion together. So please do hit bug report, get started and it gives you a template to fill in to provide all the information that we typically need to be able to help. So title description and your terminal output all the same stuff I've been hammering on about. And same stuff really give all the information that we're asking for, try and narrow it down as much as possible and tell us how we can reproduce to error. If you think you know the solution don't be shy, you know, say I think it's this bit here and if you think you know how to fix that problem even better, just make a poor request or make an issue followed by a poor request and then just submit that fix yourself because that's the quickest way. And of course that really helps to relieve the burden on maintainers as much as possible, and that's that's the way that most of us who write code within and of course kind of got into the community. So we're very open to poor request always. Right, this is meant to be a short talk and I've already gone over so I'm going to wrap up at this point. And let's see if anyone has any any questions or any suggestions or thoughts about how how they do this and and and any any cool ideas basically. Thanks for listening. Yeah, feel free to ask comment anything in the chat box in the form and meet yourself. I'm how she says you can provide mix logs along with command and configs and also error traces. Yeah, what I was just talking about there is I mentioned kind of what's printed to your terminal. And that's a really good start and that's very much easier to read. Next load also generates a log file called next load log so it's the hidden file. And that's like the verbose version of that log. And that is massive and fairly difficult to dig through but that has all the information. So if you can drop that file into Slack that really helps to debug. I don't know if this anyone has another question or James is saying that file that I mentioned dot next load log that's generated where you launch next way. So in the launch directory. I'm not saying you can prefix a version of next way to your command. So if you want to run your pipeline with a specific version of next flow, you don't have to go and download assuming you're running somewhere with an internet connection. You can go and download a new binary or reinstall next or anything. You can just prefix the environment variable and X F underscore VR next version equals whatever version you want. And then carry on with your normal next play run command and next flow itself will automatically fetch that version of next way and run with it. So if you want to check that whether it's a problem to do with the version of next way running. It's quick to do that once you do with that technique.  No, put it before the command. If you prefer you can also do it's just a regular bash environment variable. So you can do export and X F or wherever you want and then that will stick around for the whole of your terminal session. So if you just wanted it for a single next play run, you can just prep prepend it before the start of your next play run, whatever, and it will be used there. I'm not sure if next so carries on using that version afterwards or not. You might need to run next flow self update again afterwards if you've gone back. Thanks. Looks like there's no one else with a comment or a question. Thanks guys, and we'll see you next week for another by system. Thanks very much.


Minin is a whole new ballgame. The rocks don't grow back like the trees do. It's displacement and dislocation from your area. Por ejemplo, cuando vamos al dentista y nos extrae una muela, no estamos diciendo yo produje una muela. Me extrajero una muela que jamás en la vida va a volver a salir. It's displacement of our communities. Destruction of our sacred lands. And there's insufficient food supply and as well as water. There are also psychological stress, especially in indigenous women. Que toda esa destrucción que se está generando a la madre naturaleza, las consecuencias lo vivimos todos porque cuando debe de llover hay mucho sol y cuando hay mucho sol hay frío entonces el clima ha cambiado totalmente. Whatever project it is, if it's a mine or a forestry, is it going to help us become a stronger nation? If a mine was going to come into our area, to be able to look at where we were as a community and a nation when our language was intact and our culture connected to the land, to where we are now after colonization and then to ask the question of where we want to be in the future, is this project going to help you get there? Hemos buscado nuestras raíces, hemos fortalecido nuestra fuerza como pueblos originarios, hemos ido discutiendo y creado nuevos conceptos para definir un modelo de vida, una economía para la vida porque es mentira que los que no queremos minería o no queremos megaproyecto en nuestros territorios es que estamos contra el desarrollo, sino que simplemente tenemos otra visión de lo que es la economía para las comunidades, mayas, garifonas y shinkas en Guatemala. These women are really living the principles of the rights that are enshrined in the UN Declaration on the Rights of Indigenous Peoples. They are living free, prior and informed consent by working with their communities to help them understand the implications of resource extraction and to make informed decisions. And they're trying to have those decisions heard and respected as they should given the UN Declaration commitments. And so women are at the forefront of those struggles.  We as indigenous peoples of the world hold the key to the continuation of life on this planet. I just feel empowered. I feel that when women joined our hands together for our beloved mother, the earth, that she will be our greatest ally.


Hi, my name is Tracy Takahama Espinoza and this is a video on developing brains and helping kids make good decisions in life The focus here is really to look at that new information about the developing brain We know a lot more about what happens during gestation to before the kid is even born what happens in early life experiences and all of these different things that Contribute to the ability to make good decisions and we also know a whole lot about what's going on when kids Don't make good decisions. We all have experienced that We know what's like when crazy teenager jumps in a car after drinking and and that's the end of it And so these bad decisions, where do they come from? And so we know there's a lot of roots in habituating behavior over time So we want to go through that we also wanted to spell a lot of the crazy myths that are out there about how Brains develop so we want to get some clarity there about you know, you're born with perfectly functioning frontal lobes Okay, what's missing are those? rehearsals of neural networks related to good decision-making and to choice and so we'll talk about How that works and what it is that we can do as teachers to contribute to that, okay? So how can we help kids practice better decision-making mechanisms so that they don't have These terrible outcomes that might result if they don't do that and so as we go through a handful of these big ideas I really love it if you could Chat down anything that might be new or interesting to you and let me know so that when we focus on The day when we meet we can actually go deeper into those particular concepts So here's some big ideas to frame this discussion Your brain adapts to what it does most So we're gonna sort of pull that apart when we're together, but basically Habituation plays a huge role in decision-making so how you get used to making decisions makes an impact So we're gonna talk about how early choices about how to make good decisions is really important We're also going to talk about this big idea that all new learning passes through the filter of prior experience So everything new that you're gonna do has been in is going to be influenced by all the things that have already happened to you So let's just say you have this amazing fourth grade math teacher who is just gonna you know rock your world But you just had such a lousy experience in third grade That you're terrified and so you can't help but associate your interaction with that teacher with your past And so we're gonna talk about how teachers can help kids You know sort of come to grips with their past and also leverage what they already know But not be hostage to some of those Pre-conceived ideas about situations. It's also important to understand that what you know Influences what you can know This is why we say the more things that you know The greater amount of things you can learn in the future because this is basically neural plasticity, right? The more connections you've made the more potential connections you can make in the future So we're gonna explain why that's you know physically what's going on in your brain But also what that means conceptually in classes and how giving kids rich and varied experiences and multiple Visions of the same idea and concept is really fantastic for their future learning as well And also this idea that what you know changes How you know Something new and so this has to do with your own life And as it goes on and so how you actually approach things today might be different from what you do Next month or in five years or in ten years and so There's a constant dynamic change that occurs we call this neuro constructivism so your brain is sort of continually building itself, but it's always Changing slightly every single experience is sort of changing these neural networks So we'll talk a little bit about how that impacts our craft And this art of teaching that we have and then we're going to leave with this really big idea about We don't say nature versus nurture anymore. We basically say Nature, you know, you're born with your genes Via nurture you're definitely influenced by the experiences you have in the world including things that happen in school But there's this huge piece that has come out of resiliency studies that tells us that you also have free will You get to choose So you get to decide a lot of things It might be in your nature You have a tendency to have a short fuse and a bad temper temper and you have a bully in the class So nature and nurture have combined to sort of set you up for for free fall here But the really cool thing is you get to decide how you're going to react to that situation You can tell a kid, you know, I know you're angry labeling it right because Tommy took your ball from you Okay cause and effect We label it, but then we also allow them to understand. I can understand You know that emotion inside of you. I can I can sense that you're angry. Okay now What are you gonna do about it? So your feelings are not the same as your emotions, which is kind of crazy right emotions are of the body It's the chemicals that get released and the feeling is your decision about what to do about that So we're going to talk a little bit about how to help kids understand that and that they are in more control And they think they are we're gonna base a lot of this information on a study That looks at adolescence from being from eight years old all the way to 24 crazy, right? But it's a longer-term study that's being undertaken at undertaken right now It's just adolescent brain and cognitive development study and with the goal of trying to understand What tips kids what makes some kids fall into the decision of taking drugs and others not What tips kids and they're hanging with the wrong crowd to quote unquote what tips kids Towards good or bad behaviors and so looking at this over time What kinds of influences have heavier weight than others and so I'll be sharing some of that information with you We'll also talk about a lot of these myths around adolescence. I'm you know can't learn anything past adolescence It's kind of like all downhill from there. No We'll get rid of those myths and we'll talk about why As we said before all new learning passes through the filter prior experience Well, the older you are the more experiences you have the more things are gonna pass through that filter there, right? So you can always learn and you can actually learn more efficiently But we have to help kids get away from that idea that they're limited by that So we'll look at choices every day decisions So you know what people either who they hang out with or when they do their homework And we're gonna look at this in the context of understanding how your brain It takes a lot of energy to do stuff And so your brain is always trying to conserve energy and so how does it save energy by just sort of doing the easiest thing? So we'll talk about how to get around that Look at different types of Decision-making processes that your brain goes through at a metacognitive little level And then we're going to talk about some real big tools that you can integrate into your classroom that would help kids Make small decisions so they are better off making those bigger decisions So if you have ideas or thoughts about this before we meet Please send me an email so that I can make sure that I incorporate them into our session when we meet together And looking forward to it. Thanks


Hey man, just where it hasn't settled in that you're not going to play off now and things you wanted to play for now you're playing for pride here against going down to this last one. Yeah, it's always disappointing when you don't have the opportunity to get into the playoffs and keep going, you know, but we still have one more opportunity to go out there and try and play as well as we can against a division opponent, good rival, who's playing for a lot too. So it's gonna be a good challenge for us, but it certainly stings, it's disappointing. You work so hard all year to try and give yourself a chance to play and when it's, you know, it doesn't shake out you're disappointed with it, but still things to improve on, ways to get better and things to build on for the future.  I think, you know, one of the things I think we did a good job of all year was just trying to win with the guys that we had and finding a way to, you know, create problems for defense every week and, you know, I expect that that's gonna be the same moving forward, you know, Art's gonna do the best he can with the guys that we have and obviously personnel always changes, you know, that's that's part of this league, but you know, I anticipate him doing a great job of trying to find ways to win with the players that we have and being multiple, giving lots of different looks, making it hard for defense to kind of pin in on one certain thing. And how, I know you're not the GM, but how would you feel getting Corridor Real back?  Thank you. You've been, you've worked with lots of different play callers and head coaches and what has this experience been like this season with Art in like learning his scheme and kind of being a leader for his offense and for his team? I've enjoyed it, you know, I really have. I've enjoyed learning, you know, some new things, some different things than what I've done, you know, previous points in my career. You know, I've enjoyed, you know, everybody's got a different flavor, a different perspective and, you know, trying to get on the same page as quickly as possible with people is important. I think, you know, Art and I have done a good job of that this year, but as far as, you know, my take on it, I've really enjoyed, you know, playing for him and, you know, I think he's done a really good job of trying to create the environment, the culture that he wants to build on and, you know, I think there's a good foundation there for us. The game on Sunday impacts the next season at all and impacts the mindset whether it be how the coaches are supposed to speak, how players are supposed to speak, or is that too far away in terms of next season? I mean, the momentum part of it, I don't think that necessarily carries over, but, you know, you just, you have to continue to work and grow and build.  There's another, you know, tool in their toolbox to use as you move forward.  Every time he plays, he's learning so much. Same thing for our young guys up front, Jaylen Mayfield, Matt Hennessey, you know, those guys, games are invaluable for them and those reps are invaluable. And I think it certainly helps, you know, individual players as they move forward in their career. Every time you suit up and you get a chance to play, it's a learning experience. Do you have any plans at all to, I mean, just kind of looking forward but working with those guys in the offseason at all? We'll get there, you know, after this week. You know, I think right now, the focus is still on having a really good Wednesday and making sure that, you know, the part of the game plan that we're installing today, we're locked in on. But as far as the other stuff, I can wait until, you know, we're finished. When you take the playoffs kind of out of the motivation for some guys, do you want to kind of identify who's still working hard this week? Who isn't? Is this one of those moments where you can see whether guys are going to stay with it or maybe take their foot off the gas? I think for certain teams, yeah. You would find that out. I don't think we're going to have that issue in our locker room. We got guys that, you know, come into work every day and have been consistent about that from the start. Yeah, but, you know, sometimes that's human nature, but I don't think we've got those guys in our locker room. You guys had some turnover on your line to start the season this year. The sacks are down a little bit from the last couple of years, but you, the Falcons have given up the most quarterback hits. How would you grade the protection that you've had this season? Do you see signs of progress that encourage you for next year?  But I do think our guys up front have gotten better, have improved. We've gone against some really good friends, you know, all year. And they've, they've had really good challenges weekend and week out. And, you know, I do think that there's been growth there. And I'm excited about, you know, what those guys are going to do for us moving forward. We mentioned the environment and culture that Arthur's trying to build. How would you describe that?  And I think we've done that, you know, throughout the year.  And, and, you know, I think that's really the baseline for it. And then, you know, obviously adding different guys that fit that mold is going to be important for us as we move forward. I want to go back to what you were talking about, where you said that you feel like as a team that you've done a good job of trying to win with the guys that you've had. And I'm maybe thinking too much about this, but like in a year one scenario where you're installing a new, new offense, does it almost make it difficult to find an identity into evolve as an offense, kind of as you're dealing with that? Or do you feel as though that there has been evolution, even with that being the case? I think there's definitely been evolution, you know, of some of the things we might have started thinking we were going to do in OTAs or training camp, you know, you evolve, you shift to the guys that you have. And the year, every year is like this, you know, you start with the group of guys and then for whatever reason, there's injuries or whatever, you have to adjust and you've got to find ways to allow the guys that are in your building to be at their best. And everybody's skillsets different, you know, what everybody can do is different. And so I don't think it's been any more difficult because it's year one in the system. I think artists done a great job of, of, you know, teaching and given the guys the reasons why what we're trying to do, what, you know, what we're trying to expose, those kind of things. I think he's done an excellent job of that. I think, you know, you just look at some of the players, right? Some of the guys that are impacting you look at the growth and development of like Kyle Pitts, you know, unknowns of CP, Mike Davis, those guys not really knowing, you know, you have an anticipation of what they might do, but they've turned into, you know, who they've been this year. And certainly upfront to, you know, I think growth and improvement for Jalen Mayfield, Matt Hennessy, Chris Lindstrom, you know, both are tackle those guys, you know, playing together in the same run scheme. I thought we started to run the ball pretty well, pretty effectively later in the year. I think that was growth. So I do think we're a different football team than we were at the beginning.  I think you feel that, you know, and I think he's done a really good job of that. I think we've had to navigate some different things throughout the year that have come up and keeping guys together and keeping guys focused. I think he's done an excellent job of that.  I mean, it's they're all different, you know, every every year brings its unique set of challenges and opportunities. So they're all different. I don't know as though it's more difficult than any other year. You know, I think I think one of the thing everybody, you know, has learned is to be more flexible, you know, in the last two years of understanding that, you know, it's not always going to be smooth sailing. So I thought thought from that standpoint, we did a good job. That that wasn't really much of a challenge. You adjust, you adapt, you try and do the best you can with the circumstances that you're given. And our organization did a great job of trying to navigate that. I think he's he's worked hard. Just, you know, command of the system, you know, you see him in practice, calling plays, getting in and out of the huddle, understanding what we're trying to do, being way more comfortable in terms of his progressions, the timing, those kind of things. I do think he's he's gotten better through the year with that. I think anytime you're on the field, right, that just that comfort level of being on the field, being out there playing, he's got he's got a unique skill set in that, you know, he's got the ability to do some of those other things, which help us, you know, as a team, played special teams for us did a nice job with that. So I think just the comfort level of being out on the field, playing those games. I think that's stuff that can help him. The Saints came Jordan, it looks like Davenport's playing, getting his feet under him in the NFL.  I guess it didn't like not here with 7.5 in the last three games. Yeah, they do a great job. They've got good players, you know, good players up front.  And, you know, I've always had a lot of respect for for their defense and how they operate. March on kind of the back, kind of tied together for them. Yeah, I think, you know, tomorrow, Davis is one of those guys that he's an energy setter for them.  You know, always always been a tough player to go against. We've seen we've seen Kyle Pitts do some crazy things, but just in terms of the basics of being quarterback friendly, then being on time, how is he doing with those types of things that fans may not know? He's getting better, you know, every day. And I give him credit. He's worked really hard all year. It's not an easy year. That first year, you know, after he finished a college, you get ready for the draft. It's just nonstop. And I've been impressed with him of his capacity for work, you know, the capacity to push through some of the boredom, you know, the grind of the day to day, you know, he's done a really good job of that. And I think, honestly, I think his practices last four or five weeks have been some of the best of the year, which is impressive. But it helps those little things. It helps the details, you know, when you can work like that. And he's done a good job of that. All right, thank you. Appreciate it.


Do you like basketball? Do you like plants? Or you can have both with the basketball plant pot. Here's the result. Let's shoot some seeds.


Welcome back to my channel guys. It's your girl Coco styles and on this channel. We talk about beauty fashion lifestyle and styling guys so today I wanted to just come to you guys with a few brands that I absolutely love when it comes to buying either leather blazers or Leather jackets or like trench coats and the reason why I wanted to do this is because my tall ladies I know the struggle is real and It's hard even now finding good quality leather stuff. Everything is literally faux leather And all faux leather is not created equally. So let's just jump right into it And my first brand is Lamarck. You guys know Lamarck has been my go-to for the past few months and They just have amazing leather blazers I really love the styles of their blazers as a six foot tall woman having an oversized jacket blazer That's lamb skin leather Fit me the way it does. I absolutely love it now. I typically get The large I do have a medium one. They're both fine. I can do either or I am able to wear like a hoodie or something under the medium. So that just gives you an idea of How they actually run I want maybe two three I think there's two more that I want from them and then I'll be good to go like completely good when it comes to like Blazers one is like a nice green and the other one is like a camoish color but They're classic I love them. I would 100 recommend that brand if you're not into oversized definitely size down They are not a tailored fit. So they are more of a boxy stuff, but they're really really nice blazers The other brand is the Frankie shop So you guys know the Frankie shop has leather stuff that's really pricey than they have full of the stuff Um, and they have trench coats Their trench coats are top tier guys great quality even their full leather stuff I have three full of the jackets from them Um, my two favorite are the two moto jackets. Those are Immaculate especially that white one that white one. Well, they're both really really nice the black one They're the same coat But for some reason I guess because the white one i'm able to really see like the The grain in it. It's just it's immaculate. Um, those are one size fit all I believe I believe that one size fit all But they fit really well They go great with jeans Skirts for those of you girls who like leggings you can definitely do it with some leggings sweatpants Shorts, um, however you want to style it. You can definitely style like that as long as you are comfortable with it But the Frankie shop is my second place remain Berger, I think it's called Berger remain Berger. It's a brand my what is this called like my peanut butter leather coat Perfect guys I tried looking for more with this like sold out or it's not the same exact style I 100 love the way that jacket feels and I caught that on sale on The outnet So you guys know the outnet is a site. It's almost like I don't want to say it's like farfetched But it's like they said last season stuff But to be quite honest you can find you some really really nice things on that site If you have the patience and the time to look for it. So designer things um non designer things well Brands that you may not have heard of are on there Immaculate brand. I love that brand There's if I can find, uh I don't even want to say a black version. They have like a blue version of my coat I would get it and in baby blue is not my color But I already have like a vision on how to style it and stuff But they definitely have really really nice leather jackets as well um And the other place is cost even though cost is like I guess cost is family with h&m um, but My leather coat that I got from them Guys. Oh, it's so nice. They have boots They have shoes with leather and they're a little they're about 300 for the shoes and stuff But you can read the description everything is 100 level. There's no upper man made none of that stuff Um, just like this jacket this trench coat Immaculate jacket it has no hardware, which is great for me because I'm able to actually Wear silver. I could wear gold. I can wear whatever color I want to and don't and won't be tied down to a specific Um finish on my jewelry. So definitely check out cost. They do have wool jackets too that are really nice So if you're looking for a wool jacket try their runway section. I think it's like runway something Those jackets are also really nice. They are oversized, but they do have like a snatched waist Um, but they're great guys when it comes to buying wool jackets. Make sure you're looking at the details Of the item You want something that is 100 wool That way it'll last you for a really really long time Otherwise, you're gonna have to replace it over and over and who wants to do that, right? And the last brand is helmet lane Okay, I have a bomb Moto jacket from helmet lane and you guys are probably like, oh you have like multiple moto jackets This one is more of a fitted style moto jacket And if I can find a photo with me with it on I'll plop it in But it's more of a fitted style and it has like a small little belt at the bottom very feminine And that one I usually wear it with like a dress under it More of a fitted dress, but the quality of that jacket is Top tier. So every brand that I just said Have great quality and you guys know I am here for the quality I'm not one to just keep buying stuff over and over I would like to keep my stuff for a few years before it starts to get crazy on me, right? Even longer than that Now the frinky shop faux leather Moto jackets, I'm gonna take care of them as best as I can because they are faux leather Um, I do like to keep them in their packets and stuff like that I'm gonna probably end up buying some more garment bags to get them in there With some cedar balls and all that good stuff just to keep them, you know in good condition the white one It's a really white jacket So my goal is to make sure that I don't get makeup on it. I don't get like hair dye on it Things like that. And if I wore it outside wipe it down put it back inside of it's wrapping And then I'm good. This way I can preserve it for as long as I can Even though it was cheaper than like my cost jacket I still paid money for it. So I'm gonna take care of it But those are brands that I actually would recommend to anybody tall women short women average size women petite women plus size women plus size um Frankie shop for plus size and La mark you can possibly wear those those um those blazers because they do They go up to a large, but it's pretty big. So it'll fit you rather like snug, but a nice snug Um and possibly let me see who else and remain you definitely can get remained now that helmet length Probably not this stuff is really fitted. I'm barely fitting into mine But it's very fitted but the rest of them you can definitely Um try some out for my plus size girls because we cannot leave you guys out either Um, yeah, so check those out. Let me know what you guys think if you do definitely Reach out or buy from those brands. I am here to listen to your stories guys Listen, I'm like I said, I'm big on buying things that are quality over quantity So you're not replacing them over and over. It's just not a good idea to just keep buying things And you guys know how I feel about trends trends are cool but listen If you really think about how much money you spend on buying trendy items Huh, and I know like some some people are influences and stuff like that but um It's a lot of money and you know influences get items sent to them and stuff like that Most of us buy this stuff for our wardrobe when I buy things I buy them because I either don't have it Um, or it's something that I really wanted. I don't have anything like it, right? So I have two black leather trench coats. They're they're black But they're completely different fits one is a hundred percent leather more of a classic style And the other one is more trendy and more oversized. It wasn't that much money, but you know, it's cool It's cool So again guys make sure you are checking out those brands. I highly recommend them um Especially lamar guys make sure you guys are checking out lamar. They got some nice places. Okay So if you like videos like this, please comment below Let me know if you want to know about some more brands that I really like to shop at Um, I just bought a really nice sweater from What brand is this? I forget the brand But I had it in my bucket guys and it so happened to go on sale This sweater it was in my bucket, but I was not going to buy it because it was way overpriced When I tell you that thing chopped down To like more than half off. I got it. So this is what I mean about smart shopping guys It doesn't mean that we have to go out and buy every single thing that we see But if something that we really want it went on sale, then yes, go get it But let me know if you want more videos about the brands that I like to shop Especially as a tall woman. Um, if they can fit me, they can definitely fit you guys So if you like videos like this, please comment below and if you stay to the end of this video Please comment coca we see you and guys don't forget to follow me on instagram at coco styles nyc and coco styles ny And guys, you know, I have that style blog coco styles nyc.com and then my style services coco styles ny.com You guys know your girl is on tiktok now So coco styles nyc and I will catch you guys in the next one. Bye guys


David Kohn was an eager nine-year-old when he first climbed to top a pitcher's mound and threw a baseball Even though we needed four fingers to grip the baseball and couldn't immediately throw strikes that experience changed his life He became a different person because he became a pitcher a forever pitcher Kohn has never stopped thinking like a pitcher and never stopped obsessing over pitching Which is why I wanted to collaborate on a book with him a Manic pitcher with bulging eyes and a vein-filled neck Kohn always looked like he was plotting much more zealously than the player standing in the batter's box I wanted to crawl inside his frenetic mind and find out what he was thinking and Describe how pitchers can sometimes feel dominant and in a span of a few pitches suddenly feel desperate That's what we did in full count the education of a pitcher our book that was released this week 42 different times. I pressed record and interviewed Kohn 42 times he delivered with a trove of riveting stories He described his relationship with catchers and how it must be like a dance Naming his favorite and not so favorite dance partners He explained how a forgettable game with the Mets during the 1988 NLCS Turned him into a tough pitcher He dissected every out of his perfect game and at times it felt like he dissected every pitch of his career Besides offering pitching lessons Kohn also revealed some memorable baseball stories He partied with Keith Hernandez and Daryl Strawberry and the Mets. He screamed at Jorge Pasada He was scolded by George Steinbrenner and later built up enough equity to tease the boss He once punched David Wells in the face in the clubhouse during a game Yes, during a game This is a pitching journey, but it's also a personal journey Kohn discusses his frailties and his foibles as much as he discusses his fastballs as Talented as David was while winning 194 games five World Series rings and a Cy Young Award He had fears as a pitcher Kohn wanted to have endless weapons Which is why he used so many pitches and so many different arm angles He fought with his dad his first and his best pitching coach and he squabbled with minor league coaches Because he had to do things his way All David ever wanted was to be a major league pitcher and he accomplished that and became one of the best pitchers of his generation But he did more than that He became a pitching genius Something that was reinforced to me across hours of interviews How much is Kohn immersed in the art of pitching he recently told me and I quote I love pitching when I die I'll be thinking about pitching That was as blunt and honest as a quotation as I have ever heard and that bluntness and that Honesty permeates full count the story of a nine-year-old who found pitching and never stopped loving it


avor of county council to further this question of clarification. I actually feel like it's his job to provide clarification to the commission on this matter. And I'm gonna, but I mean, I appreciate that you're willing to further it. And I'm gonna abstain from this matter. Commissioner Greenberg. Commissioner Greenberg. Aye. Commissioner Maxwell. Aye. Commissioner Nielsen. Aye. Commissioner Spelman. Aye. Here's that the motion passes six to zero to one with one abstention, which I'm not sure you can do, but fine by me. Okay. So is there any further discussion on, well, we're done with this item, I hope. So thank you all very much. I know it's a difficult item in a way I apologize because I'm the source of the discussion. And I really wouldn't have been pursuing it if I didn't feel it was an important, an important issue to try to get clarified given some of its implications. So I appreciate it. And I'm sure staff will report to us as once we know what the city council has done and if they're willing to ask the AG through the county will be kept informed. And I assume that during that time period, I will have to follow the current direction from the city attorney and staff. I just want to- Chair, before we end, I apologize for interrupting. I just wanted to note for the record for the last item, there were no members of the public present who wanted to speak. Oh, right. Sorry, I forgot about that. I got too caught up in the moment. All right, thank you. No problem, just the record. Thank you. Thanks for helping me follow-up, Sarah. I move to information items. Could we have a report from our director if there are any information items? Sure. So we did have the city council approve the second reading of the section eight updates to the inclusionary ordinance that the planning commission saw in October. So that'll be taking effect 30 days from December 8th. And then on your upcoming meeting on one seven, I believe the only item that we have is the objective standards item that was continued from your last meeting with respect to the test that you'll recall the consultant wasn't available for this meeting. So we pushed it out to meetings. And then on 121 at this point in time, we only have this inclusionary item scheduled. So there could be some late additions that we would be noticing in the next few days. But at this point it's objective standards on one seven and then inclusionary items that were continued from tonight on the 121 meeting agenda. Okay, thank you. Under subcommittee oral reports, my understanding is that the housing subcommittee has now ended. Is that correct? I'm seeing the chair shaking your head, yes. It is possible for the commission to reestablish it. And I would ask that that be put on the next agenda for consideration of reestablishing the housing subcommittee. Again, as we all know, there's still a significant number of housing related issues with and without considering the inclusionary ordinance itself that are worth going to need further discussion. So I don't think there should be any objection. I think there's no legal impediment to reestablish the committee. So why don't we just ask that that be a fashion item on our first meeting in January and we'll appoint a new subcommittee. Happy to add that to the agenda. The West Cliff technical advisory committee, technical advisory group, whatever it is, is grinding forward. And I don't know if you know, Mr. Butler, when we're actually gonna see some plan. I've forgotten what the schedule is, but I'm sure sometime in 2021, we're going to be responding to a particular plan. That's correct. We don't have exact dates yet. I would say as early as February, but likely sometime in March is when it would be coming to the planning commission. I should have raised this during the information items, but I understand the council has approved the Walkmaster plan and it's been submitted or it's going to be submitted to the coastal commission. And there's a public works plan that the staff is going to be providing for consideration by the coastal commission. Would it be appropriate for us to get a report on the progress on that public works plan and how it relates to the master plan itself? Since the city is not going to be asking for a coastal permit, but going for a public works plan. I think it might be helpful to the commission to understand what that means. So the public works plan is essentially a master coastal permit that allows for a number of projects to be implemented under it. The warfare is actually in the original permit jurisdiction of the coastal commission. So they actually consider and approve that public works plan or if a coastal permit were to move forward, then they would take that into consideration directly. So essentially the public works plan is kind of like, we've got enough detail on a number of projects that we're going to be doing over a course of time and they're more or less combined into one coastal permit. So that's my understanding of how that would work. I see our assistant director, Eric Marlatt is on the line. I don't know if he would have anything else to add in relation to that or in relation to the expectation for the next public works plan as it relates. I would just add one clarification. The work master plan itself is not going to the coastal commission. So they would see the public works plan that's my recollection and I know Eric's worked on some of these procedural issues. So do you have anything else to add on that, Eric? Nothing much to add. We can certainly let the commission know when that is submitted, that would be fine. But the public works plan is going to be based on the work master plan. That's correct. Yeah, that's correct. I guess one of my concerns has to do with the sequel and what was looked at in the EIR on a project level and what was looked at on a programmatic level and how that would be treated in the public works plan. I'm not, I'm supportive of it. I just think it's a complication that isn't really totally clear to me and I'd appreciate getting an update on how that's developed. Like to respond to your question, I will say that under the Coastal Act, the Coastal Commission review of something like a public works master plan is a functional equivalent of CEQA. I'm sure they're going to be considering the EIR that the city certified as part of that whole review, but there is no separate CEQA action that needs to happen per se when they take action. There's no separate CEQA action, but there very well could be additional technical analyses that they require in order to reach the conclusions related to environmental impact and any mitigation measures that are necessary. It's just interesting that it's actually outside of CEQA because, and so it doesn't have the standard CIR or MND. There, as Eric said, the Coastal Commission's review is a functional equivalent of CEQA. So it's just... Well, the certified regulatory program under CEQA and they and some other state agencies have it, but the substantive question is whether the public works, you know, the off master plan, the EIR said two of these projects are analyzed at a detailed level, the entrance, and I think it meets common eye and we don't need to do any more CQA analysis. For all these other projects, we'll have to do other analysis later, like the new buildings and et cetera. The question in my mind is, with the public works plan, does that still hold or is approval of the public works essentially can it go beyond what was considered and what was proposed in the off master plan in terms of the next steps as to the analysis? I'm not expecting an answer tonight, but I think it's just a confusing question to me. Yeah, I'll venture an answer and Eric, you correct me if I missed that here on any of it, but I would say that it can go beyond, but only to the extent that the additional analysis are provided that give the coastal commission a comfort level in understanding that all the issues have been analyzed and mitigated. So that's how I would expect that to proceed. Okay, well, I appreciate the commission taking the time to get that question answered. Are there any items to be referred to future agendas? Seeing none. I was just gonna say, I would add one point, which is, I think, part of your questioning was probably related to what's gonna be seen by the public and I would expect that there are gonna be public processes associated with that. The city is gonna be doing outreach, even if it is something that's going on elsewhere. If we're doing the sign, for example, we're gonna get public feedback. So I just wanted to make that clear for the commission and for members of the public who may be watching. It wouldn't just be like, oh yeah, we submit everything to the coastal commission and the city and the residents aren't aware of what it is. So plus, there may, under the city zoning ordinance, it might not need a coastal permit because you have the public works plan, but it might need a design permit. Yep. And that would need to go through and that would be discretionary. So that would need to, I think there's going to be, the public, the coastal commission is going to have the public well, but I think for the individual projects, it's very likely that there'll also be a process at the city that the various projects will have to go through, even if they were, even like the sign. Yep, you know, I wasn't trying to imply that that wasn't the intention. I'm just really trying to understand how the public works plan relates to the normal city process. Because as you say, they do use a different SQL approach. Okay, well thank you. Thank you all, have a very good holiday and I hope everybody stays healthy. Thank you all. Goodnight. Goodnight. Goodbye.


Hello everyone, my name is Sebastian Guesgen, I'm the co-founder of TriggerMesh and thanks for coming to my virtual KubeCon North America 2020 talk. The title is Serverless or Service Fool and here I am recording and I hope you're going to have a good time listening to this talk so let's go and let's get the party started. We've come a long way, we've come a long way since Kubernetes was started, you know, June, July 2014. It's been six years, a little bit over six years. So it's been a while and yes, we've come a long way. So Kubernetes was created and was donated to the Cloud Native Computing Foundation, CNCF, right? At the beginning, there was only one, it was great. And now the ecosystem has exploded, there are lots of things, lots of software, lots of companies that are part of CNCF and I'm not showing the landscape to criticize it. I'm actually extremely happy to see this because in six years an entire community has been created, additional software have been created and it's been really, really interesting and enjoyable. And over those six years, you know, I think there's been three main narratives that have fueled this development of this ecosystem. One big narrative has been containers versus VMs, right? We were busy doing VM orchestration, we were busy doing OpenStack cloud stack deployment and there's been the switch from OpenStack to Kubernetes. We started dealing with containers as an application package and definitely that's been a huge narrative. The other narrative has been, you know, saying, hey, you know, we shouldn't focus on the undifferentiating code, right? So we should only work on code that brings value to the business and we should delegate boring things, you know, boring quotes, right? But if it's not bringing direct value, it doesn't have direct, almost IP intellectual property, we shouldn't, you know, really focus on it. And the third narrative has been, hey, you know what, if we don't focus on undifferentiated code, we shouldn't focus on undifferentiated infrastructure as well, right?  So we've had those three narratives that have helped craft this new ecosystem, right? So what has happened, you know, because of those narratives. Now we live in this multi-cloud environment. And I'm not saying multi-cloud for marketing reasons and so on. It's just, yeah, it's just multi, it's very heterogeneous. So we have on-premises stuff. We've gone away from OpenStack, from basic VM infrastructure, and now we have container orchestrators based on Kubernetes. We have OpenShift, we have VMware Town Zoo, we have Rancher, all of that on-premises. Even though they can talk to the cloud, but anyway. So we have that on-premises. If we don't want to do this on-premises stuff, then we use a generic cloud like AWS, Google, Azure, a more original cloud like my buddies in Switzerland ExoScale, right? And we can manage our Kubernetes clusters on those generic clouds. But we also have very specialized, dedicated clouds.   You want to store your metrics somewhere, Data.org, Salesforce, Customers, right? So we have very dedicated clouds, SaaS offerings that have emerged. And all of this makes it a very multi-cloud environment, right? And there are very good reasons for this. Again, back to the on-differentiating quotes, bits, right? We want to run critical pieces on-premises. We want to keep that close to ourselves. But the on-differentiating components, we want to delegate that, right? So we run on-premises stuff that are critical. If we want, we delegate infrastructure management to the cloud. We use a managed service. And then we have those dedicated offerings because you know what? Who best to manage my Kafka cluster than Confluent, right? Well, nobody. So might as well use them, right? So there are very good reasons for this multi-cloud environment. It's not marketing, it's not nothing, right? So multi-cloud, almost naturally it happened with those narratives pushing us. And now we know I like to do a flashback to what's a cloud? What's a cloud, you know, if we go back to 2005, 2006 definition from NIST, you know, and they say, well, three, five, but let's just focus on three characteristics. It's on-demand, measured service. So you know exactly, there is metering. You know exactly how much you're using. And then elasticity, right? You need more, you get more. You need less, you get less, right? So those were the three, maybe three of the five, the other ones, you know, network access, which is a given resource pooling, you know, kind of multi-tenancy stuff. But on-demand, metering, elasticity, three big characteristics of the cloud, right? You know, that's what we had at the beginning. And even then people, you know, were of course arguing about the cloud and you know, well, there is no cloud, it's just somebody else's computer. Well, yeah, you're right, it's somebody else managing those servers, first time I'm going to say servers, doing a better job at it than you are, right? But it gives you on-demand capability, elasticity, and metering, right? So that was the cloud. And now when we look at serverless, you know, I like to draw this parallel, right? So let's remember the definition of cloud. And now let's look at serverless. Everybody is going to argue that the poster child of serverless these days is AWS Lambda. And when you look at the features of AWS Lambda, you find built custom backend services. Well, yeah, that's where you build your API server. Bring your own code, right? Bring your own workload, fault tolerance, you know, built in from the cloud. Completely automated infrastructure, right? You know, fully automated infrastructure, you don't see where it's running and it's managed for you. So managed service, basically. Automatic scaling, right? So you need more, you get more, you need less, you know, it runs on less. And then only pay for what you use, that's metering, right? So what do you see here?  Elasticity, right? So the features of Lambda looks a lot like, you know, the core definition of cloud computing from, you know, more than 10 years ago, right? I find that fascinating.  Same way that they were saying, well, there's no cloud.  Well, there is no serverless.  So it's a cloud, right? So anyway, and that's what we're seeing, right? So we have this, you know, new multi-cloud environment, right? And when you look at the characteristics of this multi-cloud environment, it's from the beginning on-demand, elastic, you know, and then metering. And it turns out that certainly everything is looking more and more serverless. The cloud providers are saying, well, it's serverless. Yeah, it's serverless for you if you're using it, but it's not serverless for them. So I love this picture from a medium post from Pablo L'Oreal, you know, giving reference where it's due.  But then there is API Gateway, which is a serverless component. S3 suddenly is becoming serverless storage. Amazon DynamoDB or even there is Aurora Serverless, it's becoming serverless. Cognito is used in serverless applications, right? So when you look at all the cloud offerings of the main generic clouds, you realize that more and more they are branding those offerings as serverless, right? So traditional cloud is also becoming serverless, okay? And of course it's as it should be, that's the real definition of cloud. On demand, elastic and metering, you pay for what you use. So of course, you know, the clouds are serverless for you, right? They're doing the job for you, the undifferentiated, you know, management of the infrastructure that you don't want to do, they're doing it for you, right? Hope that makes sense, hope that makes sense. So let's keep going and try to have, you know, fun with it. So now the question comes up. What happens when you don't manage the infrastructure? You delegate the specialized focus, you delegate to specialized clouds, sorry I'm trying to read the slides, but you delegate to specialized clouds and you focus on differentiating business logic, right? So you delegate to specialized clouds like DataDoc to store your metrics. You don't want to manage the infrastructure you're using GKE, right? And you concentrate just on your business logic. What happens, right? Well, you go service full, which is really a better term than serverless, right? You go service full. You have services everywhere, right? Because you just traded managing servers with managing services. And here I like to quote Patrick Desbois, who was one of the, you know, creators of the DevOps movement.  You just use services. So we shouldn't say serverless, but we're going service full, right? And that's really good. And that's really what we are trying to do from the beginning as people developing and deploying application, you know, developing the apps and operating the apps. That's really what we're trying to do. We're trying to be service full, right? So my co-founder, Martin, called, published this post recently on DevOps to Dev Apps. You can find it in the news stack. And really, you know, and I'm also mentioning it because Patrick has created DevOps, but, you know, 10 years ago, almost, you know, we were all facing the traditional old world of monolithic application and siloed organization, the DevOps. And then we try to create best practices, better, you know, engineering practices. And that's where the DevOps movement emerged. The main foundation of all of this was trying to go faster, right? And as you try to go faster, you want to delegate. You want the undifferentiated bits. What doesn't really bring value to the business. You want somebody else to do it. Somebody whose business it is to do it so that you can concentrate on the stuff that your business really does and offers, right? So ultimately, you know, what we're saying at TriggerMesh is that you move to Dev Apps, right? You're building the app, you're deploying the apps, but you don't really care about the infrastructure, right? So, you know, you're more of a Dev Apps person and it's Dev Apps practice that's really serviceful, okay? So, your multi-cloud environment could be everything on a single generic cloud, could be multiple generic clouds, you know? Could be that you have on-premises stuff that are very critical, you know, for security, auditing reasons. And then maybe you still use a dedicated cloud like Data.org to store your metrics, right? There are different, you know, things that could happen here in your environment as you go serviceful and you delegate. That makes sense. So, what's the challenge? The challenge is that now you need to bridge all those things, right? You need to bridge from on-prem to dedicated cloud. You need to bring, you need to bridge from dedicated to, you know, you know, EKS. You need to bridge Salesforce from MKS, right? Manage Kafka on AWS, right? That's the big challenge. You need to bridge those services. So, you know, this is not a pitch talk, but definitely that's what we do at TriggerMesh. That's our vision. You know, that's why I'm here talking to you about this. We're building bridges, right? We're building bridges to link event sources to event targets or event sinks. And in the middle we have those brokers, right? So, that's what we do at TriggerMesh. We build bridges between services that can exist on-prem in dedicated cloud or generic cloud. So, how do we do this? Well, you need some glue, right? A lot of what we do is gluing stuff together, right? So, you need a bunch of glue. You need some bricks, right? You need services that need to be stitched together. And doing it, you need to avoid making spaghetti, you know? I had a chat maybe a year and a half ago with Joe Bida, one of the founders of TriggerMesh, of Kubernetes, sorry. And he said, yeah, that's great, Sebastian, but you need to make sure you're not making spaghetti. Yeah, that's right. You want to avoid making spaghetti, you know, even though spaghetti is very good, right? So, how do you do this? How do you build those bridges? Well, you know, you're going to use a lot of events, right? All these systems that are disconnected and sometimes, you know, I mean, often managed by different people. They have different organizational boundaries. They all emit events, right? So, the events is really, you know, the glue or the substrate between all those services, right? And CNCF helps you with the cloud event specification, right? So, you have those events flowing. And then everything needs an API. It's as old as the cloud or even, you know, before that we need an API so that we can program application programming interface. We need to program so that we can automate things. So, we have events and then all those services, of course, they have an API, right? And then, of course, we need services, right? So, you have services everywhere and they're elastic. You can use them on demand and you pay for use characteristic of a cloud service, right? So, that's what you need to, you know, build those serviceful applications. So, the API, right? What's the API? Well, Kubernetes to the rescue CRD custom resource definitions. If you need to extend the communities API, you define your CRDs, you have a declarative API, you write your reconciliation loops in your controllers. Suddenly, you can manage all of that with the GitOps mindset, the same GitOps mindset that you have for your other workload, right? And then everything you do, you fall back on your feet with Kubernetes as a foundation, right? So, we are going serviceful. We can use the cloud, dedicated cloud, generic cloud AWS and so on. We can use on-prem. Suddenly, we have a common layer. We have this Kubernetes built API, right? CRD, yes, but then the proof is in the pudding. Look, Google has come up with config connector, which is Kubernetes API on top of all the GCP products. Amazon has the ACK, AWS controllers for Kubernetes and Azure as Azure service operator. So, all the cloud providers are agreeing that fronting all their services with a Kubernetes looking API is the right way to go. So, suddenly, they expose an API, your on-prem, you have CRDs. If you could have the same thing for dedicated clouds, you're on to something, right? So, that's what we do at TriggerMation. So, those bridges that I mentioned, those bridges to link all those services, how do you make them happen? Well, you build an API, of course. You build a declarative API that's going to say, hey, I need a bridge between this and that because that's what I'm trying to do, right?  We have Splunk target. We have transformation objects, right? So, we have all of this represented as CRDs. We have controllers and with those, suddenly, you can define those bridges. You can go service full, right? And you can get to the real promise, not the premise, the promise of the cloud on demand, elastic, and pay as you go. So, I'm running out of time. I need to be mindful even though I'm recording. I could go on forever here, okay? But in our product, of course, we have an API. We have a nice looking front end. Here's just a quick snapshot that I put in there. You can define those event sources that are flowing through the system from Google Storage, from Azure, you know, Event Hub, from AWS, Cognito, you know, Oracle Cloud, if you want, Oracle Database, you know, you name it, right? All those different services are emitting events. They're saying, hey, I changed, right? They're emitting a notification that said, hey, something changed. And then we take those events, we route them, we transform them, and you can go to a destination. And once you get to a destination, then suddenly you can go and perform a task, right? Where it gets very interesting in all this narrative that we're doing, in all this ecosystem that has boomed, is that even this, going service full, which my entire point is that, you know what, when you say serverless, you really mean service full and event driven, right?  So that's beautiful. So here's just a snapshot of like a trigger mesh namespace. We have a bunch of controllers running for the different sources, the different destinations, you know, our transformation engine, our, you know, trigger flow controller, right? But if you're an operator, you're familiar with this, you can manage your event driven applications that are bridging those services together. And you could also the same way manage GCP, offering manage your SQSQ, manage your DynamoDB, you know, tables and things like this, all the same way. That's the power. So in practice use cases, of course use cases. So what are we seeing out there? Well, we're seeing a lot of people that are wanting to go service full, right? They're wanting to go service full. It can be a case of, you know, governance with very strong auditing requirements, right? You know, people wanting to say, hey, I need to keep track of what's coming out of my static code analysis, what's coming out of my Jenkins, what's coming out of my Bitbucket, right? I need to get all these events, you know, and then I need to act on them.  So a strong use case we're seeing is DevOps governance, especially in insurance, you know, big financial institution. Other use cases, you know, Salesforce to backend, you know, backend back office, right? Back office infrastructure. You need to sync between those two systems, dedicated cloud, you know, run by Salesforce where you have all your customers and so on.  And why do you want to use TriggerMesh because you don't want to manage those undifferentiated code which are, you know, Salesforce event source, targeting Kafka. You don't want to maintain and operate all of this, right? And then the final one, which is, you know, just a new one that's coming up that, you know, that we have and not putting much details here. But healthcare is also becoming, you know, very interested in this, lots of services involved in healthcare.  So, you want to be able to send those Google Healthcare API to any AWS service, right? So, the bottom line, you know, the conclusion here is that we're talking about serverless and a lot of people are getting hung up, you know, where are the servers and so on. They're still servers. What you're really trying to do, you're trying to build event-driven applications that are serviceful. They compose a lot of services, on-premises services, dedicated cloud, data doc, Salesforce, and then, you know, generic cloud like AWS and Google. You're trying to link all those services, you're going serviceful, a much better term, thanks to Patrick. And how you do this, you need a spec for events, thank you CNCF serverless working group for the cloud event spec. And then you need APIs, and that's where, you know, Kubernetes also comes to the rescue, right? So, that's it. Thank you so much. Again, Sebastian here, you can find me on Twitter at Sebgoa.  I'll be on for the Q&A if I manage to upload this talk and join the chat. Thanks for joining and I'll see you online.