The following is a presentation of TFNN. The Trader's Edge with Steve Rhodes. Toll Free at 1-877-927-6648 or internationally at<PHONE_NUMBER>. The Trader's Edge. Now, Steve Rhodes. Good morning, folks. Welcome to the November 27th. The magnificent Monday edition of today's Trader's Edge show. I'm your host, Steve. Perseverance Rhodes, who absolutely knows that each of us should always be pioneers of our future versus prisoners of our past. Hope everyone out there is having a great day. Let's make sure we have an extraordinary one. Now, the easiest way to do that is to always remember that life is happening for us, not to us. That's right. When you and I make that one little two-by-four shift, means we can find the gift in every set of circumstances that life is going to toss at us. Now, today you and I are going to go check on the circumstance of these markets. We'll go figure out what those bulls and bears, what those buyers and sellers are communicating to you and I at just past 11 o'clock in the morning. I want you to know I'm absolutely grateful for your presence here, but even more important than that. And that's this. During this next 53 minutes, I'm here to serve you. So feel free to pick up that phone. You can dial on in<PHONE_NUMBER>. Now, if you've got a question, but you can't dial in, we've got you covered. You can always send me an email. Send that off to Steve at tfnn.com. And inside the subject heading, please put radio show question. Now, if you're inside our Tigers, then any and every ping will do. So let's go ahead and get this show started on Marvelous Monday. Of course, this is Tiger Financial News Network. I'm Steve Rhodes. Welcome to the show. Slightly mixed bag out there. We take a look at the U.S. indices. The semis just slightly positive. Less than one point to the upside. Dow's off 73. Quarter of a percent. S&P down nine. Two tenths. Nasdaq is flat. It's off three points. Russell's down seven. That's a four tenth of a percent move. The largest move to the downside of the trannies are one to three tenths percent. 196 points there. You've got gold trading up 560. Silver's up 34 pennies. That's a buck, one and four tenths percent move to the upside. Lice recruit off a quarter. Natural gas down eight pennies. 30 or treasure up 22 ticks. Printed out at 115.17. The leader in the clubhouse to the upside is Mercado Libre. Up 37 bucks to 1.5 percent. Domino's Pete's $11.3 percent move there. Super Micro Computer up nearly 10. 3.5 percent. Lam Research up nine. Little over 1 percent. Roku is up $6 and change. That's a 7 percent move there. To the downside, we've got MicroStrategy. Nearly 12 bucks. Two and a quarter percent. John Deere down eight bucks. Two and a quarter percent. Eli Lilly down six bucks. Little over 1 percent. Albie Marl off six bucks. That's nearly a 5 percent move. Old Dominion Freight Line down five. Nearly six dollars. It's about one and four tenths percent move to the downside. Let's begin our day by taking a look at the daily and the weekly equity future contracts. Let's move over. We'll move over to our white background screens out there. We're going to see what we're going to see here. On the daily base, that's the upper row of charts out there. You'll see in the ES mini, and we just, you'll see a TD9 account bottom. Wave number seven bottom back on October the 27th. And now where are we at? Well, we've got now a TD9 account top that completed on Friday. We also have a bearish structured daily profile that is attempting to form as we speak. Now, the bearish structured area or the range is between 45.72. That's a clear resistance level. I've got two centers. One of my white background charts. That's at 45.41. One on the black background charts. That's at 45.56. Right now I'm going to use 45.56. And if price closes below that, well, that would signal to you and I that price should get back to that green oscillator change line. Now, regardless of the profile, that's what price should do when you create a TD9 account pattern. In this case here, it's a TD9 account top. Price should pull back and test that oscillator change line. Now, green oscillator change line is bullish. Whereas a red one is bearish. A green one tells us the price oscillator is above zero. And then it's rising above zero. Those are bullish conditions. In other words, we have bullish conditions as we speak right now inside the ESMini. That doesn't mean price won't pull back out there. In fact, it should. However, price closed above the high of two days ago of Thursday. That is 45.80.50. And negates that pattern would suggest that we move higher. Take a look at the NQ. The NQ went ahead and formed a TD9 account top. Bar number eight is the high. Today is going to be the completion of that pattern. It doesn't really matter where price closes today or where price trades to. Here what we can see, price did form a new profile three days ago. Support is down at 157.48, resistance 16.102. What price should do here is pull back and test the oscillator and change line. That's going to be at about the center area. That's about 15.8.90. Price just pulls back and test that level, rejects it, stays above it. Conditions will then be neutral for both the ES and the NQ. Why neutral? Because you'll have a top and price pulled back and successfully tested a key level of support that held that greenhouse under change line even more important than the bottom of a profile. If we take a look at the Dow equity future contract on Friday, it completed its TD9 account pattern. Now a close above Friday's high, that would be 35.4.10. There is no new profile here. What price should do is move down towards that oscillator and change line. 34.968, remember that oscillator and change line? Oh, you will. Because I like to refer to it as it's going to change as price moves up and down. So the figures that I'm giving you are really guidelines or good guidelines, but they are just simply that guidelines. So price should pull back towards that 34.698 level. We take a look at the Russell 2000. We don't have any kind of a top out here. What we do have is prices run into trend line resistance. And for that, let me just see if I can put in one of the larger trend lines. I mean, there's a couple of different ones, but if we just simply start all the way back here. There we go. So we just simply start at its high. Give me a second here. Let's draw a line, grab the line feature. So we're going to say here is the primary trend line out here. We've got other trend lines as well. I can put one in from this swing point right here down to there. There's another trend line. So we've got trend line resistance. In essence, I could even draw another one. We could use this swing point right here to draw a trend line.  And can that be a top? The answer to that question is yes. So we've got absolute topping patterns or signals. I should say patterns really inside the ES, the NQ and the YM for their daily timeframe. We look at the weekly charts out here. It's the NQ that would give us pause. The reason the NQ would give us pause is because what price has done, so in each of these we've got girly by patterns. Those form weeks ago. But in the case of the NQ, what price was able to do today, I'm sorry, last week was get up and test resistance. That was the top of its profile. And that's at the 16-130 level. Now just test the level of resistance. Does that mean it's a top? No, but you're at a topping point on the weekly chart. You've got a topping signal on the daily timeframe chart. Odd's favor, we've got some type of a top out there. But what we're going to do is we'll spend time trying to figure out what kind of top that is. And we'll do that really by taking a good one of Nancy's questions. So let's do that right now. And then we'll later get to Microsoft for you, Nancy. But let's try to answer her questions with regard to TD9 count patterns. Now, what I'm going to put up on my screen right now, this is a market analyzer. Subscribers get these on the daily and the end of day reports out there. They're always slightly different. But this one here, we're taking a look at. This shows you on the left hand side, that column shows you the cash indices, the index ETFs, the S&P 500 sectors, the Magnificent 7, John Cena, Tiger's Den asked about those, and the equity future contracts out there. When you take a look at the daily TD9 count, that is column number four out here. You'll see lots of nines and stars. If it's got a star, it's a TD9 count top that's in place. We come back to this break. We'll talk about those in just a few. Currencies, commodities, and bond markets are as important as ever right now with how they're driving the volatility in equity markets across the globe, which is why it's a great time to try out Teddy Kegstad's Tiger Forex report. Teddy Kegstad breaks down the Forex markets every Monday using his 30-plus years of experience as a trading veteran of futures, Forex, stocks, and options. Teddy releases his weekly Tiger Forex report every Monday morning with coverage of all the major currency pairs, including the dollar index, the euro dollar, pound dollar, dollar Swiss, dollar Yen, as well as many more, and he also has weekly coverage of the crude oil market and the 30-year T-bonds as they both influence Forex markets tremendously. When you sign up for the Tiger Forex report, you also gain instant access to Teddy's 60-minute Webinar Archive. He just hosted Forex Strategies and Fundamentals, What is Behind the Tiger Forex report. For all the details and to start your 30-day Tiger Forex report subscription today, visit the front page of TFNN.com. TFNN Educating Investors. You might think that if you want to be successful at trading in the stock market, you're going to need a crystal ball. After all, it's impossible to predict the future, right? Like any endeavor in life, before you decide it's impossible, get some advice from the experts. You might find that it's not so impossible after all. For daily market overviews that give you direction on the key indices, selective stocks, and commodities, subscribe to the Opening Call newsletter at TFNN.com. The Opening Call newsletter is written by Basil Chapman, creator of the trading methodology known as the Chapman Wave. The Chapman Wave up-down sequence gives you an edge in identifying price turns, finding the peaks and valleys in stock prices. Get the Opening Call newsletter by Basil Chapman in your inbox every day. First-time subscribers also get a 30-day money-back guarantee. If you're not satisfied, let us know and you'll get a full refund within 30 days of signing up. TFNN.com Educating Investors. Steve Rhodes started his trading career as a student almost 20 years ago, and the student has now become the master. Steve won the prestigious Timer of the Year award in 2018 and barely missed that mark again in 2019, finishing at number two for the year, an amazing accomplishment. Steve Rhodes is committed to sharing his techniques and knowledge with anyone who wants to learn, and he shares his vast amount of trading knowledge every day in his Mastering Probability newsletter. Steve's award-winning newsletter, Mastering Probability, is delivered every trading day with updates throughout the afternoon. Sign up for Steve's Market newsletter, Mastering Probability, and you'll receive access to seven of Steve's educational webinars absolutely free. At TFNN, all our newsletters come with a 30-day money-back guarantee, so you have absolutely nothing to worry about. Visit TFNN.com and try Mastering Probability 30 Days Risk-Free Today. TFNN Educating Investors. Toll free at 1-877-927-6648. Internationally at<PHONE_NUMBER>. Welcome back, folks. So we're taking a look at one of Steve's Market Analyzers. Take a look at a number of different instruments. All of the, or most of the indices, U.S. cash indices that we track, the equity future contracts, the index ETFs, including the Equal Weighted, which is important to have out there. Those Equal Weighted for the S&P as RSP, that's a symbol for the NASDAQ 100, the Q's, it's QQ, EW. So we like to make sure that we're paying attention to both. Those would give us confirming signals on the sectors inside the S&P 500, if we have a stock, getting rid of the MAG-7. So those that show a star next to the number under the daily, it says D-TD9, column number 4 from the left. Whether it's got a 1 because it can be the bar, following bar number 1, that we're now-all of these are as of Friday's close out there. So those are all the signals. And you can see all the different tops. Not every single indices has a top. You'll see a number 8 here for the Dow Transport. From the Dow Transport, right now, 181. So we know there's no TD9 count top, at least at this stage of the game. That's in place out there, no start. But you can see a number of different TD9 count patterns that are in place out here, which is a pretty decent indication that we should see a short term top. Now, the question becomes, is that short term top just pulling back to test support and then we move higher? Well, why would we move higher if this is just a test of support, Steve? Now, that's a good question too. And the reason for that would be because of two different reasons out here. And the first reason is this is the 126 year seasonal cycle. Just plain. Now, what I've done is I put my D trending tool on there. Just makes a little bit easier. I'll take it off. Okay, so you've got that view. Oh, shoot. I got to keep it off the screen. I don't know why that screen creates a problem for that tool. That's okay, Steve. He's got backup plans. So just give me a moment. We'll switch over to that. We don't want to lose that screen. If we lose that screen, that could create problems for Stevie. And we don't want that during the show. We have it happens after the show. No big deal. So now we're back to this chart here, which again is showing us the 126 year seasonal cycle. But I put on the D trending tool out here. It gives us a little bit better view as to what to anticipate or expect. So I know that the market should be trading in essence somewhat sideways. We're not trading sideways. We've got TD nine count tops. But this shows us that typically, or the next few days by the end of this week out here, November 30, today's a 27 that we should see then market moving higher. Now we're in window dressing time period. All that sort of makes sense. Then we get a pullback after the first week of December. And then finally, you know, this is a seasonal, this is the 126 year seasonal cycle out there. If we go ahead and we just turn this over to give me a moment. Sorry about that. We just simply go ahead and take a look at pre election years. So all those will populate right now. And again, I've got the D trending tool on what you'll see here is we're also in a favorable time period out there. So it's very possible that what we're going to get, we go back to these TD nine counts will change the screens out here just so that you can grab them so that you understand where we're at with regard to the TD nine counts out there. So here we're back at this screen. What we may just simply be seen is nothing more than a two day pullback. So let's go take a look at that for that. We're just simply going to switch down and answer. I'm going to get to your question. It just is your question is basically when they get a grouping like that. What's the signal that they're going to move higher? Well, that's actually pretty easy. The signal is price takes out that resistance level and closes above that. But in the meantime, what might be going on here? So what might be going on is if we take a look at the end queue. Now, this is the daily dance steps, right? You and I have taken a look at this.  And if we take a look at the red numbers, red digits on this chart that you and I are looking at those represent consecutive lower closes one after another and the black digits are consecutive higher closes out there. You can see that coming off the low from October the 26th out there.  Now tells us we've got a real strong market now you didn't need me or this chart to tell you that, but we are all visual, not all of us, but many of us are more visual. And so we take a look at something it kind of puts thing in perspective. So wouldn't be surprised to see a lower close today inside the end queue. And if we do, maybe all we're going to get is just a two to three bar pullback out there. Remember, we do have new profile levels and inside the end queue is not shown on this chart here. But inside the end queue, certainly the numbers that you can use for resistance and support what's in question. It's only the ES that I believe is in question the center of the box. But the top of the profile resistance is 16102. But Nancy, in order for the end queue, what's the term basil uses out there? I don't remember right now, but in order for the end queue to resuscitate itself, tend to gate that signal and tell us that we're moving higher the TD nine count signal that is you're not seeing this on this chart. Nancy need a price close above 1617350 residual strength. Yeah, that sounds good. 16153. I don't think that was the word that I was looking at. But we're headed down the right path out there. But 1617350 is where price must close above. In order to suggest to you and I that there is a that there is a that's going to negate that a signal out there that's one way to take a look at it. And we'll take a look at another way to look at it. And we'll do that when we really go back and take a look at Magnificent seven for John out there here what we've got are the intraday time periods for the end queue. In the case of the end queue out here, all that we've really got is a two hour TD nine count bottom pattern. That's the primary pattern 30 minutes as a TD nine count bottom as well. We don't see out here is any kind of a topping signal. Now you could get a sell the D point pattern on the 30 minute time frame chart. Absolutely. You could get that in the next six minutes out there that would suggest price point back to test support the oscillator and change line at 16,006 and below that 15970 would be the move out there. So and we've just had a narrow range body today, at least thus far into the trading cycle out there. The to the upside would I be paying attention to if the markets are really going to rally Nancy what we should see is that TD nine count bottom on the two hour time frame chart take out resistance and here the resistance level is not just the top of the profile which so far is active as resistance 16,042 but instead take out 16,070 150. That's its TD nine count breakdown level. So 16,070 150 would be an important level to watch to the upside inside of the NQ. So we got that cluster that we took a look at a so called cluster of indices of index ETFs, including the equal weight out there. So is that but but there still is that possibly it's just possibility of just a two day pullback. If it is a top, we should see the underlying instruments. We see if I can let me do this. Let me close this out. I think I have the NASDAQ the top NASDAQ stocks out. Give me a moment here. Where we put those? Okay. So now we're going to change screens out here. Now I hope that the screen that I show you is still showing up real white. It's I'm got a failed monitor out there. I'm gonna have to dress over the next couple of days. It's still showing up and I think your view it still shows is pretty white. You don't see the difference. But here are the top eight instruments that make up over 50% of the weighting inside of the NDX 100. If you take a look at Apple right now, the upper left hand side Apple does not have a topping pattern. And all that's taken place so far today is a pullback in testing and rejecting of that green oscillator and change line. In order for Apple to tell us it's got a change in trend, we need to see a close below the bottom of its profiles at 188 29. In the case of Microsoft out here, Microsoft does not have a top in place. In order to get a TD nine count top today or tomorrow, we need to see a spike above 379 79. Excuse me. Sorry about that. We come back to this break. We'll finish take a look at the the the Magnificent seven will take a look at the New York Stock Exchange advanced client on center bowing and so fine. We'll be right back old report. As a precious metal gold is still king. It continues to hold the most effective safe haven and hedging properties across the global major trading hubs of the London OTC market, the US futures market, and the Shanghai Gold Exchange. The Gold Report. Tom O'Brien publishes his weekly Gold Report every Monday morning for subscribers consisting of coverage of the XAU, HUI, GDX, the dollar, bonds, the South African Rand, as well as 25 different mining equities with specific buy sell recommendations. The Gold Report. New subscribers get a 30 day money back guarantee so you have nothing to risk. Subscribe to Tom O'Brien's Gold Report newsletter now at TFNN.com. Sharpening your skills as an investor is like getting better at playing a musical instrument. You have to practice sure, but you also need excellent instruction from experts at TFNN. You'll get advice and guidance from the authority and technical market analysis, and it's not just dry, tedious text either. TFNN airs live financial content streamed live on TFNN.com and TFNN's YouTube channel with Tiger TV live every market day from 8 30 a.m. to 4 p.m. Eastern for free. Each host is an experienced trader and gives their take on the market while taking calls and questions live from around the world. From the moment the market opens until the closing bell sounds, Tiger TV has eight different shows with expert hosts to help you make the right moves with your money. Watch online at TFNN.com or on TFNN's YouTube channel and become the investor you were born to be. TFNN Educating Investors. TFNN has just launched their new trading room, the Tiger Zen. Hosted at Discord, TFNN has been educating traders for more than 20 years with live programming hosted by a variety of professional traders during market hours and now they are expanding their reach with the Tiger's Den. Available to all Tigers and Tigresses for just $1 for the year. There's no catch or added costs when you join our community of traders. In the Tiger's Den, you can look over the shoulders of Tom O'Brien and the other TFNN hosts while they analyze charts during their live Tiger TV programs and join an interactive trading community with hundreds of members exchanging ideas, interact with other Tigers and Tigresses as they share trading ideas, news analysis and discuss the market action all trading day, even at night and on the weekends. The Tiger's Den at Discord is accessible on mobile or tablets as well so it's always at your reach. To sign up today and become a part of this educational community of traders, just visit the front page of TFNN.com. Don't forget, you can listen to TFNN live on your mobile device 24 hours per day. Go to TFNN.com and hit watch Tiger TV. That's TFNN.com and hit watch Tiger TV. Welcome back folks. I switched over to the Netflix chart just simply to really answer Nancy's question out here about the TD9 counter. The question specifically is when they when they when can they regroup? When can they regroup like we've got and simply go higher? And so for that each one Nancy or whatever instrument is you're taking a look at. Here's Netflix as an example. Netflix forms a TD9 count top. It does it in the bar following bar number nine. The actual trading day that it does. So you're going to take like Stevie's tools out here. It confirms that TD9 count top on November 13th. So the very first thing that we know out here Nancy is at first on that day that was telling us that price should pull back to test that green oscillator and change line. Now in this case here it was green. We don't know whether it's green or red but in this case here it's green. We already know green oscillator and change line is a bullish signal. The price is above it. It's very bullish out there. Price never even pulled back to test that. In fact the next day the pattern was negated with a close above that high. That told us about a strong upward momentum move. So strong that now what we've got inside of Netflix is it's going to go ahead and complete a TD9 count top today. Bar number eight is the high of the pattern. Thus far what should take place is price should pull back and at least test that oscillator change line for 7130. We don't have any new profiles or anything inside of a Netflix as we speak right now. You just simply have to watch price behavior. I don't know what price is going to do but what we do know is what price should do and doesn't do that. Does it pull back and test to reject that level. If it does you would certainly stay along with regard to Netflix for its daily time frame. The price closed below that short of any new profiles forming the next downside target so that people can do a risk reward decision would be at break a level. That's down at 440 to 60. So hope that answers your question with regard to the TD9 counts. If not just keep writing me questions and we will get back to those as soon as we can. But we do have call ahead seating here. So as opposed to going back to the other Magnificent 7 we're going to go right to that call and that is from Brent in Martinez, California. Brent thanks for calling. Thanks for holding. How are you today? And happy Thanksgiving or post Thanksgiving. Thank you Steve. Same to you and good morning to you and yeah everything's well. How about you? Good yeah yeah yeah just you know I got to get rid of all that pie that I ate. Oh yeah only took like a you know a half an hour to take that all in and put it on and just wrap it to the sides of my body and it's going to take two weeks to take it up I think. But you want to take a look at AMBA I believe is a ticker symbol you're calling about and if so tell us what you're doing and how I can best help you. Yeah let me just go through really quickly just what I've been doing. I've been trying to do some different earnings plays but what I do is I don't buy anything until the earnings have come out the news is out and then and it can be something that has earnings before the market opens it can be something that comes out in the afternoon it doesn't much matter I just okay have the numbers come out so I can look at them and I used to try on occasion doing trades before they came out and I just found it's better to just wait and sometimes you miss them they just take off on you can't do anything but other times it works out and so. And so are you playing kind of a momentum type of a play is that the thought process or? Yeah well there's a pretty good example the other day I did zoom video okay came out with their numbers and I want to say that was after the market closed but it's definitely before the market opened and so I went ahead and the numbers came out they beat on earnings rather new but then the stock actually dropped which is that's even more ideal and the other I guess component that's pretty important to what I'm doing is I'm looking for stocks that are at the lower end of their range instead of being there their tops when I'm doing okay I'm trying to do calls on what I'm doing so in this case it was already near its lower end and it came out with good numbers but it dropped and so when it made that drop I just bought in and I and I'm doing really well I mean probably within a short period of time certainly that morning I was able to already get out and I gained so that's what I'm looking for and so now I'm looking at kind of going now to this last weekend I was looking for stuff that's going to be this week and Anne Barrow is one of them and I also have Marbelle is another one so okay so yeah so take a good right we'll take a look at both and thanks for that explanation and here we take a look at the zoom church I want to go back to that so people can see what actually took place here I'm going to guess that the earnings date was on November 21st I don't know whether it was before the bell after the bell or so forth but what happened on that day is price did pull back and what it was testing was profile support and that was at 6276 granted it got down below that it got all the way down to 6183 but what price was doing on that day folks was just simply pulling back testing support and that in essence using support as a level to get in so that was on zoom but Brent wants to take a look at ambrilla AMBA so we're going to go ahead and refire up those charts out there and they come out with earnings sometime this week yeah I believe both of them are going to be on Thursday either Wednesday after the market closes or Thursday I can't remember now but I have it marked down but and I guess my main question is what I'm looking for from you if you can do it is just if a word to take a dip like say zoom just like you're talking about there what would be some levels to be watching for so the first though so this did form a TD 9 count top two days ago so we've got a TD 9 count top in place so what should take place out here much like I will spend time talking about what with the financing with regard to TD 9 counts is price should pull back to that oscillator and change on so the first level that you would be watching or observing Brent is around the 52 27 level again that price going to change up and down so don't use it right to the penny but that would be the first level of support turns out that just below that is the top of its daily profile so short of some kind of new profile forming between now and when the earnings are released the second area of support you'd be looking at is 5104 if this were to take a real deep dive well that mean we'll get back below the top of that daily profile and then that would trade into a support zone and that support zone would start at 4816 as I mentioned ambarella has a TD 9 count top so what that does folks is that sets up a TD 9 count breakout level and that's the area at 4816 above that is the bullish structured profile and the bullish structured profile is between at the bottom or at at the low at 4868 and the center is at 4947 so the real support zone the real buy zone don't have any idea whether price will get back there Brent but you could set up triggers 4816 4868 4977 or 4947 what you would not want to see is price close below 4816 if it does that then that tells we get back to that swing point low from the end of October or the early part of November the weekly chart here looks pretty nice it looks to me like there's a confirmed by the D point pattern and last week price closed above the top of its profile if you get a second consecutive close above it this week and the it being 5507 that would be bullish and say that it wants to move further of course in order to move further to the upside it's got to take out that daily TD 9 count top and therefore that resistance level shouldn't fail because it's the other side of that trade when they do release earnings Brent would be a close above 5624 and a price close above 5624 is trading above it its price target will likely be 6096 now 6096 is a TD 9 count breakdown level but it could also form an A to B equal cd to the upside but 6096 would be the upside area inside of ambarella into the downside 4816 I'd say up to 4947 Brent we're going to a break I might at least get that out stay with us if you would what's the second instrument you want to look at it's a Marvell to MRDL perfect we'll take a look at that we come back to this break currencies commodities and bond markets are as important as ever right now with how they're driving the volatility in equity markets across the globe which is why it's a great time to try out Teddy keg stats tiger forex report Teddy keg stat breaks down the forex markets every Monday using his 30 plus years of experience as a trading veteran of futures forex stocks and options Teddy releases his weekly tiger forex report every Monday morning with coverage of all the major currency pairs including the dollar index the euro dollar pound dollar dollar Swiss dollar yen as well as many more and he also has weekly coverage of the crude oil market and the 30 year t bonds as they both influence forex markets tremendously when you sign up for the tiger forex report you also gain instant access to teddy 60 minute webinar archive he just hosted forex strategies and fundamentals what is behind the tiger forex report for all the details and to start your 30 day tiger forex report subscription today visit the front page of tfnn.com tfnn educating investors everything in the universe is governed by the Fibonacci sequence this mathematical principle is responsible for everything from the most aesthetically pleasing artwork to patterns in the stock market to stay on top of stock patterns you can take advantage of sign up for the Fibonacci 24 seven newsletter at tfnn.com when you subscribe you'll get a weekly report from veteran day trader Larry Pezzavento on stocks you need to pay attention to and you can trust Larry's analysis after all he's got 45 years experience as a day trader Larry will also provide daily charts videos and data on the key markets that he's tracking expect notifications from Larry on market movement you need to act on at any time first time subscribers also get a 30 day money back guarantee if you're not satisfied let us know and you'll get a full refund within 30 days of signing up subscribe to the Fibonacci 24 seven newsletter today tfnn.com educating investors are china a shares hot or not if you trade china a shares now may be time to take a closer look trade chAU or chAD directions daily CSI 300 china a share bull and bear ETFs china a shares in either direction visit direction investments.com today an investor should consider the investment objectives risks charges and expenses of the direction shares carefully before investing the prospectus and summary prospectus contain this and other information about direction shares to obtain a prospectus or summary prospectus please contact direction shares at<PHONE_NUMBER> the prospectus or summary prospectus should be read carefully before investing an investment in the funds is subject to risk including the possible loss of principal the funds are designed to be utilized only by sophisticated investors such as traders and active investors distributor four side fund services LLC. This program is brought to you by Vista Gold traded on the NYSE American and TSX under the symbol VGZ. I would Brent in Martinez California we're taking an umbrella AMBA is a ticker symbol Brett before I move off of these charts I know I threw out a mouthful there so to speak any questions about the the numbers of the data the any for any of the information that I shared with you on the daily time frame chart for umbrella. Not at all see that was fantastic that's what I was looking for and I did what they're both going to be Thursday on November 30th last day of the month and it's after the close. Okay so of course Friday would be the day I'd be trading it. Yeah perfect so I'll try I'll note that on my system out here and try to remember for us to take a look at the umbrella and Marvell come Friday morning out there we're taking a look at the charts here from Marvell now in the case of Marvell it also formed a TD9 count top it actually completed that pattern on November 14th the high out there that you'd be watching is 57.43 if price were to close by 57.43 that would probably trigger an A to B equal CD to the upside price target on the daily time frame around 65 and change out there there is resistance on the weekly up at 57.61 so you need to be aware of that. Let's say that Marvell pulls back because it's got a TD9 count top and all prices have been doing since that TD9 count top it's been trading within the upper range of its profile what I mean by that is between the center at 53.78 and the top up at the 55.95 level the key level of support here Brent I would say if it could get down there would be 51.61 that would be the bottom of its daily profile out there nothing here indicating to us because this TD9 count pattern took place two four six eight days ago a trading sessions ago I should say and it's just kind of a sideways move out there on the weekly chart it's bullish it has what looks to me like it's got a buy the D point pattern price above the green oscillator and chains on signaling its intent to go retarget 57.61 the monthly chart is trying to give us an indication that it wants to go target 61.69 but we won't know that for a few days out there so the areas to be watching as support on the downside for Marvell would be 53.70 would be 54.59 53.78 and 51.61 and of course I gave you what needed to happen to negate that TD9 count top what additional information Brent can I assist you with I think that's it Steve I just really appreciate you taking the time to do that and sure we will see what happens on Friday okay sounds good well we'll take a look at it and we'll try to we'll try to provide you with some information there so thanks for the call always good to hear from you and we'll look forward to speaking with you again soon that was Brent in Martinez, California let's go to Nancy's question here which was really about Microsoft so we spoke briefly about Microsoft I'll switch back to take a look at the Magnificent 7 for for John here momentarily but here we take a look at Microsoft all we can see is so far what this has triggered is a Rosemont Dominicator signal today what that means Nancy I know that you're trading this scalping I believe this to the upside there is no topping patterns in place out here what is needed to form a TD9 count top today or tomorrow today first Microsoft must close above this is the first thing it must do today and that is close about 377.44 Microsoft does not close above that at day's end then this whole TD9 count structure goes away what will still remain though is the Rosemont Dominicator signal and that would require a bearish reversal candle if you get that that would identify a top same game playing here same rules which is price is only supposed to come back and test support to break support tells us about a change in trend in the case of Microsoft the support right now is at its oscillator and change line it's trading above that that is still bullish out there and that's at 376.90 other areas of support will be down to 365.16 366.76 and it up at 374.75 the top of that daily profile so that's what's going on we take a look at Microsoft if we go and switch over to the Magnificent 7 or really just simply the top eight holdings within side of the NDX100 give me a moment we'll get back there I think I still have those we've got to change screens here give me a moment there and we'll just run through those pretty quickly just so I can make sure that I get through whoops dang it how about cancel there we go cancels a better idea all right let me change the screen again you weren't going to get what I was intending and so I caught myself what the heck now it's taking a sweet old time out there we don't have that kind of time okay here we got the Magnificent 8 the top eight holdings within side we've already covered Apple we've covered Microsoft Amazon no topping patterned in place out here wants to continue to move higher Nvidia has got a roadsman to indicator signal but no bearish reversal cattle consolidation with inside its profile we take a look at Meta Meta has a TD9 count top price pulled back and tests and rejected its green oscillator and change line so far that green oscillator and change line is at three thirty seven ten therefore its signal is neutral even though it's got a TD9 count top Avgo has a roadsman to indicator top but price finding support at that green oscillator and change line that means its signal is neutral you've got no top pattern in place for Google that needs to spike above the high from a couple days ago in order to potentially form a TD9 count pattern out there so we're looking at here as those that do have tops in place prices pulled back and tested and rejected support I don't know what it will do at day zen John C Nancy or anybody inside of the Tigers then but what I can share with you and narrate for you where the charts are telling us is 1148 is this is likely just going to be a two to three bar pullback a normal pullback inside of a bullish move out there if we start seeing key levels of support breaking well then we've got a different thing to look at out there one key level of support that certainly we can be watching inside of the NQ out there would be its perigee pivot point if we go ahead and switch panels go over to the black background screens well you'll see out here today earlier this morning is price pulled back two different times and tested that perigee perigee is when the moon is closest to earth during the current current lunar cycle I believe that took place last Wednesday I can't remember the exact day right now but 15981 is the key level to be watching in the case of the ESMini price is not even pulled back to test its perigee pivot point in in in a summary in short term analysis as long as price is above that other than finding and identifying a topping pattern let's say on a 30 minute time frame chart that is a bullish signal out there we're trading about profile when it comes to the NQ we're trading above profile when it comes to the ESMini out there gold the area to be watching on gold is at 2001 and 10 that's its perigee pivot point silver's way down to 2382 let's recruit on a rally could find resistance at 7784 and the US dollar index is trading below its perigee pivot point at 10348 that's suggesting to you and I that we may see US dollar index that continues to move lower out there so Nancy I hope that that helped answer your question with regard to Microsoft I hope that helped you answer your question John with regard to the magnificent seven out there let's get to Peter's question and Peter's question was about the New York stock exchange advance the client oscillator so we take a look at that Peter what we can see here if you take a look at the screen you'll see in the upper right hand corner you're going to see a series of higher closes out here price moving higher in the face when you take a look at the second panel out here that's the advanced client oscillator of price actually making lower highs that is an indication of a top now of a potential top that's out there these kinds of tops don't get much in the way of traction unless we see that spot volatility in its below its 50 day expansion moving average that's the very bottom panel of screen the very bottom panel screen shows of the 50 days at 1567 the spot right now at 1274 so that says any trade or movement to the downside is somewhat muted out there doesn't mean that we don't have a top and in fact Peter we take a look at the New York Stock Exchange I'm going to pull this chart over here right now I'll put it back you're going to see that today is going to complete a TD nine count top we would expect or should expect that the New York Stock Exchange will pull back and test that 157 31 inch type area out there so I believe the top of the New York Stock Exchange is setting itself as we speak right now we'll be right back you might think that if you want to be successful at trading in the stock market you're going to need a crystal ball after all it's impossible to predict the future right like any endeavor in life before you decide it's impossible get some advice from the experts you might find that it's not so impossible after all for daily market overviews that give you direction on the key indices selective stocks and commodities subscribe to the opening call newsletter at tfnn.com the opening call newsletter is written by Basil Chapman creator of the trading methodology known as the Chapman wave the Chapman wave up down sequence gives you an edge in identifying price turns finding the peaks and valleys in stock prices get the opening call newsletter by Basil Chapman in your inbox every day first time subscribers also get a 30 day money back guarantee if you're not satisfied let us know and you'll get a full refund within 30 days of signing up tfnn.com educating investors everything in the universe is governed by the Fibonacci sequence this mathematical principle is responsible for everything from the most aesthetically pleasing artwork to patterns in the stock market to stay on top of stock patterns you can take advantage of sign up for the Fibonacci 24-7 newsletter at tfnn.com when you subscribe you'll get a weekly report from veteran day trader Larry Pesavento on stocks you need to pay attention to and you can trust Larry's analysis after all he's got 45 years experience as a day trader Larry will also provide daily charts videos and data on the key markets that he's tracking expect notifications from Larry on market movement you need to act on at any time first time subscribers also get a 30 day money back guarantee if you're not satisfied let us know and you'll get a full refund within 30 days of signing up subscribe to the Fibonacci 24-7 newsletter today tfnn.com educating investors the reality is that navigating financial markets can be risky markets can be chaotic and difficult to understand having the latest market advice can help you turn this chaos into a key for creating winning trades at tfnn we understand that it can be hard to find reliable market news that's why each of our market experts offers their very own market newsletter a must-have tool for every trader out there striving to find an edge in today's markets tfnn newsletters cover every aspect of the markets so you can analyze the market before you trade try any of our great newsletters risk-free with our 30 day money back guarantee just visit the newsletters tab on the front page of tfnn.com tfnn educating investors you got the chart for a Boeing up on my screen out here and I've got the 30 minute time frame chart I believe Dan you took a short position inside of a Boeing if so the key number for you to watch and so this is a 30 minute time frame chart that's why we're focused on it all those red horizontal lines are TD9 count breakout levels for the 30 minute time frame what we can see here is we go back into the October 26 time frame we have not seen a close below we've seen a test of a breakout level out here that was back at about 12 30 back on November the 8th we have not seen a close below a TD9 count breakout level now take us to where we're at at 11.54 in the morning we are testing at 21770 level with bar number eight that says a TD9 count pattern should form on a 30 minute basis between 12 noon and 1 pm today so even if we get a close below 21770 I'd still want to see whether this TD9 count pattern forms and if so what price does on the other hand this level here at 21770 may in fact hold so price is back the key level of support when you take a look at that 30 minute time frame now on a daily time frame and the reason why that's so important is because there is a TD9 count top that completed on Friday and that suggests that Boeing should pull back to the 21047 level so your clue on that is going to end up being closing below that 30 minute breakout area Dan and somehow negating a TD9 count bottom should it in fact form I don't have a guarantee it's only bar number eight at 12 noon so I don't have a guarantee that at 12 30 you'll get bar number nine but you know how to calculate that pattern and if you do then you know what to be watching for there and of course that TD9 count pattern fails that tells you that you're on the right side of the trade and price heads back to that daily asset or a change line Nicholas wanted to take a look at SoFi out here SoFi right now is trading with inside its bullish structured daily profile and if SoFi can close the day above 704 and does the same thing tomorrow it would be signaling to us Nicholas its intent to at least go test the prior swing high that's up at 753 but maybe get up to its profile resistance level that's at eight dollars and 12 cents out there what else can we see with regard to SoFi? not much last thing that I'll do is I'll share with you Goldilocks you want to be careful with regard to gold and let me see if I get there to show us the reasons why right here I'll put it out there real quick oh I'm on the wrong screen I can't do that well we'll get to that tomorrow for sure folks stay tuned for all the great programming have a magnificent Monday I'll be back at 315 with Tom take care we'll see you soon


