The number of bond present is the number of bond present between the two atoms in a molecule It can be fractional value of bond order is possible in case of resonance. When resonance is possible then fractional value of bond order is different. Integral value will happen there is no resonance ok CH3, CH2, CH3, CH3, CH2, CH3 all the carbon carbon bond if you see it has bond order 1 right because there is no resonance ok. When there is no resonance integral value we have otherwise we have the fractional value. Now calculation of bond order we know also one thing that bond order is inversely proportional to bond length and directly proportional to bond strength. All these comparisons we can do if you know the bond order ok. Calculation of bond order in case of equal resonance in case of equal resonance. Like for example you see the first example Nc double bond O 4 minus and it is resonating that is Nc O minus double bond 4 ok. The bond order in this case will write number of sigma bond plus number of pi bond divided by number of sigma bond sigma plus pi by sigma ok. See in this molecule the resonance is possible from this oxygen to this oxygen right only in this part. So we will count the sigma bond and pi bond in this part where the resonance is possible. How many sigma bond we have here 2 sigma bond so 2 how many pi bond divided by 1. Sir in the formula there is a number of bonds by sigma bond. Yes. In the formula there is a number of bonds by sigma bond. No. There is a number of bonds by sigma bond. Yes. How many sigma bond we have here 1 plus 2 1 plus 1 2 sigma bond and 1 pi bond 2 plus 1 2. Sir how the number of sigma bonds of this number of pi bond was equal to the number of bonding and the bond minus number of pi bond. It is not that in that case we will get integral value. No, not integral value but then no, no but that is different molecule if you have N2 like that same atom present. We are talking about this molecule say the amount. So here we will think we have resonance will use this problem. We have another formula for this also. We can also write number of bonds in all R s, but this one is the easier one, the first one. The mission of number of bonds in all R s divided by the number of R s, there is an ending in the script. Like in this one you see, suppose you have to count the number, the bond order of this bond, bond order of this carbon-oxygen bond you have to find out, bond order of this carbon-oxygen you have to find out. So how many R s do we have? 1 plus 1, 2, right? So we have 2 R s and how many bonds? Two bonds here and one bond here. 2 plus 1, again it is 1. But for this formula you have to draw the resonating structure, the bond resonating structure. But here the advantage is what? With this only you can say 1 plus 2 sigma plus 1, number of sigma plus number of pi by number of s. Second formula is number of bonds in all R s. How many R s do we have? Two. And we have to count the bond order of any carbon-oxygen bond. Suppose this one we are taking, C 1, C 2. We have two bonds here and one bond here. 2 plus 1 by number of R s. Sir, is hydrogen bonding a sigma bond or a pi bond? Hydrogen bonding. It has a sigma bond characteristic. No, because resonance is possible here, no? So take only that part in which the resonance is possible. The first method will be count if there is hydrogen bond. You have resonance here, so number of sigma bond plus pi bond. Yes, we will take only that part in which the resonance is possible. Sir, but is the first case we consider the bond order? Why did we consider both oxygen? We are considering both oxygen only. How many of you understood this? See, we are taking this portion because resonance is possible here only. This edge we are not considering. So how many sigma bonds we have? 1 plus 1, 2 sigma bonds, this we let it be. So 2 sigma bonds, how many pi bonds? 1 pi bonds, so 2 plus 1 by 2. Sir, I didn't get the second one. The formula is exactly same. Either you can use this one or this one. Look at the same answer. But the disadvantage of this is what you have to draw the R s, the entire R s. Then you have to substitute here because number of R s you should know. But if you are using this formula, you can directly say with this one, what do you have? Number of sigma and pi by sigma. Now when you draw the R s, suppose one molecule has 5 R s, 6 R s.  So better use this formula, sigma and pi. Got it? Another example right down, CO3 2 minus. What is the bond order of carbon-oxygen bond? CO3 2 minus. CO3 2 minus. Okay, how many if you understood the second formula? That's that idea. See, number of bond in all R s. First of all you have to draw the resonating structure. We have two resonating structure. Like I said in the beginning, you have to only concentrate the part of the molecule in which the resonance is possible. Now here also you see, in this part the resonance is possible only here. This part is not in resonance. So we won't take this into the count. Okay, this is one thing. Now we have two R s. Formula is this. Number of bond in all R s. Now how many bonds you have here? Number of bonds will what? Suppose we have to find out the bond order. First of all you try to understand. Bond order between two atoms will be fine. It's not defined for the molecule. The molecule is the bond renewal. It's a bond order between the two atoms of a molecule. Like you can find out the bond order of this carbon. This carbon-oxygen bond, this carbon-oxygen bond. You can find out the bond order of carbon-carbon bond. Carbon-oxygen bond like this. So we are taking only one bond here. So I'm taking this C1 and this oxygen bond. This carbon-oxygen bond. This carbon-oxygen bond. Which will be same for this carbon-oxygen bond and this carbon-oxygen bond. Correct? So any one of this bond you can take. Because it is equal resonance it won't affect the answer. Right? So I'm taking this bond. How many bonds we have here? Two. How many bonds we have here? One. One. So summation of number of bonds in all R s. We have two R s. Two bond here. One bond here. Two plus one divided by number of R s. Two. Of so many. Sir, but in the first method we counted the bonds of both oxygens. Because we are here the formula is, that's what I said. The advantage of this formula is you don't have to draw the entire R s of this structure. You have this structure, let it be. How many, since we have resonance possible from here to here? So we'll count the sigma bond in this part and pi bond in this part. So we have two sigma bond and one pi bond. Two plus one. So one point five is the bond for both oxygens. No, both carbon-oxygen bond. See, it's the same thing. When you have this molecule, since it is the equal resonance, so hybrid is what? Hybrid is this. This molecule wants to give this bond R s to. This wants to give one. Half will be given by this. Half will be given by this. So average is what? Two plus one by two. Because it is equal resonance, this and this contributes equally. AB contributed equal to AB contributed. So you'll get the average of that, that is it. So in case of equal resonance, you can find out the average. It is nothing but the average. If you look at the formula, it is nothing but the average. We have to find out the bond. So this is the average value, this is the average value. That's why we have number of R s. Bond divided by R s. It's average only. Understood this. Correct? Yes. Okay. Now what is the bond order here? Carbon-oxygen bond. Which formula we should use? This one or this one? First one. First one will have number of sigma bond. You see, first of all, here is the resonance possible. This part also and this part also. Okay, only this. Resonance possible, this part and this part. How many sigma bonds we have? One, two and three sigma bonds. Three sigma bonds plus one pi bond. Four pi z. With this also, you can do. You'll get three resonating structures. First, you'll get this, comes over here. C o minus double bond o, o minus. And another one from this is what? When this comes here, this goes here, right? C o minus double bond o, o minus. To use the second formula, what you have to do, you have to take any one of the carbon-oxygen bonds. This one. Okay, so total bond is what? One plus one plus one. Four. One plus one plus two. Four divided by R s is what? Three, four by R s. So any one formula. I would suggest this one, I'll give you one. Okay, now this one you tell me. For this one, third one. Resonance is possible in this molecule, entire molecule, right? So it is what? We have sigma bond is three. One pi bond by three. Four pi three. What about this one? This part is not in resonance. So it is three by two. Clear? Okay, so equal contributing structure you won't get. It's very easy and simple. You have to find out the average. Okay, so mostly you'll get unequal contributing structure.


