Okay, hello everyone, welcome to the Jenkins weekly infrastructure team meeting. We are the 22 of August. There on the table we get Mark White, my self-demand reporter, Stephen Merland, Kevin Martins. Let's get started with the announcement. We were able to successfully release the weekly core 2.419 last week, no problem. And today, we didn't release successfully the version 2.420. So we had an issue failure during test phase. During test phase? Yes, I haven't looked on this. Ideally we should relaunch it. I don't know, maybe that could be... I don't know if it's a consequence of using GDK17 on the agent. I doubt it. Maybe on the memory management. I haven't looked at the data metrics of the pods. There are CPU and memory metrics. Maybe the memory usage is different. Got to check. Okay. If it is an issue, GDK17, resource limits. Or maybe it's a timeout, as Alex said. Because we don't have that error on CI Jenkins in your main build. So there is something different. Let's restart the build and see. Any question? Do you have other announcements? Go free now, okay. Upcoming calendar. Next week, we'll be next week, 2.421. We'll be the 29th of August, is that correct? We have a new LTS line that should be released tomorrow. Oh no, yeah, and security release. We did have security release last week. Everything went fine, as far as I can tell. We don't have new security release publicly announced here. So nothing here for us. I have another announcement. We had to rebuild the container image of Jenkins for all Linux version and for the free past releases, so 3.1.1 and the last what's here, 4.1.3 and the last week. So it looks like we had a bug and a whole tag of the container image was built, which has the side effect of overriding some of the usual tags, such as LTS, Alpine, LTS Alpine, etc. And some versions were rebuilt and redeployed, which is really annoying. So since we provide different operating system and architecture than we used to do with that old version, we decided to rebuild the whole set for each version to avoid any risk of, let's say, if you have Alma Linux, that's okay, but if you have Debian, you have an old version. So the consequences is that the checksum of this image is changed. So we started, thanks for that, Mark and Kevin, we started a blog post to an unstat to end users, but we need to update slightly the blog post because it's not only Alpine. Well, and I think we've got users asking, could we also republish older weeklies and to repair it? So we had one requesting, hey, it's the current, so 2.419 is the current, is the most recent weekly, is it feasible for us to rebuild, to republish the, all the way several weeks back, or is that just infeasible? Technically, yes, but we have to do it on the right order, and that means republishing today's weekly, because each builds or republish the latest tag saying, oh, that's the currently built, which is the latest. Oh, right, okay, right, so. So the answer is no for the weekly. They can use either 2.419 or the upcoming 2.420. And is there any way for us to discard a republished version from the Docker hub saying, hey, we're not really, I assume no, they treat them as once you've published it, it's visible forever. Eventually, could we modify the pipeline to not push on latest, if certain. Clearly no, the only outcome of trying this will result on way more mayhem. Trust me, we simplified it as, but that would have been a good idea, if that publication was a usual image, but the controller image is not like the agent, it's way more complicated, because it has five dimensions. So that's why we publish automatically, atomically, a given release. So I'm sorry for the end users, but I will be interested on the use and the reason why they cannot use the latest weekly version. Since it's updated once a week, there will be at least two weekly late. I mean, given we have a new LTS tomorrow, and given the number of the upcoming LTS, I will suggest them wait for Thursday and either switch to the new LTS or switch to the latest weekly. I think that that is the correct answer, is that we, that may make them uncomfortable, but even if it makes them uncomfortable, we simply don't have a reasonable facility in the time we have to go back and publish, republish those outdated versions. Yep, so that means a given tag is atomic, either our OSM platform and must be rebuilt in the proper order to ensure latest. Got it. Or at least, or at least ensure latest. Weekly is rebuilt. Is always rebuilt last. Exactly. Okay. That's problem and we still need to find a solution to protect ourselves from this scenario. About your question, can we discard, we can delete the tags on the Dockerfab purely and simply. But that means this version will be gone. Yeah, and that I think is also a mistake, right? That will create a different class of mayhem, right? So yes, we could, but in either case, the problem we have is best solved by users doing what we recommend anyway, which is upgrade to the latest weekly. If you're on weekly, you should be upgrading to weekly. Exactly. If you're using. And now we're any of, yeah. Yes, yes, good. Maybe we could publish them as recently and not being able to override them for that kind of problem. That's not, the Docker registry does not allow that. It's not like eventually on artifactory, but even on artifactory, I'm not sure it's possible. It's only a mayhem artifact or not just artifact, but the Docker registry does not allow locking a given tag. And the thing is that here we are in our, we have a lot of restriction, but that's the location where putting any restriction is only based on is Jenkins behaving properly. It's really a Jenkins bug or something really weird. I will add messages because team had proposal to protect ourselves even more than today, because right now we are not publishing master branch. So that's a good thing. Now the problem is that the whole tags, we set up the job to not build tags although then three days and still they were built, which doesn't, so I might be missing something and, but that's really really weird. And the suggestion of team, I wasn't able to find the multi-branch job traits he was mentioning. There is a trait that say filter branch or pull request by name. There is a field for filtering tags. I wasn't able to find that option neither of the field on trusted CI. So that might be a plugin. I'm reasonably confident it is a plugin because branch, so filtering traits are intentionally many small plugins. So the last thing will be protecting ourselves on the pipeline level. We have the environment variable with the tag, so we have to fail the pipeline. No, that one won't work because the whole tag doesn't have the pipeline change. So that's nightmare. I would advise on removing the tags, that's the same kind of thing as removing Docker tags, removing tags from GitHub, especially when they are associated with a GitHub release. Right. I think let's not, let's admit that we've got a problem and try to not make it any worse. I'm a bit sad by this. That's really not trustable. Yeah, we'll see what we can do and I will report next week on that topic. Is that okay for everyone? Yes. So next major event, Jenkins election, start in September. So reminder, the nomination of candidates is a period of a few weeks where people, where you have to nominate candidate for the different jobs. So it's not you that goes, say, I want to be, oh. Self-nomination is allowed. Exactly. But self-nomination is allowed. But the crucial thing for me is the infrastructure officer will be up for consideration as part of this election. We elect new officers every year. Likewise, the documentation officer. So Kevin and Damien, you are welcome to continue and nominate yourself for the rest of us. We'll happily nominate you. But if you say, I'm not sure I want to do that, then you need to go looking for somebody who'll take your place as a candidate. Don't tell my boss, but I will reconsider and for nominating myself again. Well, your boss will probably nominate you one way or the other, but only after checking with you. I will not check with him. I will just push him in. Under the best. Don't forget to nominate candidates for every post, including yourself if you feel like it. That's the sign of an healthy community. That's not easy for me as current officer, trying to get to stay officer, to say that. But yes, it's important to have people presenting with the project ideas and changes if needed. And in any case, don't forget during the second period between 18 of September until November to register yourself as voter. The condition, the threshold is you have, I suppose it's the same as last year, Mark. Yes, it is. You need to be a Jenkins contributor and everyone who is on this call is a Jenkins contributor. Everyone. So please don't forget to register and don't forget to vote again. That's really the healthiness of the community. 11 of December, we will have results. And if questions, things too hard, things I forgot, things unclear on the topic of the Jenkins elections. No? Okay. So let's continue. I take it back. We've got one more major event, though. Yes. Java 21 support. Our Java 21 arrives in our Jenkins containers today. And tomorrow. And tomorrow, right? Now, it's still an early access version, saying support is too strong a term, right? Java 21 early access. How about, will be in Jenkins? Yeah, as early access. Good. Perfect. And it's so it's expected to be available today and tomorrow and encourage people to test drive it. So that's great news. As a reminder, for the infrastructure to start testing controller and production, I would prefer to wait for the initial release because it doesn't have a CVE process in place right now. So running publicly this, that might be a bit risky. Right. We absolutely do not. We want to wait till Java is released. That's for sure. We'll wait for official DDK 21 in October. September. September. Yes. Before trying on controllers. But of course, we have DDK 21 already available because we were able to build these images. Yes. Nice one. Okay. For everyone. Okay. So let's start with the walk. We were able to finish during the last milestone. So this were two weeks milestone. A lot of tiny tasks, but not a lot of person available at the same time. So we have overall the workload of one week. Let's start with unable to release plugin 401. That one has been open today. It's a contributor that's tried too early to release the plugin using the CD automated process while their token wasn't created yet by the repository permission updater. So we explained and told them to wait three hours. No feedbacks, but they were everything looked good. They had a token. It was valid. I tested the token myself. It was just a time. They tried 10 minutes too early. It's not the first help desk issue from this user. I've also added an issue in the repository permission updater to suggest adding an automatic command in merge request with explanation and timing. Good idea. I have a link. I'm ready to add a message in RPA to let the user know of the three hour time window. That's really a good idea that will help because it's not the first time. It's not really clear. There is a lot of explanation in this repository. A lot of things to follow. Absolutely. I think you're absolutely right. It's clear for us because we use it and maintain it. But for newcomers that will help them to avoid setting false expectations. Thanks, Hervé. Something else on that topic? Okay. So next topic, switch to GDK 17 for Jenkins controller and agent processes. It's done. We are using GDK 17 for all the JIVM processes involved by Jenkins. The release today was executed on an agent run with GDK 17 but still using GDK 11 for building Jenkins. It's a DevTools versus an ExecutionTools. Haven't seen any error yet. Yeah. Nothing else to say except that we have a bunch of different agent definition everywhere. So last time we were able to divide by half was able to decrease that spreading of 20% this year. I hope that for GDK 21 we will be able to have a centralized location at least one for Linux and one for Windows. So yeah, it's a personal minor failure. I was hoping that we were able to finish the all-in-one image before GDK 17. We weren't for a lot of good reasons. So it's just I'm a bit sad I was challenging but yeah, everything is working well. I hope we will see operational benefits on the memory usage but that happened to be measured. So let's wait one week and see the result. Any question? Okay. A repository of a plugin that was archived because the product behind was closed two years ago. Maven incremental commands so that was not related to infrastructure at all. However the instruction it's the same thing as RPU that's a note for Mark and for Kevin. The MVN incremental command instruction looks good on the paper but there is still a bug. And yeah, not only fixing the bug will help but also the plugin documentation could be improved by saying if you have an error you have to look on the detailed instruction here. So that's just the link and an explanation because in that case the user carefully followed the instruction from Junkins.io and still had an issue because their POMX ML was missing something because they played with it. That wasn't an easy one but yeah, with opportunity to jump on how R is Maven working with its plugins. Might be a minor update. Any question? GDK 21 support for developer to preview and try. So thanks Stefan. Notes as pointed by Tim or the Junkins.io slash Docker. A team was able based on the work done by Bruno and Stefan about locating the proper Temurine 21 binaries was able to find some hidden release which in fact are official release by Temurine, preview release with a fixed name on the release and tag name which will allow automation and tracking of updating the version until the last version is okay. So Stefan, that means as we checked together right now we are using for the infra the nightly builds while the preview Docker image will use the weekly builds. That's the only difference. So we might want to put our hands on this one if we have time but that's not mandatory topic. In any case, I'm not opening an issue if we have time we'll do it until the official release where we will have to do something. Can we use weekly with fixed tag name allowing tracking with update CLI. Any question on GDK 21? So nice job Stefan because you had a lot of places to check for this one. A lot of puppet medica. Not able to log in to Artifactory so the problem with some user that need a manual change of the setup on Artifactory for them in order to use the LDAP password instead of whatever local password they have. Still not fixed. I will come back on that topic still open but that user for that user that was fixed. Right now it's still manual casebikings. CD release fading in valid token and trusted CIG and Kinsayo. That one happened last week as far as I remember. And it's because we the administration token used by the repository permission update job which allow it to connect to a Gfrog API to create Reset token and permission on Artifactory. That's top level admin token was expired. So of course the RPU build was failing with 401 because it wasn't presenting any token. So a new token has been generated once we understood. I've updated the calendar because that wasn't the infratim in charge of that token last time. It was a three year valid token. It was done before any of us was working here. It was done by Daniel and Olivier and they didn't have the calendar. So now it's on the calendar until it's only valid for one year and I've added plenty of notifications. And also as I show to Stefan on trusted CI the token I've set the ID because they have an ID to map it to administration in Artifactory. And the expiration date is also on the Jenkins credential for that token on trusted. So Azure for you folks to understand it if it fell in one year. Any question? Finally, that was a leftover of last Kubernetes upgrades. Now the administrative user used to install and chart an application on our cluster by Infratii. That technical user is now defined as code on the six clusters. That means it's not only a script on my machine each time we recreate a cluster from scratch. Any question or things on this one? Okay. We had three issues closed as usual. No answer back from the user. Now let's jump on the big topic. The first one and top priority for now is Assess Artifactory Band with Reduction Option. Mark, can you give us some heads up on this one? So I won't be alone talking. Yeah, so Artifactory Band with Reduction we've got agreement from JFrog that if we can successfully stop mirroring central the Maven central repository that will be sufficient in terms of their expectations from us to reduce our bandwidth use. And the reason they were willing to do that is because our analysis showed that that is the majority of the misused artifact or misused mirrors. And since it's the majority they said that's fine. It's also a change that we believe we can make without requiring new releases of palms, without requiring new releases of plugins, without requiring changes to 2000 plus GitHub repositories. So we like that they were willing to compromise in that we're very, very grateful for that. We have more work to do to assess we did an initial brownout. We found positive results in ways we'd hoped but some surprising messages that need more investigation will report our latest results to JFrog in a meeting on Thursday or Friday. And so I and Damien both Damien and I both have some preparation to do to be sure we're ready for that meeting with JFrog. Thanks Mark. Was there anything I missed Damien? No, that's still still the same. So we did not have time to spend on that one either. So let's I hope we will have time on Thursday to prepare for Friday. Any question? Think them clear for folks? Okay, no, so then let's continue. A new issue that I've had it's around public cluster. So we had failures on Java doc, Jenkins IU and another website. I don't remember which one. In fact, we whether we use Intel or IRM for these services, they all have the same problem. We don't define an anti affinity, which mean all the replicas of a given service are scaled in some scenarios on the same machine. Sometimes it's a difference. Sometimes it's on the same. It's something that exists since month is that always existed because our end charts are not taking that in account. And what happened is that during a regular update process, I wasn't careful because I took the services were replicated. So I triggered the updates of the operating system for security issues. And that resulted in, yeah, the service was absolutely shut down time for the new machine to start. But it was only one or two minutes, but it was cooked by your security team because they were testing things before the last week during their security advisory. So that issue has been open to track this. That means we will have to update end chart by end chart to add anti affinity, which should have the result of scaling at least the IRM based pods to two machine at the same time. Okay, so Damian, I need to be sure I understood what you just said. So we've got today's configuration maybe running a single pod to serve javadoc.jankens.io or something like that. They are running two or more pods. Oh, they are already running two or more. All these pods could be one machine. Right. Okay, so we're already using two pods. It's just that sometimes the two pods may be on the same physical computer, which is not nearly available enough. We need it on two different computers. And the chance to have the two pods on the same host bigger with IRM because we have a little number of them. So we should only need one, not for the power, but we should have two for that kind of problem. So what this really means is if we're running in minimal case today where we only allocated one ARM64 physical machine in order to run all of our pods, we will now be running two ARM64 machines at least. Because in order to be able to reset one of them, we have to have a second machine. Makes sense. And you can say that we are saving a lot of money right now because we're using only one. Well, we're probably saving money. I'm not sure. A lot is, I'm ready to sign up for a lot yet, but yes. Definition. So, yeah. I'm not sure if we are able to work on this in the upcoming week, but I think we should. Personally, I will advise on Stefan, once you have finished the IRM64 Docker image builds, you move to this one before going back to migration of workloads to the IRM64. Yeah, I agree. Like that, the other one will take advantage of that too. Less prior IRM64 Docker, less priority than IRM64 builds, but should. But more important than Intel IRM workload migration. Okay, any question? So let's continue. The Artifactory HTTP 401 errors. So I had the meeting as reported on the issue, meeting with the support. So during five days, I checked daily and Daniel as well. The new user created an account app and logging for the first time on Artifactory were set up with the option disabled. And I tested the morning before the call, so two hours before the call. And during the call, I'm sure something was done to our instance because suddenly it started, the variable option was the default suddenly, which wasn't the case two hours. So that's a good news. So now the new user have the proper setup, which means now we only have to find a way to treat the other thousands users and ensure they have the proper setup. Didn't have time to spend on this one, given that we only have one user asking for that this week. Or whether we still need to find to write a batch script. Of course, I asked them and they said, oh, you have a nice API, you could use it. Yes. So that means some batch script will be written soon. I will be happy to share the burden or delegate to someone, but only administrator can validate and test that. So yeah, unless you want to set up a full Artifactory instance on your machine and the held up and the connection between both and the test case of users. So yeah, better to test in production. New user now have proper configuration and now needs batch existing user once. Any question? Okay, so I will continue working on this topic this week. I hope I started something on the go this week, so that's a long time thing. Plug-in site build commonly failed on Infra-CI when accessing plugins Jenkins-IO. Last time I checked before you went to holidays, you detected that every three hours, we had a peak of 502 errors when the site was generated from a fast plugin backend. I don't think neither you want high time to dive on that topic. So we did not dive more on the topic except the great error. We are not sure if it's fastly or sending the error or if it's firstly answering an error due to an error on the back ends. So yeah, we got a deep on this topic. We are not at ease with the plug-in site architecture to be quite honest. I'm not sure if we have time right now. Hervé, I believe you made a proposal and maybe it's already done. Can you remind me if you already implemented a retry on the build setup? I think you're muted. Yeah, you're muted. Sorry. I don't think so. You can check that. Proposed retry on the pipeline on short term. Is that okay? To check and if it's not done to add a retry on the build. I know it's always for builds like this one when we generate something that's the same for RPU. I know that we have a lot of developers that say, hey, we could implement retry natively inside the batch jobs and whatever. But on the infrastructure side, we don't really have the expertise to jump on these elements on the language and the domain that we not always master. So at least on short term, adding a retry, that's not the best. But one, two, three retry eventually avoids errors most of the time. So the goal is to decrease the errors, making them a bit more invisible. That's most of the time the problem. But now that one is not is visible. So let's add retry and then diagnose. Any question? Okay. Next major topic is the update symptom migration out of a native address. Herve, your turn. So if you can open the issue, I've put last status dates on it. Last, before my EPTO, I've noticed that the mirror beads equivalent service we've put in place for update touching kins.io on public ATS cluster was filling with a specific error log. Looking more in detail in the mirror beads source code, I've noticed that the mirror we're adding needs to be able to respond to FTP or ERSYNC requests to be added as valid mirror to mirror beads. So we first looked at, I've looked at Munt S3 like packets as volume. But most solutions are using S3 FS to Munt S3 as huge system, which is a no go for us as the template running with privileged context education. So I've looked at the decommissioned the mirror we had previously, as your dot mirror touching kins.io, which is using the same storage account, which was using the same storage account as mirror beads. And I did the ERSYNC server running as the one. I've transplanted this capacity in mirror beads, so we don't have to use and maintain two charts, which are almost identical. And when this service will be deployed, I tend to use it to try to add the ERSYNC 2 packets mirror with its own URL, FTP URL, and this ERSYNC demand URL running on another service. And serving the Azure storage account content we are already using as local reference repository for murals. And doing so, we will have to ensure that the content on the Azure storage account and the ER2 packets are updated in sync. And the next step will be to transplant many HDA access redirection to get similar behavior and the current updates of syncs. So you mentioned ERSYNC, and I'm not sure I've understood. So ERSYNC today is used by the other mirror repositories, like OSU, OSL, and Yamagata, and others. ERSYNC or FTP. Oh, some of them are synchronizing with FTP. Yes. I think the list of the murals is in the L chart with me. And with the ERSYNC or FTP address, we are setting them. Well, so I'm sorry, I was thinking from the provider side, from the side that we provide. So I have an update site inside my private network, and it reads from an ERSYNC server that is, I think, that is one of the mirrors of GET. But the central server is providing both R-SYNC and FTP. Is that what you're saying, Alvay? I'm trying to understand, or is it? For a mirror to be able to be added to mirror bits, list of mirror, the mirror needs to be able to respond to a SYNC or FTP request. So it can be scanned for its file list. Okay, so the mirror bit knows which repo is up to date for the specific file. Okay, so before mirror bits is willing to offer a file from a mirror, it has checked to be sure that the file is on that mirror and has the correct checks on. Got it. Yes, not exactly the file, but the first steps when you are adding a mirror is to scan this mirror, either FTP or ERSYNC, and if none of them are available, it fails. And there is also the ERSYNC you mentioned, Mark, so Alvay also had the same confusion initially. The mirrors that we provide can download the data we provide on forgetgenkin.co, so the HPI files, they can download using ERSYNC, but they also need to provide the ERSYNC server, so they are both client and server, because we need to be able to scan them, or FTP is the alternative, of course. So that's why we have today that tricky topic. If we use the S3 bucket in Cloudflare or an Amazon or somewhere else, we have a cheap HTTP server that we can replicate and the storage costs nothing, but mirror orbit is not able to scan it, as Alvay explained. So in the case of the update center, the proposal I made to Alvay is to say, let's provide the SYNC server on the reference, because we control the updates. It's atomic. That means we say, here is the update center, we copy it on the reference, and then we copy it on Cloudflare, on two locations. And once both copies have been successful, then we trigger a scan. So we tell mirror orbit, please scan that ERSYNC or FTP somewhere. So if mirror orbit points to the ERSYNC server on the reference data, it's not a problem. It will think the file is there, but we don't have the risk, or the risk is really low of discrepancy between Cloudflare and the reference. That is not possible with getjenkins.io, of course, because we don't control when a given mirror has run their ERSYNC to get the data. So we need to carefully scan each of the mirrors at any moment. It's only because we control the update of the mirrors in the case of update center. That's mandatory for us in any case for security reasons, of course. So that's okay to get started with this one. We have other alternatives. We can stop using saying, we can say normal buckets. We will use a machine or whatever service somewhere on the world and use these mirrors for at least moving a current update center to Azure on first time. Cloudflare is only there because it's cheap. That would have been a news console, and they have a foot on the China network. But if we don't have an easy solution, or if it doesn't work as I said, then let's use a virtual machine with storage, web server and ERSYNC in Digital Ocean and Azure on different locations. Also, a proposal I made to her is that given that mirror bits is not quite often updated, the code is quite simple. That will be a nice feature request to say, hey, why not adding S3 as a scanning protocol? Which means we could directly say, hey, we have S3 compliant buckets, and mirror bit could directly take care of the scanning, avoiding having to provide a nursing for these servers. All the S3 providers, AWS, Digital Ocean, Scaleway, OVH, Cloudflare, they all provide both S3 and HTTP protocol. So that will be a really useful feature for mirror bits. But that will need to put our hands together. And the go long code of the application, but still could be really useful for infrastructure. Does that make sense? Because that's not an easy topic at all. And it's critical one. So good job on that one, Ravey. Support S3 for scanning mirrors. Is there something else to add? OK, so Ravey, I believe you only walk also tomorrow, and then you're gone for holidays. So that means tomorrow you and I will have to do some kind of handover if it's OK for you. So I can continue working on that topic since it's top level priority. Is that OK for you? Do you really want to keep that topic? And we can say, let's wait when you're back and see what we can do instead. How do you feel? We'll see tomorrow how we progress. But yeah, I think it's a good idea. OK, I don't mind either. It's better if we can handover and finish earlier. But yeah, maybe you want to take the whole topic and you might be more efficient when you will be back from holidays. So I don't mind. OK, unless there is a question of the next topic, nothing to say. It's a GitHub organization permission managed by the Jenkins and admin where they are going to use our training for centralization, a word about so we have two issues that are linked each other. It's migrating third CI to a new network and restricts to VPN users who need the access to both trusted and the new third CI. In order to work on this topic, I've started to work on Terraform Coderefactor for numerous reasons of maintenance. Otherwise, creating all the proper resources, network security groups, and cloud resources for those controller will be too much waste of effort. Team already suggested that we should create a Terraform module. So it's the first instance of the same topology. In particular, trusted insert would be exactly the same topology on network level. So in order to achieve a proper VPN restriction, I chose to refactor on the Terraform module. Now CI and Trusted are using that module. So now I should be able to spin up third CI a new virtual machine and will migrate its data on this one. We expect then once it's done, not only securing trusted and third CI access, it's already the case for third CI. It's already the case for third but not for trusted, but also we'll be able to delete the legacy network to avoid wasting resources on Azure. Is there any question on this one? Put a spawn a new instance or sort. And this one blocked by below issue third CI. Migrate package origin service from AWS to Azure. So I didn't have any time to work on it. It's the same idea as WaterVis doing. I wanted to work on the foot of AirVis, especially with the work it did on improving the end charts. Since we will have holidays and eventually take cover of the updates to Nkinsayo, I propose to move that issue on the backlog until update center, until we have a clearer view. It's on the good direction, but I don't want to follow AirVis work and then having to chain two or three times because we had bad surprises in the date center. So I prefer that we start to have something, we are close to a stable situation for date center. Thanks to that job. So yeah, I prefer having less things but doing them sequentially but properly. Is that okay for everyone? Back to backlog. Time, let's see. Command prompts to avoid confusion between services. Steph and I believe you wanted to work on this one but you didn't have time. Exactly, I'm sorry. Do you want to keep it? Is that possible? Yes, please. Yes. You see it's possible. Still working on it. And next issue, ATH builds commonly unresponsive.  That's just a few pipeline code line. Stefan, is it okay if I take over this one for billing reasons on Azure? I just want to have this implemented before every developer come back from early days and start picks of ATH builds. Yes, and in fact you planned to do it but show me that. So that would be perfect if you have time too. Okay. Takes over. But we'll burn always. Only if it's not taking time of you from the RM64 build. I want you fully focused on this one. I agree. I agree. Linux foundation mark, did you have a feedback from the LF about the caching topic? I have not asked them yet. Sorry, no feedback because I've not asked. No request to LF. Right. That's still my actual item. No, it's a critical item. Cool. Stefan, RM64, can you give us a summary? Yeah, that's easy. I'm working on the chat pipeline library to be able to build our images on IMD and ARM. So the proposal is not going further until I'm able to build all the image that we plan to move to migrate in both platforms. But it sounds good. Already migrated. Yes. Okay. I believe right now you are switching to use of Docker bake files. Docker bake for Linux at least. Yes. To allow RM64. Windows and RM64 is not a thing for our cloud provider. So that will be Windows Intel or Linux, RM Intel. And the benefit of Docker bake, it's a bit of revamp and change the behavior of the pipeline library. But that will benefit because that means we can also build images for PowerPC or S390X image if you want to run custom agent or custom services on such machines. Meaning if you have a sponsor giving us this kind of machines, we can use them for production workloads, especially for HA services. That means we could have one Intel machine and then replicas on let's say cheaper machines in the future. Thanks. So you have to continue working on that. It's your top priority item. Is that correct? We need to discuss how we handle some names and stuff, but it's almost done for me. Okay. Status walking on naming convention. When you start speaking about naming convention of variables, it means you're almost there. Yeah. Last time I said I was almost there, it took me like two or three weeks more. So I should be more careful. You set up my SQL instance. So Matomo still same status. We still need to set up the MySQL instance and images and stuff. Since we plan to deploy it on ARM64 at first, that means the second task around images, I'm waiting for Stefan Effort on this one. But at least we can start setting up MySQL instance. Finally, Erwei, I believe we can put Blushen back to backloggy. That's not a problem. I just wanted to be sure, but since you are in holidays, neither Stefan or I will be able to work on it. Oh, holidays. Okay. That's all for me on all these topics. That should be a, we should shrink the next milestone. Do you have new topics you want to mention here while I'm checking for new issues? Okay. We have a blocked anti-spam system. So that's a usual account. So day to day operation. And the last stage are still on the backlog and okay. Nothing new for us. Just a word on Kubernetes 1.26. The odds limit will be October 20, 2023. So that means we should plan 1.26 in September, just as a reminder. That's all for me. Anything else for you, folks? Nope. Okay. Cool. So then see you next week for Stefan, Kevin and Hai. Enjoy your holidays, Erwei. Take care. We want you fully rested and powered up in two weeks. See ya, folks. Take care and see you next week. Bye.


