What's going on everyone? Sam here with Leighton SportsGuard, you're up in 22, 23, Panini Contenders, basketball hobby, 12 bucks, full case break, number 14, cheered random team style. Here's a look again at your random results. As always, you can find those on the website under the results tab, as well as the link that's in chat. So good luck. Let's do it. I've been loving this product this year. Oh, nice. It's stacked like that this time, so it's actually gonna be easy to take out. So that's fine with me. That works.  Or a one-on-one.  I'm in Leban auto real quick. This first round ticket of Yusuf Nurkic, big Nurk for $1.99, the crowd fighter. Say that the atrox are in. Is he honest? Jeremy's so on. First auto is Jabari Walker, premium variation rookie ticket auto for the Blazers. There's one there, Portland. Save them. We've got two 75 conference final tickets, Zion for the Pelicans. Jalen, how you doing? Variation, Jalen Green. Season ticket variation, nice. There's Ochi Vaji, nice one there. Variation rookie ticket auto. Grass Jazz, Utah, same, eh? There you go, buddy. On-card Ochi. I'm gonna change my name to Ochi. It's a pretty hard name. Announce it or? So when they actually look at you they'll be like, there's an Ochi. Yeah, it looks like an Ochi. Ochi. We got ticket stub Kyrie. Nice, four of 11. Nice one there for the Nets. Tier two hit for Chris D. Sweet shots. Buddy Hill, nice one there. Zion, superstars. We've got a Corey Kispert, soft moor contenders to 99 for the Wizards. Gonzaga legend, mustache legend, facial hair legend. You're like one of the members of the thumbnail today for us. Who's the D-Bax player? 249, that's gonna be RJ Barrett. It's actually what's it called? That's Corbin Carroll. It's the Panthers player. It would be... Who was that? Cortland Fittingen. They're recognizing him. Chet Holmgren, I honestly did not know he was on the Panthers either. Tomorrow we've got Beno Udre as well in a magic uniform. Got Malachi Bram, what is that? Magic legend, Beno Udre. I don't remember to be honest. I honestly, if you told me that he spent his entire career with the Titans and retired, I'd be like, you're right. It looked like he was there when they were in the Super Bowl. So that's like what, 2015? Around that time? Yeah, no, that's true Zach, that's true. And it goes up, if he makes the Hall of Fame, it goes up to a million. That is Kwai Leonard to 99, semi-final, stick it. No, I just said Cortland Fittingen. She dug deep to find a Cortland Fittingen picture that really threw us off. RJ Barrett. Yeah, I know. That is Jaylen Durin to 99. Playoff ticket, auto for the Pistons. Nice one there. Detroit, D-Town picking up a Jaylen Durin. How are you, Durin? The spotlight is? Nice. I'm going to go pull up from the bowman. The blaster at Walmart. There's RJ Barrett to 249. Anthony Edwards, Superstars. Were they reached out to the Dynasty Hanger fans? The flawless mega boxes. We've got Jibari Smith. That is a Trevor Keele's variation rookie ticket auto for the mix. There you go, New York. Go, New York, go, New York, go. It's only down so I don't know. One of the bounties is that you have to pick either or. Really? Yeah. I did not know that. Yeah, if you read the fine print, it's just either or. Wow. Give me the 250. Exactly, and it's like, I'll take the 250 because. That's worth so much more now.  That is the modest subbonus to 199. I know exactly after literally outplayed dad, who is what, 10-time gold glover? And like still after what, three or four years has not made it either. Variation moves to Diabata for the Clippers. Got a Trey Young. MVP contenders, 10 of 10 for the Hawks. There we go. Will M with that last spot mojo. That is awesome. Ice Trey, baby. Hell yeah, man. I would say probably. It's the first one I've pulled, and then it's gold. That's really quick to that card. We've got RJ Barrett to 249. Walker, Kessler, Rookie, Deer, Contenders, Superstar, Luca. There's just up there, Mark. Oh, we got something coming up here. We got something coming up here. Sohan. That is going to be gold. Wendell Moore Jr. Two golds to 10. That is going to be six of 10 on the premium. They keep throwing your vote out. They keep crumpling it up and throwing it in the trash every time you mail it in. Ice won their T-Wolves. Sam, A, I'm too, too, hit. Honestly, that sounds like it might be the case, Shane. It's wild that that's the case. I think he should be in too, personally. Like with some of the other people that have been getting in, like Andrew Jones' is there. By that man. It's true. James Wiseman, playoff ticket to a 249. Lottery ticket, Keegan-Emery. There's a lot of other guys with horse, stats, all that. Yeah, that are just friends with guys on a veteran committee. Steph Curry, like Harold Baines, really. We've got a Ryan Rollins, three of 49 finals ticket. Nice auto there for the Warriors, Ryan Rollins. That's on that golden state. Looks like there's a little schmack on that. Let's end that empty box and wrap with the Warriors' spot. About that golden state. A little bit of schmack on that, though. Got one more break after this. Full case of Bowman Jumbo again on the fly. That is 199, Anthony Edwards. And that'll do it for the daytime portion of today. Got four of it, it's breaking at night, as well as Kyle with some personals. Matt might sell up some spots over on, I'm assuming probably not, honestly, over on the baseball channel. Oseman Jeng, variation. That is Redemption. Caleb Houston, rookie season ticket for the Magic. That's one there, Orlando. Orlando. Caleb Houston, what do you like more? Oh, stick it in. Oh, okay, I got some over here. Next box. We've got Anthony Edwards, two 99. Semi-finals ticket. We might have another premium coming up. Trey Yung Superstar is a Kennedy Chandler. Two 99 playoff ticket, just a playoff ticket. The foil. Nice one there for the Grizzlies. Cheng S with Memphis. What's up? Not good. There's a playoff ticket. Damian Lillard, it's a 249. What a blazes. That is Zion with the Pelicans. We've got AJ Griffin. Nice one there, playoff ticket. 26 of 99, steal the draft AJ Griffin. Nice one again, Hawks. Hawks killing it as a tier two. There you go, Will. That last spot, Mojo there. Semi-finals ticket. Collin Sexton to 99 for the Jazz. Got Otto, that is Ponds Wagner. Sophomore contenders 25 of 25. There you go, Magic. Second-year fronds. This one is Orlando Johnathan. This is Anthony Edwards, two 249. O'Chag Bodger. Superstar's Jock. And some base on that. Again, last few cards are always going to be base on this as well. Variation, Wendell Moore Jr. The Timberwolves. We've got a Christian Coloco. Rookie ticket Otto on card for the Raptors. There you go, Toronto. Christian Coloco. It's too bad, Scotty Barnes is going to give Coloco his number. So Coloco could be number four. Call him Four-Loco. That'd be cool, right? Wendell, that'd be quite the nickname. Pickles Four-Loco. Pascal Siakam to 99, semi-finals ticket. There's Luca, Jeremy Sohan. We've got legendary contenders. Michael Loa-Candy, the Candyman to 199. There we go, Clippers. Let's go, dude. The Candyman. Michael Loa-Candy. Candyman. Wow. Adam Morrison as Otto is in this, too. Right? That is, I fold one out of 25. Joel Embiid to 249, playoff ticket. I was like shocked. I was like sitting there just staring at the card. We've got nice Chet Holmgren to 99. Jared H. in the Thunder. Congrats, man, on the playoff ticket. That's nasty. Let's go. Congrats. See you there, Jared H. Picking up the Chet. I'll get that magged up for you, my friend. Base and base. Now, that's just a Deontay Murray, premium ticket. And base. We've got ourselves a Paul George ticket variation. Kevin Durant, Superstar. Hello, rookie of the year. And wow, Jabari Smith Jr. to 99. Now, going to the Rockets. Sam A. Back to back. What, the number two and three pick right there to 99? Not too bad. We take those all day long. Congrats on that one, Sam, with the Rockets. Great case so far. The RJ Barrett to 199, first round ticket. I do not have fond memories of the Candyman. I was going to say, I don't think any Clippers fan is going to have fond memories of the Candyman. There's Chris Duarte, sophomore contenders. Our contenders auto ties, that is his second year. For the Pacers to 199, different set though. I do apologize for that, Mark, too. That was a tough stretch right there for the Clips. Kyrie Irvin to 249. And base. Here's Josh Giddy to 249. Here's the whole mellow. Back to ice. That is Tyler Hero, 15 of 25. One off jersey number for the Heat. There you go, Heat. We've got a Johnny Davis rookie ticket auto for the Wizards on card. Wisconsin Badger legend. Variation is Russell Westbrook. The Lakers, Palo rookie of the year contenders. That is licensed to dominate Zion Williamson. Nice one there, the super short print. Congrats, Pelicans. Salisbury, South Carolina. Twitter, Zion Williams. I could just throw that where you got it. Another redemption, that is gonna be Kevin Durant. It is Peyton Watson, rookie season ticket going to Denver. There you go, nuggets. Very nice, congrats at Denver and base. Just make sure to tag the Redemption with the team. Oh good. Yeah, I got you. We've got a final ticket to 49, Evan Mobley for the Cavaliers. Not this year, Evan. What's up? Tried. Tried. There's Malcolm Brogdon, sixth man of the year to 249. It's Nicola Jovic for the Heat rookie ticket auto. Nice one there at Miami. Got Deem, Dalla, season ticket. Superstar Zion, Laurie Markman. So we've got our permit to dominate. That is gonna be, no, another license to dominate is Devin Booker. Nice, Devin Book. That's his, is it from Michigan? I didn't know that. Devin Book. Just Twitter.  That is another redemption. Peyton Watson again, rookie variation season ticket. So we got the base and the variation. Nice one there again at Denver. Nuggets, Peyton Watson. Last box and break. Good luck everybody. See what we got. Christian Coloco for the Raptors. Nice one there. Got DeWade. Mellow, that is Jeremy Sohan. Base rookie ticket auto. There you go. Eddie with the Spurs. Jeremy at Sohan. Nice one there. Ticket stub, Yusuf Nerkic, 20 of 27. Dang, Ochaik Baji. Bahi. That is Superstar's coming around. And a Paolo rookie of the year contender base. And Tyrese Martin for the Hawks. Rookie ticket auto. Should be our final auto of the break right there. Congrats, Atlanta.  Playoff ticket. That is Kelvin Johnson to 249. Nice base and base. All right guys, do a quick recap here. Thanks, sir. I'll take those two license dominates. Thanks, sir. All right, we got Zion licensed to dominate as well as Devin Booker. Tyrese Martin, Jeremy Sohan. That is going to be Peyton Watson for the Nuggets. Caleb Houston for the Magic. And Peyton Watson again for the Nuggets. Nicola Yovitch. Johnny Davis. Christian Colotto. Trevor Kiehl's. Malachi Baranam. Corey Kispert. Ochaik Baji. Michael Alowa Candy. Chris Duarte. Jabari Walker. AJ Griffin. Kennedy Chandler. Ryan Rollins. Jaylin Durin. Wendelmore Jr. Gold. Frans Baji. We've got ourselves a Jabari Smith Jr. to 99 for the Rockets. It's going to be a Chet Holmgren to 99 for the Thunder and a 10 of 10 Trey Young MVP contenders auto for the Hawks. We'll do a break, guys. Thanks again for the fill. Next up, our final break of the day are Bowman Jumbo Divisional.