The chain reaction process in the reactor creates tremendous heat, which scientists have learned how to control. It was really a patriotic thing to harness the atom. I was excited about nuclear engineering because I thought it would solve the world's energy crisis. When everything works, there really a terrific way of making energy. The problem is that everything doesn't work all the time. Japan's nuclear nightmare continues. A second hydrogen explosion at the Fukushima Daiichi Nuclear Complex destroyed the reactor's exterior. All three Daiichi reactors have nuclear fuel rods that have been exposed to some degree, so they're teetering on the edge of a meltdown. Fukushima kind of stirred everybody to the reality of what nuclear power could do. There is no source of energy in this world that doesn't have risk associated with it. Our job is to protect public health and safety and never have an accident that jeopardizes public health or safety.  It is toxically poisonous to humans for 250,000 years. I keep saying that number 250,000 years. It's ridiculous. It's mind-boggling. Groundwater down there is being threatened and potentially the river water is being threatened. The regulators have known that this design is incapable ofwithstanding an accident since it was built. A very famous nuclear attorney told me, he said, Arnie, in this business you're either for us or against us and you just crossed the line. Literally from that day forward I could never get work in the nuclear industry. It's a blacklist. Nuclear whistleblowers are not protected in this industry. When you're doing the right thing, you don't realize that a corporation is going to be so vicious and use all of its money and power to shut down the truth. We have a lot of explaining to do and we have to rebuild public confidence and trust. We're operating a nuclear power plant. How can you trust a company who has really not taken seriously, in my opinion, the fact that we have leaking nuclear waste going into the ground? Brattleboro to Montpelier, 126 miles in 11 days. In the dead of winter I felt, wow, this would be really precious footage that would show the commitment, that would show people's really deep concern about this issue, so I decided to film. I thought, originally, well, I would film this and then maybe months or years later I would actually make the real film, but little did I know that events had other plans for me because literally halfway through the walk of the activist to Montpelier was when Entergy announced, this was in January of 2010, that there was a massive leak of radioactive tritium into the groundwater below the plant and that announcement set off a political firestorm that then began lots of attention, lots of hearings and ultimately a vote in the Vermont Senate and so I was basically filming nonstop from that point forward. Robbie, let's bring in Maggie Gunderson and Arnie Gunderson here and could you tell us when you came to meet them in the course of this because the tritium leak leaps out at me. First of all, I wouldn't call it a tritium leak because it had all sorts of other nasty toxic, which is a group of radioactive chemicals, cesium, strontium, cobalt. The NRC would prefer to call it that, but it's much worse than that. But I didn't know Robbie and Maggie and I were testifying in the state legislature and there's this guy with this camera and over the years we've got to know him pretty darn well. That's true. I was particularly impressed by seeing Arnie and Maggie testifying at the state house. That's where I first met them when I was filming there in hearings and I was impressed with their courage to speak truth to power for decades and really facing enormous pressure from the nuclear industry to silence them. I knew immediately when I met them that they would play a major role in my film. Speaking of roles, Arnie and Maggie, could you tell us what role you played in the closing of Vermont Yankee? We're still playing a role today because Vermont Yankee makes this film so pertinent today. We did a lot of testimony. Fairwinds Associates, our company and Fairwinds Energy Education leading up to what happened at Vermont Yankee in its shutdown. But now, Energy is trying to sell Vermont Yankee to North Star for decommissioning and that company has never done any decommissioning work before. It's not prepared to do it and we don't believe it's prepared appropriately. Arnie's done tremendous amount of work on decommissioning nationally and internationally and I'll let him speak to that issue but this power struggle is a documentary about what happened to date but it's still going on and Energy is trying to have Arnie removed as an expert witness as well as Ray Shattis as an expert witness, the two most experienced experts in the state of Vermont on Vermont Yankee and its issues. So Robbie, you've started off a real hornet snister. You know that it happened in Vermont? I think it makes me proud to be a Vermonter when I watch the movie and thank you for your comments about our courage. Having watched the film, it really does have Maggie and I as one of several protagonists and our long story of our battle with the Nuclear Regulatory Commission becomes part of Robbie's story. And in the film, I believe that it goes by the storyline. Robbie, you follow the story as it's happening. Yes, I'm actually chronicled the story over a five-year period through many twists and turns and I would say the underlying theme of the film is about grassroots citizen empowerment. Really, it was the citizens of Vermont rising up, getting involved, making their voices heard, taking action that made all the difference in what happened with the outcome of Vermont Yankee. And can you think of, well, there is one particular person in that grassroots movement who is spotlighted in your program. Could you talk about her for a few minutes? Well, there are many people, many activists that I do profile in the film, many groups involved. However, in a film, a film works best, a documentary film works best when you're able to make some personal profiles of particular activists. And one of the activists that I do profile in the film is Francis Crow of Northampton, Massachusetts who was 93 when I first started filming her and she's 98 now and still going strong. And so in this next clip that we're going to watch, she's featured in that along with many other activists as well. Just to give you a taste of the power of grassroots activism in this story. I'm Francis Crow. I'm 93 years old and I've been involved in trying to say no to the splitting of the atom and all of the consequences of it since 1945. When I heard about Fukushima, you know, I was devastated. I felt I got to get there and really put my body at Vermont Yankee because it's our potential Fukushima. Well, I've done everything that I know of to do and all I have left is my body and to put it in the way to say no. There are times when you feel something so strongly that just holding up a picket sign or just attending a rally or demonstration is not enough. You want to speak with your whole life, your whole body. And so we are placing ourselves in jeopardy, jeopardy of being arrested and possibly jailed in order to make the strongest statement that our consciences call upon us to make. Our struggle about the will of the people to decide what's best for them. It's a political struggle about the basic fabric of our country. It's just about democracy. So this is about whether people's voices are going to be heard. Many of you are working on is one of the great struggles of our time to create an energy future which protects not only our generation but a safe energy future for our kids and our grandchildren. That's what we're talking about. What we are also talking about is the need to transform our energy system away from nuclear power, away from fossil fuel into energy efficiency and into sustainable energy. In Vermont, if we shut down Vermont Yankee, if we move to energy efficiency, if we are aggressive about wind, solar, geothermal, biomass and other emerging sustainable technologies, this small state can lead America in a new energy direction and lead the world in that direction. Robbie, can you tell us what you learned from working with Arnie and Maggie Gundersen of Fairwinds Energy Education? Well, I just want to say that I've been thoroughly impressed by the really important and critical work that Arnie and Maggie are doing through Fairwinds. And in particular, they have been the leading advocates for nuclear safety and in particular, investigating the Fukushima nuclear disaster. And why this is relevant today is that Fukushima is an ongoing disaster and the contamination from Fukushima is not only going to affect people in Japan but people here in the United States. And in particular, what Arnie and I hope that you can talk about it now, Arnie, is what you're learning about the tiny radioactive particles from Fukushima and how, if they're going to create this dust by this rubberization process at Vermont Yankee, how that can actually be a total threat to people in Vermont and people in western Massachusetts. So I'd love to hear you talk about that. Yeah, thanks, Robbie. The thing that I learned, and I've been to Japan now for two months in the last couple years, and we came back with lots and lots of samples that were analyzed. And the important lesson that I learned in Japan that's directly applicable to Vermont Yankee is that the rubberization process, grinding up this concrete and releasing it into some fine dust, increases the exposure to people about a thousandfold because the little tiny particles are much more damaging when they get into your lungs or liver or inside your body than they are if they were captured in large blocks of concrete. So actually by rubberizing the concrete at Vermont Yankee, it will in fact make the exposure to people in Vernon and the people downstream on the river even more severe. Okay, and Maggie, can you talk about the film? Yes, and we hope you'll all go to the VTIF site and get tickets so you can join us at the film. And afterwards, David Goodman is the noted journalist and radio show host, is the moderator for the panel. And you'll get to hear more all about what's happened in this film about democracy and action in Vermont, Power Struggle, and why it's so pertinent today. Maggie and Arnie, could you go into a little detail about the process of the closing of Vermont Yankee? There was a time when there was a denial of underground pipes related to Vermont Yankee, and that was one of your discoveries in that. Well, the citizens, as Robbie mentioned, had a right to forbid Vermont Yankee to run after its 40th year. The state in 2009 convened a public oversight panel and I was the chair of that panel. One of the issues we asked Entregy was that they have underground pipes and they told us no. Well, I discovered a little later that after our report was written that that was not true, and the very next thing that happened is one of these underground pipes that Entregy denied having leaked and spewed caesium, strontium, everything else into the ground water. That led to the Senate under Peter Shumlin to vote against allowing Vermont Yankee to run beyond its 40th year, and that was a high point on the journey for Vermont Yankee shutdown.  And so, Arnie, they stopped operations at Vermont Yankee three years ago, in December 2014. So what's happening now with the decommissioning and why should we be concerned about this? We should be concerned because the activism needs to continue. This state needs to have a voice in its future of what's left on the site, and Arnie can explain the technical aspects of this rubberization that North Star wants to do, and it compromises Vermont's pristine environment. What they're proposing to do is to take the concrete from the nuclear reactor. Just think of coffee beans running through a grinder. To take the concrete, grind it up, and throw it out back on the site. So the radioactive concrete is going to be left on the Vermont Yankee site. If the sale goes through, the entity has said in previous legal hearings that they would never use this rubberization. But here's North Star seeking to overturn Entregy's commitment to the state and throw this radioactive rock back onto the Vermont Yankee site. And I don't think that's fair. And also, because the groundwater then will carry that cracked material. The radioactive isotopes are re-released and will carry that material to the Connecticut River and in the groundwater and towards the aquifer. That is tragic and fearsome. And Robbie, the film will be shown on October 29th, Saturday at 3.30pm at the Main Street Landing 60 Lake Street in Burlington, Vermont. It's in the film house of that building. And it's part of the Vermont International Film Festival. And people can find out more information at vtif.org. That's the website for the Vermont International Film Festival. And there will be a forum. And tickets are also available there. And they may need to buy tickets online ahead of time. So it's really go to vtif.org, buy your tickets and come see this wonderful film that is very current today. And we're going to have a post-screening panel with Arnie and Maggie Gunderson. Also former Vermont State Representative Tony Klein, Chris Williams of the Citizens Awareness Network and Clay Turnbull of the New England Coalition who will all be there to discuss what is happening now and why Vermonters should be concerned about what's going on at Vermont Yankee with the decommissioning. And also one of the reasons why I made the film is not only to document this, I think, historic citizen grassroots action activism having an effect, but also to be a warning about the future because the reality is that the high level nuclear waste is going to remain on the banks of the Connecticut River indefinitely. And this is true at every single nuclear power plant facility around the country and around the world. And Robbie, what are your hopes for how the film will be seen and used? Well, I hope that the film will be used as a catalyst for discussion, for education. In fact, I want to do a whole grassroots film tour. I want to travel around Vermont in particular and show the film. So if there are people out there who can help set up community screenings in Vermont or in New England and also around the country. I'm wanting to show this tour with the film around the country. Please contact me. You can contact me through the website powerstrugglemovie.com. That's a good place. Again, the website is powerstrugglemovie.com. Okay. Thank you very much, Robbie. And to wrap it up here in the studio with Maggie and Arnie Gundersen, who are in this ongoing struggle. Could you say a few last words about this? I would like to see Robbie's film go national. What we're seeing in Arnie's study, a tremendous amount, is that nuclear power companies, corporations, are using decommissioning as a moneymaker, but at the expense of the communities. And across the country, this is even more pertinent, that citizens in every state need to work to make sure their voice as the real stakeholders is heard. They need to see power struggle and see democracy in action. And my last thought would be that I view this as not a nuclear movie, but how citizen involvement and speaking truth to power on any issue is critical. Okay. Thank you very much, everyone. Thank you, Robbie Lebser. You and Burlington on October 29th. Thank you, Arnie and Maggie. And thank you viewers. Go to see this film, Power Struggle, the film. Thank you for hosting us, Mark. Thanks. Goodbye for now.


