What's going on and welcome to the solo shot? My name is Tom Vecchio. We have a 13-game MLB Slate Tonight lock is set for 705. As always, this is one of the many shows on the Feindle podcast. Network, you can find that anywhere. Whether it's Spotify, whether it's Apple Podcasts, you name it. Make sure to give it a like, follow, or subscribe. Leave a review that would be greatly appreciated and you can follow me on Twitter at Tom underscore Vecchio 1. Before we happen to things, snap into NFL action this season with Feindle. America's number one sportsbook right now. New customers get $200 in bonus bets guaranteed when you place a $5 bet. That's $200 in bonus bets, win or lose. If you've been thinking about joining Feindle, there's no better time to get in on the action. The app is easy to use and there's a wide range of betting options, including spreads, player props, overrunters, and more. So visit Feindle.com and kick off the NFL season. Feindle, official partner of the NFL, must be 21 plus and present in select states. Feindle is offering online sports wagering in Kansas and their agreement with Kansas Tarkasino LLC. First online, real money, wager only $10 first deposit required, bonus issued as knowledgeable bonus bets that expire seven days after receipt. Restrictions apply, see terms at sportsbook.feindle.com. Gambling problem, call 1-800-Gambler or visit feindle.com slash RG in Colorado, Iowa, Michigan, New Jersey, Ohio, Pennsylvania, Illinois, Tennessee, or Virginia. Call 1-800-NEXT-STEP or text NEXT-STEP 253342 in Arizona. Call 1-888-7977 or visit ccpg.org slash chat in Connecticut. In Indiana, call 1-800-9 with it. Call 1-800-522-4700 or visit kscamblinghelp.com in Kansas. In Louisiana, call 1-877-770-STOP. Visit mdgamblinghelp.org in Maryland. Visit 100gambler.net in West Virginia or call 1-800-522-4700 in Wyoming. Hope is here. Visit gamblinghelplinema.org or call<PHONE_NUMBER> for 247 Support in Massachusetts. Call 1-8778-HOPEN-Y or text HOPEN-Y in New York. All right, let's jump into tonight's 13-game MLB slate. The final solo shot of the season. Thank you all for being here, whether it was with Jim throughout the majority of the season, or here with me to close out the final month. But don't worry, there's still playing sports going on. Jim and Brandon doing the NFL DFS show on Thursdays, the recap on Mondays that can be found right here on the same feed for your podcast. And of course, UFC is back in full swing with Austin Swain. Doing that, also the covering the spread podcast, plenty of sports. And before you know it, in what is it, three weeks or so at the end of October, NBA season will be here. And I'll be back with the daily ISO bringing NBA DFS breakdowns every single day. But tonight's 13-game MLB slate lock is set for 7.05. When it comes to the weather on tonight's slate, it is going to be a mess for the New York Mets, just an absolute mess. Rain throughout the day, rain throughout the game. Wind blowing in over 15 miles per hour at City Field. I don't know if they even play this game. Major note there. Atlanta's on the slate, they're at home, nice and warm there. The Colorado Rockies are at home. It is nice and warm at Cors Field. So we are dealing with a loaded, loaded slate. Let's get to the pitching options starting off tonight. All the way up the top, Zach Gallin, 10.6. Joe Ryan is 10,000. Dylan Cease, 9.8. Lancelin, 9.5. Nathan Ivaldi, 9.4. Brian Wu, 9,200. And Yusei Kukuchi at 9,100. Round up the pitchers that are 9K and above. Now starting off at the top with Zach Gallin. He has been one of the elite pitchers this season and really is a player that we should be trusting. And one of the things I also think we need to be factoring in today would be the motivation factor for some of these teams. For example, with Arizona, they are in a spot where they can clinch their wildcard birth tonight. They have their ace on the mound tonight. Yes, is it a difficult matchup going up against Houston? Yeah, that's on the more difficult side of things. But Gallin is a pitcher that we've trusted all season. He's got that strikeout upside. And this is not a literal must win. They obviously have a few more games over the weekend to clinch. But this is as important as it could possibly get. Clinch a spot tonight. Very, very important. Joe Ryan for Minnesota is 10,000. A little bit less expensive compared to Gallin. We could say that the matchup for Joe Ryan is better, but it's also more difficult because it's that course field. So just for the sake of comparison, Colorado, they come with a 25.9% strikeout rate versus right-handed pitching with our current active roster. That's the third worst in the league. Super high strikeout team. Houston, they come with a 20% strikeout rate versus righties, which is the fourth lowest in the league. Zach Gallin comes in with a 26% strikeout rate this season, which is certainly very solid. But Joe Ryan's up at 29.4%. So Joe Ryan has a higher strikeout rate individually. Here's a better matchup going up against Colorado. But he's on the road in course field, which can always present a little bit danger. Not to mention the fact that Minnesota, they are fully locked into their playoff spot. They won the division. They can't move up. They can't move down. They're not a wildcard team. They're locked in. And frankly, Joe Ryan's going to be pitching early next week or whenever it is once they play their first round of the playoffs. Like he's going to be their SP1 or SP2 along with Sonny Gray. So if Joe Ryan gets in a little bit of trouble, it allows a few runs, a few walks. Why push him out there for 95, 90-some odd pitches? So I love the matchup for Joe Ryan. And frankly, if this game was in Minnesota, instead of being in Colorado, I'd have a little bit of a different take on it. So I think Joe Ryan's awesome and the matchup is fantastic. But frankly, he doesn't need to be out there. Galen does have a tougher matchup. The Astros don't strike out as much. But Galen and the Diamondbacks are in a very, very important game. So I do think Galen will have a longer leash compared to Joe Ryan. Dylan Cease is here at 9.8, and he's certainly been showing that strikeout rate that he's been known to have. He's been showing in some of these recent games. The 10.1% walk rate isn't great. The 27.2% strikeout rate is certainly phenomenal. He has a 4.1 to Sierra. The matchup against San Diego isn't one that I necessarily love. And Cease should be out there for 95-plus pitches. There's no reason for him to not be out there. Yeah, Chicago's been eliminated for a while, but there's no reason he shouldn't be out there putting up one final good start. Lancelin is 9,500 for the Dodgers. And Lancelin can certainly get the strikeouts going, but he also can get burned by the home runs quite a bit. 2.18 home runs per 9 is not good. Now, he's on the road in San Francisco, and this is certainly a favorable pitchers' park, and in San Fran they do strikeout more compared to the league average. There are 22.5% of their current active roster versus Wrightys, which is 13th in the league, so they are slightly worse than the league average. So that is somewhat favorable. And Lancelin's only 9,500. So the top tier we're dealing with, positives and negatives, pros and cons for all of these pitchers. If we move a little bit further down, Carlos Rodón is 8,700 for the New York Yankees on the road to take on the Kansas City Royals, and obviously started off the season late due to the injury. He's had some very clear ups and downs since then, but the strikeouts have been on display in some of these recent starts, and he's really limiting the damage. When we get to Kansas City, they come in with a 24.7% strikeout rate versus left-handed pitching with their current active roster, which is the 7th worst in the league. We also looked at Kansas City. They come with a 91 WRC+, which is 24th in the league, and they come in with a team ISO sitting at 156 versus lefties, which is 20th in the league. So Rodón at 8,700 is probably one of my favorite mid-tier pitchers when it comes to his salary. So up at the top, they want to trust Gallin due to the level of consistency that he's brought throughout the season and the fact that I think he's going to have a very long leash tonight. They're going to let him go out there. Joe Ryan, I'm slightly hesitant on just because it's a course field. Even this game could be in the middle of July, and I would still be somewhat hesitant about Joe Ryan. I understand the upside that he brings because of his strikeout ability individually and because of the strikeout matchup that Colorado offers, but it's still a course field. So Gallin ahead of Joe Ryan, frankly, it would probably take Cease ahead of Joe Ryan, and maybe even Lance Lynn ahead of Joe Ryan, definitely Cease ahead of Ryan. So Gallin, Cease, Ryan. Ryan's definitely a better pitcher compared to Lance Lynn, but then if we want some salary relief, Carlos Rodón at 8,700 certainly has a good matchup going up against Kansas City. So the top tier is a little bit jumbled, but it does offer a lot of pivots and different ways to approach lineup construction. So pitching certainly pretty strong on a 13-game slate. There's a lot of pitchers in the mid-tier that you could be going to. You know, Nick Povetta's got certainly got that strikeout rate. I don't love attacking Baltimore if we don't have to. Evaldi is OK. And 9,400, it really comes down to how deep he'd be going into the game. Again, Texas is going to need Evaldi at the start of next week. Texas has, what is it, a two-game lead over Houston. They're not fully secure into winning the division, but I have a little bit of hesitation when it comes to Evaldi as well since he hasn't been out there for super deep since he came back from the IL. So pitching tonight, pretty unique up at the top, and it's honestly a fun way to approach things to close out at least the final solo shot, not the final MLB slate, of course, but the final solo shot of the season. When it comes to stacks on tonight's slate, again, we have, of course, Field, Colorado versus Minnesota. Those two teams are very clear. We have the Dodgers on tonight's slate, but as I said, they're in San Francisco. Not my favorite spot. You know, not the best. I mean, it's a fantastic pitchers' park. I can't even say it's not a great hitters' park. It's a bad hitters' park. It's a great pitchers' park. So I simply don't want to be going there. I have kind of no interest in going to the Dodgers' tonight, which is not something we often say. The Braves are on tonight's slate at home. It's great hitting weather in Atlanta, and they have an absolutely fantastic matchup going up against Trevor Williams for the Washington Nationals. And frankly, I think I like Atlanta ahead of Course Field and absolutely ahead of the Dodgers. So Atlanta's giving me my number one stack on tonight's slate. Surprise, surprise. I don't love talking about them too much, but Trevor Williams for the Nationals is just so, so bad that we can't overlook this spot or we can't gloss over it. Atlanta is just in a spot where 10 runs, I don't think, is out of the question tonight. A 16.7% strikeout rate for Trevor Williams and 8% walk rate. 2.17 homeruns per 9 allowed. He comes from the 5.1 to Sierra and a 42.3% fly ball rate. The homerun upside for the Braves should be on full display tonight. They're absolutely a team we want to be going to. And of course, up and down their lineup, there are several options we can be going to. And again, this comes down to the salary of what we have available. That's why I certainly like Carlos Rodão tonight at 8700, opening up a bit of salary relief. Acunha, Olson, Alvis, Riley, Ozuna, Sean Murphy, Michael Harris, you name it. All these players are going to be in play tonight. Obviously getting up to Olson. Acunha is obviously number one, but he's 5K. That is very, very expensive. So Olson, Alvis, who I specifically like tonight, Austin, Riley, Marcelo, Ozuna and Murphy are going to be the key targets from Atlanta. Not too much of breaking news there. That is very, very clear. I also think we should be looking at the New York Yankees tonight. You know, their offense obviously has been a bit of a disappointment or their team has been in disappointment overall this season compared to what their expectations were coming into the season. But they've kind of shown a little bit of life in some of these recent games, not last night when they got shut out, but some of these recent games, they also have an awesome matchup going up against Jordan Lyles with Kansas City Royals, who's simply not a good pitcher. The Yankees come in with a 4.8 to imply to run total tonight. We look to Jordan Lyles, who's allowing 1.99 homeruns per 9. He has a low 16% striker rate, 6.1% walk rate. Nothing good from Jordan Lyles on top of his 5.17 skill and interactive ERA along with a 48.8% fly ball rate. As I mentioned, it is nicer in Kansas City in terms of hitting weather. I did mention Rodone that I do like him. That's strictly due to the strikeout upside, but I do like the hitting weather here in Kansas City, specifically going up against Jordan Lyles, we know allows far too many homeruns. So I think we can be looking to the Yankees and outside of Aaron Judge at $4,500, who's been on fire in some of these recent games with multi-home runs. The Yankees are actually relatively affordable. Judge is $4,500. The next most expensive player is Labor Torres at $3,000. So we actually can look to the Yankees for a bit of value. John Carlos Stanton is $2,900, and he is striking out at such an insane rate right now. Of course, he has that power upside. I honestly don't love going to Stanton. If I don't have to, I prefer just to spend up for Judge, take Labor, go to DJ LaMague at $2,700, and go to some of the other value options on the Yankees rather than going to Stanton. And I know, yes, the power upside is there, but I just prefer some other players. So going to the Yankees tonight is actually a really good stack, and Judge should be the priority. Much like the Braves, obviously it's a little bit different to their salaries, but Acuna is always going to be the priority when it comes to the Braves. If you can get to him, 5K is a lot. $4,500 for Judge is a lot. If you can afford to get them in your Lyons, of course, do so. Multi-home run upside for both of them. Acuna is going to be stealing seemingly a base every single game as he set the record this season, or the 40, whatever it is, the 3070 record, 4070 record, whatever he set the other night. So I like the Yankees. I like the Braves. That's not too much of a surprise. Coorsfield is on the slate. Of course, Roll with Coors field. And then I really like the Arizona Diamondback tonight, going up against JP France for the Houston Astros. France has kind of been all over the map this season in terms of he looks good at times. He looks bad at times. He's back to looking good. He's back to looking terrible. He's walking too many hitters. He's lying too many home runs. It's kind of an entirely mixed bag for JP France. And as I mentioned, Arizona, they are in a spot to clinch tonight. So I'm going to be looking to teams that need to win to close out the final three days of the regular season. A 17.4% strikeout rate from JP France is nothing we need to worry about. An 8.1% walk rate, 1.25 home runs per nine. He has a 4.96 skill interactive ERA and a 37.4% fly ball rate. When we look at his stats, at least on a game-by-game basis, this is where I'm saying he's all over the place where low strikeout rate in overall in the season, but then he's up at 25%. He's down at 13%. He's back up at 23%. And the same thing can be said about his walk rate on a game-by-game basis where it's down at 4.8% against Kansas City in his most recent start and then against Kansas City in the prior week, it's up at 18%. And against San Diego, it's up at 20%. So his control is all over the place and that has led to a lot of upside for some of these teams. And I will take a matchup against JP France given what we have on tonight's slate. And when it comes to Arizona, a team that I generally like stacking because of the power that they have, I've mentioned it time and time again about Arizona. They have multiple hitters we've been going to right from the top and, you know, frankly, they're not too expensive compared to some of the other teams on tonight's slate. They're not as expensive as the Braves. They're not going to be expensive as the hitters at Coors Field. Corbin Carroll at 4,100 is fantastic. We know that. But Christian Walker could tell Marte going to those two, I think, is a solid way to start the stack even if you have to leave off Corbin Carroll because they're both 3,600, adding in Tommy Pham at 2,900, adding in Lourdes-Goriel at 2,900, adding in Pardomo at 2,700, whatever it might be. This is where we get a little bit of value from Arizona, really. And whether it's out of Thomas, whether it's Jake McCarthy, whatever them, end up making the lineup at 2,500 and 2,400, we're actually getting a good bit of value for a team that's in a really good spot. So, you know, if you have to leave off Acunia from a Braves stack, I don't love it, but it kind of makes sense. If you have to leave off Corbin from an Arizona stack, it kind of makes sense because it allows you to full stack each team while still paying up for some potential pitching options. So, yeah, if we could afford every single hitter, it would be Carroll, it would be George, it would be Acunia every single night, but that's obviously not the case. So, give me Olsen and Riley and Murphy and Azuna and those hitters from Atlanta, and then give me Walker and Marte and Pham and Goriel from the Diamondbacks and that still allows you some flexibility when it comes to pitching. So, tonight's Slade, I think Arizona, the Yankees, the Braves, all very clear. Coors Field also very clear. I wouldn't mind going to St. Louis. I know they're not the best team in the world, but I like to match against Brandon Williamson and maybe take some one-offs from St. Louis. As I said, Cease is a good pitcher for the White Sox. He certainly has that strikeout upside, but the walks and the homeruns continue to be an issue for him, but San Diego certainly has plenty of power hitters in their lineup, so I wouldn't mind taking a few one-offs from San Diego as well. Let's close things out with the Dinger calls. Ozzy Albie is number one for the Atlanta Braves. I just love this matchup with the lefty splits going up against Trevor Williams for the Washington Nationals. Very clear upside for Atlanta tonight, and like I said, I'm not going to be surprised if they put up 10 runs. It's not going to be a surprise any single night that they put up 10 runs, specifically tonight against Trevor Williams. A lot of runs early and often against him. And then, of course, going to Aaron Judge. So Judge is the easy answer on tonight's slate. I think the matchup against Jordan Lyos is just way, way too good to be passing up given the potential fly ball issues, or we know the fly ball issues that he has with the 48.8% fly ball rate this season. Judge could certainly put that on full display. And then Ozzy Albie, as I would say, is a bit of a longer shot. He's not one of the main power hitters for the Braves behind Riley Ocunia and Olson. So give me all of these. Give me Judge for the two home run calls to close out the final episode of the solo shot this season. Thank you all for being here again. Plenty of shows across the Fandal Podcast Network, whether it's football, whether it's UFC, NBA will be back at the end of October, October 25th, 26th, wherever that start date is, running throughout the entirety of the season. All right, so that does for today. As always, this is one of the many shows on the Fandal Podcast Network. You can find it anywhere, whether it's Apple Podcast, whether it's Spotify, the video version we found on the Fandal YouTube page, found on Fandal TV Plus, and be found on Fandal.com. Watch, you can follow me on Twitter at Tom, or Becky, or one. Until next time, good luck in your contests.