Welcome back everyone. We will continue studying about spirit senses and how we perceive God's communication. Before we get into our lesson, Divya had a question in the chat section. She says, how to train ourselves in these, in other words, how does one identify when this happens. So, Divya, it's part of the chapter here. We'll get into it. Just give me maybe about five minutes. I'll touch upon the sense of taste, the sense of smell and then get into training of our senses. So, we've so far understood feelings, seeing, hearing and right now we talk about the sense of taste. And yeah, if it's smell, touch is another sense that we have not yet spoken about. So, there are scriptures like, oh, taste and see that the Lord is good. How can we taste God? The meaning, the actual meaning of this isn't the spirit we can.  So, our spirit is actually, you know, it has that ability of taste. And that's why you have scriptures like that even Ezekiel, he says, you know, God told him that you spill your stomach with the scroll, okay?  So, you see that he tasted the scroll which God gave him to eat or he received the message of God and it was in this form. So, that is a spiritual experience. Now, talking about touch, right? Or smell, remember smell, we are the aroma of Christ. How can we be an aroma? We, you know, are, we are not particles in the air but it's a spiritual sense that one can have where they can smell the fragrance, you know, of the presence of God or the child of God. So, in this manner one can perceive, smell or touch. Now, Jesus, you recall, in Mark, chapter 5, when the lady comes, she touches Jesus with the faith. He says, who touched me? Was he talking about physical touch? Not really because so many people must have been falling on him and touching him on this, in the crowd, in the crowd, you know, on the street. But he did not perceive that as touch. He is specifically telling the lady who touched me because she approached Jesus with faith and this is how the spirit perceives communication from God. So, we have to be ready to receive what God is saying. Now, coming to the question that Divya asked, she said, how can we train our senses? How can we use this, you know, to walk with the Lord and be a blessing to other people? So, what we must recognize? The first is we must recognize that all of us as believers, we, definitely we have a spirit, right? That's how God has created us. So, we are tripartite being, we have a spirit man and we must recognize that all us spirits have these capabilities. So, somewhere in our heads, we think, oh, somebody who is, you know, maybe in the five-fold ministry office, they can pick it up, I can't pick it up. But that's not true. Every believer can pick it up because we all have a spirit. All our spirits have the five senses or even more than that. So, first thing is I must recognize I have been designed to hear from God. Now, if I convince myself that I can't hear, that's, you know, nobody can help. But it's a reality that all of us have been designed to hear from God. So, that's the first thing that we must settle in our minds. The second thing that we must settle in our minds is that God communicates. God speaks. Will God want to speak to me? Yes, of course.  And I, now that we know of the different channels through which he communicates, we must be open. So, when I'm praying, I must do something like try to perceive through one of these ways. You know, am I feeling something? Am I seeing something? Is there a word which is being dropped in my spirit? Or am I seeing a word, you know, or a sentence or something in my spirit? Am I able to grasp that? Or can I taste? Can I sense? So, I have to have that initiative. Do think that, okay, God will say something. So, I'm ready to receive it. So, have that kind of an attitude when we pray, when we approach God. So, each time we do this, where we know that, yes, I'm capable of listening, God speaks through all these channels and I am ready to receive, you'll notice that you begin to hear more from God, okay. And you, and as you hear from God, it just becomes a whole lot easier to pick up the communication as you go forward. So, it's like, you know, when somebody calls us on the phone for the first time, we don't know their voice that much, but we speak to them. But if that person is regularly calling us, okay, over a period of time, what happens? We pick up the call, even if we don't know, I mean, if it's not a mobile phone and if it's like your regular telephone as well, when you, as the moment we pick it up, we say, hey, Shanti, hey, John, because we are so familiar with the voice of that person. So, it's very similar when it comes to hearing God's voice, the more we practice or the more we, you know, receive his communication, the easier it becomes to pick up more communication. And that's what Hebrews chapter five, you know, verse 13 and 14, it says, it says something like those who are full, are a full age, that is who by reason of use, notice, practice by reason of use have exercised their senses to discern both good and evil. So, believer who's growing in the Lord, one of the things that this growing believer needs to do is to exercise their senses. And that simply means putting it into practice. We are listening, listening, listening, hearing, perceiving, receiving the message of God. So, the more you tend to do it when the message of the Lord comes, then what happens? We just know that, hey, this is God's voice, you know, it's not any other, you know, because initially, when somebody starts off listening or perceiving, you know, the prophetic message from God, there can be doubts where we say, maybe I'm making it up, it's coming from within me, or is it really from God? So, initially, that is normal. But now that we know in the Bible, see, it's nothing, it's common for God to speak. And especially when I pray and I say, Lord, speak to me, then God speaks. And it's not my own voice that I'm hearing. So, in this manner, I start to listen, right? And remember what we said earlier? We said, there is also a process in that table, we saw how the message comes. And then I have to employ my soul, my mind, my will, my emotions, where I'm ascending. Okay, this is what the word says. This is what the Spirit is saying. Is it an agreement with the Word of God? Okay, so all that is going on. And that will help me. So, that is also part of the practice. That is also part of exercising the senses. So, then my soul part will give me an outcome and say, actually, yes, this is good. This is from the Lord. And you can use it. You can share this message. So, as often as I do this, hear from God, process it, release it, hear from God, process. What is happening? What Hebrews 5 verse 13 and 14 said, exercise your senses. And the more you exercise, the better it gets, the faster it gets, the quicker it gets. So, that is the training process. Many times, when we hear preachers say, train your spirit, spirit man, develop your spirit man. So, one part is also to train it in this way, right? First of all, train it with the Word so that you are able to then accurately receive a prophetic message, okay, and process it, and then be able to release it. So, that is the way we would train our senses. So, it is a continuous learning process. Now, can mistakes happen? Yeah, sometimes mistakes can happen in our perception of the, see the gift is pure. I have already told us that. But when it comes to the human vessel, maybe in terms of our interpretation, sometimes a mistake may happen. But we learn from it. So, the next time we prophesy, we should be aware of maybe all the loopholes of the past and try to get better at it, improve ourselves. And that's the way to become more and more accurate as far as hearing the voice of God is concerned, okay? And a couple of things that can hinder it, if we recall the passage about the sower, okay? The sower sowing the seed and some seed which falls on good ground bears much fruit. But then the seed which falls on other places, it's not able to bear fruit because there are hindrances such as weeds, stones, dirt.  Mark chapter 4 verse 19, it describes as the cares of the world, the deceitfulness of riches and the lust for other things. So, when we are distracted, in other words, you can just put it into the box of distraction. There are many distractions for all of us. When our mind is pulled into several directions, we are not at peace. Even if God is speaking, we are not able to perceive it. So, distractions can be a hindrance. Stones, in Mark chapter 4 verse 17, it is described as afflictions and persecutions. So, you know, sometimes when we are going through a law, because of all the issues, different things that are going on and discouragement and disappointment, if we are not careful, that can also affect our hearing from God, okay? So, the Bible warns us and it says that, don't let it hinder you. Even going through persecutions, difficulties for the Lord, don't let that be a hindrance to hearing the voice of God. Dirt is, you know, different things from the world that affect our mind. That's why the Bible calls us to renew our minds. So, how do we cleanse ourselves on a daily basis from the influences of the world washing by the water? That's how the Lord Jesus cleanses His bride, His church, isn't it? So, when we renew our minds, even that will remove the filth that the world puts on us and we can better hear God. So, these would be the hindrances that will stop us from hearing from God. And, you know, sometimes the challenge is that we put God in a box and we assume that He will speak in a certain way. For example, you know, I pray for somebody and then I think that, okay, you know, God is going to speak and He will give me a picture. As I start praying, if I don't get a picture, I'm disappointed. You see, what's happening there? I have an assumption that God always speaks like this. But it may not be the case. He may want to, you know, speak to us through a certain spirit sense of feeling in that moment. Or, you know, in some other way, we might think that God will only speak through a certain person. But God can speak, you know, in scripture you find that the donkey spoke and brought a message from God. So, we have to be open to the communication of God, the method through which it comes and the means or the person through which it might come. So, if we are not open, even then, there can be a hindrance because, you know, we are waiting on the Lord to speak in a certain way and then He speaks in a completely different way. So, in 1 Kings chapter 19, verses 11 and 12, you know, God speaks to Elijah. And when He speaks to Elijah, it says that, you know, Elijah was listening to what God was saying and the Lord was not in the wind. And after the wind and earthquake, but the Lord was not in the earthquake. And after the earthquake of fire, but the Lord was not in the fire. And after the fire is still small voice. So, finally, what did God use to speak to Elijah? The still small voice. So, another thing that we usually say is, we must be open to the supernatural and not necessarily to the spectacular because what a lot of believers end up doing is we feel that if God is speaking, it should be, it should accompany lightning and thunder and action and drama and you know, that's when God is actually spoken to me. What if it doesn't? What if God just gives a word like Philip God, overtake the chariot? That's all. So, it's more to do with our assumptions about how God is supposed to speak that gets us stuck. But when we are open all the time, see even a little child, we are praying about something, but that message can come through that little child, you know, so it can come anyway. So, as a believer, I'm open all the time, all the time, not just when I'm praying, but all the time. What is God saying? What is God saying through the circumstance? What is God saying through this conversation? You know, so then when you're in that state, you can pick up what God actually wants for us. So, let me pause here. Any comments before we go ahead? We will take some time to pray. I'm here from God. And then I will go to chapter 10. Yes. Yes, Divya. Yeah, thank you, Pastor. I was just thinking about when God speaks in those small sentences just it might not be spectacular, but just in small sentences. Like if the person who hears, it doesn't obey. We don't know, because in the Bible it never records a person who would disobeyed like that voice of God. But I mean to say the major people. So, in our lives, like when God is it like we, if we disobey or if we do not listen, then God doesn't speak or is it like as we obey him, he speaks more. Is it like that? So, I just want to know how God deals with that. Okay. Yes, Divya. It's the way you said it is correct that when we obey God, we will notice that we are hearing more. But when we are disobedient, we'll notice that the communication seems to be lesser. Because why would God want to give us a message if we are not going to use it? Right? So, yes, there is that danger of gradually having reduced communication and no communication. A classic example would be Saul in the Old Testament who disobeyed God and he went away from the covering of God's protection. But we are under the new covenant now. And so, as you know, regular normal believers, for us, the advantage is that through the cross, we are also under grace. And so, when you look at passages like Hebrews 7, 25, the Lord, he saves to the uttermost. That means that God's rope is very long. His patience is very long, long suffering. So, he will give us 14 chances and be gracious to us, be ready to restore us, all that. But as the Bible says, right, Hebrews 6, Hebrews 10, that if we push it to the limit, if a believer pushes it to the limit, if they fall away from the faith and they live a life of disobedience where they have treated the blood of Jesus as having no value and, you know, the cross, they have dishonored the cross, then, yes, they will ultimately go to a place where they no longer are able to perceive what God is saying. But please know that this is a warning, yes, but for a normal believer who's trying to have daily accounts with God and, you know, confess their sins and all, you don't really have to be worried too much that, hey, will I go into that? That's a very rare occurrence, very rare occurrence. Yeah, yeah, got it, Master. So, I was just thinking of maybe sometimes when God asks us to, you know, maybe go share the gospel with someone, it's like a prompting, right? I don't know whether it's an audible voice, but maybe a prompting to go share the gospel. And if we do not do that, so I'm just wanting to know, like, as you said, yeah, I understood, as you said, like the frequency and even the perception of when God speaks to understand it, even that can reduce. That's true. Gradually, yeah. Gradually, yeah. God will give us many chances, but, you know, despite that, if we are continuing with disobedience, then yes, the frequency will come down. So, yeah, it's like that parable also, you know, the talents. Oh, yeah. Yeah, so we must, the gift, the prompting gift, it's like that. It's like a talent. When we stored it well, we put it to use, it becomes a blessing to people, then it increases on its own. Yeah, got it. Got it. Thank you first. Yeah, sure, sure. Yeah. Any other thoughts before we take some time to pray? Can I make a comment? Yes, please. Yes, brother. Yeah, thank you, Pastor. I was just listening when you were talking about hearing from God and scanning his voice. It's a matter of exercise, and I just want to say, I like the illustration you gave about the telephone conversation at times, and that's very true. When somebody begins to talk to you the first time, you cannot properly grasp his voice, but if over time, the person continues to talk to him, to sorry to you, you can completely know and be able to. So, this is Isaac speaking. I like that illustration. Thank you very much. Praise God. Yeah, happy to know and thank you for sharing, brother Isaac. Yeah, so that's how we build our familiarity and train our human spirit. So, let's go ahead. We will take some time to pray for each other. And in the last class, when we did chapter eight, where I talked about the three simple steps that one can take in order to prophesy, and that is to pray, to perceive, and then prophesy. So, what we will do is we will pray first, ask God, God, speak to me, speak to me about this person or speak to me about somebody, whatever, you just pray. And after that, the Lord, as He puts things in your heart in answer to our prayer, we have to pick it up. So, what would He communicate like everything that I shared just now? Maybe we feel something in our spirit man, or we, you know, see something or hear something. It could be any form of communication. And the third one is to prophesy, prophesy is to share it, release it. Okay, so let's try and do this. This will be very helpful. And after that, when we do chapter 10, you probably will have more questions. All right, so let's do this. I would encourage us for the next one minute to just create the spirit. Okay, just a moment. Success has a question. Yes, brother. Good morning, everybody. I'm sorry, it's not actually a question. I want to ask, is there any, you know, in our course that you can, with students and lecturers, perhaps time to pray together for maybe like 30 minutes or 20 minutes as case may be? We do have, like, personally, if some students request for a time like that, then there is a possibility. Okay, so I would, I mean, just if you can email me a request, let me know and then I can see what could be done. Is that okay? It's okay. Thank you. I will email you. Sure. Sure. Wonderful. Yes. All right. Then let's, let's, I was saying, let's take a minute to pray in the spirit.  Heavenly Father, we thank you for your word. We thank you that, Lord, the gifts of the Holy Spirit are for today, the gifts of the Holy Spirit are for every believer. Thank you, Lord, that, Lord, you speak to us, Father God, through the gift of prophecy. And Father, at this time we pray in the name of Jesus that, Lord, you will put a word, Lord, in each of our hearts, Father. Yes, Lord, each of our hearts, Father God, Lord, speak to us, Father, speak to us, Lord, speak to us for ourselves, speak to us for each other. Speak to us, Lord, for the people in our lives, Father God, and Lord, cause us, Father God, to be a blessing in Jesus' name, we pray. Amen. Amen. So class, I want to encourage you, we are going to take maybe 30 seconds, 40 seconds to just perceive. So we will all be quiet, silent, you pick up what the Lord is putting in your spirit.  But if there are people who feel like, hey, I think I have something, you can either post it in the chat or unmute and you can do share it. Yes, Sivya, please go ahead. Yeah, Pastor, it was just like a worship kind of came to me, like an amazing God. This was the term and I was reminded of the song, Indescribable by Chris Tomlin. And I'm not sure whether like a finger of God, something like that. Yeah, I don't know the connection. Yeah, but maybe, yeah, I was feeling this presence, like, very strongly in the fingers. So that's why I said finger of God, I didn't hear anything on that. But yeah, but the song was indescribable by Chris Tomlin. Yeah. Okay, so when you when you're saying that you had this amazing God and amazing love and indescribable, how did you how did you perceive it? How did you get it? Like, did you see those words? No, I started actually, I was reminded of this song, Amazing God was a term. And I was instantly reminded of this song by Chris Tomlin. It goes like indescribable, uncontainable. I can put the lyrics over here. Yeah, so it and the and strong sense of God's presence in my fingers. So I, I'm not sure what is the connection. But these three things were coming. Okay, so yeah, so anyway, you shared the different parts of what you perceived. So that is good. Now, we could if someone has an interpretation for what Divya has perceived, you may share that, but I will move on to what Jefina has posted here in the chat. She says, I saw Sam 119 in verse three, which says, you want to go ahead and say this, Jefina? That'll be better. Okay. Yeah. So, as I started frame, I just want to start and I felt that there is something over this that I was to share for this and I also was clearly sensed that it was three. So then I saw it's the verse was and before that, even before starting, I saw the hand of God pulling some hands towards this. I was just the number how the angel of God pulled load when he was in the room. Even when he was given an instruction to go out, there is a verse that say the angels literally pulled him towards the way. So I was just reminded of it. And then I saw this verse and it says that they do not compromise with people and they were one meaning. So I just felt like this batch should be some this batch should be a batch where we don't compromise sometimes, but we keep holding on to him and keep walking with him and God is always there to pull us towards those ways. That's it. Yeah. Thank you. Thank you, Jenina. So, when you say that I saw Psalm 119 verse 3, how did you perceive it? Just want to understand. So, as I told, I just started playing in terms of the very first thing that came to mind. And then, you know, it's kind of the very long song. I can't say the long song here.  So, and then I just kept pushing forward. So then I didn't see verse 3. I saw this image of God pulling us. So, I was just wondering what it might be. And I think I just kept asking God through the process, like what he wants to say, what. So that's all that I did. I think he just connected the thoughts. So, and then I saw number three. I was able to see number three. I think Psalm 119, I felt it on my mind, but I saw the number three. So, it was like that. So, then when I saw the word, I was able to connect it with the image and God just let me to pray for everyone here. And he's really about who's who's who. Okay. Yes. Thank you, Trevina. So, you so again, you know, a nice thing is coming through in what you're sharing. So, we can't compartmentalize.  So, but you got the message, right? So, in different ways, the message actually came to you. So, that's nice. And thank you, Divya and Trevina for sharing. If there's anyone who has a word you may please share. Otherwise, we're going to pray again. Okay. And then we'll perceive again. All right. So, there were two things that I perceived. I just felt like there is revelation. Like, there was a dark place, but through the word of God, there is now revelation regarding certain matters. And that is one thing I saw. And I felt like somebody is praying for wisdom. And God is giving them wisdom to simplify, wisdom to simplify some situation. So, if anyone relates to that, you could please post it in the chat and let me know. What we will do now is we will pray for one person. So, is there any volunteer who needs prayer? You please say that they, you know, pray for me. And then we'll all pray for you. And we'll see what the Lord may speak for you. Yes, pray for me. Okay. That's great, Brother Paul. He spoke first. So, we are all going to pray for Brother Paul right now. Let's do that. Okay. I will mute myself, take a couple of moments to just pray. And if you have a word for him, let's go ahead and share it. And Brother Paul, what you can do is once everyone has shared, you can tell us, you know, what was relevant, what was applicable. If something was not applicable, that's also fine. Okay. So, that's what we're going to do. Okay. Sure. Let's all right, class. So, if you have a word for Paul here, please go ahead, share it. I just sense this part when Ananias was praying over Saul, this word that God spoke to Ananias to tell Saul, saying, you are a Chosen vessel. So, this suddenly sends that scenario in my mind that one person is going and praying for Saul and reveals this word. So, I just quickly turned this issue in. Acts chapter nine was 15. For he is a Chosen vessel of mine to bear my name before Gentiles, kings, and the children of Israel. So, this word Chosen vessel to encourage as a word of encouragement. Thank you. Thank you. Thank you, John. Yes. Yes. Yes. Success. Please go ahead. Praise God. Mr. Paul, you have been chosen to worship God for a while, in festive worship.  And the nations who are running towards you in tears by the means of lifting their hands to heaven. Take time to worship God. You will see the heart pulling of God. Very clear. Thank you. Thank you. Thank you. Success. Thank you for that word. Paul, anyone else? Anything else that you saw? So, Brother Paul, I just got this sense of bones, some issue with the bones that hinder the walking that the Lord is healing that. And I also got this word in my spirit saying daughter. So, I don't know if you or someone you know is concerned about their daughter, praying for their daughter for a certain matter, but that also came to me. So, now we let Paul speak. Do let us know if the words that you heard, does it relate to you, does it make sense to you? Please share with us. Thank you, Pastor. Maybe you repeat yours. The rest I got, but yours I did not get. Well, maybe first repeat again. Yeah, sure. So, I was saying that I had a sense of bones. Okay, bones are actually more specifically joints as if there's prayer happening for somebody who is unable to walk because of some issues with the bones, joints. So, like the Lord is healing them. That's what I felt. And I also felt the word daughter.  And I was reminded of that. Those were the two things. Okay, thank you. I get you now. Starting with the first one where John Paul said he got the word from Acts chapter 9 verse 15. Yes, I've been having that calling. There have been called God spoke to me to be an evangelist. So, it makes that one also relevant. And then also what success talk about worshipping gods and the nations who are crying. Yes, it still relates to that international calling. God has ever spoken to me to do that. So, as he said, I should worship God says I will continue worshipping God for that to come to pass. And then, Pastor, what you talk about the bones and the joints. I don't know very much, but there is a woman whom I know is in our church. She is on her way here. She was our family friend. All the time when I look at her, I feel a burden. I feel a burden. I feel like if God one day could even touch me, I go and touch those bones and then she begin walking. It would be good. That is what has ever been in my mind. Then about the daughter. We have one choir member. She has marriage issues. She got married to a Muslim and she's almost got stuck there. She's in the body. She's a Christian and the Muslim man is unfaithful and now the family was trying now to see the way of rescuing her. And what I did, I offered a hand to help them. They come from another district to come and see how they can help this daughter of theirs. She has also financial issues, so I offered financial help to this Saturday. They will come and meet the daughter, meet the church, meet the Asban to see how they can help her. So those are the few things that are relevant to the message. Thank you. Yes, thank you. Thank you brother Paul for sharing. Really blessed to know that these words connected to you. We'll just take a moment to thank the Lord. Let's pray together. Heavenly Father, we thank you Lord. We thank you that you speak to us. We thank you that you know us, oh God, through and through. And for each word Lord that has been spoken over Paul this morning, Father, we believe that it has come with its power, God and Lord. In each of those circumstances, situations, Lord, we release the mighty presence of God, the mighty power of God and Lord, we ask for a turn around, oh God. We ask for your anointing to make manifest, Father God. Open doors and healing and deliverance, oh God. And Father, let your name be glorified, Father God. And Lord, we pray your strength and comfort, Lord, upon Paul and his family, Father. Thank you Lord for each one who brought the word as well. We give you the glory and the honor, Father. In Jesus' name we pray. Amen. Amen. Amen. So, you know, we just want to continue to praise and thank God for the words that we have received today. I know we wish we could, we could all be in person and maybe have half a day to do this because it's just so wonderful to hear from the Lord and to bless each other. I see Brother Abu Beker is also requesting. I want you to pray for me. So, there are only two minutes because he's requested. Let's quickly pray and if there's a word, let's share. We'll close the class with that today. We'll go into interpretation of prophecy in the next class. Okay. And also one quick note, transces. I think we've listed out enough transces. So, I'm just leaving it at that because I told you all that I'll share more but I think we've already listed enough. So, let's pray for Abu Beker and please share if you have a word for him. Yes. Yes. So, please feel free. You can post, type it on the chat or unmute and share. So, Abu Beker, I feel like the sense I had is season of preparation. Okay. So, season of preparation. Okay. Anything else? I was reminded of Nathaniel, John chapter one where Jesus tells him that there is when he was under the victory, I saw you. This is the man in Israel. There is no guy. Yeah. That was a portion that I was reminded of. I'm not sure if it's relevant. Yeah. But yeah, this is what I was reminded. Yes. Thank you. Thank you, Thavia. Anyone else? Well, so I was just praying for him and I saw a lamp on half a night and I saw on Ahalia chapter 13 verse 9. So, basically what happens here is everything is being restored. So, the house of God is being restored. So, I just felt like he's going to be a night where he will tell us whatever he's deciding towards. I don't know much about him. What he's deciding towards. He's going to be a reformer. He's going to be a life that makes things, make people feel that these are things you should not do. He will be someone who will add things to the house of God, who will shine much more brighter. So, Abubak, I hope that you are able to relate to it and that it's a blessing to you. You may share maybe in the next class if that's okay with you. We'll wrap up for now and I want to request one of us here to please pray and be close after that. Thank you so much, that system of declaration is very very correct. Praise God. System of declaration, I know I'm preparing for great things and I know so this is a confirmation that God is in it. So, thank you so much. I really appreciate you. Thank you, Jevenna. I can't hear you clearly, Jevenna. Maybe you can help me to put it on a sharp note. So, I can't hear you clearly. So, if you can help me to put it on a sharp note, so I'll be able to read it there. So, thank you so much. Yeah, thank you for the confirmation, Abubak. So, we'll pray and close now. Could somebody lead a prayer? Let's pray. Father Almighty King of Glory, we thank you for this session. We thank you for the words of revelation. We thank you for your shown, your mighty hand upon us. You have shown us our destiny. You showed us a plan that you have for us. Father, we now thank you that let them come into fulfillment. We pray that you continue using this class to reveal to us our destiny. We pray and declare only the name of the Father, the Son, and the Holy Spirit. Amen. Amen. Amen. Thank you, Brother Paul. And one last request, if you can use the stream page on Google Classroom and post words for each other. Even that will be amazing. That's a way that you can practice.  So, please feel free. You can use the stream page and leave words of prophecy for each other. So, be close today. We'll come back again next week and continue in the prophetic ministry. Thank you, everyone. God bless you. Be a blessing to others. See you. Bye for now. Thank you. Thank you. Bye.