In this video we will show you how you can connect SuperOffice CRM with Cisco WebEx. You need to have administrator rights to do this. You can only connect to one video meeting provider at one time. When you are logged into SuperOffice CRM, go to the Settings menu in the top right hand corner and choose Settings and Maintenance from the drop-down menu. Here you can administrate and configure SuperOffice CRM. In the Navigator menu on the left hand side, click on the Preferences button and open the Video Meetings tab. To connect SuperOffice CRM with Cisco WebEx, click the Configure button. A new browser tab will open. On this page, you can configure the connection between SuperOffice CRM and your video meeting provider. Please be aware of the requirements for each individual video provider. To connect SuperOffice CRM with Cisco WebEx, you need a Cisco WebEx account. Start by clicking the Cisco WebEx button. Next, you will be forwarded to Cisco WebEx authentication portal. Here you will be asked to enter your username and password to complete the authentication and validate your user credentials for your Cisco WebEx account. We have now shown you how to connect SuperOffice CRM with Cisco WebEx. To remove the integration between SuperOffice CRM and Cisco WebEx, you can click the Disconnect button on the configuration page. Your connection with Cisco WebEx is now set up. Make sure to close the configure settings web browser. This will prompt SuperOffice CRM to reload and activate the Cisco WebEx connection. When you go back to the user side of SuperOffice CRM, you'll see that the Video Meeting button is now available on appointments in the diary. Thank you for watching. For more information on how to improve your productivity with SuperOffice CRM, please visit our community website.