I have no idea where I am. I know I'm across the street from a casino in something called Jed's Jerky. I'm roughly two hours north west of Las Vegas. I slept last night. This was all covered by trucks last night by the way. Now. It's totally empty. There's only two people sleeping in and I think it's like 8 30 in the morning. I was actually pretty excited that I cleaned up last night because it's quite nice not to have to have to do that first thing in the morning. The only thing I have to put away really is this pot that I cooked the soup in last night and everything else is pretty good. I'll be quite honest with you. The reason I'm starting the engine and not editing right now is so I can drive across the street. Take a leak. All right. Here's the setup so far. I have a really gross casino truck stop coffee. No joke. It's it's pretty bad. Just exporting some Lightroom pictures. If you guys haven't checked out my Instagram, please do. I am working on my photography as well as my videography. That's why I got this big camera to properly document because I can't recapture a moment. So who knows maybe I'll make a coffee table book or something of my travels. And I've been trying to work on the captions as well having the more personal and explanatory if that's even a word. Is that a word? Anyways, yeah, I'm just gonna work for a bit and I'll see you guys on the road. Because I chickened out on staying at the ghost town last night, I did notice that there was a ghost town about 10 miles away called Riolite. It's not probably a spooky and authentic as the one I stopped by yesterday called Bonnie Claire, but since it's so close, I mean might as well stop by. There we are. So the first thing to look for when you get here to Riolite is on the left hand side to have a free museum and have this interesting, I don't know, let's call it an art sculpture with some ghosts. This installation is called The Last Supper by I don't know how to say the name, Zugalski. That is a free museum right there. There's a couple other little sculptures there and there's like mosaic couch up there and some other stuff. And over here, doesn't it look like Donald Trump? But there's like orange hair, yellow hair, and orange thing. Anyways, it is now time to continue on. We're going to check out the ghost town part of Riolite. Here's what's left over from the miners union hall. Not really sure what that means, but this is the spot. Across the street from the union hall is the old school, which actually to me looks fairly large. I'm not really sure if it was a two-story building or if it just had high ceilings, but that's for a small little town way out here. That seems like a pretty big school, must have been a lot of kids in there. This looks like an old caboose from a train. Wow, look at how epic that is inside. That is going to make for a wonderful photo. Do you guys know what this is? This looks like a stove and I would guess it is probably a wood burning stove. If anybody knows for sure, feel free to comment down below and educate everyone else. I'm just parked in front of what was the, well I don't know, it says prospering businesses. It doesn't say exactly what this was. My guess is that could have been a bank, could have been an apartment building, could have been a brothel, could have been a lot of things and unfortunately there's no sign which says what it is and also there was no, well I guess there was an information thing down below, but there's no kind of clear explanation of exactly what this is, but I can tell you it's beautiful, that's for sure. Well I can't tell you with absolute certainty that there is a lot more to see here in Ryolite than Bonny Clair which was basically two or three buildings although way less touristy than this place it was a lot smaller. So I kind of got the best of both worlds I suppose because I got to see a more preserved place although it was a little vandalized. The other place wasn't vandalized really it was just really old there's no graffiti so see that's the thing it's like the more populated areas will naturally become more destroyed because of you and I not really you and not really me but because of people and the other places which have a lot less visitors will be a lot more like they used to be I guess a lot a lot better preserved because really no one's out here watching this stuff I mean literally you could get away with murder out here unfortunately so on that note I need a shower if I'm gonna go meet people I'm gonna head towards Vegas I'm about two hours away also guys I am trying to schedule a meetup in Las Vegas I haven't had too many meetups at locations and it's been a little hard because it's like I never know where I'm gonna be and I don't really go to a lot of big cities I kind of pass through them so anyways let's see how this works I know a few people have said they are available so yeah it'll be fun it'll be awesome to meet you guys so if I'm passing through let's hang out come to a meetup starting to feel the effects of having had nothing but bananas and coffee today also I'm very ripe and still need to take a shower and I thought I would stop and get everyone at the office some donuts so I'll get probably like two dozen or so I had a place called pink box donuts hello good how are you yeah here you guys like the voodoo donuts of Vegas huh but better but better sweet what's your name by the way taylor jacks come say come see taylor over at pink box donuts are we like where's the chinatown area there you go this is what I would say successful trip to the donut shop all right next up I'm gonna try and find a truck stop to take a shower at uh normally showers at truck stops cost about 12 bucks or so um so I'm having a little trouble with my phone because I think I've been using so much data but I just realized I have GPS here and I wonder if I could find how to find something here there you go find so uh next stop take a shower at the truck stop so this is how this works um you basically put in this little code into this little thing all of them are different let's see if this works 41141 there we go this ladies and gentlemen is what a truck stop shower consists of you got your own private toilet a little shower over here and you got little things to scrub yourself with and dry yourself off with so how about those potatoes I also got my little shower bag in action with some goodies inside of it including battery powered shaver thingy trimmer and soap then all the goodies see you in a minute we're back except I'm missing some facial hair and uh a lot of bad smelling body odor but I uh broke through security it was a tough fight and uh I'm going up quite a few floors caution I think I think it'll work let's see all right guys so I know a lot of you asked me how I make money and I want to introduce you to part of the team who helps me put gas in the gas tank right here um if you guys are an influencer hit me up and I will give you a special code uh otherwise mum's the word we're gonna do a little bus tour with my influencer agency all right who's ready for school I got these for you oh my god we got LEDs so you can change the color and stuff so it looks like I'm going to say goodbye to everybody I'm going to continue on the road and I hope that I'm not eating in and out burgers by myself at this meetup so bye guys burgers in the world it is absolutely delicious and uh there's a really good chance that I'll be uh eating solo but that's all right at least I tried huh all right time to go get uh what am I gonna get let me get a double double with fries yeah animal style uh mustard extra pickles that's how I like it all right got my burger so far it's a table for one looks like it was just me and the pigeons uh at the meetup which is again totally okay uh but yeah this is you know when I originally started this project for those new viewers who don't know but I was trying to meet up with people all over the place like viewers and people who follow me and stuff like that and subscribe um but it's really hard people are not as available as I am because obviously you saw kind of today how I make money which is uh kind of over the internet so uh I found a place that has like the cheapest gas in town using uh an app called gas buddy I'm probably sure some of you guys use it I love it because it saves me money this is not a sponsored endorsement but I you know gas is super expensive in this thing I'm on empty I'm guessing at two dollars and 49 cents it's gonna cost me for let's say we get 50 yeah between 50 and 55 gallons uh two dollars that would be a hundred bucks plus uh 25 percent to 125 I'm gonna say it's gonna be about one yeah like 130 on this fill up so that's a lot of money found a place for uh 249 uh if I was paying cash it would be 239 uh I just find that using a credit card for this stuff by the way it's a credit union credit card um I find it just to be a little bit easier to keep track of my expenses uh because everything is a write-off and um so anyways it cost me five dollars more to use a credit card than cash and uh prepaid 130 bucks so I was right right on the money in between 125 130 moment of truth let's see if I was right oh we were pretty close 49 gallons let's see how much we can squeeze out of there because I already prepaid whoop check this out I totally had to top this sucker off but I did it this thing is completely full of diesel