Hi everyone, my name is Kyle Knapp and I'm a software developer at Amazon Web Services where I primarily focus on developing Python client-side tooling such as AWS CLI, AWS SDK for Python, also known as Bota 3, and a Python micro framework for developing serverless applications known as Chalice. And today what I'm going to talk to you about is how you can go about writing server-side applications using Chalice. To start what I want to do is go over an outline of what I'm going to talk about. First I'm going to give an introduction into serverless applications, mainly talk about what they are, why you care about them. I'll give an introduction to Chalice, so getting started with Chalice and some of the core concepts. And then I'm going to go ahead and actually have a sample application show you how you can build it from the ground up using Chalice features. So before I talk about what exactly a serverless application is, let me talk about why you care about it and the benefits of serverless applications. To start, serverless applications mean you're not managing or provisioning servers, so that's less of a DevOps load for you.  And finally, you get scalability. So in terms of serverless applications, they're usually hosted by a service and it handles all of the scaling for you, so you don't have to worry about load balancing to meet the request needs of your scene for your serverless application. So now let me talk about what exactly a serverless application is. So here we have just a client and a server, and on the server, we just have a simple hello world function running. When the client sends a request to the server, it will go ahead and run the code and reply back with hello world. So with a serverless application, this all completely goes away, and it gets replaced by a service such as AWS Lambda. AWS Lambda is a service for hosting your serverless applications, and what happens here is you have a bunch of code, you upload it to AWS Lambda, and AWS Lambda will store that code for you so that when you make a request to AWS Lambda, it will go ahead and execute that code and return the response hello world back for you. So the key part here is you don't own the server, you're not managing it or anything. It's all handled by AWS Lambda, and it will handle all the scaling for you as well. So now with that brief introduction of what serverless applications are, let me talk about Chalice. So Chalice is an open source Python micro framework for managing serverless applications on AWS Lambda, and integrating those serverless applications with other resources in your AWS cloud. So to get a better idea of what Chalice can do, let's go over a common use case you may use Chalice for, and that comes with REST APIs. So with a typical REST API, you send a resourceful request, so you're sending a git to the root path of your API, and you'll get a HTTP response back, or maybe you send a git request to the resources component, and you get all the resources back from the REST API, or maybe you want to change the method, maybe you want to put a specific resource into your API and apply back with the HTTP response. So the way that it takes AWS Lambda, it uses as the back end your core functionality for your REST API, and another server is called Amazon API Gateway, which is essentially the front door for your serverless application. It's handling the HTTP requests, sending the HTTP responses, handling the throttling, and any authentication for you. So now if you send an HTTP request here, it'll get sent to Amazon API Gateway. Amazon API Gateway will then invoke your Lambda function, or run your code, and return a response back to Amazon API Gateway, giving you an HTTP response back. Okay, so now if you kind of take a look at the simplified version of how it's set up, it looks pretty simple. It's just a two-way directional relationship, but in reality, if you were to go ahead and start this from scratch, it's a little more complicated than that. In reality, you need to worry about setting up an IAM role for your Lambda function, so you know what permissions you have. You need to actually take your code, dependency, zip it up, and set it to create a function. You have to create a squagger document to create your REST API for Amazon API Gateway, and link it all together by adding permissions for Amazon API Gateway to go ahead and invoke it and create a deployment so you can hit it with an HTTP request. The nice part about Chalice, though, is that you don't really have to worry about this. If you were to do this by hand, you'd have to go through the console. You'd have to use an SDK or a cloud formation template, but Chalice handles this all for you, allowing you to focus on the actual Python aspect of your application. So what I have here is a video of how you can kind of get started with Chalice. The Wi-Fi's been a little spotty, so I wasn't going to do a live demo, but in order to save some time, in case things don't go as planned, I have this video being ran. So first, you need to pip install Chalice by using pip install-pre. Right now, Chalice is 1.0 beta, so you need to use a free flag. And once you do that, you can go ahead and run Chalice new project, and that'll get you started with a new, brand new Chalice project application. It'll create a new directory, and inside this directory, you'll see two files. There's an app.py in requirements.text. The requirements.text initially is empty to start, and that is where you specify all the dependencies for your Chalice application. So what happens with Chalice is that if you specify dependency in your requirements.text, it'll go ahead and download the dependency when setting your deployment package to Lambda. So the second file, the app.py file, is where all your core functionality exists. And if I open it up right here, you'll notice it's actually very similar to if you're familiar with Flask, where you create an app object, and you go ahead and specify routes for that app. So right here, we're registering a root route, so that if a HTTP request is sent to it, that's a git. The index function would get ran and return hello world. So let's go ahead and actually quickly just deploy this app using Chalice. So as this Chalice app is getting deployed, one thing I want to mention is, while this application is just sending hello world, this is a production-ready application. You can send as many requests as you want, and the AWS Lambda will scale it up for you and be able to handle any incoming requests. So once it's going to be done deploying, it will go ahead, and there's one more thing we're going to need in order to start hitting the API. And that is a Python library called htbpy. That's pretty much a command line tool for making HTTP requests from the command line. So if I go ahead and actually run Chalice URL, I can see what my API URL is again. Go ahead and copy it and send a git request to my API.  Cool. So now what I can do is if I want to add more routes to my application, I can go into my app.py file and go ahead and add new routes. So for example, I'm going to go ahead and add the foo route to this application so that if a git request is made to foo, I will go ahead and run the foo function that will return foo bar. So now once I have that updated, I can go ahead and run chalice deploy again. And I'll update my Lambda function. And I should be ready to go in and actually start using this new update to my API. So now I'm going to get my URL real quick because I don't have it memorized. And I go ahead and paste that and add the foo component to my path. And from there, what I'll get is the expected response I want back. So it should return foo bar, which it does. So the two things I really hope you guys got out of this demonstration was how quickly you hit the ground running using a chalice application to start using just chalice new project and chalice deploy. And also the fact that chalice is handing all of the AWS resource set up for you. So you don't actually have to worry about AWS. You just have to focus on the Python-specific logic of your application. So now what I want to do is go to some of the key components of a chalice application. And by going over the sample app on the right. So what I have here to start is a app object that I create, and I register a bunch of routes to it. So let's take some sample HTTP requests and see how the app reacts. So here we're just sending a get request to the root path. And what that will happen is we'll match up with this route, and therefore when AWS Lambda gets invoked, it will run the index function. Once it runs, it will return back Hello World to the end user, and Amazon API Gateway will forward an HTTP response back saying Hello World. So now let's take a get to the resource Hello. This will match up with this route here and run the Hello Europe Python function. And once it's run, it will return Hello Europe Python as a HTTP response back. OK. So now let's actually look at something different now. So with this request right here, you'll notice that the exact path doesn't actually match up with any of the literals here in the app.py file. What will happen is it actually matches up with this route. And that's because if you provide a curly bracket in your path, it means it's a variable. So you can provide any value you want. In our case, we're just providing Kyle as a variable. So as a result, Lambda will run the Hello name function returning back using the name provided. And this name parameter is passed in using the variable in the path. And as a result, the value of name will be Kyle, and go ahead and return Hello Kyle back to the end user's HTTP response. So the final one I want to talk about is the post. So with the post, what happens? You'll notice that it uses the resource Hello, but it doesn't use the second from the top function. That's because it's a post. And the route registered only allows for a post if used in the method's keyword arc. So by default, if you don't specify any methods, it will only allow for gets. So as a result, Amazon API Gateway will invoke this Lambda function with the post function involved. And if you're looking into the post function, you'll notice that it uses the app.currentRequest. That refers to the HTTP request that triggered the Lambda function. And you can get properties of other requests, such as the JSON body. So for example, you will have the value JSON body when you're actually invoking your function. So now that when you return, you'll notice that the JSON body matches up with the actual request. Cool. So that was just a brief introduction, Chalice. Let's talk about the main points I covered. One, in order to start a new Chalice project, you just need to run the Chalice new project command. It lets you hit the Regan running and immediately deploy that. Chalice deploy, if you make any changes to your application, all you need to do is run Chalice deploy. And you can immediately start using it and sending HTTP requests to it. App.Route, that allows you to run specific functions based off the HTTP request path or method that you sent. And finally, there is the current request property, which allows you to access the current request that triggered your function. So let's talk about the sample application part. This is the meaty part of the talk. In my sample application, what I did was I created a trivia app. So here is a video of me running my trivia app. If you're interested, you can go to that URL. It's a public S3 object or a bucket. And I'm going to go ahead and kind of demo this from the video. So here what happens is that the application will ask my REST API a specific question. So it'll give me the question and a list of possible answers to use. And what will happen now is let's try to answer this question. Hopefully, everyone knows where they currently are right now. In case you don't know, we're in Rimini, Italy. So let's go ahead and select that answer. And then there's a separate API request that will now let you post the answer to figure out if you got it right. So of course, by posting the answer Rimini, Italy, we got that right. And we can go ahead and query for another answer on our REST API. So now here's the second question, asking about spaces, how many should be used for indentation. Let's say we're completely new in Python and we put none use tabs, which is obviously wrong. So the chalice app will send a request and it will tell you that you're wrong and you get the next question. So let's just say we've been answering a lot of questions. We want to keep track of our score, where we are. So we have this additional ability to go ahead and sign up as a user and be able to log in and keep track of our score over time. So I'm going to go ahead and add this as my username being Kyle and then give it a password. And then from there, I can go ahead and log in. So once I log in, what that will do is take me back to the original question and I can start answering. So for this first question, let's say I forgot that it's 2017 and I thought it was 2016, I put Bill Bowdown, which is obviously wrong. Now let's actually get this answer correct. And once we submit four here, we should be able to go ahead and get the next question and see what our current score is. You can see that total correct is one, total answer is two. I can now say, let's say I want to take a break and go ahead and log out and resume later. So if I go ahead and log out, it will return to me back to the original question and I can go ahead and log in again. And that should take me back to where I left off was that third question about the Zen of Python. So that's the gist of my application. What I want to do now is actually talk about how you go about writing this application with Chalice. So there's three steps in writing this application. One, you have to worry about the question to answer API, that whole idea of getting a question and then posting that answer in order to determine if you're right or wrong. There's the web application portion, so specifically the browser logic to make sure that you can work in the browser. And then there's the third step, which is authentication users. So being able to handle registration, login, and being able to track user score. So in order to show the rest, the git answer in a post-answer API, let me go over this new video in which what I'll do is, I'll show you the initial branch of, right now I have the master branch that has all the prod stuff on it. I am using this initial API branch that just has the git and post. There's additional APIs that I'll need later on. But to kind of show you Chalice deployment, what I'm gonna do is deploy this branch to AWS Lambda and API Gateway. And I wanna make you understand that in this command I'm running, I am running it with a dash dash stage argument. So the purpose of dash dash stage is that it'll allow you to combine your resource into specific stage groups. So right now I have a bunch of resources running my prod application. So if you went to the browser page, it's hitting all my prod resources. If I'm gonna go ahead and deploy, deploy new resources, deploy new logic, I don't wanna be deploying straight to prod, right? I wanna be deploying to some other stage that has all the resources isolated. So that is what I'm doing here. And then once I feel comfortable, I can go ahead and deploy it to prod. So in order to hammer that point home, all I have to do is run Chalice URL with a stage URL to show that the actual URI that I get back is completely different from what the dev stage is. So now let's actually get into the question and answer a part of the API. So if I want to actually go ahead and get a question, I go ahead and copy this URL in and I add the path components questions and question ID. So in terms of how we do questions, that you have to provide a question ID. They start at one increment by one each time. So by running a get on this URL, you will get the first question for the tribute application. So when we run a get on that, you'll see that it returns back that EuroPython where it's being held and the possible answers they can use. It didn't reply to an answer back, so you're gonna have to go ahead and post this answer. We allow for a post the same URI. And then what we're gonna do is include a JSON body in this post for our server to be able to figure out what the correct answer is. So we provide the answer key and the actual answer. And once we actually go ahead and post this, it'll tell us if we're correct or not, in which we were work correct. In the case where we submit a wrong answer, it'll do a similar thing. But so let's say I put down Bilbao Spain instead for this. And what will happen instead, it'll just tell you, all right, the correct answer is actually Remini, but the, and you got your answer wrong. So let's go ahead, now that you have an idea of how the REST API looks, let's actually go talk about how you'd go about doing this. So let's imagine we have our get question API. We have a question table that has all of our questions. In order to set up a REST API for this, all we need to do is stick a Chalice application in between the two, so that if you send a get request, it will be forwarded by Amazon API Gateway to Avis Lambda, which we'll read from the question table, and return the information back to the user's HTTP response. So now, if they provide a question that doesn't exist, that would be the same logic, but Lambda will realize it's not on the table until Amazon API Gateway to give the user a 4.4 at the very end. So here is some sample code on how you actually implement it. Don't worry about trying to read through it all right now. I'm gonna step through it one by one, so make sure you pay attention. So to start, I just import Chalice here. The second thing I import is a ChaliceLib.question. So this is not a dependency of Chalice. It's actually a built-in functionality. So if you want your application to grow outside of an app.pf.wifile, like you want more than one file involved, you can use something called a ChaliceLib, which what it'll do is you can create a new ChaliceLib directory in your Chalice app, allowing you to put new modules. Like I added a question spy module into my ChaliceLib directory. And this is a lot different than requirements.txt because requirements.txt is mainly for third-party package dependency. So stuff that you didn't write, but you just want to take a dependency on. Afterwards, I go ahead and create my app object. And then I register my route and a handler for it. It accepts a question ID because question ID is a variable in the URI. And now all we have to do is create a questions table called getQuestion. This return none if the question doesn't exist or a name tuple of information about the question. So if the question doesn't exist, we're gonna go ahead and raise this Chalice.notFoundError. So Chalice has a bunch of built-in exceptions that allows you to raise it in your code and Amazon API gateway will propagate the specific status code back to the end user. So by raising a Chalice.notFoundError, you will raise a 404 to the end user. So now after all that's been gone through, we can go ahead and return the question ID if it was found. So the post side of it is very similar to the get. All you have to do is in ABS Lambda, once you get the question back, is determine if the provided answer is correct. And if it is, go ahead and return true to the end user. So here again is the code required to do this. Don't worry about reading this all through right now. I'm gonna step through it again. So to register the route to start, we use the same path as before, but instead we specify a post. The last route we registered was only a get. So now we go ahead and create our function handle in which we accept question D as a parameter because it's a variable in the path. And then from there, the very first thing before we do any core logic is to make sure that the answer is actually in the JSON body. And if it isn't, we raise another built-in Chalice exception, which is the bad request error. This will raise a 400 error to the end user in terms of an HTTP response. And then from there, what we can do is do some of the more core logic and figure out what they provided and get the actual question. Make sure that the provided answer is a list of possible answers. If it's not, let's go ahead and raise another bad request error, another 400 and tell them you need to provide an actual answer, the list of possible answers. Once all those checks have been complete, what we go ahead and do is return if they're correct, what was a provided answer, and the actual correct answer. So that was the question and answer part of the API. Let's talk about what we kind of learned in this section. First, we talked about Chalice stash-stage, so the idea of being able to group your resources into different stages so you don't interfere or deploy over your existing resources. So if you wanted to experiment with a dev stage, you can keep your prod stage running and not have to worry about deploying over what you had previously deployed. We talked about Chalice exception handling, so raising a built-in Chalice exception to go ahead and propagate a specific status code you want back to the user. And we also talked about Chalice Libs. So if you wanna outgrow your app.py file, you can go ahead and create a Chalice Lib directory and create your own modules inside of that. So now that we talked about the question and answer API, let's talk about the web application portion of it. So for the web application, there's two things we're gonna have to worry about. There's, we're gonna have to add ability for cores and we're gonna also have to get an SDK to be able to interact with our API in the browser. So with cores, right now what I've been doing is just making API requests with my laptop to my REST API. I don't really have to worry about cores. But the minute I put a browser in there, we have to worry about data security in terms of making cross-domain requests. And to do that, we have to abide by cores. And here's an example for a simple get request. What happens here is that when we send a get request, it'll send the same response back, but we also include this header right here. The access control allow origin header, which specifies what origins are allowed to read this resource. In our case, we just provided a star, meaning any resource can. If the request gets a little more complicated, maybe it's a put or has some extra headers, the browser will also send some preflight request in terms of an options HTTP method. And in order to do that, it'll determine what permissions it has to send in this request. So specifically, the server will apply back with what headers you can reuse in your request, what methods you can use in sending it, and also what origins are allowed to access this resource. In order to enable this in a Chalice application, it's quite simple. You just add cores equals true. That'll give you all the default values. It'll get you a star for the allow origin. It'll give you a preset of headers. And any methods that have been labeled as cores will also add that to the enable methods, allow methods for the cores headers. If you want anything more specific, you can go ahead and run it with cores config instead of a Boolean, and you can get specific values that way as well. So now what I wanna do is talk about generating SDK. So the front end application I have is already in JavaScript. Don't worry, I'm not gonna show you very, very much JavaScript. This is a Python conference. I'm way more confident with my Python abilities, so I'm gonna spare you guys of that. But with the Chalice Generate SDK, what allows you to do is generate a JavaScript-based SDK to interact with your API. So here is an example of how you go about doing it. So all you need to do is just run Chalice Generate SDK and specify a directory. And what's gonna happen here is that Chalice will make an API request to Amazon API Gateway, and Amazon API Gateway will go ahead and generate your JavaScript SDK for you. Chalice will then download it and unzip it into directory that you specified. So now if I go ahead and CD into this directory, you can see the different files that have available to me. And you can see that I have an API Gateway client, JS file, and under here you can see some client code. Let's look at the more specific things related to our application. So for example here, we have our invoke URL. You can see this is exactly the same as our dev stage. So this is the URL we're gonna be hitting in the end. Then if I skip along a little bit to the later on in the file, you can also see some of the methods, so some of the routes. So you can see here, this is just the questions. So this is the get question part of the API. This allows me to get my information about a question. So that's it in terms of how much JavaScript I'm gonna show you, but it just gives you an idea of how you can have easy access to your API from a front-end application. So continuing on, let's go ahead and talk about the last piece that we need in order to complete this application, which is authorization in users. So in terms of authorization in users, the one thing, if you remember from the sample application, there was the ability to log in, there was the ability to register yourself and be able to keep track of your score and where you've been. So Chela's has a bunch of different authorization options available to you. There's of course none, which we've been using the entire time, we don't have to be authorized to use our APIs. There is IAM Authorizer, which is using AWS Crenshut credentials and Amazon SIGV4 signing to give authorization. There's Cognito User Pool Authorizer, which is using Amazon Cognito, which is a managed service for managing users and user pools and handling credentials and login and registration and whatnot. And finally, there's ability to define your own authorizers using the decorator app.authorizer. So in your Chela's code, you can go ahead and actually implement all the logic that you need for your authorizer and then link that up with your REST API handlers. For this application, I'm going to be using the Cognito User Pool Authorizer, mainly because Amazon Cognito User Pool gives you a lot of functionality right out of the box. So mainly, it's to be able to manage users, so it's to be able to manage all the user data there and handle login and registration all for you. It provides SDKs for user registration login, so my front-end application is just a simple function called to get my credentials or to register a new user, and also provides AWS Lambda triggers. So while it provides an out-of-box solution, if I want to customize it all, I can create Lambda functions that will customize the process in terms of how a user signs in or registers himself. So in order to talk about how an authenticated user answer would be, let's talk about the anonymous one first. So here's the setup for the anonymous one. If we want to actually add an authenticated answer API, we go ahead and add the user component here. And in adding the user component, we need two more resources, one being a user table. We also need Amazon Cognito. So in terms of the workflow, in order to actually keep track of the user's answers, we need to do the following. First, the client will have to make a request to Amazon Cognito using their username and password to authenticate themselves. Once they've been authenticated with Amazon Cognito, they go ahead and return a JWT token back to be used in subsequent requests. And from there, you can go ahead and post your answer. But notice that there's an authorization header included that matches the exact same JWT token. And Amazon API Gateway will then check to make sure that they're authorized. And go ahead and invoke the AWS Lambda function. AWS Lambda will make sure that what their answer was was correct. And based off the result, we'll go ahead and record that in our user table. And finally, return that HTTP response back to the end user. So to actually implement this, here is sample code on how you do it. I'm going to step through this one by one again, so follow on. Here, what I have is the poolarn. So the Amazon Cognito user pool, I set this up prior to any Chalice deployments. And the poolarn is essentially the identifier for this pool. And from there, what I do is create a Cognito user pool authorizer. So I provide my poolarn to that to have an authorizer that I can then take my route and assign it as my authorizer. So any request going through this route has to have Cognito user pool authentication in order for it to pass through. So now from there, what we'll go ahead and do is create a function. And go ahead and run to answer question function. If you remember from before, answer question comes from just anonymous post questions question ID route. Once we have the answer data, we need to actually figure out who the user was to just answer that question. And in order to get that, what we can do is go ahead and run this helper function called get authenticated username, which uses a property on the current request object, which is the context. The context provides information about what exactly triggered my Lambda function and just information about it. And if I open this up, you see I get a big JSON dictionary. I actually shortened this dictionary because if I didn't, it'll fill up the entire page and it didn't have any room. So I shortened it just for the specifics that we want. And specifically what we want is the Cognito username out of it. In this case, the username was my username. So another point I want to make out to you is that ideally, if you're keeping these in a database, you probably want to be using the subtoken. This is a uniquely generated ID by Amazon Cognito. So if you're trying to add these users to a user pool, you probably want to use that as a primary key. But I'm just using Cognito username for simplicity and reading for this talk. So now I go ahead and create my user table. I update my user score and return the answer data, which came from the answer question. So now that we have log in all handled and keeping track of user score, the one thing we haven't covered is how do we handle registration of users? So like I said before, Amazon Cognito provides to you a out-of-the-box solution, but you may want to customize it. In my case, I actually wanted to customize it. Specifically, in terms of registering new user, usually you sign up and then you have to do a confirmation of this. The user has to then confirm themselves. I wasn't particularly interested in doing a confirmation, so I wanted to be able to disable that. A second thing I wanted was that immediately after a user registered, I wanted to keep track of them in my DynamoDB database. I did not want to only have access to users that have just answered a question, because that's the only way I'd be able to track it by adding them when I invoke the lambda function. So in order to do this, I add two more lambda functions, one lambda function for auto-confirming functions, auto-confirming the users, and another lambda function for actually adding users. And the way it works now is once you register, you send a username and password to Amazon Cognito, and Amazon Cognito will start the registration process. And these lambda functions are hooked up to specific points in the registration process, so that Amazon Cognito will then invoke the lambda function on a specific point. So at the pre-signup trigger, we'll go ahead and invoke our auto-confirm function, in which case the lambda function will respond to Amazon Cognito to go ahead and say, you can go ahead and auto-confirm this user. After they've been signed up and confirmed, there is another trigger called the post-confirmation trigger. And with the post-confirmation trigger, what we'll do is have the Amazon lambda function go ahead and actually add the user to our table. It'll turn back a response, and Amazon Cognito will tell the user, you're all signed up, you're good to go. So the auto-confirm function. It's not very difficult to do this. All you have to do is, in your app.py file, go ahead and add this function right here. So this is a little bit different than you've been seeing previously. We've been using routes as a decorator. This time, we're actually using the lambda function decorator. So what that means is a standalone lambda function. So it's not connected to any API gateway, so you can't actually make a REST API request to it. And it's also isolated from your API lambda all the logic that's handling your routes. So this function now accepts two arguments. There is the vent in context. The vent is usually a dictionary that has all the parameters that triggered this lambda function. And the context has information about how the lambda function got triggered. If I actually look at the vent here, you can see the different information I have available to myself for this presignup event. And specifically, what I'm interested in is telling this auto-confirm user value of false and setting it to true. And after that, I'll go ahead and return the vent, this entire thing, telling Amazon Cognito to skip the confirm signup step. So in order to add a user now, this is not too difficult either. All you have to do is add another lambda function here. And like I said, like I did in the last one, the lambda function is a standalone lambda function because it's using the lambda function decorator. So it's not connected to Amazon API gateway. And the event that it takes in is this event here. And out of this event, I can get information, such as the username, which will allow me to go ahead and add the user to the user table. I can go ahead and return the entire event to Amazon Cognito. And then that's all it takes for the entire registration process to happen. One thing I also want to mention before is that after these lambda function deployed, I have to go ahead and add these as triggers to my existing user pool. It's a one-time setup thing, but I'm using Chalice mainly here, so I can handle the deployments and updates of my lambda functions and my Chalice application because it makes it very easy for me to update it. So going back to that line, let's talk about what we learned in a section. We talked about how to use Amazon Cognito to give authorization for your Chalice application. We talked about app.currentrequest.context, so being able to get information about your lambda function and how it got invoked. And then finally, we talked about the app.lambdafunction decorator, so being able to set up a standalone lambda function that is not connected to Amazon API gateway and just runs by itself. So given the time constraints, there's some other Chalice features I really wish we got to talk about, but unfortunately, it was not able to. One feature being the app.schedule decorator. So this is like the lambda function decorator, but it's cool because you can essentially have cron jobs running for your serverless application. So every X minutes, every X hours, or a specific day of the week, you can have a lambda function run. So that's very convenient. Another one is dependency management. So if you remember before in the intro demo, I talked about requirements.txt and how it downloads all the dependencies you need for you. While that's pretty straightforward, but when it comes to C extensions, it gets kind of complicated because with AWS Lambda, its underlying operating system it's running on is Amazon Linux. So if you send up a compiled version of the C extension that isn't compatible with Amazon Linux, you're gonna have a lot of problems when you're Amazon and you're AWS Lambda function. The cool part what Chalice will do though is it will actually download wheels for you that are compatible for Amazon Linux, unzip it into your deployment package and go ahead and allow you to run that in the lambda. So for example, if you're doing your deployments from a window machine and you had a dependency on NumPy, for example, it'll go ahead and download those wheels for you that are compatible for Amazon Linux and go ahead and include that deployment package so you can have NumPy run in your Lambda function. It doesn't matter in the operating system. So last thing I wanna talk about, additional Chalice feature is the AWS IAM policy generation. Which what it allows you to do is if you remember from the very first, one of the first slides where we're talking about the setting it up from scratch about the IAM policy. So Lambda needs a bunch of permissions in terms of if you're gonna access other AWS resources. What Chalice will do is scan through your source code, determine all the operations you're using, all the AWS resources you're using and actually generate that IAM policy for you so you don't actually have to worry about that part of the Lambda deployment part. So now let's start wrapping this up. The one thing I really hope you guys got out of this talk was the benefits of using Chalice. From the beginning it showed how it allows for easy and fast-paced app development. So from Chalice's new project, you can get quickly started and deploy that application and quickly iterate on top of it. There's not a lot of boilerplate code you need to worry about in deploying Chalice application. I think in the end my app.py file for this entire application was less than 100 lines of code. So that was really nice. Another point is it handles all the AWS resource manager for you. So it provides a nice abstraction on top of your, top of all the AWS Lambda and API gateway stuff so you don't actually have to worry about that. It'll handle it all for you. So you can just focus on the Python specific aspect of your code. And finally it produces production ready applications. Production ready being it's being ran on AWS Lambda and therefore it's handling all the scaling for you and all the infrastructure management. So you can go ahead and deploy it, just leave it there and not have to worry about it or worry about any of the DevOps related to it. Okay, so the final thing I wanna mention is that we released Chalice 1.0 beta last week. So what that means is that while it's still developer preview we're getting very close to actually going GA with this and having that 1.0 release. So between now and when we actually do 1.0 it's only gonna be small enhancements based off user feedback and trying to polish up the final interface. So I really hope this talk motivated you guys to all try out Chalice, try writing some serverless applications. And if you have any feedback, come find me or there's another dev here, James from the Chalice team or you can also post an issue on GitHub. And any feedback we can get between now when we go GA is very valuable. So we'd be grateful for it. So one thing I wanna say is here's some related links. Here's a Chalice repository, Chalice documentation and also all the code I use for my Chalice trivia app you can find it here. I need to fill it out to read me a little bit so if you're trying to deploy it initially you might have a little bit of issues but you can at least get a gist of how I actually went about writing this application. And you can follow me at Twitter at VCalNap for any updates related to this talk. And also if you wanna talk about AWS, Chalice or any of the libraries that I work on please come find me or my team member team member later this week I'll be here the entire conference. So if we have time for questions, we can do it after but thanks everyone for coming and listening. We do have time for a few questions. So let's get started. Hi, hello, is Chalice providing, good talk by the way. Yeah thanks. Is Chalice providing any way to manage resources like S3 buckets or databases or anything else? Not currently, the closest thing you could do is it provides the ability to have CloudFormation templates where you can have an S3 bucket there but one feature I really wanna add is some of the major resources like S3, DynamoDB something you'll be using a lot in your application and being able to manage it but that's something on the roadmap. Yeah hi, thanks for your talk. In terms of data persistency, so databases because you show user table, a question table what options are there? Can you repeat the question I can't hear very well, sorry. So in terms of data persistency like databases what can you use? Can you use like my SQL, Postgres, DynamoDB? Yeah I mean whatever table you have available to you whatever you can connect to you I was using DynamoDB in my user table so that's really nice because it just integrates really well with the AWS just resources and whatnot. Does that answer the question or? Yes, thanks. Hey thank you for the talk and what about testing because the code you showed was really really tight coupled and oh sorry, what about testing? Yeah so in terms of testing you can go ahead and just test those general function the general handlers but in terms of actual framework if you're familiar with Flask and how it has its own testing framework Chalice doesn't really have anything specific like that but it's something we want to add in the coming days. Thank you for the talk, very nice slides thank you person for what we've seen yesterday.  Yeah I hear you saying so the thing with Elastic Beanstalk is that you still have the application up and running but if you're using AWS Lambda though you're only paying for the execution run time so you still may have your Elastic Beanstalk application still going and you're still paying for that resource both AWS Lambda you only have to worry about whenever it gets executed. That makes sense. Last question. Okay and another question.  Or does it work? For the we're talking about DDoS thing. How does it work? Yeah denial of service so I get a lot of traffic the Amazon can handle it but to all my expense like how does it work? Oh yeah so what you'd have to probably set up is you can actually set up throttling through API Gateway and that'll actually handle to make sure that your Lambda function doesn't get evoked way too many times so you can avoid that. You can just kept it right? Yeah. Okay thank you. Actually I think we have time for one last question if anyone has one. Hey thank you for the talk. So I just looked it up on the internet and it seems like there are some limitations well of course it's everywhere and it seems like you can have only 1000 parallel threads like threads in process executed for one function, one Lambda function. So my question is what if you need to serve more than 1000 QPS? Can you repeat that again? I didn't catch the last part. Yeah so basically I looked at the Amazon website talking about restrictions. So there are limitations. You can run I think 1024 threads in process for one Lambda function in parallel at the same time. What if you need to serve more than 1000 QPS? I believe that's just, sorry. So I believe that's just your cap on terms of Lambda functions. In terms of having it invoke I believe that's not the limit is it? Well that's what I've seen. Maybe I may have understood it.  I think that's what the current limit is of just simultaneous Lambda functions going. Like they're separate ones. Oh okay so it's a separate function. Chalice will have the same Lambda function for your API so you can hit that as much as you want. There won't be an issue with that. Okay it makes sense so it's not in vacations. Okay cool thanks. All right thank you everyone. All right thanks.