basically a new narcotic or psychotropic drug that in its pure form of preparation that is not yet controlled by United Nations drug conventions but that may pose a public health threat comparable to those substances that are already listed. Basically something new that hasn't been scheduled, that hasn't been focused on by either law enforcement or public health organizations. And just to kind of put these things in context literally the weekend before I planned on coming out here a music festival in Florida in the United States had a bad batch of one of these novel psychoactive substances that are as yet undetermined of an identity that resulted in the death of two in the hospitalization of 57. That is a substance that we still have no idea what it is and it was flagged as some type of molly or amphetamine type stimulant. This is the this is the standard ladies and gentlemen people don't know what the stuff is but the news is going to flag it as something such as MDMA or a psychedelic because they don't know and until they don't know whatever kind of previous and pre-existing bias that exists about drugs is going to be slapped onto it. And to give you a sense of the scope of the problem this is from the EMC-DDA last year. That's the number of novel substances that have been picked up by the organization just in Europe alone. And I do want to emphasize that the bottom half that's 60 new substances the red and green bars that's entirely taken up by those and the amphetamine type stimulants that have potentially psychedelic effects or synthetic cannabis like K2 and spice those fake pots that have been showing up all over. And these substances are not just different brands these are unique chemicals that are being synthesized and sold in gray markets all over the world. This is a chemical structure comparison between some of the more classic substances like THC and amphetamine and the other drugs that are now showing up such as UR-144 and MDPV like you saw earlier. This is some data from the National Health Services report from Scotland basically talking about drugs and drug effects every year. And I don't really know how to make this any more stark. I am not familiar with Etizelam which is designer benzodiazepines. I am not familiar with ethylphenidate which is a chemical iteration on Ritalin. But these are substances that did not exist on the radar of medical practitioners in 2012 and are now killing more people than all classic psychedelics and MDMA combined. This is a study from a music festival out in the United States basically an organization stood outside of the booth and told people hey listen we'll give you 20 bucks if you tell us what you took what you're planning on taking and you know if you give us a blood or urine sample so we can confirm. And a lot of people had a very specific understanding of what they were taking. They you know largely believe they were taking marijuana, alcohol, cocaine and MDMA. But out of the 104 participants even though 30% had said they were taking MDMA many many individuals who had said they were taking it also tested positive for a bath salt called alpha PVP. Additionally they were also testing positive for methylone, ethylone or butylone which are three amphetamine type stimulants that are considered novel psychoactive substances. And this means that straight up many many individuals that are consuming these drugs are not consuming them on purpose. They're purchasing something underground from either a dealer or a friend and they are literally getting something completely different. You know this is a very very different situation than when you would purchase LSD and you would get a piece of paper. You know there's a very big difference between getting simply nothing and getting a totally different substance that approximates the effects you were looking for. This is some research that's actually still in press by Dr. Joseph Palomar at NYU. And I would like to kind of emphasize the findings so I'm just going to read the table results. Racial minorities were more likely to report no lifetime bath salt use but have a positive hair sample for bath salts. And additionally those who reported no use of bath salts but tested positive for an NPS were more likely to report having earned less than a bachelor's degree. This starts to paint a very very disturbing picture of the idea that the individuals that are not getting the psychedelic that they want are generally lower income, maybe less educated, maybe a minority individual. And that is a trend that is deeply concerning for me. The idea that your class, your race, your ethnicity or your education would in fact determine whether you are able to have the psychedelic experience of your choosing. I think that is something that is only now developing as a problem and we need to start taking it seriously because it affects not only are you know the perception of psychedelics but the actual experience that people en masse are having. This is a study from 2013 in published in drug testing and analysis that showed just you know look for the data for yourself. I know that some of us may be familiar with 2CI and 2CE but I do not recommend consuming 25I, PMMA or you know 4FMA unless you have very very specific understandings of what these drugs are and these are total notifications by member states to the monitoring organization so that these are the number of times these drugs managed to hit an ER that were totally novel and the systems didn't know how to handle them. And when I do mean there are a lot of drugs I mean there are a lot of new drugs. I'm not familiar with most of these. I don't think anyone in this building is actually familiar with most of these you know and that is hugely worrying because if all of a sudden you have a forensic psychologist I had an NYPD forensic examiner call me and ask me about one of these sedatives. I have no idea. I mean these drugs didn't exist two to three years ago and now they're starting to show up in autopsy reports. My biggest concern is that one of these is going to be deeply problematic. Speaking about those synthetic cannabinoids just in the United States the stars mean that they're schedule one and the other drugs are not.  So one brand may be 100% legal for human you know for having not been scheduled yet and the other one could be a class one felony. So just because of how crazy this is I wanted to take professor David Knutts words directly. You know one of the dangers of this approach is that has been taken if we ban every new drug without a balanced view then people will keep making more new drugs to replace them and eventually they will make something that's extremely toxic which when the kids take it they will die. That I don't want to be a fearmonger I don't want to try and be aggressive about this but I think that the amount of new substances that have hit the market in the last five years that mimic classic psychedelics or have similar symptoms is tremendously problematic and even though we may not interact with them on a day-to-day basis some people are. So some of the more problematic ones that we have evidence for firstly 25 I I don't know if anyone in the room is aware of this substance but it's something that can be used safely. There are definitely people that I know that have preferences for it under certain environments under certain conditions but it also has been associated with 17 deaths in the United States in the last six years. We have had individuals be medically transported from festivals because they've had seizures at half an hour after dosing. You know one of the biggest problems with it is that it's active at a microgram level just like LSD but because of the fact that most people are usually only getting it from either street dealers or festival dealers they're not getting exact dosages. You know the biggest problem with that is that LSD is a relatively harmless substance. You may not have a the best day if you take five tabs accidentally but you'll be fine. You know you'll you'll you'll wake up the next day. This is not the case with n-bomb. There are reports of seizures happening to cardiovascular events, agitation and aggressive behavior and renal failure. You know this is this is being scheduled. It's schedule one in the United States. It's going to be scheduled in Canada as well and it's definitely not something I'd like to be caught with in the European Union. One substance that got very very big and then was quashed thankfully is a second generation bath salt commonly known as alpha PVP. The street names for it include flocka and gravel just in case you wanted to get a sense of how awesome this substance is. This is I think a pretty stark illustration of the problem where this is just the number of crime lab reports submitted between MDMA and synthetic cathenones. This basically means that around 2011 MDMA purity essentially evaporated in the United States and synthetic cathenones rushed in to fill the void. Basically in 16 months you had 63 deaths in one city in one state alone. That's not including all 50 states because those numbers are still kind of hard to generate but when you're getting 20 ER visits a day from a substance that didn't exist five years beforehand there's kind of a huge pressure on law enforcement public health and governmental authorities to do something. One of the biggest steps forward they were able to make was they were able to push and pressure China to stop manufacturing the substance so with that combined with an extensive law enforcement effort across the United States cases of alpha PVP intoxication dropped to almost nothing which in my opinion is a very very good thing. It shows that targeted interventions for a lot of these substances can actually work. However that also means we have to see them and we have to do something about it. You know just to give you a scope of the problem again that's the number of different brands that were found in just Gainesville Florida of synthetic cannabinoids and synthetic cathenones and the list of side effects that go from anywhere from self mutilation, tachycardia, transient ischemic attacks, nausea and serotonin syndrome. These are drugs that have risk profiles and side effects that classical hallucinogens and psychedelics have never had and because of that fact I think they're deeply problematic for the continued push to mainstream and normalize actually non-harmful psychedelics. You know just to give you a little bit more information about synthetic cannabinoids they're actually the proper term is synthetic cannabinoid receptor agonists because they're not actually cannabinoids. They're chemicals that were used to explore the cannabinoid receptor system and there are three classes of them but at the same time they are all full agonists of CB1 and CB2 even though THC and CBD aren't. You know these aren't drugs that were created to get high from. These were drugs created to explore the animal model of the cannabinoid receptor system. You know the biggest problem is they have no quality assurance or quality of control policies when these are being created so not only do you have cross contamination between brands of these synthetic cannabinoids you have what are known as hot spots. Hot spots are basically what happens when someone's making drugs in their basement where you take a pile of plant matter and you spray the synthetic cannabinoid receptor agonist on it but the coverage is uneven so that means you have differential quality and purity within the same bag of drug which is insane if you think about it for any you know for more than five seconds but there's nothing to be done about this because they exist in this gray market universe where if you stay one step ahead of a regulator you can buy this stuff at a gas station. You know there's this this writer that I know he has this blog called the dose makes the poison where he talks about different substances and their problematic you know their problematic issues from a toxicology perspective and I think he said it the best. You know the vast majority of people using these substances and products are consuming substances of unknown identity with unknown pharmacological and toxicological profiles and unknown combinations unknown dosages. This is probably the craziest thing that I've ever heard like the fact that it's not just a hallucinated fantasy but the reality of thousands if not tens of thousands of drug users all across the world is deeply kind of troubling to me. I'm going to talk very quickly about two substances that have been showing up in other drugs such as fentanyl. Basically U18 is a novel opioid or is considered a novel opioid that has started showing up in benzodiazepines and designer benzodiazepine mixtures and it's an opioid that has no activity at any of the opioid receptors even though it's seen as approximately 10,000 times as powerful as heroin. We have no evidence of opioid receptor activity but it's being considered an opioid. This is madness you know the the the narrative is completely different than what's actually going on in the science you know and in the United States and Canada we have additional problems when it comes to high potency high strength opioids infecting non-opioid medications where you have because I can tell you right now I can't tell the difference between those two benzodiazepines. One of them is actually made of venopioid that could probably kill you. The other one is Xanax. I mean Xanax is not a great drug but at the same time it's certainly not lethal.  So now I want to talk about kind of why it's different this time around you know this is how we report those issues you know we don't really say what the drug is we just slap the term rave onto the party and molly onto the drug and we say this person was hospitalized because they overdosed on molly just as a show of hands or you know call out. What color is molly? Okay does the fact that I heard five different answers bother anyone else? Like if your daily painkiller was three different colors would you take it? You know and obviously that's kind of you know a push out but at the same time ecstasy and molly are a very very loaded term lsd means lsd psilocybin means psilocybin but now we have these catchall phrases that include almost anything if I take molly that has mda in it it's going to be a little bit more psychedelic if I take molly that has mdma and a stimulant in it I'm going to be running around for three hours but at the end of the night I'm still going to have the term molly associated with an array of behavioral symptoms in my head so when we talk about it we're going to have two completely different definitions but we're not going to confirm that I'm not going to go hey was your molly speedy like I'm just going to think that it is because that's what my experience was you know and more importantly nps is most of them can't be detected by drug tests yet I mean this is one of the reasons why people do them you know you work in security you have work in you have a you know parole officer you have all of these kind of concerns and you can't be caught with a drug test you can't be testing positive for cannabis or cocaine or you know anything so you have one of these other options which you know you maybe won't get arrested but you might die and also like specific details and this is where I think it affects the psychedelic research renaissance can slip through the cracks you know there was this very famous story a couple of years back of this bath salts causing this person to like eat this other person's face and it was terrifying except there were no bath salts in a system it there were no there wasn't even any cannabis in a system he was just mentally ill but the story was run and pushed past and got super famous in the same way that every time there's a molly overdose what the drug actually is is kind of completely ancillary to the story chasing you know there was there was a case in a university in the northeast of the united states where somebody had taken a bunch of what seemed to be mdma but it was actually a synthetic cannabinoid and that's a psychedelic but at the same time the story had already kind of come and gone and a certain drug had been demonized that's where we are now you know the psychoactive substances act in the UK passed recently and now we have this forensic strategy where we're going to be illegalizing drugs based on the receptor that it acts on which one it only acts the law only stated that receptor activity at cb1 GABA 5ht2a nmda mu opioid or a monamine transporter would be affected so if you can create a drug that gets you messed up on uses a different receptor you're good which i think that's the problem we're just going to keep pushing innovation that pivots around these laws because we're using a very very poor fat you know measure of psychoactivity and this leads to unfortunately my nightmare you know what happens when an exceptionally damaging synthetic cathenone or novel psychedelic is created and then pushed into a recreational drug supply and then consumed by someone important i.e. Donald Trump's daughter you know what happens when say for example at fashion week or you know a very important party in washington dc or something like that in europe where something goes horribly wrong because a drug that is novel is introduced as a replacement or a cut into a classical chemical if that happens we're going to see a lot of this environmental like friendliness get very very cold very quickly a lot of the research and a lot of the funding that people in this room in this building are relying on is going to dry up because i guarantee you they won't know the difference you know we barely know the difference between a lot of the more novel and nuanced substances i can tell you that Donald Trump will simply not care you know so kind of bringing it back to us you know what can we do i think we need to check our drugs like people need to test their substances if you're going to go out you need to stay hydrated you need to understand that if you're taking a novel substance that you shouldn't be redosing that you shouldn't take one and then take two more an hour later you know there are great harm reduction services such as zendo and the harm reduction services at the boom festival in portugal these are all organizational structures that need to be supported because really they're the only ones that are preventing this from happening and more specifically especially for my advanced psychonauts out there we need to accept that trip reports on arrow wood and blue light are not research this is one person's story in one environment about the psychedelic that maybe has no bearing on whether it's going to be safe for you to consume so please please be cautious you know what one of the other things that i would love to see this came out of switzerland where they were documenting all of the psychosactive substance environmental cases that they had seen there was no bias they said here's all the stuff that we saw we tested everything and here were the new novel substances that we are not really familiar with that that kind of conversation in gender safety and also one last thing is we need to stop treating psychedelics users like children you know messages that recognize drug user subjects as events incompetence responsibility and a desire to reduce harm while simultaneously pursuing pleasure maybe experience is empowering by young users you know don't tell them that it's going to kill them because they kind of have already done the research a lot of stuff isn't going to kill you but if you tell everyone that pot's going to kill you acid's going to kill you ecstasy is going to kill you they're not going to listen to you when they get to n bomb they're not going to listen to you when they get to bath salts so in closing you know like where do we actually go as a you know collective from here you know it's very specifically realizing that we cannot schedule our way to safety we just can't there's too many drugs and the iteration cycle of drug development is getting faster faster and faster you know we're seeing third and fourth generation bath salts we're seeing substances that have already overtaken 25 i and a number of others and that's just going to keep happening as these companies pivot around scheduling systems i think we need to we need to start exploring the facets of the psychedelic drug experience as an array of symptoms not as a preference for a certain substance because we're now in a place where it's not just about i prefer lsd to psilocybin it's i prefer this kind of visual space this kind of mental space this kind of activity level because we have choice and we have choice now like we've never had before but that also means there are probably ones that are safer there are probably ones that are better for certain types of activities there are probably ones that no one should be doing you know more specifically we need to actually understand how certain substances are affected by dose setting and privilege but of course the easiest way to actually make this better would be to just end the war on psychedelics so people could get the drugs that they wanted thank you very much fantastic dog thank you so since most people don't have the access to a mass spectrometer my more sophisticated festival goers are using test kits yes and so the the issue with these is that their color change and so if you get an admixture which most of these things are yep and say something is 60 mdma and 40 pma how is that gonna how does that test out in the color changes and how likely is it one to get a false a false positive so one of the one of the best case practices when it comes to those color change tests is you say for example if you have something to test positive for mdma there's a secondary test that can test for you know a bath salt pma something like that so there's generally you can run up to four tests on a certain substance to give you four yes or no questions because you know we have to treat drugs like we're asking a genie things um i think the biggest thing is to also understand that a lot of people are also probably not going to take those steps because you have to use a piece of the drug you know i i i spent all my money on the mdma i'm not gonna then take the mdma and waste it um i think what you're getting at is exactly the clinical limitations of harm reduction in this environment you know absolutely test it tested at home test it not under low light or black light or you know something like that but also you know this is the difference between the privilege of an individual who has a regular dealer and someone who's buying something at you know Glasgow or Ibiza or something like that and you know we we we i want to tell you you know don't buy drugs from strangers but at the same time it's that's something that people simply won't do you know they're going to and they're going to be in that environment so we can only say listen test it if it looks wacky don't do it you know what i i do harm reduction drug checking for events in New York City and some other places and thankfully when we have tested and someone's stuff had come back as completely ridiculous i've i've never seen them take it i've never seen them go okay this is not what i thought it was i'm still going to put it in you know i i've found that most people once they realize that they've gotten something that they aren't prepared for are generally willing to back away which is hopeful hope inducing for me oh absolutely um ecstasy data pill reports blue light you know that the biggest issue the biggest limitation with those is that batch to batch batch to batch differentials you know and also copycats where just because one's pill has you know large purity etc you develop a lot of copycat presses that people want to cash in on you know and the thing is europe is actually kind of having an opposite problem because after a specific drop in purity which gave rise to bath salts in 2011 2012 we're now seeing this giant spike in purity where we're having where there are pills that are showing up in certain countries that are potent enough to be two or three doses and and i i think if you look at the data there you're going to find that bath salts kind of don't stack up people aren't doing them anymore because i think there's a very clear preference for classical psychedelics that you only get into this other stuff when you can't get what you want i'm kind of tailing on that what are your thoughts on any possibility of centralized distribution in the near future at least possibly of gray markets possibly like decriminalization so i mean that's that's definitely a much more policy discussion that you may want to talk to rick doblin and the you know the individuals that spoke pretty you know long about i think it strengthens the case and you see a lot of policy public policy makers stating that they hope that this helps push the conversation along because the only way to really fix this stuff is to get that decriminalization or centralized distribution created i was mostly curious that you were saying that it seems to you that traditional empathogens traditional psychedelics are taking the blame in the press most often for new psychoactive substances in the uk we've seen the complete opposite so when methadone was still legal almost every death that occurred due to any drug was blamed on methadone and in actual fact david nut has pointed out quite almost ironically i'd say that when methadone was legal we saw a drastic decrease in drug related deaths from cocaine and emphatamine because in actual fact it's much less toxic and once methadone was made illegal then those deaths spiked back up again so i would ask you like do you not think that the issue is not necessarily to do with these being novel substances but more to do with prohibition in general i mean you've advocated intervention against them but i feel that all of the problems you've mentioned haven't been due to prohibition what needs to happen is we need to have a serious discussion about what these the damage that these drugs do and when they're useful there are definitely people that i know in new york miami la that prefer methadone to cocaine or mdma depending on the situation but right now the biggest issue when say in the united states is that i can't trust methadone's purity you may be able to in the uk and exact that speaks to exactly the point exactly and and that that is exactly until because of the fact that prohibition is a binary issue that has a significant amount of resistance that is going to be a very very long uphill battle i think in the interim we kind of not only do we obviously need more research in what these drugs do but we also need more funding such that the research when it comes to human trials actual like you know basic understanding of what happens with these things independent of just blue light trip reports etc such that we can actually turn these into legal above ground medicines and consume you know consume around that stuff you know one of the biggest things that i've seen is that independent of all of the stimulants that were made illegal in the united states in the 90s a lot of methamphetamine had come in to replace that and if they could get something like methadone ephedrine something like that they would be able to satisfy a need without necessarily going for a drug that's tremendously harmful of course