So, you know, this talk is about improving iVersion. iVersion is the thing we have in the iNode struct that, you know, kind of tracks changes. So, the motivation for this is NFS, obviously, so V3 relies heavily on watching time stamps and time stamp, Linux uses coarse-grained time stamps when it, like, updates the C time or the M time, A time, and those time stamps are around one jiffy of granularity. And, of course, lots of things can happen in one jiffy, and that can lead to problems in the client, you know, thinking that it has an up-to-date cache when it really doesn't. So, for V4, what they came up with was this idea of a change attribute. So, it's just an unsigned 64-bit value, and that has to change anytime the C time would be updated. It's usually, it was, you know, originally considered to be sort of an opaque value, or at least client should treat it as an opaque value, but there are some advantages to, there are some advantages to providing a value that increases monotonically. In particular, the client can know that certain updates, that if it sees an older or a smaller iVersion than what it has, it can know to throw that out and that it's not valid anymore. So, V4, NFS V4 II also gave us a way for the server to report what type of change attribute it has, so the client can make a decision about how it should treat it. In particular, the time metadata is particularly useful. Right now, we pretty much always report it as undefined. What we'd like to do is be able to report it as monotonic, which is the zero one. So, when should it change, right? So, it should change anytime that the metadata change time should change, so the C time. Some servers can ensure that the thing is, that the change to that attribute is atomic with the change itself, but we can't do that in Linux. So, for that one, it should change it. We can either do it, we can bump the iVersion before or after we copy the data into the page cache on a buffer. Right, right. In particular, we, if we, right now, the next bumps it before the change is visible and that's bad because someone can race in with a get at her, see the new C time value or see the new iVersion value and then do a read before you have a chance to copy anything to the page cache. And now, all of a sudden, client has now associated this new iVersion value with an old state of the cache. And that's bad. So, if we do it after the change comes visible, it's still a little racy, but at least the, you know, the client should catch up pretty quickly and realize that it is, that its cache is out of date. And so, if we increment it before and after, that's also acceptable. So, in the field, it's basically just a dedicated U64 Instruct iNode. We have two flavors, right. So, if you were running like an NFS client or a stuffFS client, really what we want to do there is just copy whatever the server sends us, right. We don't want to try to manage this thing ourselves. But for local file systems, we have a kernel managed value. So, that's where we, you know, the kernel is responsible that whenever the, like, whenever it goes to update the time stamps, it also needs to bump this iVersion field. And we have some infrastructure in the generic VFS to handle this for a lot of stuff. And you can opt into that by just setting SBI version. We have this in ButterFS, EXT4, XFS, and TempFS so far. So, the kernel managed one is the really interesting one. We enable, it's enabled in all those files that I just mentioned, also requested it recently for GFS2, but they haven't done work on that yet. So, the original implementation of this was a, just a simple counter. So, but that turned out to be really costly for EXT4 and XFS. Because every time you increment the thing, you had to log it to disk. And so, in 2018, we changed to a new scheme where we used the lowest bit in the counter for a query bit. So, anytime you go and do a get at or against the iNode for the iVersion, we set this flag and then we know on the next time that we go to update the thing that we have to go and bump the counter. Otherwise, we can leave it alone because if no one has viewed it, we don't really care, you know, there's no, you know, there's no delta. So, it's okay. And then with this, we were able to recoup almost all the performance that we lost when the count, when we first implemented the counter. So, right now, in fact, EXT4 originally had a, had a mount option for this and we just recently deprecated it. So, yay, because it can be on all the time now. But it has problems. In particular, I did some work a while back and I started noticing that sometimes I was getting weird cash invalidations and I found that XFS and EXT4 both were bumping it on A-time updates, which was bad, right? You know, you don't want to invalidate your cash just because somebody did a read. So, we fixed that in EXT4 recently, but XFS uses their iVersion counter for some other uses and they don't want to make that change. So, we can't, we don't have a solution for that just yet. The counter is also bumped currently before copying to the page cache. So, like I mentioned about the, you know, client that can cause the client, you can race in and get an invalid cache. And then we also have the potential for lost updates due to crashes. NFSD doesn't wait until you've, until we've logged the value to disk before it starts presenting it to clients.  And then, even worse, you can do another write and now the client has a iVersion value it thinks is associated with the current state of the file, but it really isn't. It's a duplicate iVersion that represents two states of that file and that's bad. So, what NFSD does is it tries to factor in the C time on the, on the file to, you know, to sort of mitigate this, right? Because if it crashes and comes back up and you, you know, hit it, then presumably you have a different C time, you'd be able to use that to distinguish between the two states. But, you know, then you could have a potentially a clock rollback that could result, you know, after your crash that could result in you seeing duplicate values, but there's only so much we can do. And the other problem we've got with this thing is it's really difficult to test, which is why the, you know, it was broken for so long anyway with, as far as like A time updates go. We don't really have good test cases in XFS right now because there's no way to query it from user land. To find this value you have to go through NFSD currently. So, anyway, I talked about, you know, when, when should we do this? So, queries of iVersion, we don't have any locking around it. We usually update it alongside the C time. So, for directories that's C times are usually updated after the operation. But for rights we usually do it before. So, here's some possible solutions. One of the things we can do is separate the iVersion update from the C time update. You know, still bump the, there's some, you know, do we really want to change when we bump the C time?  So, I'm a little leery of doing that. But bumping the C time, or the iVersion after the operation would be fine as far as we're concerned. So, one of the things we could do is just do an extra iVersion bump every time. So, we bump it before we do the operation when we set the C time and do it again afterward. Most of the time that, because of the way this, you know, because we are using that flag-based, you know, scheme to determine when we should do it, that second bump will probably be a no-op in almost all cases. The only case it wouldn't be is that someone raced him in the get-out. And none of this is actually needed for XTFS since they serialized buffered reads versus writes. I thought it EXT-4 did, but Jan pointed me out that I'm wrong. So, butter of S, EXT-4 and temp of S probably need to bump, need this extra bump afterward. Crash resilience, that's a problem. We have some potential. We could, one of the things that was bandied about on the list as we were discussing this a few months ago was we could factor in a crash counter, stick it in. We probably have to be tracked by user land somehow. So, it's an idea. You know, one of the things we could, but the problem is we have to, like, estimate how many, how many potential increments could we lose, right? You know, if, you know, what's the, what's the maximum number of times we could bump this thing, the counter, beyond from when it was logged to, you know, what, the last one we handed out. So, you know, there's a way we could do this, but it's not trivial. So, anyway, this is some things I'm looking at. I haven't gotten very far with this one yet, but. So, this is an idea here that Dave Chinner came up with, actually. He mentioned, as we were discussing a lot of this stuff, he said, we should just use the C time. In fact, what we could do is just, you know, use the, use a similar scheme where we flag the C time when, when someone queries it, and then know that on the next C time update, we're going to need to do a fine grain time stamp. And this one actually works pretty well. I have some draft patches for this that I've sent to the list a couple of times. I do see some test failures with this currently.  And then, you know, with these patches, sometimes that, that last coarse grain time stamp looks like it is before your operation finished, right? And so that, you know, that causes a test failure. And those are really problems in the tests. The tests are assuming that the file system uses coarse grain time stamps. And with this, we're breaking that assumption. So, but this is where I really want to go.  And in fact, what I, what I'd really like to do is build a gated write. So I'd like to be able to do basically what you see in the pseudocode code here, right? Be able to fetch the, the, the change attribute, do a read, modify it, and then try to write it back, but only if the version hasn't changed. It's kind of like what Jan was saying, like we were doing with the read where we would just, you know, repoll the thing every time. And the nice thing about this is, and I used a very similar scheme to this when I built some, some work and I did in Cepha a while back and I, and I really liked this because I didn't have to use any locking.  Yes. Yes. We could totally implement this with verify. If you're doing this, perhaps your better off if I version isn't incommented for things like Jamod. I'm sorry, what? Perhaps your better off if I version isn't incommentative things like Jamod. Yeah. Yeah. Unfortunately, you times. Yeah. Unfortunately, you know, our semantics are kind of set, at least as far as NFS goes. So I think we would have a tough time. I mean, what you want is an AFS style change attribute, but we don't, we don't have that. So, so yeah, you might get some false positives if this were to happen. But I, you know, my, my feeling is that problem is not the best. What if we decouple this change cookie completely from my version, combine that with the crash counter idea that, you know, we had discussed earlier. In that case, the change cookie could just simply be an in memory value. Well, I guess we have to worry a little bit about what happens if the inode gets pushed out due to pressure, memory pressure. But, you know, in some ways, if we didn't actually have to write it out or could rely mostly on C time, then, you know, we avoid some of the extra overhead of having this extra thing that the file system has to track that has its own unique semantics about is metadata changes like Chimad included, yada, yada. Well, I think that would be fine if we, if all we wanted to do with it was this. The problem is that NFSD still wants to use that version two. And if you were to crash and come back, then all of a sudden you're, we can't keep a really an ephemeral one for that reason, I think. I think I might have already mentioned this on the list. The only thing that I find important is when we expose this cookie that it has clearly defined semantics and hopefully consistent semantics because I, I always, when I see stuff like this, which kind of feels like it's not really clear what it indicates, I've always has F F F underscore FS ID in mind in stat FS, which is like nobody literally on a man page has nobody knows what it's supposed to mean. Yeah. Yeah. I mean, that's fair criticism, right? You know, I've been trying to define this and, and really, you know, unfortunately, POSIX doesn't contain this, right? You know, so this is a totally a thing that, you know, AFS and NFS cooked up, right? But yeah, I think we can do that. And kind of what the, the semantics we come up with is that basically anytime you would change the C time, you would need to increment this thing. And that is pretty well defined by POSIX. So I think that we actually know when, you know, what it represents and when, when it needs to be in incremented, but, but beyond that, you know, but yes, you're right. We do need to document it before we ever expose this thing. Absolutely. One thing that might mitigate against double incrementing it is the way, with the way AFS does things, you do a right to the server and you get back a new iversion, a new data version. You know, it's going to be plus one. If it's the old version plus one, there's no interference with your right. If you double increment it sometimes and not other times, you don't have that guarantee anymore. Well, you know, we don't have that guarantee with NFS anyway, really, because it just, it changes. Yeah. Yeah. And I don't think we can really, I don't think, you know, unfortunately, AFS's change attributes semantics and NFS's don't really mesh, you know, AFS has a change attribute too, but it's only bumped on content changes. So it doesn't, it doesn't care about metadata changes. Yeah. And you do it exactly once for every right, which we can't guarantee. I don't have the exact discussion in mind anymore.  Like basically what happens, why isn't it possible to just say, okay, I need to re-query iversion after a crash? Yeah. I mean, that's potentially something we could do. The danger right is that, let's say you have an iversion of two, right? And then you do a right and you get an iversion of three. Okay. Now you crash and that iversion of three never made it to disk. Server comes back up. So the client was aware of this, right? But someone else races in and does a right. Now we have another iversion, you know, iversion was two after it came back up. Now, now someone else does a completely different right. Now we have an iversion of three again. In between the crack. Yeah. Yeah. So we can't, yeah, that's the, that's the real danger, right? You know, the, the rolling back is not so bad. It's that you can roll forward again and get a duplicate value that represents a different state of the file. So that's the crash. Yeah. The crash, you know, mitigating crashes is a really tough part of this. And I don't really have great solutions just yet. I'm open to suggestions for this.  Yeah. Well, even then, I mean, it's not, yeah, I mean, you could just, but then that's nasty for performance, right? You know, so yeah, the crash could, the crash mitigation part is actually really tough to deal with. And I'm not sure, you know, we have some sort of hand wavy ideas. Yon had a good one. I mean, it was like, you know, that we should do this crash counter thing, which we could totally do. But you know, we need, you know, need to sit down and really work out this. I think AFS has something like that per volume. If the volume has to be recovered, update the timestamp on it, wipe everything. They don't have to deal with random file systems. Yeah, I think the other reason why AFS is a lot simpler is you don't have to worry about local rights. Exactly. That's the reason why you can guarantee the it bumps by one when the users make a change. You don't have to worry about a local right interfering. The one thing I was going to note here is we already have a boot UUID that gets regenerated each time the system reboots. You know, we've actually had that for a long time because, you know, we had the UUID and generator and it's, it's, it's in DevRandom. It's, it's essentially each time the system boots, we generate a random, you know, 16-byte UUID. You can fetch it. It's like a global variable. Never changes after you reboot. Now it's not a counter. It's 16 bytes. You could hash it somehow. So I'm not sure how useful it would be in the context of fitting into the existing NFS protocol, right? But there is easy ways that you could, you know, have the NFS server tell, oh yeah, you know, we've since rebooted if you wanted to, you know, somehow use the previous version of the boot UUID and see that the boot UUID has changed since changed. That's a good idea. Thanks, Ted. I'll take a look at that. Anybody else have questions or comments? I might be raining on your parade. But one comment I've been hearing multiple times in the room is, well, we're not sure what the semantics of this are or the semantics of NFS treatment of the attribute. It's not the same as AFS. And so I'm wondering if we might not be better off if each of these protocols handle this in their own way. The one thing you mentioned where you wanted this to be like exposed to user space because the only way to test it was through NFSD. It seems like, you know, going over a loop back or using PyNFS seems like a good way of testing that it does exactly what NFS needs. And I'm just wondering if maybe we might want to rethink the idea that we want a common implementation for all file systems. Because the one thing is not mentioned here is that the performance overhead is if everybody did this themselves versus it being done by the file systems. Could you talk a little bit to that? So you're talking about having the file systems manage the i-version or maybe the VFS? Well, what would the performance overhead be if NFSD did this for itself and AFS did it for itself? Because the semantics aren't the same. I don't think we can really do that because, again, we have to deal with local rights, right? You know, NFSD doesn't know if someone has walked in and started doing rights to the file system, right? So one thing that may help me understand context a little bit better is when I grep for i-version, I see XFS. It looks like it manipulates it. Do other file systems, Ceph and EX24, the rest, basically ignore it. But it looked like there were some libFS helper routines that mess with it. So it was not clear to me whether the VFS, looking at the code at first glance, whether the VFS bumps i-version without you having to do anything, or whether this really is a flag that only three file systems can bump counters on. Yeah, I mean, if you set SBI version in your file system in the i-node, then the VFS will do that for you. So whenever it goes to update the C time, it will take care of the i-version as well. Because I looked at that, and I'll go look at it again, but I didn't think there are very many that set that. There aren't. Yeah. And I don't care.  But what puzzled me is, if really it's just three file systems that set it, then what if VFS is mounted on overlay FS or I don't know what it picks? Then it manufactures a change. It manufactures the change attribute from the C time in that case. This is why I'm going to, one of the reasons I'm going to this multi-grain time stamp idea. For instance, the XFS guys don't want to put a new field on their disc in their on-disk i-node. But if we can do this, then we can still manufacture a change attribute from the C time. And it's good enough with the fine-grain time stamps. I think having this be a helper, for example, and this being done in the VFS seems fine to me. I mean, three file systems, okay. Inputation, what's the right number for something to move up to the VFS? That's fine. The only thing that I didn't point out I was trying to make just to clarify what statics change cookie being part of user space API is that users have a difficult time making sense of a value that is exposed to them that has different meanings for very different things. And that's the main problem. When you suddenly have statics change cookie, I'm opening up the man page and I see for XFS, for NFS, and for AFS. And then I have to read through all of that and like, okay, this means three different things. That's the thing that I'm concerned about. Yeah, I don't think that, I think in general, all the local file systems that use the SBI version have the same semantics. And those semantics match what NFS uses. The only real odd man out is AFS. And so I probably just won't wire up AFS. If we ever were to present this to user land, I just would never, I just probably wouldn't wire it up for AFS. Or we have some, we have what the statics file attribute flags or whatever. We have one already where the file system can claim that it's monotonic or that it's statics change cookie is monotonic. We could do one that said this is an AFS style statics or time stamp or an AFS style change cookie. Monotonic but not metadata. Right, right. This one won't work for metadata changes. And maybe user land can sort through that. So look at it and say, oh, I need metadata changes. I can't use this. So basically the only thing we really want this for is for NFS state to export. Currently, right. But eventually I would like to use it. Because if you're going to expose it to user space, what's the minimum promise we can use a space that you need to make? That it will be bumped anytime the C time would change. Is that the minimum? Well, yeah, but what would user space be using it for? Is it to detect changes to the file? Yeah, but could it be sufficient to say anytime M time changes? And stuff there? Because like someone said that. Well, no, because I send a set X after on it. It'll change, for example. Yeah, if you put an X after on it, the time thing changes, right? No, I mean, you're arguing that we should use adopt AFS semantics. I'm saying that NFS wants this. We already have semantics in all the other file systems to do it a different way. So I would not be a, I would be opposed to that idea.  Because the other thing I want to be using this for, but from the FS clients point, so the NFS clients point of view is tagging the local cache, which means if someone does Chimote, I can go to your local cache. Exactly, yeah. Which is unfortunate, right? You know, that part is a bummer, but those, those kind of changes are pretty rare. Yeah, but actually if you do these multi-grain timestamps, then you just base code basically just use the C time to detect and doesn't have to bother with some obscure argument like obscure static. Yeah. And in fact, you know, this is, I'm liking this better because this means it works for v3 too. Yeah, it's also it's much easier to understand like for the user space application, but it's actually getting. Yeah. And in theory, you know, the most user space applications should be fine with the change in semantics here too, I think. So I'm probably going to, I see myself probably implementing this kernel wide eventually. I'm probably going to do a piecemeal per file system to start, but I imagine most kernel file systems will want to adopt the scheme. Yeah. So my point is that if we do this, that I don't see then such a need to implement the static's cookie, change cookies. Yeah, we may not need it after that. Because then it's utility would be very, very limited. I totally agree with what you're saying is that this can be as 100 nanoseconds is 100 nanoseconds good enough. But why wouldn't you use m time instead of C time if you're worried about the Tramod example is m time good enough because everybody can explain to a user space what m time is in C time. But why isn't m time good enough for 99.9% of it? It's fine. It's just the 100 nanoseconds good enough, by the way. If I do it right, a new version of a plus one, I know that it's changed 100 milliseconds ago, 100 nanoseconds ago. I don't know that there was the time stops are not enough information. Yeah. So one other really quick thing, which is earlier in the slide, you said that the kernel only uses a second level granularity. That's true for the stat system call stat 64 uses a time spec. And in fact, most of the major file systems are providing sub second granularity anyway. It's not just XFS because, you know, make can compile an awful lot of files in one second. So yeah. Yeah. Oh, and the other thing is the reason why people like C time and not m time is you can fake m time using the U time system call and warp m time. Whereas you can't warp C time. The next session is actually in the BF cross talk, but they're not on time. I mean, I can see on zoom that they're not on time. I'll go check when the time, but you guys can okay. Yeah. Yeah. I mean, and I'm kind of moving thinking that yeah, probably I'm going to move most of this stuff to using the multigrain time stamp now because that again, I'm just in early days on this, but but I think that's probably where we want to go. Unfortunately, I have to fix a bunch of test cases, it seems like. Yeah. So like for internal in NFS use, I can totally see you doing the I version thing. Yeah. But for user space, I believe the multigrain C time should be enough. Sounds good to me.