Today we are going to talk about Newton's three laws of motion and how they relate to vehicular accident investigations. Let's look at Newton's first law. The law states an object at rest will remain at rest unless acted on by an unbalanced force. An object in motion continues in motion with the same speed and in the same direction unless acted upon by an unbalanced force. This law is often called the law of inertia. In other words, objects tend to do what they're already doing. Inertia means that an object will always continue moving in its current speed and direction until some other force causes its speed or direction to change. This is why it's important to wear seatbelts in cars. When a car is moving and comes to a sudden stop, your body will want to continue to move in the original direction of the car. The same goes for objects that are not moving. An object will remain at rest until some force makes it move. So, there are two states of inertia, the state of rest and the state of moving. Sometimes it's hard to see inertia because of a force called friction. When two objects rub together, they create energy that causes a release of heat. You can feel this when you rub your hands together. What you're feeling right now is friction. Friction is a force that resists the movement of an object by acting in the opposite direction of the moving object. Think of the brakes you use to stop your car. If a car comes to a stop at a stop sign, it slows because of the friction between the brakes and the wheels. The friction stops the wheels from turning and counteracts the inertia moving the car forward. What happens if that same car tries to stop when it's raining? Friction is still there, but the liquid makes the road much smoother and decreases the friction. Less friction means it is harder to stop and easier for a car to slide out of control. That's why there are so many accidents in bad weather. Newton's second law states that acceleration is produced when a force acts on a mass. The greater the mass of the object being accelerated, the greater the amount of force needed to accelerate that object. This is expressed by the equation force equals mass times acceleration. For example, large cars have more mass than small cars, and it takes more force to make them accelerate and decelerate than it does for small cars. This is why large cars guzzle more gas. Newton's third law of motion states for every action there is an equal and opposite reaction. This means that for every force there is a reaction force that is equal in size, but opposite in direction. Whenever an object pushes another object, it gets to push back equally hard in the opposite direction. For example, when two cars experience a head-on collision, the cars will exert forces on each other, and they will be propelled away from each other after impact.