You start hissing you can go can't you?  I Can't read chat right now cuz he's just sat in front of it. Good job, Tanykin.   You're fine.  Yes, okay? He drink it drink it nothing nothing nothing nothing. Yeah Dr. Hodge, I have to feel this power. Please. Yes. Yes. We can go We can go power right now. Yeah cheap shot. Yeah I'll be clocked. I can stop the measure Okay Calculated I looked into playing early. I have no Just feeling free Yeah I got cheap shot I'm sheep full sheep full. Yeah, what do you want to drink it? Yeah?  No one for your right.  Yeah I'm here miss Anything on road, please Cheap cheap cheap me watch out.  Please stop re-stop re-sheep Okay, okay, re-sheep Stop third Okay, okay, we're right then I think yes, I'm not gonna fear priests for increase.  From fire, okay, I'm gonna stop stop show and go No, they're not they're not stop anything ready. Yeah, ready.  You got it.  You're fine. You're fine Okay, can we go power, please? Yeah, I fear him five Yeah, sure. I'm gonna help you with him I'll cheap shop gosh here cheap shop stun me getting fit. Yeah, you can get lining next Yeah, I'm fearing fearing fearing double double double so much damage so much damage so much damage Bubble has to be bubble. Yes, I'm trying bro. I'm trying. I think well Bubble you can't Five sec for fair Double fair double fair Nice Trying to PSA you're lining me


