Ok, bonjour tout le monde, bienvenue à la Team Meeting de l'infrastructure Weekly de Jenkins. Aujourd'hui, nous sommes le 5 mars 2024, mais ce n'est pas le 23 mars, c'est quoi que vous faites ? Sur la table virtuelle, nous avons ma saison des portales, Hervé Le Meur, Mark White est off, Stéphane Mer, Pounovarton et Kevin Martins sont ici. J'ai oublié quelqu'un ? Non, ok. Nous commençons avec l'annoncement. Le week-learn est 2.448. Donc, le part de package est ok. Nous avons eu des comportements de l'agent. C'est la première fois que nous avons perdu contact avec l'agent durant la phase de synchronisation du mirroir. La deuxième build n'était pas dans le monde, il n'y avait pas d'erreur, mais c'était locké. Il n'y avait rien à faire avec la machine remote. Mais tout était déjà mirroir. J'ai joué le step manuel directement sur la machine de pkg et tout est gris. Mais c'est drôle. J'ai ajouté les steppes sur la chaine githènes. Si cela s'occupe d'une fois que je ne suis pas là. Donc, l'information est chérite. C'est un script pour renseigner le machine mirroir. L'image docker est ok. Il est publié, donc pas de problème. Kevin, tu as un update sur le change log? Un change log est publié. C'est disponible sur le site. C'est cool. Merci. Ok. Il y a quelque chose d'autre sur la release. C'est à dire que nous sommes prêts à rouler, Stéphane, pour l'update de infrascii. La prochaine semaine. Je ne serai pas disponible. Je ne me souviens pas si nous avons choisi de maintenir ou de consulter le meeting week. Mais je vais avoir besoin d'une personne pour prendre soin de ça. Si nous gardons le meeting. Est-ce que j'ai été arrêté ou est-ce qu'il y a un problème? Non. Ok. J'ai besoin d'une volontaire pour rouler. Vous avez besoin maintenant? Nous avons volontaire avec Hervé. La prochaine semaine. Je ne m'en souviens pas. Ok. J'ai un problème avec le milestone. On va avoir quelqu'un pour le replacer. Je vais vous déterminer. Je vais essayer de penser à ce moment-là. Juste en temps pour obtenir la proper permission. Vous avez un autre annoncement? Non. Ok. Je vais essayer de faire le calendrier. La prochaine semaine. La prochaine semaine. La prochaine semaine. Je ne me souviens pas. La prochaine semaine. La prochaine semaine. Ok. Nous avons eu un lts depuis la dernière fois. Marche 2020. 2020? Merci. Vous savez la version? 2440.2 Vous disait 20? 20 marches. C'est la semaine, vous savez. Je suis en train de lire les commentaires. Marche 2020, c'est la semaine. Oui, je suis désolé. J'ai parlé au 21 juillet. Ok, merci. Et le premier annoncement pour cette version. Merci, les gens. Cool. Nous avons un annoncement pour l'adversaire de la sécurité de l'adversaire. Si je ne m'en souviens pas. C'est le 6 juillet. S'il vous plaît, n'arrêtez pas d'arrêter le CIG. Ne faites pas n'importe quoi sur cette machine jusqu'à ce que le système soit prêt à rouler. On va laisser un jour entier pour tout le monde pour faire son travail. Parce que c'est un ordinateur. Ce n'est pas un ordinateur. Ce n'est pas un ordinateur. La prochaine événement sera la conférence de Scalics en Californie. Je crois au moins Marc, Basile et Alissa. Oui. Je vais me couper l'année dernière. 17 à 19 de Marche. Si vous voulez rencontrer Junkin, c'est le perfect place. Est-ce qu'il y a un annoncement du calendrier? Ok. Pardon. Je crois que j'ai oublié quelque chose. Ok, on va continuer. Let's have a check on the tasks that were done during the past milestone. Array, I might need your help from time to time. Delete Gerabot issue and delete users. That was fun. Ok, cool. Improve robustness of the city tool chain. In the incremental team Jacob has added some code to avoid failing the job when we encounter a 503 error from Kitabaki and 403 error too. So it's more robust now. It might also result in some potential not stored in Jenkins CI organization repository with the build child with C3 tentative which repository so we might have some for one error reported in a desk but less than now. Thanks. So Kitab city process fail with 401 correct. So Alex remained me and showed me that running the repository permission update job entrusted was sufficient to renew these maven settings stored in Jenkins CI plugins repository secrets. Ok. Same for the next one. Cool. That was the week of the error failing. Nice. And finally You were able to fix the issue on the mirror export. I used a better page and the mirror stats one and the pro is now we are not depending on the specific file presented on any mirrors. The con is that we lost the continent information of each mirror but it's not main information from this report so it's not that important. Ok. So I see we have already a new version because this schema was changed that's nice. Ok. Good. Any question on this task that were fixed? So we have two issue closed as not planned user opening an issue with no details and when they are asked question they never answer. If they don't answer. Now walk in progress I'm going to try to Oh what happened? I had an issue sorry. I'm going to try to sort by priority. So right now the first priority was easy copy Can you give us an update on what was done on that topic? There was three main repository using the plugin site and all of them has been migrated to new storage accounts from standard to premium and to version 1 to version 2 as most of them had cost related to transaction putting them in premium as a result to not pay any transaction so we have minimum of around 20 dollars per month per storage account as minimum cost but we don't have the variable cost so far most costly one was Jenkins data.io which was at 70 dollars per month all of them has been porté to this new storage account and are using service principle to generate short lived SIS token to synchronize the content to the other file storage Azure file share and the big benefit here is the time for uploading so main the reduction is quite big for Javadak we went from 40 minutes to 1 hour on Carter to 11 to 14 minutes with ACT copy the other build were reduced so first build less cost and secure development and up-to-date tooling nice the next one are the mirror scripts executed from the pkg virtual machine I have it's related to the next one the blocking point for us to add azure click on this machine so we can use it with service principle to generate SIS token as soon as tools is present in the puppet setup I'll be able to rework the existing script to use to generate SIS token instead of using one standard production team decision to stay on the access key code system as azure SP would add over in this context ok the service principle is for the updates in detail so I should be able to finish this week I think ok I've got the puppet part and the script part will be shouldn't bother me ok don't forget to announce it when you will change it engine just for the case if az copy changes metadata on the files or change the behavior of the copy that might have impacts on the update center so just announce it so if something goes wrong that is un foreseen then we will other persons such as daniel or alex will know and they can go back to that change ok for you and don't forget we will have to clean up if it's not already done there are many clean ups to do for the preview storage account I also saw some others that haven't been updated since 2 years and we that we might be able to remove be careful with stuff not used for 2 years last time daniel killed us it wasn't 2 years it was just a week so ok yeah yeah so a big step of clean ups will be the last step of this helpdesk the next one we've update the thinking that I owe is ready to the next step of the previous one I need as a plea to be able to finish the script as a full request where we are testing your jobs on the data thinking that I owe entrusted is already up to date with the code to generate ss token but we don't have as your plea on this machine right about entrusted agent token used un entrusted agent entrusted agent entrusted agent it's non ok my missing piece it need to be installed on both entrusted and pkg VMs see next steps ok so I assume once you will have everything working on one that will un block the other anything else on these tasks on this one no should be really soon as soon as the puppet party is ready we will be able to ask a drinking security team to review the main request nice good job this one is my fault I forgot to renew ss token used since the cryo jobs ok and the cloud flare r2 token so this weekend I renew the ss token in azure and replace the credential entrusted but the r2 bucket start was failing but azure synchronisation was restored ok and this morning we renewed the I had an issue also on updating the token on our private repository d'afforme state jpg error that we resolved together this morning so I was able to renew the ss token update the credential so we have now to restore crawler r2 bucket synchronisation part that we commented this morning ok I will let you do that task then ok in terms of priority we moved some tasks for next week so I'm gonna finish with the task working progress but we have on top priority RM64 oh what did I do I might have clicked the wrong ok so RM64 is on top priority do we have something more prior I don't see certain on RM64 can you give us a quick status yes sometimes you go you stop and then it's going fast I'm not sure if you want to have everyone got it ok so that's a connection problem or a very good example yes we I'm fighting with one usage on Jenkins.io I had an error with the usage of pod in RM64 et AirV pointed me that it might come from the size of the pod so as for another task he created new pods as large RM64 I tried to use it but then that was a rabbit hole and I found out that those large RM64 were not able to spawn because we are missing a nut pool those large nodes and then those nodes were not able to be created because of the Kubernetes version that was a little too old so we both tried to upgrade that patch version to 1.26.12 instead of the 1.26.6 and then we we had kind of a nightmare because the upgrade killed the connection through the agent so the agent cannot finish correctly and kept the lock on the terraform state so we called emergency which is Damien du Portal and this morning we were able to remove the lock and get back to work but then by discussing about that usage of a large agent we decided to try with a VM instead because the pipeline used on the CIG in IO is running on a VM and we plan to merge both pipelines so I did changed my aim and try a VM like an hour ago and I'm not sure it went through but it's on it's way ok I might be mistaken but I remember both of you mentioned a second job was it a Kuntap or something that require a bit more memory so same context for a Kuntap it was a Kuntap on a question progress in a few weeks already and we discuss it together on this progress the agent was killed and we might want it to compare the HDK 17 on CI to check in IO plus sources to compare them all to info on CI it was a 4 CPU 1 frame versus on info on CI alpha CPU 1 gigabyte of RAM so I created 2 template info on CI large 64 on info on CI it passed my build passed ok both of you might want to check that we are not on a word case solution could be also using virtual machine it's not I would say it can be the same cost or even cheaper to use virtual machine than pods but that's a hard take that I'm making but that's a viable solution something else on IRAM64 is it is there another task or what will be the next task taking I got all the checkbox to check for that image you can check on the issue if you want but there is a lot of work yes ok you have plenty of nice next topic someone in Romania was blocked from downloading they were redirected to the ARCH on university web server there has been a discussion I believe that issue might be closable I don't know if we keep it for STCO mirror that's a secondary topic that's fine I will create a new issue but the goal is just can we check that I ate the cloud was able to don't know everything I think so yeah last week because they never answer to the last message from C auto cool my proposal is we check if that problem is solved for I ate the cloud then we can close the issue and start a new issue which name is a new mirror for STCO ok so let me comment it let's confirm each user is now un blocked let's open a distinct issue about the new mirror provider survey do you want to share with us the new provider status this person this person this admin contacted us and he has he has to put in place ercing or ftp server on their mirror so we can integrate it with mirror bit for us to check in mirror bit almost there but that's cool that may be a new provider for the eastern Europe thanks for the offer to lock any country we want to push people to offer a new mirror for that country nice that's a good way to push people to offer mirroring I mean that's a way, that's a technique we have a reek sorry let's go on the order now I will read the third one in priority yes I agree update CLI step fail regularly when processing Jenkins IO pull request the title could be github app github action are failing because it's not only update key it's a label check every github action are it's not the only one I saw ok are we sure it's the github action on Jenkins IO yes I had the issue with the label one I don't remember what it's doing but that's really annoying label conflicting pull request workflow ok so that mean we might need to add the tidbacks solution then if not already the case that's weird it's using its own yeah that's why so this is because the same ok that's why it was failing too so that could be worth an explanation first on the issue just for the self documentation the github token here is the author of the pull request so that mean the API rate limit applies to the person who open the pull request so there are multiple solution at least this one shouldn't use the github token like this it should use the tidbacks to use the github app and then generate a new one hour value that will renew the the rate limiting ok so that one is to be checked that's an annoying one ok we'll have to find a proper solution on this one so yeah to be addressed we can create a github application and set it to this repository and generate the API rate so we'll see you later not that easy because that's a public repository you will have a permission issue the problem here is that we're not on infrasci so anyone opening a pull request the github if that's not that easy I don't think it's that easy because we don't want an external user running an update CLI command with the github token of one of our github app that will be a great way to extract information we can limit first contributors but it won't prevent people who are already contributed I see what you want we could check tbx but the problem here is because of the emitting user so yeah that's an annoying one or we can move the update CLI process on infrasci what will be the danger I'm thinking out loud but on donker Jenkins Weekly we are also using a github app to generate token to create a pull request you know we know let me gather on the update plugins only on the main branch we choose tbx for that I'm sorry to kill the game but don't you think we should discuss that after yep not true not an easy one issue open by Alex he's asking to exclude some repository from the ACP why not I'm still not sure depends on artifact that's machine generated if a new version and therefore not available okay I'm not sure to understand their problem but no problem to remove that that means it won't be cached that's only for one plugin so that should be okay any objection already open the pair looks good okay plugin ill scoring configure new job and see ijan kinsayo I discussed with instead of its using a statics file instead of querying the api for the plugin site so okay he created a pull request that emerged today that generate a report with content of the api the same call the plugin site is making so now we've in the plugin site we can atom code to query this report instead of the api so we don't have to have the plugin scoring with the api nice don't forget to add the references on the pull request then yes I have to discuss with him about this job the open this issue before we discuss this report is it okay for you to drive the topic since you started it or do you yes no problem this question in that makes sense with adria is to decouple plugin site generation from plugin health static file better availability nice we still have free minor issue monitor builds on our private instances so as I understand that one you worked on it can you give us a short summary I've got report of every jobs of private instance but but it's using token which we don't have good way to manage their life cycle on their restriction so I don't know if this work will be usable at all I have to exchange with chanking security about it with Daniel back chanking user token used to pull information from each controller life cycle permissions on each okay thanks for this one so I propose this one to be put on hold put on hold until we get a security feedback next one thanks for that I I I I updated some range protection on some repository when I when I see them I but I haven't separate more pipeline this week ok, that's really low low low priority and same for the other I believe something has been I saw you open an issue yeah I reported I reported a two or three repository I've done before I opened request on the main tank in San Francisco and Alex made one ok nice ok, so this last three will be put on hold or removed from milestone at least ok ok ok now let's have a look at the new issues is there any question on the walk down or being done 2, 3, no ok so let's consider first what we scheduled for the upcoming milestone we have a few issues here as well first upgrade to Kubernetes 1.27 so Stefan you started to work again on it what's the planning planning is AWS first so I did prepare the comment with all the checkboxes but the first step is to redo the reading of the changelog but with AWS in head and not Digital Ocean and and yes planning it on Thursday if you are ok with that looks good and next will be Azure we have a little discrepancy right now as we did upgrade the private K8S to 1.26.12 while the public K8S is still in 1.26 6 so this may give us problems we may have to upgrade to the same patch version but should be ok unless we have a problem worth mentioning it that means we have 2 weeks to wait for before having everything on the same page so no worries on this one that should be ok ok I'm switching these to the milestone ok and the next milestone we have a lot of issues past release sites are taking long time to load I propose that we move that one on hold we put that on hold because it requires not that much of work but still some work let's remove milestone from this one we have the migration leftover from public K8S to RM64 I won't have that much time to work on this one I believe let's remove this one to another milestone for later same intermittent out of memory we don't have the bandwidth for this one same for this one I won't have the time to spend on this it's not blocking same for the open VPN clean up removing the central cache this one must be moved somewhere else that one is important and that one is top priority as the same as update center and I don't know for docs jenkins are you are you able to spend some time on it no I was in the black fixation so for the next let's keep it but in low in the bottom ok update I'm trying to to add the proper priority unexpected delay is building a small plugin on linux agents so for that one it looks like it was due to digital asian we should re-enable digital asian on cian jenkins you to see what is happening do you think you will be able to try it at least or we have to re-enable digital asian and run a job so yeah ok so I'm letting it here that one is low priority as you say that one is to be treated update CLI I think we have the right order of priority reminder the new private kubernetes cluster the goal is to have the build agent from infrasci to be built on a new cluster that will run as your sponsored subscription for instance the rm64 not pull you trifled with should be on that new cluster so you will have separated cluster between controllers and agents is it clear for everyone yes but that one is not that important compared to the aws cluster from cloudbzaws that one will allow us to create one or two new eks cluster the question was should we upgrade 1.27 for these clusters propose that we don't try to couple them that one require setting up the account checking the credits are present preparing the work on the terraform project to see how can we use multiple aws account on the same terraform project resources could be spread bit that would also be the opportunity for us to upgrade to the new eks module I was planning to start spending bit of time on this one this week is the goal clear is there any question or objection ok cool we can really realistically start looking at the triaged issue so artifact proxy does not deliver incremental jars that word so that need to be analysed is that correct rv that legit issue we have cannot login success so that need to be checked inside account app to see what the result is so i'm adding it to the milestone they didn't receive any email so worth looking at the logs of account app see if their account exist etc most probably they are mixing up account app and their own Jenkins so proposal from basil stop stop excluding the maven central repository on ACP that will increase the storage and the bit that will increase a bit the workload but that will help to achieving faster builds so that will be removing the exception on the settings xml and see what is happening the risk is that if we forgot why there might be a reason or word thing we might have to roll back that change I don't mind taking care of this but once I will be off again I will have to be aware of what will be the condition to roll back it is that ok for you folks ok there is a repository to archive so I've already I'm taking care of this one so we can remove the triage there is a discussion between jc and basil regarding le support log formateur ok on a to let them decide but that's not triage and finally evaluate clean owner it's a new functionality from kitab global kitab action that does a quickly clean up of code owners and remove old members create a request to remove old members or in code owners interesting ok worth checking with team since he's the admin we can try even on the genkins in 5 needed ok I think we have covered all the new issues yes yep I thought I removed triage just been removed ok do you have other topics to check for the milestone stuff do you have other topics you want to mention ok is the prior set of priorities that ok for you I will have one last look ok so the last good news is that we spent the 4.4k last month on azure which is way above the expected threshold so congratulation to everyone and we continue decreasing because I haven't checked in detail the work from airway but I totally believe that we will gain a few dollars for each of the premium account storage that replace their quantum parts without the transaction cost so yes nice work so I'm gonna be there in 2 weeks see you next week for the people who won't be in holidays let me stop sharing my screen and stop recording bye bye bye