This is what peak yoru utility looks like. Sorry Omen. We're having, going around, a lot of peeks in one main one. There's one over there. Nice. First in one top, so we're going to push. There he is. Coming from heaven. I can flash out, I'm gonna flash. Nice, did he turn? Oh yeah, he was looking.  There is nothing worse than getting trolls and AFKs in your valorant game. And everyone needs a break from it sometimes to blow off some steam from ranked. That's why you should play enlisted. Enlisted is a new kind of FPS that combines PvP and PvE combat. You take control of a squad of customizable AI soldiers and fight in huge battles with other players. Each soldier comes with individual skills that can be customized, equipped, and upgraded from both action snipers all the way to SMG engineers. One of my favorite parts of the game is how they also have campaigns you can play through that are so detailed they feel like their own individual games and offer their own unique weapons, vehicles, and equipment with incredible graphics. Use my link below and go play enlisted completely free on PC, Xbox, and PlayStation. You'll get a free bonus pack with multiple weapons, soldiers, and premium content. Thanks enlisted for sponsoring the video. And if you don't know, I'm racing my twin to 100 wins this sect, but today I will teach you how to play Yoru on every map. So we'll cover the tips, then the races score at the end. I think a lot of people still really underestimate the value of ulting right when the walls drop for a fast flank on defense. With my history on Sunset, I've really been trying to approach it with a lot more patience. I found that playing tiles or A site is a bit easier for me. So I've been favoring that.  It'll be like $20 CPM, which basically means that they'll pay you $20 for every 1000 views you get depends on the brand. But sometimes you can get like two grand sometimes you can get like 1500 like mobile game mobile game companies like Raid Shadow Legends have deep pockets bro. They got really deep pockets. That's why that's why you see a lot of creators work with them because it's just good money. What bro like what? I just don't understand how he doesn't shoot the clone there. Like does he just know like appreciate that. Breeze is the only map I don't mind starting a sheriff on especially defense. The range is really nice and I never found myself in a good position to use pop flashes on defense through Viper walls. Another good thing about Breeze is because it's so big, you can set up really good crossfires with your clone.  Then next thing you know the defeat screen pops up and you have no idea what happened. That's what that felt like. But I didn't let that demotivate me and went into my next Haven game with full confidence. I love Haven because it's just so good for spawn teleports. He's so close, he might get detained. Whenever I play on bind, I tend to favor long. Hookah is just really annoying to push especially when the enemy has shotguns and you can close the gap really easily with your teleport. The orb is also really easy to farm for your ult so it makes attacking pretty smooth. Flash Trigger. It's two hit, two hit. Set the f*** down for your sh**. Sky Tp Day. Yeah, he has Sky. She went CT. Could be elbow, could be elbow technically. Yeah elbow. I think they're all through there because Sky just dodged, right? Yeah, I'm sorry. I've always been against the judge and I never thought I would say this but the nerfs have kind of made me sad recently. The double flash play on mount is one of my favorite Yoru plays in the game and with the clip nerfs it just doesn't hit the same. It's so much better to use a rifle now. It could be holding like the flint still. Alright, on B. Yeah, I'm just gonna sit now. I'm gonna sit now. I'm ready. Double C. If there's one thing I'm learning about the sunset, it's that there will always be a lurker. The map is so small and it's so easy to rotate quickly, there's no reason not to. So I like to send my rotation TP extra late and try to find them. You pretty much have to approach it like you could get shot in the back at any time. Okay. Got the Cypher lurking. I can pop flash out of the smoke if you guys are down. Ready? Doing enough. Nice. Okay, I take back everything I said. Nerf the judge again. That's it for episode two of the race to 100 wins. The score is six to five and it's my lead. Click here to watch the next episode when it goes up and join us on Twitch to watch me live. Link in the description. Don't forget to check out and listed with my link in the description for your free bonus pack including weapons, soldiers, and premium content. Thanks for watching.