Hello and welcome to the session. This is Professor Farhad and the session will look at parts of standard unmodified audit opinion report for specifically non-public companies. Every time we are done on public companies it means we are dealing with the AI CPA. This topic is typically covered in an auditing and attestation course and obviously on the CPA auditing exam. As always I would like to remind you to connect with me on LinkedIn if you haven't done so. YouTube is where you would need to subscribe. I have 1600 plus accounting, auditing, tax and finance lectures. If you like my lectures please like them, share them, put them in playlists. If they benefit you it means they might benefit other people so share the wealth and please connect with me on Instagram. On my website you'll have additional resources, additional lectures, additional PowerPoint slides about auditing and if you're studying for your audit exam 500 plus CPA questions I strongly suggest you check out my website for additional resources if you are serious about passing the exam. So what I'm going to do with the audit report I'm going to break it down into eight components which is those are the eight components of the audit reports anyhow. We're going to go through it step by step then I will you know and I would reveal the audit report. The first part is the title. The report title should include the word independent so that's the first that's the first part. Why the word independent because remember the auditor is passing an opinion so for the opinion to be relevant for the opinion to convey credibility you have to be independent from the client so it has to say independent auditor's report so that's the first part. The second part who is the audit report addressed to usually it's the stockholders and the board of directors not management again to convey independence because if you are reporting to management and auditing management your independence might be might be jeopardized so that's why we we address the report to the board of directors or to the stockholders basically the stockholders and elect the board of directors and in the situation to general ring company. The third component which is this used to be the last component in the old report so this is the new report goes the auditor's opinion so notice let's at the beginning of the report basically okay it used to be at the at the end of the report well the AI CPA thought that it's since the opinion is important you want to put it first rather than last so this is this is the auditor's conclusion what the auditor thinks about the report so let's take a look at this and see what do they say in their opinion okay we have audited the financial statements of ring company which compromise the comprise the balance sheet as of December 31st 2019 and 2018 first they tell you which financial which financial statements they're auditing and the related statement of income changes of equity cash flow for the year ended as well and notice it's comparative now here comes the opinion and our opinion and our opinion but before we go to the opinion notice that they explicitly said we audited audited means we did not issue a compilation we did not we did not conduct a review we audited because audit has a higher assurance level than compilations in the review okay now in our opinion this is important this is where the auditor comes and talks about what did they find in their opinion the financial statements present fairly what does it mean present fairly it means they follow the guidelines that that we used whatever it's us gab or IFRS they present fairly in all material respect the financial position of the corporation as of December 31st and as a result its operation of cash flow for the year ended in accordance with except generally accepted accounting principle of the united states so they're using the us us gap us gap so this is the basically this is the most important this is the most important why because when you look when we when we think of the audit report we think of the opinion that's what we think of so that's why the opinion is extremely important okay now remember this opinion is not absolute this it's a reasonable it's based on a reasonable basis okay so they have to tell you which framework they use they use us gap now how did they come up with that opinion basis for the opinion so what did they do to come up with that opinions that's in the fourth paragraph so this is the fourth paragraph in the fourth paragraph they talk about the basis of the opinion we conducted our audit in accordance with what did they use auditing standard generally accepted in the us basically what we called gas g a a s g a a s gas so that's what they followed obviously gas our responsibility with those standards are further described in the auditor responsibility so they're gonna tell us what they're gonna talk a little bit more about what was the responsibilities what did they do we are independent again they mentioned this word independent repeatedly that's that's important of the company and we have fulfilled other ethical responsibilities in according with the relevant ethical requirement related to our audit so we follow ethical standard we believe that the audit evidence we have obtained is sufficient and appropriate those are keywords to provide a basis for our opinion so what is sufficient and appropriate well we will learn about this when we look at the evidence but we're saying here that we have enough evidence to issue our opinion so the basis of our opinion is we follow gas that those are the techniques we collected enough evidence sufficient and appropriate not enough sufficient and appropriate to provide a basis and we are independent from the company so this is how we came up with our opinion the fifth the fifth one is the fifth part of it is management responsibility and this is important we want to know what is the management responsibility okay we're auditing the financial statements we told you our basis but what's management responsibility so this is important okay management is responsible for the preparation and fair presentation of the financial statements in according with gap so management prepare the financial statements also management responsible for the design implementation and maintenance of internal control relevant to the preparation and fair presentation of the financial statements that are free of material misstatement whether due to error or fraud so basically what we're saying is and this is important that you get tested a lot about this concept who's responsible for the financial statements management is responsible for the financial statements all we're doing is we're issuing an opinion okay so in preparing the financial statements management is required to evaluate whether conditions or event is considered an aggregate that reception substantial doubt about the company's ability to continue as a going concern also management will have to assess if there's any going concern issue are we going to be in business in the foreseeable future the management will have to decide that now auditor can't pass a judgment on that but that's the management assessment that's the management assessment the going concern assessment so it's very important that the financial statements are the management responsibility then in number six we're going to look at the auditor's responsibility now this is important so what is the auditor responsibility we know that management basically responsible for for preparing the financial statements so what is the auditor responsibility in all of this the first thing we have to say is what did we do what's our auditor responsibility our objective is to maintain reasonable reasonable means not absolute assurance whether the financial statements as a whole are free from material nervous material not all the statement whether those statements are due to fraud or errors and to assure an auditor's report that include our opinion so reasonable assurance we're using reasonable assurance to assure an opinion what is reasonable assurance is a high level of assurance but not absolute we can be 100 sure therefore it's not guaranteed that an audit conducted in according with gas will always deduct material misstatement so what they're saying here is look it's reasonable assurance we followed gap but we cannot guarantee there are no errors so the risk of not detecting a material misstatement resulting from fraud is higher than the one resulting from errors and what they're telling us here is if there is a fraud issue the fraud will be higher to detect because the fraud may involve collusion forgery intentional emission misrepresentation or the override of internal control so they're just warning us that if there's any fraud it will be harder for us to catch the fraud because the error if somebody made an error they don't try to cover it okay but the fraud you know part of it is try to cover the error okay material statement are considered material if individually or an aggregate they could reasonably be expected to influence the economic decision of the users made on the basis of these financial statements now what is materiality we'll talk about materiality later on so within this section we have this is the first paragraph the second paragraph they again they they specifically spell out how they conducted the audit so again we're still we're still in paragraph 6 but it's basically broken down and I'm going to break it down into three categories so we looked at the first one talking about reasonable assurance and opinion now basically we're going to look at the scope and performing an audit in according with gas what did we do we use professional judgment and exercise professional skepticism we were on the lookout we're all we had a questioning mind we did not let things slip through we identify and assess the risk of material in the statement of the financial statements whether it's it's due to error or fraud and design and perform audit procedures responsive to those risks such procedure include examining on a test basis we didn't look at everything evidence regarding the amount and disclosure of the financial statement here the auditor is basically spelling out exactly what they did we also obtain an understanding of the internal control relevant to the audit in order to in order to design audit procedure that are appropriate in the circumstances so we obtain the understanding so we can audit and not for the purpose so notice here we they explicitly said not for the purpose of issuing expressing an opinion on the effectiveness so we collected this information about the internal control not not to express an opinion but to make sure we can design audit procedures to test those control but we're not expressing an opinion okay we're in order to audit procedure that are appropriate in the circumstances to be able to learn about the company but not to express an opinion that's important we also evaluate we also evaluate the appropriateness of accounting policies used and reasonable of significance accounting estimate made by judgment management remember management makes those judgment selecting the accounting policies principles making significant estimate but we can evaluate those okay and also we evaluated the overall presentation of the consolidated financial statement okay conclude whether in our judgment there are conditions or event considered in the aggregate that very substantial doubt about the general rank ability to continue as a going concern within one year we also did this uh this going concern judgment we also looked at remember management look management uh management raises substantive management look at the going concern assumption and the auditor also evaluated that going concern assumption as well and the third paragraph within the auditor responsibility they tell us that they are required to communicate with those charged with the governance regarding among other matters the planned scope and timing of the audit significant audit finding and the internal control related matters identified during an audit so they're telling us also that they do communicate with the board of directors about certain issues about planned and scope and timing of the audit significant finding so on and so forth so they tell you this the seventh part of the audit report is the signature and address of the audit firm the signature Anderson and Zinder PC CPA and in what city they are located so they tell us where are they located in the name of the firm rather than the name of the individual rather than the name of the individual because technically the firm is responsible not the individual that conducted the audit that conducted the audit in the last part is the date this is the eighth part and the date is February 15th 2020 the audit report date that date the auditor has obtained sufficient and appropriate evidence now remember the financial statements are as of December 31st so it took them a month and a half all of January and half of February to issue those financial state to issue the report and it's the date is important why because what we're saying is we are responsible up to until February until February the 15th so we were looking for material unrecorded transaction that occur up to February the 15th that's what they're saying here so that's important so those are the eight parts of an unmodified audit opinion so it's very important that you are familiar with the audit report with the format of the audit report because on the CPA exam they do ask you what goes where and this is a new audit report the old one they used to have the opinion this opinion here the last the last so this is I broke that into two powerpoint slides because it's a long report in the next session what we would look at is condition for standard unmodified audit opinion so when when can we issue this unqualified standard unmodified audit opinion as always I would like to remind you if you like my lectures please like them go ahead and click on the like button it doesn't cost you anything share them put them in playlist and if you want additional material to supplement your studies or to help you pass the CPA exam you may need those extra seven to ten points check out my website I do have those resources study hard the CPA is worth it