And we can do kind of like a Q&A for the guys on YouTube, for the guys in chat. Who wants to come on? Let's see, I don't think Bao's here. So what we can do, Joe, you wanna come on? You available? Chipotle not accepting Bitcoin. They're giving away 100K of Bitcoin.  Who's here? Who's here? Joe, you here? Someone get Bao in here. Where's Bao at? Someone go tell Bao to come in here. I need a partner. What do you guys wanna talk about, man? Post some topics of conversation, guys and we're gonna get your questions answered. Post your topics of conversation, ask on YouTube. We'll see. And we can definitely get some questions answered. We can go over some details. We can go over whatever you guys wanna talk about today.  Actually, I can go through each ticker as well if you guys want. Let me, yeah, let's do a little bit of that. Maybe Bao will come in later. So, guys, what do I talk about every single day? I talk about this literally every single day. It's actually mind-blowingly simple. The thing about trading is, look, trading is not an easy career because, and I'm just gonna rant on a couple things for a sec, is it gets you guys head right or maybe give you some different perspectives. Trading is a job whether no matter how good you're doing, whether you're doing poorly, whether you're doing really good, you're always kind of on a little bit of adrenaline.  We've all been through all of it, right? And the feelings associated can sometimes be very whipsaw, but the thing I wanna say is, even if you're on a two-month green streak and every single day is green, you're still on a level of adrenaline, right? So it's stressful, right? Like there's a level of stress that's always gonna be associated with risking money on the line, but the thing that I wanna put out there for new traders or people who are looking to get consistent is keep it as simple as you can. This is something I talk about a lot, right? So the whole general kind of process at MIC is not doing the things that don't work and maximizing and capitalizing on the things that do. So when something like CLRO today, guys, just for our literally guys that don't even know anything about price action, when it comes to VWOP, one of the first things you're gonna know about VWOP is it's a sentiment. It's a sentiment indicator. It's the only indicator we use because of how powerful it is and institutional money can be around it and big money and it's the average price that people are willing to buy it or hold their position. So the thing about VWOP right here, guys, is you have to understand is when something by the open, right? So let's take a look at this. When something by the open is trading, it's far from its highs. Like that's like one of the first things that you wanna pay attention to, right? So like, where's this arrow? Dude, that's a high. Like that's a top, right? I'm gonna make this very clear for you guys. Where is it opening? How far away from all the rest is that, right? So what you notice is, is because these are bag holders, because these are people underwater, these are longs. So I'm gonna make it like even as literally as clear as possible for you guys as I can. By the open, everybody from here to here on the long side that bought today is underwater. What does that mean? They're down on their position.  All of these guys, this, look at this FOMO right here. These wicks are just pure panic. These are, wow, what's up, man? Okay, we got the man. Let me bring, let me bring on that, guys. One sec. All right. Now I think you're already, I can't see you. One sec. You under modern rock? Oh, he's gotta probably click the link. Let's see, I'll go back up. One sec, guys, let's get down on one sec. Me, someone have the link at the ready real quick? I think it's up here somewhere, but who got the link? Send it over if you guys got it. I think I may even have it. Yep, there we go. Cool. All right, let me get them on. There we go, there's modern rock. A lot of talk, one second. Hey, do you hear me? What's up, dude? Yeah, of course.  I figured you were.  Oh my God, dude, I lost track of time. Dude, how'd you do? What do you want me to main chat? You'll see what I did.  Let's see what you did, brother. Let's see what you did. No, I forgot to see what you did. Well, for the past two days, I spotted this algo that we just kind of killed it on the channel trading all day long. What were you hitting, Val? You were just hitting VTSI. Well, Wafoo, I keep calling it Wagyu. Baby Wagyu every time. Oh, that's right. This was the one Alex actually had a lot of trouble on last Friday. W-A-F-U, W-A-F-U. Yep, yep, here we are, and here's today. So here's today. Look at my chart. Let me post it again, dude. Here, I'll go to the webinars. Yeah, post that stuff. Let's talk about it. So let's, here, I'll post it right now. Can you guys see this? Cool. Cool, man.  You didn't give it a break, dude.  So, Val, what'd you find out with the algo, man? Is that something you want to share? Yep. So, Joe Kelly talked about this yesterday in the webinar, which you guys should have all attended, even I attended it. He talked about pattern recognition. So all trading is, guys, is pattern recognition. All these setups, all these things is pattern recognition. The earlier you can spot the pattern, the more insecure you are. So the moment I spot this algo, I mean, I'm just calling it an algo. It could be anything, guys. I mean, don't look for these phantom Chinese algo things that people talk about. It may or may not exist, but the point is there is a pattern to every single stock, guys. Some stocks is more obvious than others. So the pattern would be wait for the top to set, wait for the broken, that's a pattern, right? For your pattern is a death candle, right? That's one of my favorites, absolutely. Correct. So whatever it may be, the moment you spot a pattern, take advantage of it. So I talked about this before. There's many ways to trade to make money. There's many different strategies to make money. My advice is the first thing you do when you start out trading is to pick one strategy and become very good at it, become very consistent at it. That becomes your bread and butter, right? If you are a short seller, low hanging fruit is the best, in my opinion, the best strategy. If you are a long buyer trader, the first bounce, finding stocks that shorts are upside down, stuck using VWOP, you can tell who's stuck or not, and then you only long those type of stocks, right? That give you the advantage. So once you learn your bread and butter strategy, you can now branch out and learn new things. My advice is to learn new things, guys.  So you utilize your time wisely, but first of all, becoming very proficient at one strategy, because that becomes your bread and butter, and then you can now start to pay for trade and learn new strategies. So one of the strategies that I've been teaching the members is channel trading. So in the morning, we talk about all the time, hitting the lines, you know, broken stocks and all that, but during the midday, volume slows down. The algos are more apparent. So algos doesn't, if there's like millions of volumes of shares, it's very hard to manipulate that stock, right? Because it's natural volume. I call it organic volume. During the midday, it becomes, hold on, let me please, let me please some of these words. You're crazy, man. You're absolutely crazy. Oh, fun. That was funny, a new algo as we speak. So during the midday, what happens is volume slows down, so it becomes not organic anymore. When volume slows down, I call it, everything's an algo, guys. Everything's electronic, right? So when I talk about algo, I'm just talking about electronic trading, which is basically the system that the stock market runs on, right? So what happens is this, the volume slows down, they now can manipulate, meaning they see your orders already. They're trying to match orders, right? All the algos are doing is just matching orders, right? Matching a buyer and a seller. But if they see that there's an imbalance, more volume, more supply and demand, et cetera, et cetera, right? They can start to manipulate that stock up or down, depending on your order. So they can work, they're basically working against you. So there's different strategies that you do. So one strategy that we're talking about is channel trading. Channel trading is basically, we see it trapped going up and down within a channel. So what do you do when that happens? For me, I've been doing this a long time, so I'm starting to take advantage of that channel. It's bouncing off the walls, right? From the ceiling to the floor, back and forth, back and forth. So what I do is all I do is I figure out what the floor and the ceiling is. It's all lines.  Avoid the middle lines. That becomes noise. And so these algos are running these things extreme.  And then it stuffs it, it goes down. So all trading is basically pattern recognition, guys. And what happens is this breakout trading used to work back in the day, it doesn't work anymore. It could work again tomorrow, who knows? But the point is, you basically have to adapt your game to whatever the situation is. So if everybody's going long on a particular NFT stock or a crypto stock, that is the pattern.  So right now I see a pattern where they are jamming stocks all the way up to the outer line and then stuffing it all the way back down to the outer line on the other side, on the bottom side. And so that's what I've been teaching these guys. So VTSI was the yesterday stock. Today's stock that they're doing is WAFU. And if you take a look, I called it right there. I said $16, this is the line. This is exactly as VTSI the other day. So I mean, you don't have to talk about all this VTSI but the point being is this. You start to learn that how this works, right? And all works from line to line, guys. It's just which line do you use, you know? For a low hanging fruit, it's very difficult for a low hanging fruit to work its way back to the outer line of yesterday. So I tend to be more aggressive on the low hanging fruit because it's a dead stock, right? I just wanted to bounce enough so that I get some meat on the bone. So during the zombie hour, volume dies down and these stocks are still over VWAP. That means that they are, shorts are still stuck. So as long as shorts are still stuck, you have to be careful. And these are usually low floaters. They're low float, that's how they can manipulate. Someone owns a chunk of this, that's called locking up the float. Someone locked up the float, right? And so that's what we've been doing over in a main chat the past two days, educating on a new strategy that right now has been working which is the channel training. And so you take a look at my trade. It looks all over the place but as long as the red arrows are way above the creep I'm making money, right? Exactly. That's what we're doing. And then eventually it'll break down and exactly what I said and do same thing as VTSI it tanked back down at 230. So right now we're at 230. Well, about what you said earlier is like the thing that I love and I was talking about this in the beginning of this webinar when I was kind of just ranting in the beginning before we actually started is like this is the key to trading guys. Like you have to find one setup that works before you branch out to everything. So you know, new guys that come in, man the key to the key to every kind of master you're getting good at anything is specifically choosing one and finding your comfort level in it and being like, wow, you know what? I tried all these out on a simulator for two weeks and guess what? I really line up with low hanging fruit. It just makes sense. My comfort levels aligned maybe my trading account size aligns maybe the option side whatever the party that you like and you resonate with then you just sharpen your tool and you get so good at then you can branch out to the first resistance then you can branch out to the deadline and that's what Bao is doing. So every single day obviously he's incorporated all of these into his play style or the repertoire of trading but the key is he's focusing on what he's good at and Bao is really good at seeing these kind of patterns and these channel trades while that might not be my greatest strength or that might not be Alex's because we incorporate the first hour and then we cut off by 1030 but the point is like you've got to go with what you're good at and then maximize it and then just sharpen the tool and that's what Bao is showing right here. Like he's so good about finding these outer lines and levels that coincides with a previous resistance or a channel and then he maximizes on and if you notice like Bao if a brand new trader tried to copy you he would probably stop out over and over again because he doesn't know that above VWAP there's a certain size you use if you're doing front side shorts it requires front side covers he doesn't realize that there's a real give and take to price action and based on what side of trend you're on, right? Correct. And it all originates from knowing how to draw the proper lines guys. Everything originates around support and the resistance and pivot lines. Yeah, so really quick guys let me actually show you this because I get a lot of PMs on this weekly. Again, when it comes to lines you know how do I draw my lines? We have setting up lines within the video library list we have every kind of category you can imagine guys like anything you need to find is right here. You literally write line setup like look at this search and then here's how to do it. Here's my thing this is what I was talking about this is me and Joe put this together it's like a 40 minute video on how to even use TD Ameritrade which I use for charting and then going further into it it's how to set you know pivot points how to do pivot points on DOS like there's no excuse man I'm telling you guys any resource that you guys need is here. Guys that's a huge thing before Joe Kelly and figured this all out about pivot lines on DOS and TOS no one used pivot lines. I was paying $500, $600 every month for right now an obsolete trading charting program that only had the pivots, right? Because no one had it no one figured out how to put it on there.   Yeah exactly. No one, the indicator is basically a self fulfilling prophecy.