Hello, everyone. This is Alice Gao. In this video, I'm going to explain the answer to clicker question on slide 22 in lecture 22. So we're considering the whole more dancing game and this question asks you which one of the outcomes is a dominant strategy equilibrium, or is there even a dominant strategy equilibrium of this game? The correct answer is that dancing dancing is the only dominant strategy equilibrium Let's take a look why? So first of all notice that this game is completely symmetric Right Alice and Bob are completely symmetric So we only need to consider one of the players and the other players the analysis for the other player is Completely the same. So let's focus on Alice Let's look at how Alice wants to play the game Given a particular strategy for Bob. So Bob has two possible actions One is to stay at home and the other one is to go dancing So what happens if Bob stays at home? If Bob stays at home, we are looking at the left column right here I've highlighted that the left column and Given the left column What happens if Alice goes dancing versus Alice stays at home? So if Alice goes dancing her utility would be one as given by the matrix here If Alice stays at home, the her utility will be zero. So one is bigger than zero Therefore Alice prefers Alice prefers going dancing then stay at home What happens if Bob goes dancing? Then we're looking at this right column and Similarly we can look at what happens if Alice goes dancing her utility is two and What happens if Alice stays at home her utility is zero two is better than zero So again Alice prefers going dancing to stay at home In both cases Alice prefers going dancing, right? This means Regardless of what Bob does regardless of Bob's strategy Alice's Utility for going dancing is Better than Alice's utility of staying at home and also notice that both inequalities are striking qualities, right? so this means that Dancing is a dominant strategy for Alice because it satisfies the definition Let's recall the definition the definition should say that if dancing is a dominant strategy for Alice then Alice's utility for going dancing should be Weekly better than her utility for any other strategy Given any strategy for Bob and here that's the case because going dancing is Definitely weekly better than stay at home regardless of Bob's strategy And the second condition is that Alice should strictly prefer going dancing than stay at home for at least one strategy of Bob And in fact for this case for both strategies both actions of Bob Alice prefers going dancing than stay at home Right, so this satisfies the definition which means Dancing is a dominant strategy for Alice and because the game is completely symmetric So dancing is a dominant strategy for Bob as well Therefore dancing dancing is a dominant strategy equilibrium of this game And this is the only dominant strategy equilibrium of the game That's it for this video. Thank you very much for watching. I will see you in the next video. Bye for now