and welcome all to the 2 p.m. update with me David White well we've got a market that's at least kind of a little bit of everything of course a lot of people running into the safety stocks in the Dow it's that fairly strong at about eight yeah let's call it eight tenths of a percent NASDAQ's down about one and a quarter percent where the S&P is down about three tenths of percent and the Russell actually up one and a fourth percent so what's the mixed bag out here well it certainly is a rush to safety in some of the Dow stocks of course if you ever investigated the Dow I don't use it as a big indication for its value mostly because of the shares of the Dow 30 96% are institutionally owned that means there's only about 4% that actually ever trade extensively so it's fairly easy to push most of those stocks around significantly about 26 out of the 30 can be moved without much in the way of actual volume and price change so I don't look at a great deal of it but when you see this the entrances like I said kind of narrow and exits are narrow too in the Dow 30 stocks but what we're really seeing here is a kind of a thought that maybe we want to see stocks that have been around for a while and have a lot of cash on the balance sheet and of course that overflows some of the other stuff going on in the market and that is if I can get it up here of course the dollar move it certainly looks like the Treasury is active the bond market starting to come back and respond to that TLT is at 9724 after blowing through the all-time projected lows of about 101 and going down much farther now kind of coming back just a little bit of course most people are talking about meta I call it meta Musil and I say it has IBS to down but more than 20% today the Mobilee Mobileye IPO did come out and we did kind of start to see some weakness as as usual when big IPOs suck up cash in the market we back in just a few minutes for the show the reality is that navigating financial market