My vision is about focusing on positive contributions rather than simply trying to mitigate negative action. I wanna make sure that the environment that I live in and designed for is a beneficial contribution to society as a whole. We need leadership at all levels within our organizations and that means from our executive management teams through to our new hires. We're positioned as solution providers for our clients and stakeholders, but we need to get comfortable with asking questions and acknowledging that we don't have all the answers because really the best solutions tend to be collaborative.


The President's budget proposal eliminates public media funding. Learn how you can help at lptv.org slash action. Supporters of Great River Rescue rallied at Bemidji Bowl over the weekend to fundraise for the animal shelter by taking part in the annual Fur Bowl. Josh Peterson shows us how people of all ages work together to raise not only funds but awareness. For years, Great River Rescue saves and cares for companion dogs and cats and then works to find them a loving home. The shelter is a non-profit and depends on the support of the local community, which is why events like the annual Fur Bowl at Bemidji Bowl is important to the success of the rescue throughout the year. We use the money to care for the animals, to take a man to give them shots, to spay and neuter them, to make sure that they're a staff that's able to care for them continually and then to adopt them into homes with the responsible pet owners. Nineteen lanes were filled with fur bowlers of all ages and experience levels but it's the bowling for a cause that unites this large group. Oh, I think it's great. We're having a great time. I'm not any good at bowling but we're sort of having a good time. For some of those who took part in the event, it's not only about raising money. It's about educating people and getting them involved. Most important thing to do is to get out and make people aware that there's a need and go out and drive for it. But you didn't have to bowl to help out with the Fur Bowl. Several artists turn regular bowling pins into fun works of art to be awarded to the top fundraisers for the event. We have special pins designed by the artists of Gallery North and the top fundraisers, they get the first pick of those pins. For some of these bowlers, one common message unites them. Simply check out the rescue and get involved. Take a little trip down to the rescue here in town, look around, see what we've got down there for animals, ask how you can help. In Bemidji, Josh Peterson, Lakeland News. The Fur Bowl raised over $7,000. If you've enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland Public Television.