What's going on everyone? Sam here with late in sports cards. We are ripping 22 upper-deck Skybox Metal Universe Champions, hobby one box break, number 10, random pack style. We've got our 15 participants. 15 pack numbers, one through 15. Let's roll the dice. Let me go eight times on each one. Two, three, four, five, six, seven, eight. Richard H down to Will Z. Eight times on your pack number. One, two, three, four, five, six, seven, eight. Eight down to 15. That is Richard H number eight, Troy H three, Don G 13, Will Z five, Shawna M six, Will Z four, Wang J seven, Shawna M 10, Bryan L 12, William M nine, VDM with one, Shawna M 14, Peyton H 11, Bryan L two, and Will Z 15. All right, let me get those copied over really quick. All right, let me get the random clear. Sort these by number. All right, good luck, guys. Here we go. This thing just popped up and almost took my thumb off. What are we doing here? All right, so we've got packs, one through five, right here, six through 10 in the middle, and 11 through 15 on the right.  Sam Howell and Michael Jordan. Nice one there in the metal shredders. Good ol' MJ. Congrats, BD. Bryan L at number two. Good luck here, Brian. Mary Drew Jones, a cut above.  I kind of like these inserts. They're unique. They're cut above. And Jabari Smith, Fresh Foundation. Three, we've got Troy H, here's Troy. CJ Straub. That is a Joao Felix premium. Traylon Birx and Jose Pardomo. Four, Will Z. Here we go, Will. Carson Strong. Brian Acunha. It's a DJ Yuga Lele. Scoo Anderson Z-Force. Nice one there. And Katerina Makario on the metal shredders. Number five, we've got Will Z again. Good luck, Will. Blake Willis, Ray Cooper, Nolan Hickman, Michael Jordan, Joao Felix universe, and Diego Jota, metal shredders. Number six, Shauna M. Starting off our second stack here, Shauna M. Bryce McGowan's Shields. Bryce Young, Z-Force. And A, Gareth Wilson. Foundation. Number seven, Hwang J. Good luck here, Hwang. Jeremy Sohan. He's been in lab. That is a premium Walker Kessler. Nikolayovic and Oswald Paraza for the Yanks. Number eight, Richard H. Here we go, Richard Bergewine. Boy, there's looking into the future, Henry Davis-Dyka. And Jackson Holliday. Number nine, William M. Makario, Intimidation Nation. Jabari Smith Jr. Jacob Gonzalez and Alex Alcala. And number 10, rounding out our second stack is Shauna Tiger Woods. Jacob Gonzalez, Kendall Brown, and Ricardo Pepe. Starting our last stack, Peyton H at number 11. We're up here, Peyton. Griffey Pepe, premium, Breece Hall. Hey, Scoot Henderson and Walker Kessler. Fresh foundation. Number 12, there's going to be Brian L. Good luck, Brian. We're going to insert in here, Traylon Burke, Desmond Ritter. That is a Jeremy Sohan on the Z-Force. And Allen Iverson. Don G at 13. Here we go, Don.  PMG coming up. Willie T. Ribs. Kayla Harrison. PMG. Jose Perdomo. 42 of 75 on the pink. Congrats, Don. Gorgeous PMG coming up. That is awesome. Marcello Meyer and Michael Foster. We've got 14. Shauna M. Good luck, Shauna. My precious metal jam. Swanson Celestin, Johan Dotson, base, Kenneth Walker. Fresh foundation Otto, Caleb Williams. Nice one there. Congrats on that, Shauna. Hell yeah, man. That's so sweet right there. That is so sweet. And Isaiah Spiller. And 15, Will Z. Tony Pettis, Walker Kessler, Perdomo, Smith, John Pack, Will Zalatoris, Universe, and a Alex Alcala. That is going to do it for the break, guys. Congrats, PMG going to Don. We had Shauna with the Caleb Williams Auto. Appreciate the fill as always. Up next is number 11.