Hey everybody. How's it going? Good to see you all. How's the conference going? Good, good. I'll try to keep the, when you leave, I'll try not to have everybody doing this. We're going to talk about how testability drives observability today. So it would be a lot about open telemetry, a lot about tracing, and how to instrument distributed applications. A little bit about me. That's what I like to do. I like to be on the river fishing. I was very good. I do catch and release, so that fish lived. But a lot of fun. From Memphis, Tennessee, I have started a couple startups before. I started one in 1999, 1999. So I'm old as anything. And it was in the real estate industry, 2008. Real estate crisis hit. I started my second business, which was cross-browser testing, which by the time I sold it, had 4,500 customers around the world. So as competitors were soft slabs and browser stack. From there, I went to work at SmartBear, who acquired the company, which is a leader in testing software, including tools like SoapUI, etc. So Swagger, other tools, API related tools. And I think long time technology developer was the last semester at my local college to use punch cards. So once again, old as hell. So agenda. We're going to level set on observability, open telemetry and distributed tracing. Then we're going to go through and look at what the typical adoption life cycle as you start to instrument your app. What does that process look like? We're going to introduce a new concept called trace-based testing, which leverages the data and open telemetry trace to enable testing. And then we're going to show how using those traces and testing with them makes for better observability. So it helps the whole cycle. If you're basing your test on or your traces or your test with traces, you're going to find that when you're in a two o'clock in the morning, the system is breaking and you look at your observability tool, the quality of the data is going to be much better. And last, we'll wrap up and go through some questions. All right. So what's observability? Observability allows you to look at an application and tell what's going on without pulling out the code, without adding more log statements to it. So a couple of different definitions. I like this, the more observable a system, the more quickly and accurately you can navigate from an identified performance problem to its root cause. And this is key without adding additional testing or coding. So do you ever actually have a perfectly observable system? I doubt it. There's probably a lot of cost involved in that, et cetera. But you get close. And the goal of this talk is how can you have a system where you get closer to having an observable system? All right. Another definition was observability. Bill, you measure the internal states of a system that's a little more technical. Internal states by examining its outputs is considered observable if the state can be estimated only using information from the outputs, i.e., you don't have to go add code or add new logs. This system is providing the information you need to tell what's going on. Typically, when we start talking about the observability space, there's three signals or metrics that people look at. One is metrics, so CPU usage, et cetera, time series data. One is the oldest form of observability logs. We've done logs since I've been writing code. And lastly is traces, which is newer and is super powerful. And I'm really excited about it.  So we had lots of different languages, lots of different systems. When you did an API call to look at a iPhone in a live test, the process, it went through like 12 different processes to get there. And when something broke, we would have 12 different screens up, and we'd be looking at logs from all of them, which you could do in a development environment. There's no way you could do that in a production environment. There's just too much data streaming. So we implemented our own version of tracing. Now there's standards around tracing to enable it. And they would help us many a time. So what's the standard? Open telemetry. Who's heard of the Open Telemetry project? Okay, great. Tons of people. That's great. So it is a standards-based approach, and it covers the three metrics, traces, metrics and logs. It is vendor-neutral, and the vendors, the industry support is really outstanding for it. So this, I threw this slide together. It's kind of cheesy, but I went through some names, Google Cloud, AWS, Microsoft, Sumo Logic, Splunk, New Relic, Dynatrace. If you go through all these sites and you look at what they're doing, they're all supporting open telemetry tracing. So it's really expected in the industry now. I think it's a good thing for everybody. As a customer, it's better to implement with the open standard and that way if you want to change vendors, you can. From the vendor point of view, even for these large companies like a data dog or a light step, it's hard to support everything, to have tracing work on every version of MySQL, every message queuing type system, every language, every version of language. That's a lot of load for any company to take. With the open source approach, everybody's contributing to managing that load of work. So we're going to drill down and focus specifically on what distributed tracing is. So distributed tracing refers to methods of observing requests as they propagate through distributed systems. And to kind of spell that a little bit more, if I have five services and API is called and the request goes from one to another, to another, to another, to another. Distributed tracing provides you visibility for that one call across all five of those services. So here is a Jaeger dashboard. Who's used Jaeger before? Okay. And I'm going to flip to software for a minute. I'm going to hang, actually hang my shamrock around the pedestal since we're going live or I'll just spit it out. So it's always scary. So this is a transaction we're going to deal with a lot today. In the examples, it is a post to a Pokemon import. So we built a little microservice based on the Pokemon API. And this is Jaeger showing a trace from it. And in a trace, the different actions that are happening as we go through here, they're referred to as spans. And particular spans are going to have tags here, but we call them attributes. So these are details about for this specific action. What was it? Okay, it was a database and we got database response and that operation was create and the type of database. So we get this detailed information about it. We'll also see if we scroll down, there's a span ID on the right. So every span has a unique ID and every trace has a unique ID. Okay, and this, this covers that traces a group of spans with parent child relationship. And that's why you get the fan diagram. Each span has a unique identifier and the spans contain information about the operations. So that was just a level set on what is open telemetry, what is tracing, what's observability. Now we're going to talk a little bit about the lifecycle of adding instrumentation to your app. So you develop a product. Maybe this is, maybe you're, you don't have tracing or you don't have open telemetry implemented. So the first time you're adding some instrumentation. We goes by and you have a production problem. You have a bug.  Did it help you solve the bug? If it did, awesome. I've got a developer I'm working with and he uses the word awesome. And he puts a passion in it. So you can hear awesome throughout this presentation. So it's like, awesome. It worked. But what if it didn't? What if you looked at the trace and you're like, I still can't tell what's going on. I need to add logs. I need to change my telemetry. Oh no. We need to go back and add instrumentation. And this is a cycle that I don't think there's a way to totally stop it. But I think there's ways to do it better. So the instrument better on the front end. So this process of continually going through a bug didn't work. Add some stuff. A bug didn't work. It kind of reminds me of a movie I watched. Live, die, repeat. So it's kind of a brute attack force. We'll just keep trying day after day until we kill the creature that's trying to take over the world. So observability is hard. It's not a natural part of normal development cycle. I think over time it becomes one. But I think initially it's kind of a bolt on. And then the only way we know something's wrong is when we need it most. And we need accurate information. You might have a trace that might show value. But did you actually test the trace? Do you actually know the values that are in it are proper and working? So wouldn't it be nice to be able to test your telemetry before you deploy it to production? And this is what gets me excited. But wouldn't it be amazing if we could do more than just test your application telemetry? Who else implemented open telemetry tracing in a production environment? So trace, yeah, great. Trace test uses, which is a product that I'm founder of and will be using as examples. We use trace test to test ourselves. And it's hard to implement tracing, but it's cool when you can get other benefits out of that work. And we'll talk about that in a second. Okay. Immediately we'll talk about it. So I'm going to introduce the concept of trace-based testing and the value of it, what it is, what's interesting. Trace-based testing is a testing method that leverages your current tracing data, which you spend a lot of work to get into your system and makes it accessible to your tests. It then uses that information to assert the behavior of the system under tests. So I'll give you an example. Who's done some form of API testing in their career? Okay. So what are the parts of it? Usually you trigger an API call and you check the response. You assert against the response. So if I was naming that, I would have called that response-based testing. Trace-based testing is you trigger an API call or a GRPC call or whatever and you test against the response and the full trace of what happened. So it's a much deeper view of what happened in the system. It introduces some interesting concepts with a response-based testing system. I don't have to ask you, well, which thing do you want to test against? I have to ask you which attribute you want to check about against the HUB status code. That's the attribute, but I don't have to specify it's the response. It's always the response.  All right. So let's compare this to a traditional end-to-end test. So a traditional end-to-end test, you would have a system. So you've got three microservices, one talking to external service, they're talking to the database, and you need to instrument, your test runner needs to do calls out to these different systems to gather the information, to get visibility into what happened when you did an API call.  With the trace-based tests, your system's already instrumented. All these microservices are already sending information to your back-end, tracing back-end. All you do is put in place a test runner that can initiate a call and it needs to have access to the finished traces. So it orchestrates, it executes a call and it orchestrates with the tracing back-end to get the full trace and then it runs assertions against the response and the trace. All right, so what are some of the advantages of trace-based testing? And we'll show this with live software in just a second. You can test your telemetry before you change, before deploying changes to production. Who does testing of their code when they're at code? Okay. Who tests their telemetry? That's good. I'd like to talk to you about how you're doing that, so it'll be interesting. But how would I put it? What's everybody's track record on untested code working properly? It doesn't. It typically doesn't. More times than not, it doesn't. So testing's good. So believe it, and this is, I think, a really cool thing. As you create a feedback loop where you improve your test and the tests are based on your telemetry, by the nature of it, your telemetry has the stuff in it that's actually important because you only write tests on stuff that's important. So your telemetry gets better and as a refactor, you add tests case, your telemetry continually gets better and your tests get better. And I think we kind of addressed this on the previous slide. It is hard to add all this instrumentation in a traditional end-to-end test. With trace-based testing, you rely on the work you've already done. You've already instrumented for open telemetry tracing, so you get to leverage that work. And lastly, if I show you a trace, which I can't do right now with the screen dead, but if I were showing you a trace and I'm new to the organization, I'm a QA person you brought me in, I can look at this picture and go, all right, you're getting a Pokemon. It looks like you do two calls out to a database. I can figure out what's going on. I can look at a picture, people are good at looking at pictures or diagrams and understanding what's going on. So that's a great way to write tests. If I can do it graphically against a picture, it's much easier than, hey, we've got 20 microservices and there might be some old documentation somewhere that describes how they work together. Good luck. So this should say demo instead of show how tracing is, testing his traces with TDD impacts instrumentation. We are, as we go through this, we're going to end up using test-driven development. So I'll write my test first and then I will implement code changes and then we'll run the test. So we'll run the test with it failing first and then we'll change the code and we'll see that the test gets better. I'm going to start off the demo though with just a basic, this is how you build a trace-based test, a normal one. All right, the system we're going to show is a very important system. It's the Pokemon microservice app, otherwise known as the PMA. It's a little demo app that we have out in GitHub. It's got two microservices. One is API front-end and one is a worker process. It's got a RabbitMQ message queue right in the middle of it. So API comes in and message gets put on RabbitMQ and then the worker pulls it off. And after the worker gets the data, it accesses external service to PokemonAPI.co and does a call out to it to get a Pokemon and that writes it to a database. So a few pieces, not as complicated as most microservices but enough complexity to demonstrate the use case. We're going to be using trace tests. I'll try not to make this the commercial. Trace test is an open source project, MIT license. It gives you web UI to create and manage tests. It's got a command line. We will create tests both with the UI and with the command line. And it's got, with the command line, you can put these in CI CD processes and run them. All right, let's take a look. All right, let's start with a documentation on the endpoint we're going to look at so that we understand fully what's happening in the code. This is a flow diagram for the first microservice. We're going to be testing the Pokemon import, which is a post. There's a validation step that happens and then we put it on a message queue. The worker app pulls a message off the queue, does a call out to the poke API website. So that's external call. Once it's got the information, it saves the Pokemon in a database. So fairly straightforward flow. So I'm going to start by creating a test. So we've got different ways to trigger tests. We can do it via HTTP requests, GRPC, some other methods. I'm going to pick HTTP. I'm going to fill in some details that I have to type. So we're going to do the import Pokemon, but I'm in my local environment, so paste in that. And we're going to get the Pokemon with the ID of 52. We'll create the test and what the system did just now was it ran the post and you saw it came back super quick, came back in seven milliseconds. And that's because the API part of the process just gets the request, throws on the message queue and returns immediately with a 200. The real processing happens in the background. If we look at the trace, we can see that we did the import, the validation, put on message queue. We did an import of the Pokemon where we reached out to external service. And then once we got the data back, we insert in the database. So that's the flow we're going to be working with. Now I'm going to use trace based testing to ask some questions and build a test on this. I'm going to go to the top. I'm going to say when we do the post, I'm going to look at some of the attributes and I expect the response code to be 200. So I'm going to create a test spec for this to assert that this specific span and this selector is tuned to get this one span. If I were to change it, let's say I wanted to apply this test against all the HTTP spans, we now see that it selected this one and this one. So the selector lets you say what parts of the system should this be applied against. And then we said we want to check that the HTTP status equals 200. So we'll save that test and we can look at the test and see that we expected 200, we got 200. So that would be a black box test. I checked the incoming call. I said it should return 200. What's cool about trace based testing is you can go deeper than that. So I'm going to go down further in the system and I'm going to look at when we call the external service, what do we get back? All right, we see that we get back. I can't say this. How do you say me off? Is that I don't know my Pokemon as well as I need to know my Pokemon? But I'm going to create a test spec for it regardless. And I'm going to say the response body. And I'll just say it should contain me off. Save that as another test. Okay. And then lastly, I'm going to do a more generic test. I'm going to say and I'll just do this one from scratch. I'm going to say that I want all my database spans. And we should see if I did it right, we're going to see them selected. I think I did not do it right. Yeah, lowercase. All my database spans, we got three selected. And I'm going to do a timing based test. I'm going to expect that this length of time each of those takes should be less than 100 milliseconds. I'm going to save that. I don't know where my shamrock went. It failed me. It left me. Oh, I've got my shamrock here. That is an issue. So anyway, so we added three tests to this. And we can publish the tests. And at any point now, we can rerun the tests. And we'll get test results. And I could take this test and run it via the CLI. I could take this test and run it via build process. So here's our test. Does that make sense? I'm going to stop for a second before I move on to the kind of the next stage because next stage, we're going to change code. Everybody with me? Okay. We've got a production problem. You know, none of y'all have had production problems, but I always seem to have production problems. I don't know. I don't know why. And this is it. We've got a fellow Pokemon import that's happening. And it's causing issues. So I'm in operations, and I'm going to look at the span or the trace and try to figure out why. So I see that we're getting all the way down to where we're reaching out to the external system. But I don't see the database rights. So let's take a look at some of the attributes and figure out what's going on. All right. I see we're getting the Pokemon. So I know what the request was. I don't have much response data. What do I have? Oh, I got something saying there's an error. Anybody know what error? Looking through it. That's all I've got. So what's my next choice? I can go look at the code and try to figure out what's wrong. But in the course of doing that, I really want to prove the observability of the system. So the next time we have a problem like this, we can fix it. But first I got to figure out what's wrong. You know, I did notice that the response or the request, 999, I'm not sure how many Pokemon there are. So we'll go and look at the poke API site where we can test things. If we try to get a low number, we get, there it is. So we get a JSON object back. I'll try to get 999. And we get nothing. So we don't even get JSON back. So that's not nice. I would expect it maybe give me a JSON structure with an error or something nice to deal with. I'd never tested this boundary. So I didn't know what happened with this external service when we called it. So I'd like to do a couple things. I'd like to look at the code. And then I'd like to design a test to, I want to add some instrumentation to the code. And I want to have a test that's going to check that. I'm going to start off with a test. I'm going to specify what it is I want to be checking. So if you ever watch anybody with like cooking shows on TV, okay, I've pre-cooked this cake. So you don't have to watch me type. But I've started creating a test called bad Pokemon. And down here is our test. Currently it's just checking the hotel status code is equal to error, which we saw that was already there. I want to add a couple assertions. And the assertions I want to add are up here. So what are we going to do? In addition to checking the hotel status code is error, we're also going to check that the HGV status code returned to 500 so that we know there is a failure. And then we're also going to make sure the HGV response body contained not found, which is what that API returns when it doesn't find anything. And it's not, it is not JSON. So I'm going to save this test. And with test driven development, I'm going to go ahead and run the test. And I haven't changed the code. That stuff's not there. So it's going to fail. But we'll go ahead and see it fail. So we are running that test. It's collecting both the response and the trace. And then it's so starting against it. And we see that, yep, that set error for the hotel status code, but the other two tests failed because they're not in the code yet. So we're going to go add those to the code. Both HGV status code and the response body. So let's go into Visual Studio and open this section of code up and uncomment it. So what's this code do? First off, I can see now what the problem was. Without this code, we were trying to get the Pokemon and we were trying to convert it to JSON. We didn't have JSON when it was a high number. So the code would fail at that point. So we're going to add in, if the response coming back, there's like a sensor that knows what I'm near the screen. If the response coming back was not okay, we're going to put some more information into our open telemetry trace. We're going to put the response status and the response text. And we picked the fields that we're going to put them in. With the response status, there is an open telemetry has a concept called semantic attributes, which are documented on the open telemetry site. So there are standard strings to use to identify certain attributes. So we're using the standard string for HGV status code. There's not one for the response body. So we've added one into the system that HGV response body is what we chose. So we've added our code. I'm going to save it. And now we're going to restart that microservice. So this is a worker process. We've restarted it. And now we're going to take that same test we ran a second ago and see if it works. Okay, it sort of worked. It worked mostly. It sees that the response body contained not found. You know, if I recheck the Pokemon service, I will see that it actually returns a 404. It doesn't return a 500. So I made a mistake. So I can go to fix my code real quick or fix my test. We'll run it again with the test paths. So what did we do there? We had air. We didn't have good observability for the system. We used test driven development to say this is what this test should work when we finish development. We changed our code. And then we tested it. And we now have a trace that's going to give us detail that would help next time we have a problem in production. So I wanted to kind of do a little wrap up. We said some of the benefits are it helps you test helps you test your telemetry before deploying your changes to production, which we just saw they did. It creates a feedback loop to help you make better telemetry in your system. If we base our test on it, we're going to have the valuable information in our trace. A like trace based testing for it enables you to make deep assertions without having a lot of connection information to the backend databases, different logins, different security keys, etc. You just need the trace. And then it's really easy to write tests. It's easy to understand the flow in the relationships. And due to that, I think you can write more tests and you don't have to have quite as technical people writing the tests. So we are open source project. We live and die by feedback and input. So we would love stars, but more than stars, I'd like feedback. So I'd love to see y'all download the product, try it, tell us, hey, it'd be useful if it did X. So we've been in production how long? We released our first version in June. It was pretty usable. July, by July, we were testing ourselves with it. We're now adding variables and chaining to tests. So it's going to get even more useful and that'll be out before cube gone. Yes. Any question? Very good. Any questions? Yep. So you can export the results. We have J unit as a standard. So you can specify, hey, when you finish export J unit, we also expose that via the UI. This one doesn't have any tests on it. So it's not popping up, but it would give you a J unit result. And that's one thing we're kind of interested in is what format should we output everything in? I think there's probably multiple answers to that. Any other questions? I think so. So I think there's a case for setting up tests and running them at scheduled times as a monitor. And if there's an asynchronous process in the middle of that, you're really not testing much of anything. Any other questions? I can't, I don't have my glasses on. I can't read that time. One minute. Okay. I'd like to thank y'all. I'd love for you to go out to trace tests, try it and give us feedback. Thanks, guys. Thank you.