The Senate has passed a bill to repeal and re-enact the Customs and Exides Management Act 2004. The passage of the bill followed the consideration of a report by the Committee on Customs, Exides and Tariffs. Chairman of the committee, Senator Francis Alemi Kenna, in his presentation said the bill, amongst others, seeks to assist the Nigeria Customs Service Administration in driving economic growth and trade facilitation. The added that the bill, when signing to law, would make the NCS a legal entity on the supervision of the Federal Ministry of Finance, Budget and National Planning with a board to serve Nigerians and facilitate international trade. The Nigeria Customs Service is a legal entity other than the supervision of the Federal Ministry of Finance, Budget and National Planning with a board to serve the Nigeria and facilitate international trade. Methodology, the committee adopted the following methodologies incurring out East Legislative Assignment. One, the committee meetings. The committee hereby recommends that clauses 1 to 6, A to 283, clause several deleted and explanatory memorandum be passed. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Putin's government also arrested Navalny's body, mother of late politician is being pressured. The mother of Russia's late opposition leader Alexei Navalny said that she has seen her son's body and that she is resisting strong pressure by authorities to agree to a secret burial outside the public eye. Lyudmila Navalnya said investigators allowed her to see her son's body in the city morgue. She said she reaffirmed the demand to give Navalny's body to her and protested what she described as authorities, trying to force her to agree to a secret burial. They are blackmailing me. They are setting conditions where, when and how my son should be buried. She said in a video statement from the Arctic city of Salikhard. They want to do it secretly without a mourning ceremony. Navalny's spokesman Yamish said on X that his mother was also shown a medical certificate stating that the 47-year-old politician died of natural causes. Yamish didn't specify what those were. Navalny's mother has filed a lawsuit at a court in Salikhard, contesting officials' refusal to release her son's body. A closed door hearing has been scheduled for March the 4th. She appealed to Putin to release her son's remains so that she could bury him with dignity. Navalnya said that she had spent nearly 24 hours in the Salikhard office of the Investigative Committee where officials told her that they have determined the politician's cause of death and have the paperwork ready, but she has to agree to a secret funeral. They want to take me to the outskirts of the cemetery to a fresh grave and say, here lies your son. I don't agree to this. I want you to, to whom Alexei is dear, for whom his death was a personal tragedy, to have the opportunity to say goodbye to him, she said. Navalnya accused the authorities of threatening her. Looking into my eyes, they say that if I do not agree to a secret funeral, they will do something with my son's body. Investigator Voropeev openly told me, time is not on your side, the corpse is decomposing. She said, reiterating her demand to release her son's body immediately.