It's going on everyone Sam here with late in sports cards rip in at 23 Bowman Chrome Baseball HDA choice 12 box case break number 4 Random division style here is a look again at your random results as always you can find those on the website under the results tab As well as the link in chat. It's good luck everybody. Let's do we're gonna need to get you a charger I don't know there's got to be some there's something you could turn on What you said It's real, I was good. Yeah, I've got an older one still Me Verizon. Let's make this a good one guys. Here we go See some bangers come out of this. That is a first base auto Adrian Pinto For the Blue Jays eight nice to 150 at Brian Bettencourt for the NL West. Hey, what up Cliff? How you doing, buddy? Blue Jays AL East and purple Joey Ortiz the 250 AL East congrats on that AL East Carla Jeremy with some personals. Thank you. Zoey's Jeremy On the next do soon. Oh, yeah Darryl Laverde AL West that's a Griff McGarry base auto NL East and at least and NL East he actually signed this one Justin Henry Malloy to 299 To none and I'm up late did well going to the NL East. I swung there and at least And at least on that Got a choice exclusive Jose Gerardo or Gerardo probably Gerardo going to the NL East choice exclusive to 150 and Then at least again Jose Gerardo to 99 on the true green this time true green the West Daniel Mateo Base auto nice one there AL West Yeah, oh, yeah, Brett. We don't do a lot of group breaks of it We'll get stuff we'll get them in for personals all the time. We did do random box style of both of those But I think we're out of them right now. We might have some select left Rev. I think we're out of AL East Louise paralysis base auto AL West Yeniel La Boy to 499 ya boy La Boy There's been a lot of stuff that's come out for wrestling recently. I think select the last one to come out That is NL central Abner Uribe. Do you mind just wiping this one down? It's hella dusty. We'll get that wiped down for you NL central Rick E That is gonna be base auto And at least Ricardo Perez There is some smudges on that. We'll get an empty box and rapper and at least And at least getting a box in a proper now west 150 eggy Rosario on the rookie auto nice one there first rookie auto We've seen out of choice today Very nice very nice Again, here is your link to Number three plates and patches at 20 spots remaining 20 to go Gonna be fun man. There's some good stuff in there First time since 2019. They've made plates and patches a standalone product Got Daverson Gutierrez going to the NL East base auto AL West That's gonna be Kenny Gomez Kenny Gomez AL East by our AL West by way of the Astros Andre picking up a spot in four and a mega dual case spot. Thank you and Andre Appreciate you buddy mega dual case down to 25 to go now everybody and Vincent Parazzo to 250 NL East on that one as well on the purple Very nice. Very nice. All of the next There's NLS Jesus Bougarin got AL central Dario Barreiro NL East the 250 purple Everett Cooper the third Everett Cooper the third Yes, this is Bowman chrome choice Bowman chrome HDA choice Wicked silence So basically when Bowman chrome comes out comes in hobby and choice Hobby and choice and a West junior Franco base first auto Got AL central Christian manna 299 green lava and AL East Luis Serna to 299 white speckle white speckle so down to 20 21 on our two plates and patches full casers Get those filled up Getting there for sure everybody. Thanks again is one cornel NL West Base auto AL central that is gonna be Omari Daniel 299 green lava No, Turtwig. He was last year 20. He hasn't had a tops rookie and his first was 2022 Bowman and Yonatan Henriquez stood 499 refractor first auto for the NL East. I think it's a cool idea I like it, Brett. I think it's interesting for sure. I'm glad they make made them super rare too Is they're not like super common from West is Jacob Melton Can't decide on choice or hobby Can't decide between choice or hobby I mean in choice you're guaranteed you get three autos across the board That's it versus hobby. You're gonna get colors You're gonna get the chance at base and stuff, you know base numbered stuff So it's it depends on what you're into that is a Omari Daniel 50 of 50 Gold shima for the AL central and Carla Ailey Samuel Bassio refractor first auto by way of the Baltimore Orioles Grats on that. Yeah, mantle retrofractor would be pretty sweet. I agree on that. I like hockey. I Don't follow it super heavily, but I like it like I know enough Great to watch man. Yeah, playoff hockey is great No, I don't think Pardar is gonna be a boss. I think he's he I think he's a sure-fire as McDave it is Yeah, nice, Bassio. Can you mag that one? Which one? The Bassio that one? We got an orange coming up now everybody. Kate Hunter First base auto got Kennedy Corona first base auto AL West Kate Hunters NL central And then we got an orange. We got an orange. I'm gonna orange wave Kate Hunter Eight of 25 nice one there for the NL central on The orange just YouTube right now wicked just YouTube Yeah, you he's on Twitch right now. Yeah, YouTube and Twitch. Yep. That's gonna be Yonatan Enriquez and I'll East Got an L central Dylan. Oh, oh, oh Ray Brewer sit fair and then go into the AL central Omari Daniel to 4 at 99 499. All right, still quick recap base autos Dylan. Oh, Ray Yonatan Enriquez Kate Hunter Kennedy Corona Jacob Melton Juan Corneal junior Franco Dario Barrera Jesus Bougarin Davison Gutierrez Kenny Gomez Ricardo Perez Abner Uribe Luis Perales Daniel Mateo blade Tidwell Griff McGarry Dario Loverde Adrian Pinto Got refractors Omari Daniel Yonatan Enriquez y'all a boy to 299 Luis Serna Justin Henry Malloy to 250 is Everett Cooper Vincent Peruzo Joey Ortiz the 150 we've got E guy Rosario Jose Gerardo Brian Bettencourt to 99 Omari Daniel Christian Mayna Jose Gerardo To 50 Omari Daniel to 25 Kate Hunter and then for 99 refractor first auto Samuel Bassio That'll do it for the break guys. Thanks again for the filp up next plates and patches