It is house tour time. I'm gonna be showing you all of the different areas of our beautiful home. All grown-up teens start Tia Mowry, twin sister to Tamara Mowry, currently lives a comfortable family life with her husband and children in Studio City, California. She showed off her home back in 2018 and she's lived in this modern farmhouse build since 2015. In 2019, Tia also sold a gorgeous home shown in Agora Hill since 1996 and prior to Studio City she and her husband lived in a Mediterranean-style mansion in the Valley Village neighborhood. Today we'll check out a few of her homes we even found the listings. In these videos we don't reveal any addresses and even though I've done a house tour of my own place, please do not show up at any private residences because it's not safe for anyone. Tia Mowry hard-dressed as an actress who is first known for her starring role as Tia Landry in the sitcom Sister Sister alongside her identical twin Tamara Mowry which aired back in the 90s. The pair also starred in the Disney Channel movie Twitches and its sequel, later getting some more movie and TV roles. They were also featured in the reality show Tia and Tamara from 2011 to 2013. While the twins are still super close during the pandemic last year, they weren't able to see each other for over six months. Tamara lives in Napa Valley with her family while Tia is in Studio City so they had to make do with video chats and virtual happy hours for quite some time. Tia spent most of her quarantine if not all in her current Studio City home with her husband Corey Hardrick and their two kids, Cree and Cairo. They moved into this home in 2015 when it was newly built and they have since stayed put. The home is bright, sunny, and decorated with every detail in mind which you'll see shortly. Currently it's said that Tia has a net worth of about four million dollars or more and she's been investing some of her bank into a gorgeous real estate since way back in 1996. Hey guys, it's Kara the Vampire Sair and today we're bringing you another house tour here on Famous Entertainment. Be sure to hit that subscribe button or ring that bell. We post a new video daily. Today we're looking at one half of the Mori twins Tia Mori and where she's settled down with her family including three of her properties past and present. If you want to see one on her sister Tamara don't hesitate to drop a comment below. On this channel we talk about celebrity houses but have you ever wondered about things like Kim K's crazy engagement rings from soon to be ex Kanye? We recently started a new channel Famous Fashion where myself and some other hosts are reporting on all things celebrity fashion and purchases. Join us we'll link you to one of our latest videos and be sure to subscribe. Most recently in what seems to be a Valentine's Day weekend gift to herself, Summer has yet another big car to add to her driveway. While it may seem more practical her new designer SUV was far from cheap. As usual don't forget to follow me on Instagram to chat and now let's get into this video. In 2019 it was reported that Tia was letting go of her former home in a posh enclave in Agoura Hills California, a far western suburb of Los Angeles. The neighborhood is located between the Simi Hills and the Santa Monica Mountains bordering Ventura County. While Tia was selling the place for $1.5 million she allegedly bought the home way back in 1996 when she was still a teenager for just over 650k. Online resources claim that Tia's mom had been occupying the home for at least the last few years so I guess she decided to move. The home was somewhat built in a transitional traditional style but wasn't very specific in its architecture. While inside it covered nearly 4,200 square feet with five beds and five baths. The home was decorated beautifully and clearly looks like it's been updated for a spot bought back in the late 90s. Walking in there's a large open living area that flows common spaces together with high ceilings and huge bright windows. The formal living room here boasted a marble fireplace and opulent furniture while the dining room that joined it had a double high wall of glass. The eating kitchen could benefit from a modern day renovation but it was still roomy and upscale with cherry wood cabinets, large island and granite counters. This room opens to a casual carpeted family room with fireplace and built an entertainment wall. All four of the guest bedrooms are on suite and spacious so good luck deciding which one to call yours. The master suite here boasts a marble fireplace, huge closet and bathroom with jetted guarded tub and carpeting which if it were me I would probably can. While the master is nice another sprawling bedroom offers multiple windows and views straight to the mountains. While the backyard doesn't offer a pool the rolling lawn has plenty of space just asking for one to be built. Outside there's a sports court built in barbecue area, children's playground and a vine-cheated patio to eat or lounge at. Not to mention the property allows for 180 degree mountain and canyon views. Tia and her husband Corey married since 2008 moved from Agora Hills to a Mediterranean style mansion before moving to their current home in Studio City. Let's check it out. Located in Valley Village, a neighborhood in the San Fernando Valley of LA and close to Toluca Lake this home most recently sold for just over 1.5 million dollars and was built back in 2006. Lissy materials do claim the residence was a celebrity-owned home and was also advertised as turnkey in one of the best pockets of the area. Inside Tia's former house span 3992 square feet with five beds and four baths and from the exterior it looked like a perfect suburban villa. The home opens right up to high ceilings and a formal living room to the left with hardwood flooring and a fireplace and opposite the space there's a wrought iron staircase leading upstairs. Also on the main level the open spaces continue with the formal dining room and a more casual living room with second fireplace, TV and doors opening to the patio. This unfilled kitchen had a breakfast nook with booth as well as the stainless steel appliances and the entire home had updated finishes throughout. Upstairs there was an office and one guest room was converted into a children's playroom while the large master suite had a fireplace, entertainment unit and private balcony overlooking the pool. The yard here wasn't very big but it did have a covered patio area, swimming pool and spa as well as high hedges for a complete privacy. These days Tia and her family live in the Studio City neighborhood of Los Angeles where they bought a newly built modern farmhouse back in 2015 for 2.6 million dollars and they've been living there ever since. While the home may look like your average upscale family home, Tia went all out with designing it and creating the perfect space. Satras has said she loves her home for its open floor plan which is especially noticeable in the kitchen where she can prepare meals while hanging out with her family at the same time even if they're watching TV in the attached family room. Tia's kitchen also offered inspiration for the rest of her home design since it's their center of gravity. It's decked out with Calcutta marble and natural elements like wooden chairs and bowls while her pantry is super super organized. Tia's house spans nearly 5,000 square feet of space with 5 beds and 6 fasts. Walking in, you first see the formal living room fitted with a sleek black couch and black fireplace against more neutral furnishings. The couple added a white coffee table and rug to contrast the black. She also wanted the design to flow from room to room and follow a theme. In the dining room, there's a long dark wooden table with mixed chairs and a bench for a casual vibe as well as a vintage Turkish rug. Tia also has a cozy screening room with leather recliners and a huge projection screen. She says that the family uses it for movie nights of course but it also doubles as a quiet spot for sheer her husband to rehearse lines in. There's also a white and bright family room that Tia says is one of her fave rooms in the home. There's a built-in fireplace with TV overhead and sprawling white sectional couch covering almost the whole room. Apparently, that couch has Tia's fave piece of furniture in the whole place and let me tell you it looks super comfy. Of course, her son Kree has his own custom bedroom with space for all his toys and activities and elsewhere, Tia's daughter Cairo had a nursery at the time. Though I think that about wraps it up for a Tiamari house tour. I can tell that the actress really loves her Studio City family home and I can see why. So much thought was put into every detail and they've really made it their own.  After checking out this spot as well as two of her former properties in Valley Village in Agora Hills, what did you guys think? Did you have a favorite? For me, it's hard to choose between her current Studio City spa and the Villa style home they lived in just prior. Honestly, I love the quiet little pool area Tia's former home and just how private it was. Let me know what you guys thought down in the comments. Be sure to subscribe to my personal channel if you want to get to know me better. I love reading your comments on there and getting to chat. Well, thank you one of my latest videos. Oh, this is a childhood gem. Oh my gosh. I forgot about these pictures. Not looking at that. There's a creepy X there. Thanks for tuning in. Don't forget to follow me on Instagram and tell me whose house throughs you guys want to see next. I'll see you all in the next video. Bye.