I'm really happy because we bounced back from a tough loss last night against Juniata and the guys just let that go. They learned from it and they really turned it on against Teal today, who's a really scrappy team. They've taken teams to five like Marymount, who's one of the best teams in the country and we just didn't let them side out and we blocked really well and served really well. Well that was huge. I guarantee it's a winning season and it's just always good to win, you know, kind of just the whole locker room, the whole, you know, the guys that are not playing that much, you know, are happy. Also they get a chance to play and get in there. So that's really important going into this next week. We have four matches so we wanted to get back in the winning mode. Well I think we're just taking it one, one match at a time, one practice at a time. I mean basically we have three practices left this year, Monday, Wednesday and Friday. So we have matches Tuesday, Thursday and Saturday. A double header that I hope everybody comes to because that'll be our senior night and we have EMU, the Mennonites coming to town. They're really tough.


Alright, not usually a basketball guy, but so many of you requested this. We're gonna give it a shot. It's brought to you by DraftKings. We got Yannis and Wagner with the headbutt. But earlier on, Yannis just getting thrown around by the Nets, getting thrown around by everyone, not happy about it. Watch out!  Oh, oh, sorry, uh, Rep.    Yannis on the ground, then he's shooting daggers at him as he runs away, says, yeah, that wasn't my foot in your armpit. What of it? Then, alright, they're coming down the court, everyone's watching on their TV screens, and then he's like, bam, that's what of it? I'mma drop ya. Boom, boom. Greek on German crime. Boom, then comes, he whispers in here, says, that dog's supposed to be a kid. We're putting my foot in your armpit. He's like, whoa, okay, that was easy. They sent me in to piss this guy off, and that worked out pretty well. And then Yannis is like, wait, wait, wait. You called that on me? What? No, no, no, no, no. Then they come up to each other, and I'm not sure what's going on here. We get the headbutt, the headbump, whatever you wanna call it, everyone prairie dogs in the back, they're staring at him, and at this point, I don't get it. Like, what's Wagner doing? He's walking into him, they're walking into each other. Yannis just gets ahead of it, says, hey, if we're gonna bump chess, if you're gonna bump into me, might as well bump into a hard part of my body, and puts his head out a little bit, like a sprinter trying to win a race. Like, I'm just gonna get to this spot first. What's Wagner's plan? They're bumping, he just goes for a little headbump, that's all, nothing of it.  Get over it, NBA has a history of weird headbutts. It's kinda like, let me put my forehead on your forehead and see if you like it, because that was a one-game suspension there. This was a one-game suspension here, I believe, and it's kinda like, hey, how's my forehead feel?   They cool Yannis down, he goes to the sidelines, I think he got ejected from this game, and then he got suspended for one game later on.  As well as brought to you by DraftKings, go to DraftKings, download the app, use promo code Johnboy, and again, not a basketball guy, don't know much, but I'm guessing just put Yannis on your squad and then win a bunch of money via DraftKings.