Hello and welcome to this session. This is Professor Farhad and this session we're going to be looking at chapter 11 bankruptcy. In the prior session we looked at chapter 7. This topic is covered in advanced accounting. It's also covered on the CPA exam direct section and indirectly on the FAR section. As always, I would like to remind you to connect with me on LinkedIn. If you don't have a LinkedIn account, please subscribe to my YouTube. I have over 1500 plus accounting, auditing and tax lectures. All my lectures are free on YouTube. Please like them, share them, put them in playlists. Let the world know about them. If you're benefiting from my lecture, it means someone else might benefit as well. This is my Instagram account. This is my Facebook account and this is my website. On my website I often have CPA offer. For example right now, Becker is offering $1,000 off for unlimited access for the CPA program. This is a limited time offer. If I was in your shoes, I will buy this course if I'm studying for my exam or if I'm still a college student where I can supplement my studies during college. Let's go ahead and get started and talk about chapter 11 bankruptcy. Now what is chapter 11? What's the difference between chapter 11 and chapter 7? In chapter 7, what we learn about is the company liquidate. The company go out of business. They go out of business. They're gone. Okay. In chapter 11, what happened is this. The creditors believe it's in their best interest to keep the business alive. So they don't want to put the business out of business because they believe there's a chance that that business might survive in the long run. So what they do is they try to work a plan. They can work the plan informally like what we talked about in the first recording, basically some sort of a contractual agreement or they can go through chapter 11 bankruptcy. So chapter 11 is a reorganization. It's not the liquidation. It's a reorganization. This is liquidation. This is chapter 7. So if a creditor of an unsolving debtor believe it can rehab the business, then they can agree to a plan for reorganization. The plan can be informal and we talked about contractual agreement earlier in the chapter. Look in the playlist or it can be formal, which goes through chapter 11. Now bear in mind, although it goes through chapter 11, the company have an exclusive right to develop its organizational plan within 120 days after which any interest that parties may propose a bankruptcy plan. So first they give the company a chance to reorganize itself. Now the court can extend this reorganization period up to 18 months. So they basically they'll give them the chance to put their act together and hopefully they can reorganize the business. Also the court is supposed to appoint a committee. The court appoint a committee of creditors holding unsecured claims. Usually the committee is composed of the largest seven creditors, obviously because they have the most most of the money involved. Also they could appoint a committee, additional committee of creditors or of stockholders. Also stockholders can be involved as well. In order to assure both creditors and stockholders are represented. Now if a committee of stockholders is appointed, again it will it will be composed of the seven largest equity security holders. So the seven largest equity holders. So what are the power and duties of the committee? Well the committee select and authorize the appointment of one or more attorneys, accountant or other agents, consultant, banker, actuarial, science, whatever is needed to perform services for the committee. They can consult with the trustee or the or the debtor or the debtor concerning the administration of the case. They can investigate the act, conduct, assets, liabilities and financial condition of the debtor, the operation of the debtor's business and desirability of the continuous of such business and any other matter relevant to the case or to the formulation of the plan. So simply put they can look into your assets, your liabilities, your financial conditions, your revenue, your expenses, anything that's relevant to the business they can investigate. They can participate in the formulation of a plan, advise those represented by the committee or of the committee's recommendation as to any plan formulated and collect and file the court acceptance of a plan. They can also request the appointment of a trustee if the trustee has not previously appointed in the case because if first there's a committee sometime the court might assign a trustee. They could request the appointment of the trustee and perform other services in the interest of the people who are represented, who are the interests of the people represented, creditors and to a second degree shareholders but creditors are the most interested. Also the court may permit the debtor to maintain possession of the assets and to conduct the affair of the business or it may appoint a trustee.  So if a trustee is appointed what is the duties of the trustee? Well be accountable for all property received obviously because that's their job to look after the interests of the creditors. Examine claims and object to the allowance of any claims that's improper. Look at the claims of the creditors whatever is proper we accept whatever is not proper we reject. Furnish information about the estate and the estate's administration to interested parties if somebody's interested what's going on with the what's the status of the case furnish this information. If the business of the debtor is authorized to be if the business of the debtor is authorized to be operated now file file with court okay periodic reports or with any governmental agency charged with the responsibility of collecting any tax arising of such operation you have to file that paperwork. If the debt or has not done so if the debtor not the debtor file with the court a list of creditors a schedule of assets liabilities and the statement of debtor's financial affair usually that's if that's if it's not but usually that is filed. File a plan of reorganization and after the confirmation of a plan file such report that are required by the court to basically make sure the paperwork is being done that's what the trustee is making administer administering the whole operation. Now what would your what would your organization plan involve what would it look like okay it may propose the alteration of legal contractual and equity interests of any class of creditors or equity security holders basically one of one of the reasons or one one reason could be the the the company might have a strong union okay and that union were demanding high salaries and that's why the company could not survive many companies go under because the union is so strong that the company cannot keep making payments so what they do they go through reorganization and as a result the contract between the union and the company will be renegotiated so that's what we mean by alter legal or contractual obligation and sometimes what you do you maybe you wipe out the common the common shareholders or you wipe out half of them or replace them what preferred you do some type of reorganization that's what that's what the whole thing is about what you would do with unsecured creditors they would generally accept a payment that's less than the face value so and they would cancel the remainder so let's assume your unsecured creditor is is a million dollar you would say i have 600 000 i'm gonna pay you and wipe out the rest basically zero the rest now bear in mind the plan must be equitable to all parties by providing for the same treatment for each claim or interest of a particular class so what you do is you take each class separately and you prorate the the benefit to the whole class so you don't treat different people differently within each class and the plan must also contain adequate means for its own execution that is it must contain specific provisions so the plan should have other conditions if this happened what would happen for example the retention of any property by the debtor when would the debtor retain any property the transfer of the property to other entities if you have a sister company when do you transfer the property if there's any merchant or consolidation of the debtor with another company what would what would we do under those circumstances for example the sale of property or the distribution of property to parties of interest you know for distributing any pop and any assets how is that going to be done or the issuance of securities of the debtor for cash property or existing securities of the debtor if we're going to be issuing securities stocks for cash if we're issuing stocks for property or stocks for other stocks how would that happen so basically we have to have a clear plan that's what worse that's what we are saying here so after the plan is filed it must be accepted by two-third in terms of amount okay and one-half which is 50 and the number of allowed claims for each class of creditors so each class of creditors you might have a senior versus secured versus unsecured two-third of the money so if we're looking at a hundred thousand we have to make sure that two-third of this sixty six thousand sixty six point six six plus and half of the creditors agree to that plan okay and two-third in the amount of the allowed interest of each of the class of stockholders again two-third of the shareholders must approve the plan in addition the court must approve the overall fairness of the plan before it will be accepted also the court would review it after the plan has been filed to make sure it is fair so this is basically chapter 11 reorganization the next thing we'll look at is once you get out of chapter 11 you'll get this fresh start we'll talk a little bit more about the fresh start if you have any questions about this topic please email me if you happen to visit my website for additional lectures please consider donating if you are studying for your CPA exam as always study hard it's worth it and see you on the other side of success