air support from the sky has now enabled a US Marine Corps high-mass system, the M142, to now move into a firing position. You can see these systems now driving to your 12 o'clock location in the open field where they will set up their final firing position to engage a depth target momentarily. The aerial fire support from the AC-130 gunship has provided excellent cover to enable a coordinated phase forward of surface fire assets. The US Marine Corps high-mass unit is core site empire and they will strike back deep into the enemy area to your direct front onto a identified C2O more than 15 kilometers in the distance. This US Marine High-mass battery firing today is the first fully operationally capable long-range strike unit in the Marine Corps and comes from the 2nd Marine Division. The AC-130 Spectre gunship supported by forward observers have confirmed after 40 seconds of flight the size of six rockets have met their target and the enemy C2O has been neutralised. We have the 300 kilometers and a variety of future munitions in Devalville that will offer extended range again. High-mass has seen here today delivers affordable, quick, long-range precision strike fires. The Australian Defence Force will acquire the land-based long-range strike high-mass system. The high-mass system will provide the Australian Army with a significant capability boost enabling it to provide a persistent, long-range rapid response capability which is both operationally deployable and tactically fire a salvo of two rockets totaling six rounds into the target area and supported by joint observers on the ground. Strike on target has been confirmed and the enemy has been destroyed. Ladies and gentlemen, that completes the fire power demonstration for today. Here in detention has now been removed. Please remain seated inside the viewing area until all weapon systems have been made safe and the Director of Practice confirms that all weapon traces are closed.


Hello everyone, this is a quick video to show how to install NTA on a laptop or an AVM. So first thing you have to go to HTTPS slash RET dot HTTPS slash MTA, which is migration token for applications web page, and you can go to the download page and download the latest version. In this case, I'm using 5.1.0, and once you have the zip version, by the way, I'm downloading the web distribution, you can unzip it, and then you will have a folder with all the content that is going to be able to launch MTA. So what do you need to be able to launch MTA? Where does it run?  And to run it, you only need a JDK version 108 or 11 by OpenJDK or by Oracle, which are the ones that we test. And then once there, you just run the script, run MTA, and it will launch. If you run it just like that, there will be no authentication, it will lock you in directly, and you will access the interface. How did you access the interface? Well, you go quickly to localhost 8080, and then it will take you to the interface once it's running. Once here, you just first create a project, like migration project, and then you just could point it to a path where you have the source code for an application, or simply upload a binary. Once I upload this binary, I go to code, equation, sample apps, and I get that binary. So let's just get this binary, click next, and choose the targets. So in this case, I want to move these to an EAP7, JVOS EAP7, and then continue the session to run it on OpenShift, on Linux, with OpenJDK. Let's say that we are coming from WebLogic on Windows using Oracle JDK, and we would like to move it to this target. So I select the four targets, click next, it will analyze the packages in the application. The packages that are not common, the application itself is not part of WebLogic, or the typical packages are automatically selected, click next. If you can add custom rules or custom labels, and choose your custom options, but if you don't have any, just click next, and then save and run, and you're done, and the analysis will take place. So you're good to go.


Today I'm going to show you guys how I attach the collar for this pattern. The instructions ask you once you interface and press up one of your collar pieces up five-eighths of an inch. The instructions ask you to sew them together right sides facing like this on all three sides and then turn them out. So instead of doing that how I attach the collar in a less difficult way to the shirt is I take the piece that is not interfaced and go ahead and match this piece up with the collar opening and attach it right side down so they're kissing and then match up the notches on the neck hole opening and the collar and you should get here and there should be that five-eighths of an inch seam allowance that sticks out from the side just like this go ahead and leave that opening right there and just pin this down you should have another five-eighths of an inch gap on this side make sure you have that go ahead and pin it in place so now what we'll do is go to the sewing machine and sew the first layer of our collar down at five-eighths of an inch once you finish sewing that collar and pressing up the seam allowance as you look something like this you match up now your other collar piece right sides facing to the collar piece you've just sewn so now when you sew this collar piece at its five-eighths of an inch seam allowance you just want to make sure regardless of if it's five-eighths or not because this is actually pretty tight that I'll start actually with this amount and get right here on the edge making sure not to stitch onto this part but start right here and go up grade into five-eighths go all the way around at five-eighths come back down and then grade into whatever the seam allowance is right here so here are my stitching lines on both sides so you can see I have five-eighths of an inch seam allowance up here but then grade it down to where it would evenly and sharply fit this part and do the same on this side as well and that's definitely just a little thinner I'm going to trim this down and then turn out the collar so once you have this all pinned down matching the existing stitching line you can go right over this and edge stitch the whole collar down along the bottom I love this way of attaching the collar so much better and here's the finished result I love how neatly the collar and the button placket meet try this method of attaching the collar and let me know what you think