So, with this talk, we hope that you can get a good understanding of how the contribution workflow works on the Diego team and as well as other Cloud Foundry projects, and how does the engineering team engage with the community to deal with issues and take requests and that kind of thing. We also hope that you get encouraged to get involved and start contributing to either Diego or any other Cloud Foundry project if you are not doing that already. And we'll do that by giving you a general overview of how that process works with some background. And we'll show a walkthrough of how a simple contribution makes its way through an issue, then becoming a forecast and then finally getting merged into Diego. And lastly, we'll give you just some quick tips about how to go about sending a contribution and getting that accepted and preventing it from getting protected, basically. So some background. Pour request, if you're not familiar, is a term on GitHub that signifies a request to merge changes onto a project. So that's a great way to collaborate because it allows you, it's basically a conversation started and it has, you can comment and have multiple people basically review the same change set together. And Diego is first and foremost a team on Cloud Foundry that's part of the bigger Cloud Foundry project. And it's a team that maintains the Diego project, which is the container scheduler and orchestrator within Cloud Foundry. The full description of Diego is kind of a cytoscope of this talk. But the team is composed of four and a half bears, like we like to say, which means nine engineers and then one product manager. And these engineers are from a variety of companies. So like I said, I'm from Pivotal. Jenny here is from HPE. We have a few engineers from IBM on a team and we've had folks from SAP, GE and other companies before on the team as well. So it's a very diverse in that way. Those developers work full-time on the project and are responsible for not only putting the project forward and developing the features that the project has to work on, but also engaging with the community and dealing with issues and PRs. The team rotates fairly frequently. Like I said, I was on the Diego team, I'm no longer on the team. So we rotate within Cloud Foundry every few months and sometimes a little longer than that. But yeah. So to get involved and to get in contact with the team, we have a few things you can do. You can open a GitHub issue if you already have a bug report and you know the steps to reproduce it or you just have some suggestion that is a little more consolidated and then you just want to propose that just a specific project of Diego or of Cloud Foundry. Or if you just want to have a conversation or you have a question about how to get started, you can join us on our Slack channel on the CloudFoundry.slack.com. Each day we have a designed interrupt pair. What that means is in the morning we'll assign one of the pairs to be responsible for looking in Slack. So on the top of our Slack channel, on the subject line, there will be a couple of names listed. Those are the people responsible for answering to the community on Slack. So you can come by and ask any question you might have. And lastly, if you have some longer conversation that needs more eyes, maybe it's not with only one team, one larger CloudFoundry discussion, you can use the CFDAV mailing list as well to get started with that communication. So let's get to the walkthrough. So Jen will play a developer that's not on the core team of Diego. So she does not have commit rights. And she noticed an opportunity to improve one of the code bases. And she wants to contribute with that change. And I will play a developer on the core team that will assist her with that contribution. And I will be responsible for community for the day. So the same way we have an interrupt pair, we also assign one pair to deal with community. And what that means is we will look at issues and poor requests and interactions from the community for the beginning of the day to just be responsive to the community and make sure that those contributions are making their way through efficiently. So like Luan said, I'm an outside contributor. I'm poking around a little bit, Diego. I'm trying to understand the code a little bit better. I'm taking a look at, in this case, the executor code base. We have lots of separate code bases inside Diego. And we'll talk about that in a little bit. But I'm poking around. I'm taking a look, trying to get a little bit involved. And I notice there's one opportunity for a bit of a refactor. And so before I want to dive in and actually start working on it and submit the pull requests and stuff, I want to first just verify with the team that they agree that this is an appropriate refactor. This can save you a lot of time. Because if you go through and run all the tests, do all the work to make the PR and then submit the PR, and then later it turns out like the Diego team doesn't really agree with the direction or it conflicts with other work in progress or something that's a lot of wasted effort on your part. And it's just a lot of frustration for everyone involved. So in this case, I take a look. I notice an opportunity for improvement. I create an issue and I say like, hey, I notice this. Is it okay if I actually go ahead and fix it? All right, so Jen then sends the issue. And I, as the pair responsible for that community interaction on that day, will notice that a story will get created. So we have a thing called Gitbot that will look at our Git repos and create stories on our Pivotal Tracker so that we have more visibility into the state of that and what's going on there. So a story will get created in the community backlog and then we'll all look at it and respond as quickly as possible. So in this case, I'm just telling Jen that I agree with the change and I'm just giving her the thumbs up to go ahead and do it. So just a quick note about how our repos are structured in Diego. We have one repo called Diego Release. This is kind of the parent repository of all of our other microservices. This serves as our Bosch release. It's also a go path. It's sort of the parent of all of our other microservices. Each one of our other sub-components is all a sub-module inside of the Diego Release repo. So all of our go code is generally in one of these sub-modules. So most of the time you're not going to be submitting pull requests to Diego Release directly. You're going to be submitting a pull request to one of these sub-modules. And then later, once the pull request gets accepted, someone from the Diego team will go ahead and make a commit to Diego Release to bump the sub-module, meaning update the SHA of that sub-module to match what you just submitted. So in general, you're not going to be needing to make PRs to Diego Release unless you're doing something related to the Bosch release itself. So that means if you're changing the way the manifest are generated or the way the jobs are deployed, then there's going to be stuff in Diego Release. But if you're changing go code, that's not going to be in Diego Release itself. So we're going to be playing some videos as these go. But the details of what we're running here, like you don't have to jot down exactly what's being run here. All the instructions here are in this document right here. This is the contribution document where we list out the exact steps you need to do to set up your environment and stuff like that. So what we're going to do now is I'm just going to set up my environment. I got the okay from Luan to go ahead and make this fix. But I have a brand new MacBook. I've never worked on Diego before. I need to actually go and set up Bosch Light and configure my environment so I can work on Diego. So the very first thing we're going to do is set up Bosch Light. Some of you might be familiar with Bosch. It's like the orchestration tool that we use in Cloud Foundry. Bosch lets us deploy to multiple different eye ases. So you can deploy to AWS and Google Cloud and all these things. You can also deploy to a local VM called Bosch Light. And that's what we do for all of our testing. So we have a real live Cloud Foundry and a real Diego. It's just running within individual containers in a VM on your local machine. So we use this for running our basic acceptance tests and stuff like that. So here, we're just cloning the Bosch Light repository and running Vagrant up to get our local Bosch Light up and running. Next thing we do is we need to actually pull down CF release. So Diego release depends on Cloud Foundry. CF release is a repo that's pretty similar to Diego release in that it's made up of lots of sub modules. So CF release has even more sub modules than we do, so there's a lot to bring down. So when you bring it down, there's gonna be like a script in there called ScriptsUpdate. You can run this basically just as a get pull and updates all the sub modules and initializes all the sub modules. Once you actually have the CF code, then we're gonna actually do a Bosch Create Release and a Bosch Upload Release to get that code all set up on the Bosch Light box itself. So you can see here we've sped up a bit the process. This actually doesn't take quite so fast. You'll find that out when you try to do it yourself. But it should be pretty simple to do. It just can take a little bit. I'm just gonna skip the rest of it for now. So the next step is to actually get Diego release. So like I said, Diego depends on CF being there as well, but we also obviously need the Diego release code as well. So now we're gonna pull down Diego release. We're gonna do the same thing where we're gonna clone it and pull down all the sub modules, do a Bosch Create Release and a Bosch Upload Release. Again, all of these instructions are laid out in the contributing documentation. Next step is to actually deploy the releases that we just uploaded to Bosch Light. So what we've just done is we have now some tar balls that contain the source code for CF release and the source code for Diego release. But nothing's actually been deployed to our Bosch Light yet.  So now we're gonna generate the manifest. That's the deployment manifest for CF release. That's the thing that describes how this Cloud Foundry is supposed to be configured and what properties it has, what VM sizes it needs, and stuff like that. And the CF release repo and the Diego release repo both have scripts you can use to generate a Bosch manifest that's specific for Bosch Light. So you don't need to tweak anything yourself. It's already configured to be sized correctly and have the right properties for Bosch Light. So we run the scripts, generate Bosch Light, dev manifest, and then we actually do a Bosch deploy and we get CF running on our Bosch Light. And then we're gonna do the same thing with Diego. Diego actually requires not only CF release and Diego release, but it also requires either Guard and Linux release or Guard and Run C. Those are the two options that we have right now for running for the actual container runtime. And there's a RudaFest release and either at CD release or SQL release.  And in one of the previous steps, we also had to download and those tar balls and then put those on to our Bosch Light as well. Okay, so our Bosch Light is all up and running. We can also verify that, we didn't do it in this case, but we could verify that the Bosch Light is working correctly by just doing a simple CF push and making sure that it's actually using Diego and just do some basic verification. We also have a big suite of unit tests. So what we're doing right now is we're just, before I even start coding, I wanna make sure that my environment is clean and that everything is working right. So I'm running our unit test right now. Our unit tests run directly on your host machine, on your development machine. So in this case, it's a Mac. And so it's actually running directly on my Mac. Usually the unit tests are pretty well isolated and they run pretty quickly. We also have another test suite called Anigo. Anigo runs a bit more integration type tests. These tests that when we have multiple of our microservices all deployed and running together that they can talk to each other. It's not a full Bosch deployment. So it's not really a real Diego or real CF. It's just testing that if we have this component running and this component running they should be able to still talk to each other even if it's not deployed on Bosch and we do some basic verification there. We run these in a container on concourse. Some of you may be familiar with concourse as a CI continuous integration tool. We use concourse in this case as just a convenient way to run a containerized job locally. We can run it either locally or we can run it on our actual group CI pipeline. So if I don't want to wait for it to run on my machine I can run it on like in our case we can run it on our AWS deployed concourse. But for an outside contributor you're gonna have a local concourse most likely that you're gonna run this against. And the steps for setting up concourse are again in that documentation with everything else. It's also a vagrant box so you just bring down concourse light and you vagrant up and then you have a locally running concourse and you can run these tests. Now onto our third suite of tests that are run on your local environment. These are the acceptance tests also called CATS. These are what we need Bosch light for. So these are gonna be actually verifying CF is working correctly from sort of an end user perspective. These tests actually use the CF CLI directly and make sure that the basic scenarios are all working end to end. So this is why we needed to deploy Bosch light in the first place. And so again we want to make sure that everything is working with these acceptance tests locally before I actually start doing development. Because if I start doing development and then things are broken then I'm like I don't know if I messed it up or if it was messed up to begin with. So we just want to make sure I have a good clean environment, especially the first time I start doing development for Diego. So now my local environment seems fine. All the tests pass, everything seems good. So I'm ready to fork the repository. So in GitHub, some of you might be familiar with this already, but when you fork something, it means you're making a copy of it under your local username. So this is gonna create a copy of the executor. The executor is one of our sub modules. It's gonna create a copy of the executor and it's gonna put it under the gen spinny user. So it's gonna be just like the repo that exists in Cloud Foundry, but it's gonna be under my name. Now that I have, now that I check that out and I do a get pull from my, from my version of the repo. I'm gonna first start off by writing a test. I'm gonna see that it's a failing test to make sure that I'm actually writing a test that is actually testing what I want to implement. And I'm not just accidentally after the fact, writing a trivially passing test. And then I'm gonna actually code up the fix. And then once I'm satisfied that my code makes the test I wrote pass, I'm gonna run all those tests again. So those three test suites that I just showed you, the unit tests, an ego, and the acceptance test. I'm gonna run all those, make sure everything is green. And once that's all done, then I'm ready to start to open the actual PR. So when I go and I do a push to my branch on my forked repo, so gen spinny slash executor, when I push to a branch there and I go to GitHub, I'm gonna see this little thing pop up that says, do you wanna do a compare and pull request? And so I click on that, and then there's an opportunity for me to write a little bit of a description. So here I'm gonna reference the issue that I made at the beginning. So I'm gonna just say, as I said in this issue, I wanted to do this little refactor, that makes it so everything's kind of linked together. And if it's not Luan the next day, if it's some other person from the Diego team, they can follow the track of work and they can go back to the issue and say, okay, they had this discussion and it just keeps everything well linked. So there's some things to keep in mind when you're sending a request. Specifically about testing, we wanna make sure that we are covering edge cases and error cases. So when you're writing your test cases, add your happy path, but also think about what could go wrong in there. And if that's not present, we'll likely send a PR back. So hey, can you please add a little more test coverage around these scenarios? So can just be proactive about that. That helps a lot in the team make sure we're getting a good contribution. And also make sure you run out of tests before you submit the request. Jen said that, we're probably gonna say that again before the end of the stock. But it's also very important that the test pass because if the tests are read when we get the request, we'll likely not merge it. That said, I'm again the community pair and I noticed that Jen has sent her request like she had promised. So the first thing we generally do is through the GitHub UI itself, we'll look at the file changes just to have a quick glance of what was changed. If there's any obvious things we can recommend should be fixed. In this case, the request Jen sent had one style of reference that the Diego team does that she didn't necessarily follow. The particular example here is the order of the arguments is not what we generally do because we generally have a logger as the first argument just to have a standard since that's kind of all the methods we call. So I just send that feedback to her and instead of just fixing that, I send the feedback so that next time that she sends a contribution, she'll know and not make the same mistake again. And then after I give some feedback on the lines, I send one message saying, hey, I wrote some feedback to your change. It looks good otherwise, it's good to merge just if you could just fix that and update the PR then we can just merge that in. So I see his comment, it's an easy enough fix to do. I just reorder the arguments in that function. After I do that, I'm going to do a git rebase. I'm going to do this so that I can squash my two commits because I don't want to submit this as two separate commits. But also because I want to see if there are other changes that have gone in since I did this, I want to rebase against Origin Master, like against the Cloud Foundry version of the executor. In case, while we had this back and forth, there might have been a couple of days that went by and maybe someone else committed. And so I want to make sure that I'm rebased on top of the laziest version of Origin Master so that my PR can go in cleanly. Then once that's all done and rebased and I have a single commit, I'm going to do a force push to my branch and this is going to automatically update the PR. Once I do the force push, I'm going to go back to GitHub and I'm going to update the PR and say, hey guys, I updated it with your feedback. Can you take a look again? Well, and then finally, when I get to the updated pull request, I will look at it again just make sure that the changes make sense. And if they do, we'll pull the code down locally so that we can run the tests. If there is any less minute things that we noticed like a typo, for example, in this case, I mentioned there was a small typo, so I just fixed that. So we'll do small fixes like this one in the last minute. But we'll run a test, make sure it's all good, and then we'll merge it. When we push the merge, GitHub will automatically update the story, the pull request, so Jen gets a notification. We'll also update our tracker story just signify that this is all merged and get to go so that our product manager knows to take a look at it and accept the story. Yeah, and then at that point, contribution is merged and all done. So we just want to cover some common rejection reasons, or not really rejection, but reasons that we might come back to you and say, oh, we're not ready to merge this yet. So if you don't have adequate test coverage, so remember, we want happy path tests, but also edge cases. And depending on the scope of the work, that might mean unit tests or that might mean a Nego test or acceptance test. We'll probably be working with you through that, if it's a big enough feature that you might need one of those. We'll point it out to you. But in general, you want to be thinking, am I testing every edge case? Is my code fully tested? Another reason we might come back to you or just flat out say we're not taking the pull request is if it conflicts with work that is already in progress. This is more if you don't talk to us before you do it, if you just submit the PR. So if it's conflicting with our roadmap, meaning someone else is already working on something similar, or it's just something that we don't think is the right direction for how we envision the code going. So just a reminder to talk to us first. Another reason we could come back to you and say we're not ready to merge it is if the code is not re-based against master, meaning it won't merge cleanly. So this is a little bit unfortunate that sometimes pull requests can take a couple of days to go through because there's a little bit of back and forth. And in that time, if it's taking a while, other people come in and actually make commits in the middle. And so you have to go back and re-base and make sure your branch merges in cleanly. Another reason is untidy commits.  In general, for most cases, you probably want to have just a single commit. So you want to squash your commits. So it looks clean in the get history once we actually merge it. The other issue would be not running the tests. And so you have some failing tests. And then we catch that, and we come back to you, and it lengthens the whole process. So lastly, if you want to get involved, but you don't have a specific feature you're dying to do or you don't find a bug or something like that, you're welcome to come to our Slack channel and say, hey, my name is blah, blah, blah. I'm interested to get my feet wet with Diego, but I don't know where to start. Do you guys have some bug I could work on? Is there something I could do? And we'll work with you. We'll try to find something. Our tracker is public, so you can look at what we're working on right now. But I wouldn't go and just pull something off of tracker and assume that you can work on it. For the most part, we assume that the tracker, the stuff in tracker is stuff that we're going to get to. If you see something in tracker you want to work on, you can message us and say, oh, I really want to do this, and then we can talk about that. But in general, the tracker, we assume that the core committers are going to be pulling things off the tracker backlog. So just the main point is just talk to us if you don't know what you want to work on, or even if you do know what you want to work on, recommend talking to us first, and then we can have a conversation before you invest a bunch of work and energy. So with all that, is there any questions? Sorry, the question was about license, like contribution license. That's a great question. I don't know if we have some automated software or anything that goes through and checks for it. So the question was about. So to send a contribution, you have to sign a CLA. That's actually an automated process, but that's for the individuals. It doesn't necessarily solve the problem of someone sending a contribution that is copied from somewhere else. Yeah, but we have an automated process for signing CLAs, which that's basically how we have automated. Yeah, so it's tricky, you know, it's tricky. But yeah, there is a point that we didn't mention here, which is that if you try to submit a PR and you haven't signed the CLA, there's an automated box that's gonna come back and say, you know, you need to go and sign the CLA, but it doesn't really solve the problem of people going in like stealing code from places they shouldn't be stealing it. Yeah, people don't think about it. Yeah, I think it's kind of a problem for any open source project is, you know, you kind of are trusting the people that are bringing the code in to be doing it in an appropriate way. Any more questions? That's a good question. And you should stay for her talk after this because the Diego team actually has three time zones now. So generally available from what, it's nine on US East Coast until six on West Coast or yeah. So there is a good 12 hours there, but yeah, there's some availability issue there. Any more questions? Cool, thank you everyone.