It's the season to be jolly, but I'm not feeling jolly so this for me is more like just a season. I have of course been playing a lot of games recently. My time at Sandrock, the new Super Mario RPG remake, Super Mario Brothers Wonder, Detective Pikachu and of course a lot of Harvest Moon, The Winds of Anthos. I've been playing all of these games and it's been a season. Definitely. I have a lot of mess on my table, I have a lot of things to go through so in this video I will give you my quick opinion and review on a ton of games, basically all of the games that I've been playing lately. Then I will be unboxing a ton of stuff that's just sitting here waiting to be unboxed. My channel has now reached 100,000 subscribers and I will make another dedicated video about that. Also I'm waiting for my plaque that's coming in the mail, so that's gonna be another video later. But now let's talk about the games and I can just as well start with Super Mario RPG. I got this from Nintendo Berksala. It is a remake of the old Super Nintendo game and I am sure you are either one that has already bought it and played it or you're on the fence and like you've listened to the reviews saying that it is a short game and that it's not worth their 60 dollars. I'm gonna be a person that tells you it is something just in the middle of those two opinions. First of all I think they have done a really good job with remaking this old classic and I remember this classic. I have played it all the way through probably three times and I played it on the virtual console on the Wii, so of course this game is really nostalgic to me and also it is probably nostalgic to a lot of you guys. If you have never played the original I would say this is a really good remake of that game. It captures the charm and it has improved the graphics tremendously but they have also made small fun cutscenes that look really sharp and really crisp on the screen and I've said this so many times that a lot of games are struggling on the Switch, let's be real, but first part in Nintendo titles they just never do. They are so perfectly made for what the Switch can do and this is such a game also. For me it was fun to see all of the old friends again, the old party members that I remember fondly. Bowser is really funny in this story. It's an RPG game where you are leveling up, you have this overworld map and you are progressing around on this island going from one adventure to another and for every little village and city that you come across there is like a local problem that you have to fix and have to solve and you are essentially trying to figure out what the deal is with the sword that has gone through Princess Peach's castle. So you know Bowser is not really a bad guy in this one. That's good. Bowser actually joins you in your party. Now I think this is a fun game and I think you would have a wonderful Christmas if this is your Christmas game. I recommend you get this for your friends or family, sons and daughters for Christmas and it will very likely be a success. It is not the longest game but I would still recommend it because they have simply kept all of the charm and maybe I'm talking from a nostalgic standpoint but this one is Isha Gaming Approved. I was very happy to jump back into it. I'm not done, I will be playing this more in the holidays this season to be jolly. Look at this Christmas tree, terrible. Okay the next game that is probably also going to be under a lot of Christmas trees this year. That would be Super Mario Brothers The Wonder. Now this is a side-scrolling 2D Mario. The original genre that Super Mario Brothers is known for and we have some new power-ups this time around. You can be an elephant. Even Princess Peach can be an elephant and it is adorable. It is adorable. I mean you can't argue with elephant. I have only heard good things about this. If 2D side-scrolling Mario games are your thing this will also be your thing. It is a solid Mario game. I like the overworld map. I have three cats under my table right now. They are having fun and I think you will also have fun in this game if you like that genre to begin with. I have always said it. I much more prefer 3D Super Mario games over the 2D side-scrolling games. Even having that sad I can say that this is a good one. I mean elephant Mario. Also something to give to people for Christmas. Christmas-y game. But I like this one more. I mean you know me by now I guess. Okay so another game sent over by Nintendo. We have this one Detective Pikachu Returns and I have not heard anyone on my discord talk about it. I don't think I've seen in my subscription feed on YouTube anyone talk about it in particular. I mean this one has been sliding through everyone's cracks. I'm gonna be honest with you and say that I tried to like it but I don't like it. I don't want to be too harsh but it is not my type of game. I don't know who this game is trying to cater towards. Maybe it is more for children maybe. And that I am just too old for that? I don't know. I'm just gonna say that it is not hooking me in. So this one I may actually give away as a Christmas gift maybe to some kids in the family of Isha Mann. Isha Mann's family. I don't have kids in my family. Okay watch another review. This review was terrible. And on that note Nintendo sent over some merch regarding Detective Pikachu Returns. A notebook. A key chain. A pin. Very good. Oh and while we are on it they also sent over a key chain with Super Mario RPG. And the most adorable pins ever. Look at these pins. That's for Super Mario RPG. My Christmas game. I will be playing that a lot in Christmas. I will beat it in Christmas at Christmas times. What. And a little standee. This was originally standing on something but it broke. I broke that. That was on me. Definitely on me. But cute. Also we have pins from Super Mario Brothers Wonder. You know a lot of these things has just been sitting down here for like a month. I haven't recorded a YouTube video in a month. Because I'm not feeling jolly remember. Now the truth is I haven't been feeling well. Well first of all I have been sick. And secondly of all one of my cats are missing. Been missing for a month. And I find that really difficult. Now here is a Detective Pikachu Returns mug. Thank you Nintendo for all of the things. Oh and a tote bag. Super Mario Brothers Wonder. Now we are logging into my Nintendo Switch to have a look. And perfectly honest with you guys. I am replaying Rune Factory 5 again. Started it all over again. Very good. Now let's talk a little bit about Harvest Moon The Winds of Antels. The more I play Harvest Moon The Winds of Antels the better it gets. And you know I am so thankful that I listened to one of you guys on Discord. And also in my inbox saying that you should give that game more of a chance. Do not put it away. You have to upgrade the barn. You have to open the open world. And you just have to get over the rough start of the game. And boy am I happy that I did. Because also I bought this game for neighbor Stefan and he is sweaty gaming this game. So much. And he has already progressed how far I am into the game. We are so addicted and it is such a good game. Maybe a little rough around the edges. But once you get into the actual gameplay of such a farming live sim game that it is. It is a really good game. I am having so much fun in The Winds of Antels. There are so many animals that you can tame and collect. There are so many farms that you can actually do farming on. And the world is really big. It is a really good game. Highly recommend. Now another game that I recommend but not on the Switch. My Time at Sandrock. It is a game that you should not play on the Switch. Because I have the Switch version. And I started playing it. I was like no. This is not doing it for me. The performance is terrible. It is blurry. It is stuttering. So stuttering. Unplayable and enjoyable. I was breaking my immersion all the time. I was trying to be immersed. Like now I am in this sandy town. And I am going to be a builder and help the people. And you know try to get my mindset that I am this person in Sandrock. But the immersion was so broken. Because the game was so broken. At least the Switch version. So what ended up happening was that I bought it on PlayStation 5. And now I am remote playing it. So I am still having the handheld experience of my Time at Sandrock. Which I will be talking more about in another video I think. How I am remote playing my PS5. Anyway. And now I am getting into the actual game. I am not distracted by the performance anymore. Also I heard the PC version is really good also. So what I am trying to say. Is that this is a game that you can go totally nuts in. I am in one of the crazy fan groups on Facebook. There is a crazy fan group. Where people are posting all of the crazy stuff that they are doing in my time in Sandrock. At Sandrock. And mixing up the ads in the ins. And people are posting some ridiculous stuff that they are doing in the game. And I am just like miles away from that progression. But it is essentially such an addicting game. Where you are doing crafting. Farming. And collecting. And building. Socializing. Doing quests. Collecting stuff. Decorating. All of the wonderful things. Basically. And my time at Sandrock is also the type of game that is just sucking you in. And it gets better the more and more you play. So good. So good. I still have a lot to do in that game. But that is something that I have been playing a lot. Remote play. PlayStation 5 wise. Not on the Switch. Because the Switch is the Switch. How long have I been filming 18? Wow. Some other games I am playing. I am still playing Tower of Fantasy. And I know I promised you guys a dedicated video on Tower of Fantasy later. It will happen later. I am still playing it. And I am stuck on a quest. And I am trying to figure out what to do. Maybe I will look up a guide just to progress through that quest that I am stuck on. You know what I am saying. It is the common theme of every gamer. And here is my rule. I usually never cheat in video games. Like look up guides. But when I have been stuck at one particular place for more than one hour. This is my rules. You know. If I have been stuck for more than one hour at one spot. And I am at the point where I am close to leaving the game. Then I will look up a guide to progress through that spot. And then hopefully never cheat again. I had to do that in Atelier Sophie too. I was so stuck. And then I looked up a guide. And then I progressed. And then it was all good. Relatable, isn't it? I have a few more things. I have to unbox these things. Now the Silent Hope developers. They sent me some Silent Hope merch. A t-shirt. There you go. I like the art style. The art style is good. The history was good. And another t-shirt which is just a blue version of that purple version. Thank you. Now lastly some gifts from Epic Games. Because they were happy that I worked with them recently with the Alan Wick stuff. They sent me some stuff. Monsters wear manifaces. I actually wear caps all the time. Pretty cute. You know what? This is kind of funny. And this is a secret. I hope Iserman doesn't watch this video.  And he ends up wearing them every single time.  He never knows what he is wearing. He is just like that will do. Man. A crew neck. Oh it's the thick kind of crew neck. I like that actually. Alan Wick 2 crew neck. Thick. That one is not going in Isermas's closet. It's another one of those termesses. And we have a mask. Alan Wick 2 mask. Creepy. And a clothes I think. Good. I think this is a raincoat. And do not open this. You did it. You linked all of the murders. Good. Thank you Epic Games. That was fun. Good stuff. Now my table is definitely a mess. Now thank you so much for watching this update video. And played lately. Basically. And if you are planning on picking up some Nintendo titles digitally. I would love it if you bought your eShop cards from my store. And I have a discount code now out December. Which is eShop5. Gives you a discount on everything on my store eShopGaming.com. I would appreciate it if you use this for all of your holiday purchases. Affiliate link down below. Now thank you so much for watching. And I will see you later.


Hello and welcome to nursing school explained. Today's topic is heart failure. So let's take a look at the basic physiology first. So I've drawn out a little diagram of the heart and lungs here. So we have the right atrium, right ventricle, left atrium, left ventricle, lungs in blue. Then we have the superior and inferior vena cava bringing the blood back to the heart. We have the pulmonary vasculature going to the lungs and then the aorta leaving the heart. And I'm a big fan of knowing the physiology of how the system is supposed to function. That way if something goes wrong you can really refer back to and say well I know it's supposed to function this way. Now if this is going on what kind of signs and symptoms am I going to see in this patient. So first of all the normal blood flow through the heart. Remember the blood comes back into the right atrium from the peripheral vasculature, flows through the right ventricle, goes out to the lungs, returns back in the left atrium, goes to the left ventricle and goes back out into the body. Now when the heart fails, so the heart is not able to pump efficiently then we have right or left sided heart failure. So either one of these two sides can fail. Now the most common heart failure is left sided heart failure and the most common cause for that is hypertension. So basically when there is an increased blood volume in the patient system the heart has to pump extra hard to pump all that fluid around. So if the blood pressure is elevated it takes some extra force of that left ventricle to create the cardiac output and after a while that heart muscle will wear out and it will lead to heart failure. So now if we think about it if that left ventricle is not working the blood is going to back up to where it came from which means the lungs and so the patient's complaints will be mostly shortness of breath or I also wrote down orthopnea and orthopnea basically means shortness of breath with activity, they might have some chest pain, they might feel fatigued, they might have some nocturia, they will definitely have some weight gain because they're retaining all that fluid, they might have paroxysmal nocturnal dyspnea, PND and I wrote in parentheses here pillows. So that means when the patient is sleeping at night typically we sleep flat but because there's so much workload now on the heart when the patient is flat because all the fluids are at the same plane that in order for the patient to get some relief they need to elevate the head of the bed and usually they prop themselves with extra pillows because they can breathe easier when they sleep up, when they sleep sitting upright and the term for that is paroxysmal nocturnal dyspnea and when the patient tells you I'm using three pillows at night to sleep that's usually a warning sign that there's something going on with heart failure where that fluid is backing up into the lungs and the patient might have left side heart failure and then also pink frothy sputum is another thing that we need to watch out for and that's more in the later stages so if there's so much congestion now in the lungs because the heart is not pumping the fluid through the body efficiently and it backs up into the lungs it can cause pulmonary edema and then the lungs get congested and the way that the body tries to get rid of that extra fluid from the lungs is by sputum production and there will be a little bit of bleeding in there which is why that sputum will be pink and frothy. Now for right-sided heart failure is usually most commonly caused by left-sided heart failure so if there's something going on with this ventricle the fluid backs up into the lungs eventually it'll get so bad that the lungs get so congested and then fluid is backing up all the way to the right ventricle excuse me it will have all the signs and symptoms of right-sided heart failure now another cause of right-sided heart failure is some pulmonary pathology so that can be pulmonary hypertension asbestosis any of the things that stem directly from the lungs that could cause some lung congestion and then the lungs are not really profusing and that fluid is backing up into the right side of the heart so symptoms of right-sided heart failure basically the fluid will back up and it'll get back into the systemic circulation so symptoms will be peripheral edema very typical patient while complaining of lower big complaining of lower extremity edema a sidey so now if that right side of the heart is not working and the blood is backing up into the peripheral circulation there could be fluid sitting being pushed out by the principle of basically osmosis and the oncotic pressure so that there's extra fluid collecting in the abdomen and now they'll have asides they can also have hepatosplenomegaly because again if the fluid is being backed up the organs that sit in that superior infirmenia kebab that come up the organs are the the liver and the spleen so if the fluid is backing up it might back it up into the liver and spleen making that enlarged and hepatosplenomegaly basically just means enlarged liver and spleen and then the patient can also have JVD jugular venous distention because again if that right side of the heart is not pumping efficiently fluid is going to back up and you will see that in their jugular veins