The study found that allium jesdeanum, an endemic species native to Iran's Sagras Mountains, has moderate to good antibacterial activity against four bacteria, especially be serious, and may be considered a natural source of antioxidants. This article was authored by Abdullah Gassami Purbaluti.


Islets encapsulated in immunoprotective microcapsules are being proposed as an alternative for insulin therapy for treatment of type 1 diabetes. Alginates for medical application should have an extreme high degree of purity and lack pathogen associated molecular patterns, PAMPs, to avoid activation of the recipient's immune system. This article was authored by Genaro Alberto Paredes Juarez, Milica Especijevic, Marieke Faus and others.


Hello, my name is Philip Tarrant. I'm the research data management officer for Arizona State University. My role at the university is to lead in partnership with the ASU library and other university units, our initiatives to expand and accelerate our research data management infrastructure. Be effective in this role. I also collaborate with colleagues at other institutions to explore broader research data management efforts, share ideas, and learn from each other. Our research is conducted in many ways. But if we think of the conceptual research cycle, there are several phases. This graphic is one way of viewing the progress of a research study from its early beginnings through to a successful conclusion. In the early ideation phase, it may be just an idea, possibly based on previous research. During this phase, that idea is developed and potential grant opportunities, collaborators and funding sources are identified. That formulated idea is then developed into a compelling proposal that includes collaborators, plans, and budgets, eventually being submitted for funding. If the proposal is awarded, the investigator is able to pull the project team together and conduct their research. And once the study is complete, then all the necessary activities take place to complete the work. In today's world, that includes making data available, as well as publishing results in journals and presenting at conferences. All our research activities produce some kind of data. And we are starting to see digital data creation in nontraditional areas, as well as those more familiar research fields. For example, we have dance professors using CGI techniques to map the movements of dancers during performances and then analyze those data using computers. Vast amounts of research data that we produce today need to be managed from creation through to publication. And because of the diverse nature of research, we have communities of researchers needing technology and data management support that do not necessarily have mature data management practices in the field. Our goal is to ensure for our respective institutions that our research data will be consistently collected, adequately documented and quality controlled, analyzed using techniques appropriate for the research question and field of study, and ultimately published in a way that makes them fair. That is findable, accessible, interoperable and reusable. Consequently, it makes sense to recognize that research data management is a fundamental part of the research cycle and support that activity at the institutional level. In order for us to provide effective support, we need to understand what our researchers need in the way of technology and data management support and to engage with them early in the proposal development phase, so they're educated regarding the services we provide and to be able to budget for those services if needed. Arizona State and Penn State have been developing collaborations in a number of areas, because we recognize the value of sharing ideas and leveraging our efforts so that we don't have to do the heavy lift alone. This working group was set up to explore how we might collect the information you need to provide timely and cost effective data management and technology support to our respective research communities. So my name is Matthew Harp. I'm the Research Data Management Librarian and Director of Research Data Services for the ASU Library at Arizona State University. I'm going to provide some use cases our library team experienced this past year that the data needs form could help improve. They include last minute proposal support requests, research data not ready for publication at the time of submission, and the need for boilerplate and cost information at a large institution. Within a week or two from the due date of a grant proposal, we typically will receive a referral for help on a research data management plan, and it is generally clear from the content that the team had not apparently looked over the requirements of the proposal, such as a one to two page limit, nor are they answering the questions the reviewers will actually be looking for. They may be repeating information or provide a narrative out of scope of the proposal such as partnership information and background that is well better left the supplementary information, or sections of their proposal. In many cases teams are not aware of the level of support available to them. They may be unaware of the Office of Research Data Management, the library research support team, or the DMP tool, and thus they are missing out on guidance and general advice linked to the funder's requirements after providing initial feedback on a recent request. A proposal grew in pages, rather than trained to the two page limit. The situation demonstrates a lack of awareness of support and an unfamiliarity with what information the proposal reviewers will actually want. So in addition to socializing our work with our researchers we hope this form builds better awareness of institutional support options and corresponding needs so that we can adapt our work. So integrating into the proposal development process should be an adaptive and flexible and address the funding agencies requests, providing advanced context starts conversations that will help us align resources to the project. So researchers are not having to completely rewrite their data management plan days before it is due. So sometimes data sets are just simply not ready for publication repository services regularly receives data publishing requests when the research data is just in kind of an unstable form. The research project has been completed and now the team needs to share their data per the funder mandate, yet our team has not been informed, despite the repository and our services being actually written into the proposal. So researchers didn't budget for storage. They may not have the appropriate documentation or organize our data in a way that makes sense to the other researchers methodology documentation assisting others and understanding how the data was collected or analyzed maybe missing, or that information might be embedded in a journal article, but they have not provided the basic information directing users to where it lives. This is an unusual and indeed a part of our job is to help them get where they need to be, but this also comes as an unexpected frustration to the researchers at a time that well they're just not ready ready for it. The data needs form brings direct awareness and an opportunity to request research data management consultation services and training for research teams and lab technicians, so that they're preparing to share their data before collection and analysis of data even begins. We also receive requests for a blurb on the data repository, typically at the end of the proposal drafting process real world requests as for boilerplate information or a narrative on the data storage and our repository capabilities. They may even mention that they would like to know how the repository aligns with fair principles and that if a cost is involved to just let them know. We can add it to the proposal, however, even basic cost can vary depending on the nature of the project, and any statement provided should be flexible enough to account for changes to infrastructure and research practices. So the situation is not just about sending over a paragraph to them, but developing a better understanding of their needs. It's difficult for us to provide cost information when we don't have advanced notice of what is coming our way, or we may need to reach out to other support units because we're so large. We need a shared knowledge base to coordinate activities and plan for services that may be months ahead. In the data needs form into the proposal process could allow us to proactively ask questions based on user input and develop a menu of services that could then be added to a proposal for and the budget lines beyond just the storage and backup costs. Hi, I'm Rihanna Wham. I'm a research data librarian for STEM, as well as data learning center manager at the university libraries at Penn State University. The goal in creating the data needs assessment tool is to reduce research or burden by facilitating a just in time single point of entry for researchers to a coordinated research data support service network. In designing this tool, we wanted to create a flexible framework that is platform agnostic and could be adopted and adapted by other organizations based on their needs and the tools at their disposal for implementation. To create such a framework, we first needed to determine what data services to include, acknowledging that the framework will directly impact the form that the tool takes. A major consideration in the creation of this framework was how to make the tool comprehensive, but not too complicated, tedious, or additionally burdensome for researchers. Thus, we developed the framework to be not too far into the weeds, but rather gather enough information to make connections with the vast array of research support services at each of our institutions as navigating these research support services alone can be challenging. Additionally, in designing the framework, we wanted to focus on building a tool that allows for increased crosstalk and collaboration between research data support service providers, as well as transparency of the process for researchers. Throughout the process of developing this framework, we went back and forth on how specific to make search and sections and decided to only add additional information requests where we see the potential for integration with other tools such as the DMP tool or automation between current systems such as our proposal systems. Ultimately, we determined that the framework should touch on data needs throughout the research lifecycle, and so this would include things such as data management, data acquisitions, ethics and legal compliance, storage and backup, and data sharing support needs. We then decided to create a structure that determines sections for researcher review and completion based on their selected data needs. So first, a researcher will see the data needs components, and these include things such as creating or collecting original research data, acquiring research data, data management needs, where the data is being acquired from, storage requirements, as well as information for data transfer and public access to research data. Once these sections are made based on the researcher's needs, a researcher will be presented with some additional questions that then enable us to provide better support. Hi, I'm Doug Dodson. I'm a research computing and data analyst with the Office of the Associate CIO for Research at Penn State University. As we've said, we're working toward a framework that is platform agnostic and flexible. However, we also wanted something more than slides, something that would show that solutions using this framework could be developed rapidly using tools that most organizations like us already have. We created a Word document to capture both the questions we wanted to ask, as well as the form those questions would take on any associated tool. Once we refined our list of questions, we created a flow chart to visualize the branching needed to collect information. This flow chart succinctly and subtly exposes the two primary information related components of our framework, something to present the questions and something to store the associated responses. At Penn State, we decided to create a Power Apps app for our prototype, and at Arizona State, the decision was made to use Microsoft Forms. Microsoft Forms is an example of a tool that many institutions like us already have at our disposal, that is fairly easy to learn, and that has enough capabilities to develop a functional and useful prototype. Power Apps requires a higher level of licensing, and takes longer to learn, but has a robust set of capabilities that could eventually be leveraged to develop a much more capable tool. Microsoft Forms and Power Apps gave us the tools we needed to show different ways for presenting our questions. When it came to storing the associated responses, Penn State decided to use a SharePoint list while Arizona State uses storage features provided by Forms with the option to export the responses to Microsoft Excel. We've also shown that we can leverage integrations with other tools, such as using Power Automate to send an email notification when information changes in a SharePoint list. Very capable tools have been developed without a requirement for extensive technology or programming skills on the part of the developers. Once our respective prototypes were created, we began to schedule demonstrations for potential stakeholders and users of a research data needs smart form app, and we collected their feedback as part of our process to continually improve our nascent framework. It's important to emphasize that we feel strongly that our framework will ultimately support information capture tools from paper forms all the way to high end web applications connected to a back end data store. Once we thought our prototypes were ready, we reached out to a broad spectrum of groups and individuals to schedule demonstrations and discussions. Research administrators, IT staff, researchers, librarians and leaders of sponsored programs offices and research institutes. Basically, anyone who is heavily involved in interactions with research data. These demonstrations have gone well. Feedback includes points and questions such as focus on return on investment, especially what researchers will get in return for the time invested in providing details on their data needs. Communication across the various service providers who could be impacted is critical. Can we connect this with other tools and services such as DMP tool and IRB processes to help streamline them? How do we ensure proper groups are notified and that actions are being taken on the information provided? So what have we learned from this exercise so far? One, we have discovered that the challenge is larger than just understanding data management needs. There are other types of support that investigators require during the life of their grant. We should think about how we understand those requirements and address those too. We originally thought we might integrate this effort into our proposal submission system, but we have realized that actually we need to engage earlier as part of the proposal intake or development process. We now understand how engaging early to understand technology needs can trigger other meaningful discussions about research data management. These discussions have the potential to improve the final outcome and the quality of the data products that investigators produce. We also recognize that researchers will need to see the value add in this process if they're going to take the time to provide the information we ask for. These are all good lessons and as we continue to develop a better understanding of how to support our university's research efforts, we're also developing the tools and processes that they need to be successful.