A fundamental phonological division of English varieties depends upon a difference in the phonotactic distribution of the consonant R. In accents with a high degree of roticity, the R is often overtly realized in a wide variety of phonetic contexts, including post-vocalic environments such as farm or far. In the accents that exhibit a low degree of roticity, R is not used in most post-vocalic environments, thus we get both farm and far without a post-vocalic R. Mostly the varieties of English are classified as non-rotic for example RP or rotic for example standard American English. However even in the so-called non-rotic varieties there are contexts in connected speech where the R can optionally be inserted. Such effects are referred to as liaison. So it seems reasonable to define degrees of roticity rather than using a binary distinction of rotic versus non-rotic.


Welcome to Hyperledger Kochi, Kochi Org Book Meetup. So Kochi Org Book is a community initiative that aims to bring in the concept of decentralized identity to reality. It is based on Hyperledger Indie which focuses on self-sovereign identity management. Today's agenda is a quick overview of Kochi Org Book project followed by demos on Popman and email verification service. This meeting will be recorded and uploaded to Hyperledger YouTube. So I now invite Kochi Org Book team to deliver the session. Thank you, Nikhil. Hello, good evening everyone. A warm welcome to our session. Let me introduce myself. My name is Eric Joy. I am part of the Wipro Cybersecurity and Risk Services team. I am a community member of the Kochi Org Book initiative as well. I have Arun Suresh and Sumod Rajan Josh with me today. Can you guys introduce yourself please? Yeah, thank you Eric. Hello everyone, good evening. My name is Arun. I'm a part of Wipro Cybersecurity and Risk Services team. And I'm also a community member of Kochi Org Book initiative. Good evening everyone. My name is Sumod Josh. I'm part of the Wipro Cybersecurity and Risk Services team. And I'm also a active contributor to the Kochi Org Book initiative. Thank you Sumod. Thank you Arun. The agenda for today's session is the overview on Kochi Org Book initiative, then the demo on KOB man utility, demo on email verification service, and later on Q&A sessions. The objective of this session is to introduce you all to the Kochi Org Book initiative. We are looking for community members who are interested to contribute. This is a pure community initiative and the first of its kind from Wipro. Let me start with an overview on Kochi Org Book initiative. All of us have digital identities and we use them to build new relationships, in case existing relationships. Today many sites permit us to log in using Gmail ID or Facebook ID, which is a convenient way for us as we do not need to remember passwords for all our relationships. Well, it has provided convenience for us to build new relationships and avail new service offering. I would like all of you to think through on these lines and let us know. Is it safe to use it? One second. Are we exposing too much information from our end to the likes of Google and Facebook? What all do they know about me? Is it limited to what I have just shared with them or anything more? Do we really own our digital identity? These digital identity management systems are centralized in nature. A single entity has full control on managing our identity information. They decide what information to share and how to share it. This takes the control from our hands to manage our identity details. As a solution to these issues, we are focusing on decentralized identity management leveraging Hyperledger Indie and Ares, which enable individuals to manage their identity information using constant management. We are not discussing about Hyperledger Indie and Ares in this session as it can be done in a separate session. The Orbook is a verifier organization network for the city of Cochin. This is a modeling from the government of British Columbia's The Orbook Initiative. This initiative is the production and the Canadian government is extending these two other provinces of Canada. The objective of this initiative was to enable business entities to avail permits or licenses from the government in a transparent and efficient manner. In Cochin, these are many associations and in the current form it may not be feasible from an ordinary citizen to confirm it. Confirm if the associations are valid or not. We often trust the documents they present. As you know, today's documents are being forged and it is quite easy to miscut anyone using the forged documents. With Cochin Orbook Initiative, each association will now be able to present digitally credentials which has been issued to them from a trusted entity and can be verified by any citizen of Cochin using their mobile water app. Cochin Orbook is a technology demonstrator to launch and de-centralize the identity based utility complaint with the TOIP standards to enable trusted digital verification service for various associations within the city of Cochin. We can schedule a separate session on TOIP foundation later on. Today to avail a service, we need to share a lot of documents to provide our identity for eligibility, etc. Often the whole process takes time and a lot of our effort to follow through till we secure the approval. This utility aims to cut down the red tape and improve the overall efficiency of the current process. Internet-scale digital trust with close to one million digital credentials on the network. Next, let us discuss on EU cases of Cochin Orbook. Medical practitioner getting an expert opinion is not an easy thing today. QoB would permit a citizen to identify a doctor with specific expertise and secure their consultation service without compromising on their privacy. Laws. Similar approach to be leveraged in this case as well. Driving license. Ability for an individual to prove his eligibility to attend a driver's license test. Issuing mark sheets. Enable universities to verify the credentials shared by the student to confirm the eligibility for admission to a course offered by the university. Next, we will discuss about the generic use cases for QoB, which will exist in all of the use cases which we just discussed. Search association organization. The initial actor can be credential requester. A credential requester enters search criteria and is written a list of association matches based on the criteria. Another use case is verify credentials. The initial actor can be claim requester. The claim requester selects the association and the type of the claim and request verification. QoB sends the request to the sovereign blockchain node which verifies the request and returns the verification information to QoB. QoB then presents the verified claims to the claim requester. The next use case can be revoke credentials. The initial actor can be associations here, in this case QoB registry. At any point the claim issuer may revoke a previously issued claim and sends a request to the update the ledger in order to revoke a specific claim. The next use case is issue credentials. Here also the actor can be association. At a predetermined time an association's QoB registry will forward new public data as a CSV extract to a drop location where it is picked by QoB bootstrap tool and convert it to JSON format. QoB agent retrieves the files and loads new association information into Kochi Orbooks searchable database and add verify credentials into the association's wallet. If you take a look at the picture here on the right you'll be able to see the generic use cases, the pictorial representation of generic use cases that I just explained earlier. The benefits are QoB is a decentralized in nature, process building trust among participants, cuts red tape and improve efficiency, display public data in verifiable and authentic manner, empowers individual or entity to manage its identity. If you take a look on the next slide, you'll be able to see the Kochi Orbook subprojects, Kochi Orbook, the Orbook for the city of Cochin. QoB connect wallet application for QoB users. QoB registry, the base code to set up a QoB registry. QoB deflow, QoB decentralized workflow for QoB. QoB man, QoB man CLI for managing the QoB projects. QoB worn, worn network for the city of Cochi on top of sovereign hyper leisure entity. The below is listed the links to each of this project. You'll be able to redirect to the specific projects via the link. Next is the community groups. We have actually divided the community side into four different categories. One for developers, the next one for DevOps engineers. The third one is for solution designing and domain. And fourth is the community. If you take a look on the slide, you'll be able to see the activities of each domain and the requirement, the skill set that is required for each of the domain. For instance, for developers, if they are working on QoB connect project, the skill set that is required here is Android app or Angular skill set. For QoB deflow and worn, Python, Django, all these kinds of skill set are required. Likewise, for DevOps solution designing for community, the skill set that has been required is listed there. If you take a look on the activities for the developers, code refactoring, enhancements, issue fixing, for DevOps engineers, code integration, CACD GitHub, for solution designing, identify potential business use cases and documenting them. For community contribution, all of these activities are involved. We are actually welcoming the contributors here. Current status of QoB project is we have created the repose for the QoB project in the GitHub. Features has been captured and put in as the product backlog, sir. Features tracks as issues under specific project repose. Identified few community members, teams being onboarded to work on each specific project for QoB initiative. Initiated work on some feature leveraging the community members. How to contribute to QoB? Participation in events hosted by Hyperledger QoC community for QoB. Participation in local hackathons. Pick up issues and start submitting pull requests against various QoB code repositories. Participate in use case modeling workshop for QoB. With this, we conclude our first part of the session. We will now proceed with the demo sessions. Then take up on the questions. I hope this is fine with everyone. Let me call upon Arun to walk through the demo on QoB man utility. Over to Arun. Hello, everyone. So we'll be doing a demo on the QoB man CLI, which is a command man utility for the virtue of the initiative. And then we have also built a verification service called QoB email verification service. We are planning to play the video recorded videos of these two. So some more will be the one who's playing it. So how the QoB man utility. Okay. So what QoB man utility does is that it's an easy way of installing all that any elements that we just show. Since these elements are having a certain number of steps that you should really follow to bring it up. And it can be a little bit tough for someone with no previous experience. So QoB man utility deals that with just a simple set of installation and installation. You can just type in a command and then install all those and manage for yourself. That's easy. So more hello, can you hear me? So this is a way of confirming that the QoB code installed. Now QoB man's features gives out the UTPs version 003. The next command is the QoB list command which lists out all the elements that the QoB man UTP can install. And they are also listed on all the versions available for those elements. Now we have listed down QoB man as well as Aries Dev.  So that a developer can work on issues or new features that it is. Aries Dev is a Cloud Azure Python project. Now the next command will be to install. Hello, am I horrible now? Yeah, I'm sorry about that. So please continue the video. Okay, so the next command is to install these environments. So to install, we just have to type in the install command which is QoB install. So what can you please play the video? Thank you. QoB install minus cnv. Then mention the environment that you want to install QoB man. Then the version that you want to install minus v and 003, which is the latest version available. Now, once we run that, we'll be prompted to give the user's namespace, which is your GitHub ID so that QoB man can create a fork of QoB from Hyperledger QoC into your name, under your namespace. And the dev environment will be created from your own forked version of QoB man. So once you export it and we run the command again. So right now, it isn't promptive for that. But it says installing hub, which is an extension of GitHub. Now, hub is used to fork the QoB man that was in tree into your own namespace. And that could take a while depending on your network speed. So please do pen us. If this video is audible for everyone. Please read. Are we having an issue with the... Yeah, let me just share it from my end. Okay, thank you. So now that we are done with the QoB man CLI, I hope you are able to see my screen. Okay, then. I don't know how much clear the audio was for you guys. Can you just please confirm like how much you are able to listen to? Was it clear enough or... Okay, so if there are any questions from your end. Can I ask one question, please? Yeah, yeah, sure. Can you please state your name, please? Hi, my name is Nidupam. Okay. Hi, Nidupam. Can you state your question? Yeah, what is QoB CLI? Okay, it's a bashell scripts based project that we created for the purpose of setting up the new projects for... It will be... If we created... If we set up a new project, we'll be able to identify all the steps, right? So once we identify these steps, we will be categorizing it to one of the environment and once we identify it as an environment, we can add it to the QoB project so that from next time onwards, if some developer is trying to set up the same environment, right? He will be able to do that just in a jiffy, like by using a command like a QoB minus ENB install that project's name. So it's for the developers mainly for setting up the project. Yeah, you're welcome. So, folks, we really apologize. We don't know why exactly the audio was not really clear. We will try to make it up for the next time. So any more questions? Yeah, it was a good session, Eric. So can you just explain what the email service actually does in a short one minute so that because the audio was not... We couldn't hear what you are doing in that video. Yeah, of course. Like the QoB email verification service, it's actually an Ares-based project. It has an Ares agent beneath it. So what we just did was like, by using the QR code, we established a connection. If you are aware of what an Ares agent does is, it's actually for making the DAD-based exchanges, the Ares agent is required. So in this project, the Ares agent, we established a connection with an Ares agent. With that connection, we are not really doing anything here. For using that established connection, using the credential, there was some other project that was using the same Ares agent. We might have been able to verify the credential that we created. In this project, we just simply created it. Okay, so I don't know how much the audience is available about the Ares part. Okay, and Nikhil, just to clarify, what we're trying to do here is we're trying to actually create decentralized services, which can be leveraged to actually issue credentials for certain credential proofs for certain credentials. Right now, if you look at it in any online registration form, you'll have to submit your phone number, you'll have to submit your email IDs, you'll have to submit your address details, etc. Now, what we're trying to do is we're trying to actually build, separate out each of these credentials, having a separate decentralized service, leveraging the Ares cloud agent capabilities to follow the system to actually verify your address details or your phone number details or an email, and issue a proof stating that you are the trusted owner of this particular phone number or the email number, or the address that you've shared is a valid address. Now, this could be a credential which you can actually later on leverage to do for establishing, let's say, for example, if you have an entity which is already on-border as part of any DID-based network, and they have their registration process being made as an online service available on the DID network, then definitely this would give you an opportunity for you to actually share these credentials proof and help you to establish your identity with or actually sharing your information in a plain text format. So as part of that initiative, that's cool, right? We have actually decided to break down some of the basic credential information into a set of series of independent decentralized services for offering credential proof. So one of them is actually the email verification service at which we just showed. Okay, I think that made the point clear about the email verification service. So are there any other queries regarding the demo or in general about Kochi or Book Projects? So if anyone have anything, any queries you can ask now? Just to reiterate, your book is more of a technology demonstrated to showcase the capability of how DID can actually enable associations to have their own rhythm and vote themselves as a verifiable organization. And the citizens in a jurisdiction or like a city like Kochi will be able to avail various services using their credential proofs that have been issued to them and avail services in a secure manner whereby there is no compromise to their privacy. Today what happens is any online digital service that you have to avail, you have to share them a lot of your personal information. And by default, many of them ask you a lot of information which may not be really required for you to really avail those services. But the problem there is you end up sharing a lot of your personal information in a plain text format and you have absolutely no idea how this data is going to be stored in the database of the service provider. What kind of security mechanism does a person employ to ensure that your data is not being passed on to someone else? And I'm sure all of you on this call are very much aware of the mess-up that Facebook had done with a lot of personal information being shared with third party vendors which had assaulted a lot of people losing their privacy to external entities. So the objective of the Q&A is going to help establish and showcase the beneficial benefits that you can actually avail by setting up a database network and enabling and empowering the citizens to actually manage identity which in today's digitization world it is of utmost importance. We have government bodies across the world formulating various policies and legal procedures to ensure that the privacy of citizens are maintained and it is not being compromised for availing any kind of digital services. Okay, so if any of the participants have any questions they can ask now. We already have our code available in GitHub. It is hyperlegiccucci.com So it's available because you can take a look at it. In fact, under the hyperlegiccucci name space in GitHub we have quite a number of projects that we have actually included which is part of the overall scope of K.O.B. You guys can take a look at it. Right now we are focusing on K.O.B. Man project and then the other part that we are focusing is on creation of these decentralized services. Okay, so if anyone want to join the hyperlegiccucci.com or K.O.B. project, it's a community initiative. So anyone can participate in the community initiative and be part of the K.O.B. project. I think we have covered almost everything regarding the demo. So, Sumod, if it's fine then can we conclude the session? Yeah, I mean if anyone has any questions that you would like to drop us a mail you can reach out to Nikali, he has got our email IDs. So feel free to drop us a mail if you have any questions. I'm sure you may not extremely apologize for the audio quality that we have today. Okay, so one question is if there is any process for joining the Orgboop project. Do send us a mail, it will help you get onboarded. So can you share your email? Yeah, I'll put it in the chat window. Yeah, sure. Okay, then that was a wonderful session on Kochi Orgboop project. So it's an exciting community initiative based on Hyperlegia Indi and we saw the demo on K.O.B. Man and email verification service. So I hope we can collaborate further on when you have some other, I mean exceeded or gone through another phase in your development phase then we can have another demo on some other initiative that you have done on Kochi Orgboop project. So we really want to have more sessions with you but I think unfortunately, I mean just a suggestion, can we plan something on the weekend? I mean I know it might be of inconvenience to people but at least I think we can definitely do away with these sort of network related issues which is impacting the quality. Yeah, we can all do that. Definitely we can include it in the weekends if it is okay for the presenters also. Yeah, I think that should help us because usually what we have seen is towards the evening, at times we encounter network issues and it disrupts the audio quality as well. So once again, let me extend our apology for that. Yeah, that's no issues for now. We have seen the demo and it was a nice demo and we had a wonderful session and we had the clarification also. So that's all for this session. So I will end it here and you can all, I think we will gather again in one another day and we will share the progress of Kochi Orgboop. And Nikhil, thanks once again for hosting this session for us so that we could get initiated at least on getting people to know what Kochi Orgboop is all about. Definitely we'll have other sessions as well and I'm sure that will help you guys to get up to speed on what we intend to do where we have progressed so far and how you will be able to contribute back to this community initiative. All right. Thank you everyone.


They made you feel worse about yourself or they made your life less peaceful Then maybe you actually haven't lost anything at all. Maybe that she gained from not having them there Because here's the deal.  What if I had someone amazing in my life that I've lost?  They shake up the foundation of everything and then they leave leaving you To rebuild the foundation stronger to work with yourself to make yourself better in order to deserve somebody like that in the future Because here's the deal if somebody was meant to be in your life right now. They would be So stop focusing on someone who season has already passed when there might be somebody out there Who season is coming up and is meant to be in your life because if you're focusing on someone who's gone You might miss out on the person who's actually supposed to be in your life


I don't want that license get off the motorcycle and follow me in the vehicle take off your helmet here we go look at our foot pedal welded repair in the light of day wow look at that whew that is absolutely solid now I think that's probably even more solid than it was before it broke wow what a result ready for the next drop yeah thank you thank you bye bye we'll turn here there we go we're on our way good morning world welcome back to the channel it's day number 363 on our circle navigation around the globe by motorcycle and we are here in the town of Yinotega in Nicaragua and we're surrounded by beautiful forested mountains and we were super lucky because last night we managed to get our broken foot pedal fix by an amazing guy called Tito with the help of another amazing guy called Len a crazy evening we spent the whole time just hanging out with everybody whilst everything was kind of getting sorted and it was always like are we going to be able to get this done are we not going to be able to get this done but in the end Tito got it done we got our foot pedal welded we got it back on the bike and now this morning we're ready to go yes the main difficulty was actually that it was a public holiday so all the shops were closed and it was like quite hard for Tito to figure out like where can I get the aluminium from and who can weld it so he called up a bunch of people at like 10 o'clock in the evening everything got fixed love you guys so it does mean that we are ready to make our way and today we got a super exciting day because we are heading to the border of Honduras country number 18 18 country number 18 oh my god yeah it's about three three and a half hours over to the border and then from there the capital of Honduras called Tegucca Calpa is about another two two and a half hours so depending on how we get on today with crossing the border we might be able to reach the capital yes we have a big mission today to cross the border into Honduras and to go it's already 9 o'clock so better hit the road let's go some traffic jams there's like a whole herd of cows running across the road hey guys where are you going oh my lord oh hello cutie they are super cute hello I love them so very interesting here where we are right now because the road is actually all bricks which is absolutely crazy when you think about that they had to lay every little brick you know next to each other a lot of hands over a lot of hours days years we're just stopping here in this super cute place for a bite to eat look with like a really really big parrot ha cool look at that very nice no no that's on the menu nice so apparently they have like queso frijoles frijoles is beans which is nice I like it so it's like a cheese and bean patty wow looks really nice I mean this is like the best ever yeah definitely okay cool so I don't know maybe four frijoles four she see is just cheese and frijolito is cheese and beans all nicely fried up on this big frying pan here absolutely incredible cool cool I'll look all the ingredients there and then just amazing nice it looks like a really local coffee yes look it's made it's made just here hey nice and then they've got plantain chips I like them two cheese and two frijolitos and two coffee with milk only black coffee okay black coffee okay thank you thank you so comes with a little salad comes with a nice dip pretty tasty hey that whole thing is just cheese that's the biggest cheese thing I've ever seen oh my goodness thank you so from one out of ten I got some dessert I don't know exactly what it is it's like mashed up fruits with some sugary sauce on top wow it's very very sweet and this whole like restaurant complex super cool because it's I don't know if you guys can see but it's like on this beautiful little river system here and just got all these nice decorations everywhere and it just looks like a little paradise here hey guys I don't know if you've noticed us wearing these t-shirts before well these are our overlander teas and we're selling them on our Etsy store we actually designed them ourselves so you better like them if you love what we do and want to show your support why not buy one of these super cool teas by doing so you'll be helping us get a hot meal or a cozy air conditioned room for the night head over to our Etsy store and order one today we get it shipped out for you wherever you are in the world thanks mom and dad you can find the link to the store in the description below thanks so much guys and now back to the video so I think it's about time to tell you guys a little bit about country we're 17 on our trip the land of sea and volcanoes Nicaragua so the area what is now Nicaragua has been home to people since at least 12,000 BC the country was colonised by the Spanish just like everywhere else in the 1500s and they got their independence as well just like most other countries in 1821 as part of the Mexican Empire they then became part of the Federal Republic of Central America and didn't gain independence as a sovereign nation until 1838 the country now has a population of 6.3 million people and the capital and largest city is Managua and it's actually super cool because this country is home to the Bossawa's biosphere reserve which is the second largest rainforest in the Americas behind the Amazon rainforest of course so who knew that this country in Central America had the second largest rainforest it's insane the name Nicaragua has like two main theories of where that came from the first theory is that it's named after Nicaral who was a chieftain of an important tribe in the area when the Spanish arrived and the second theory is that it's a combination of local indigenous words from the Nahuatl language and one of the possible meanings is surrounded by water which you can actually see because you can see a lot of lakes and I just go through the cante should we just continue filming or not I guess so we're already filming so yeah Hola Buenas Buenos dias Documento de tránsito por favor I think it's in the back eh where is it this one there where are you going Honduras border, license United Kingdom where does it come from England England and Germany first time you pass through Nicaragua yes, first time Costa Rica, Masaya Matagalpa here Honduras Nicaragua again dialogue I had to do the turn on the other side not through I had to do the turn thank you when the driver passes there it's explained what a transaction is maybe you can try to translate it I'm going to explain to see if I can understand this is an infraction ok, he wants to give us an infraction ok when you commit an infraction in the law of transit here in Nicaragua a multa is applied with this this as a monitor this ticket is delivered and I stay with your license do you understand anything? no, it has translator it has internet translator hello this ticket you have to pay in the bank bank? the bank is closed but there's a problem you can't leave the country with this ticket I wish I understood I don't understand I'm sorry do you have internet? do you have internet? yes, perfect Spanish is bad I just need to drink some water whatever we just want to license back the traffic infraction is applied to you pay it in the bank look there we are really sorry sorry we will take the ticket do you want to read it out for him? ok motorcycle and follow me in the vehicle take off your helmet please ok to apply the infraction ok got my license or do I have the license? I think he has the license let's take this one what is this one? this one? I believe he is going to keep the license until we pay the infraction if he wants us to do it we can give him the money for the infraction now because we have to continue I mean they can't really take the license off of you can they? we need the license back please give me the license back I will pay on Tuesday no problem 5 minutes later if he didn't know we were leaving the country it would have been fine it's my bad I did commit an infraction apparently you are not allowed to do that at least he wasn't trying to get a bribe I think he wanted to but he couldn't because you handed him in front of two other people that's not how you are supposed to do it you are supposed to be way more subtle than that a bit of a tricky situation but it turned out ok and now we are only an hour from the border good to go police barrier number 25 Bienvenidos a Honduras what's that noise? can you see something? so we had a little inspection here of the wheel