 So so from that they are fetching these chain codes and do they fetch like get installed contracts or do they fetch get approved or get committed? How is the fetch up happening? Whatever it is like committed chain codes only they are fetching. So this chain code like whatever the chain codes that we try to install right as part of chain code installation process. So that is being fetched from the peer. There are three steps right like install, approve and commit. If it is fetching like get installed then it could be on single peers and then get approval happens on an organization level commit happens at network level and and there are APIs for all three like get approved chain codes, get approved, get committed chain codes. I think there is also an API called get installed chain codes. So this chain codes I think... No worries I mean we can check that back but that's just most likely why this discrepancy is happening. Whatever it the reason it might be but you know in the chain codes like when we switch to other channel what are the part of this particular channel right? So those chain codes has to be we have to fetch right? Correct so the way it happens is the install step which is like so okay let's let's imagine it this way right install is a command that we typically run to copy something into the peer node and once we copy something into the peer node we tell to we say that hey I installed a package which has this ID and I'm willing to run this at the sequence number that's the approval that happens at our organization level and the third step is somebody in the network across organizations will say all the organizations have now some version of contract with them and they have all approved their own respective packages let us all commit to this sequence. So when we talk about channel we can we can either do like approved contracts shown here or we could do only committed contracts shown here. If it is approved contracts then again it's at organization level and there should be some kind of abstraction defined so that we have whatever you're saying right? Those APIs which are available I'm not aware Arun so I'll show you the method for just fetching the chain codes okay. Maybe we could add like a new column in this which which says these are the contracts that were sent for approval and this is the sequence where it was approved these are the organizations that have approved and then if it is already committed we could also say it's committed that way it shows both the status and the current like the only the ones which are belonging to the channel. This is query instantiated chain codes okay instantiated chain codes we would get so installed and instantiated to two I think that instantiate is like the previous to life cycle if I'm not wrong okay I think the the main significance would be for the committed chain code because this explorer is main intended to show the network view. We can have some approved as well but I think install will not have that much significance because now when we talk about install chain code we are talking about the peer level details and when we talk about like like Arun said when we talk about approve we are talking about the organization level when we talk about commit we are talking at the entire network level so we need to like the just that the the network tab which is there right it shows the height across all the peer nodes the unsigned height right same right so that that is the view at the peer level but for chain code as well if you if you want to give the install view then we have to give it at a peer level if you want to go for approved approval view then we have to give the odd level or if you want to give just a network right now it is then we can show the committed chain codes only so we could do something like like we don't support the old way of chain code deployments anymore in the explorer tool as part of the next release and we only support life cycle based chain codes and that will change from getting instantiated to get committed chain codes there should be another API for that instead of getting instantiated yes this anyways we have fixed the issue so now we could able to you know fetch the right chain codes as part of that particular channel okay nice so these two issues have been fixed one is a query change so with respect to version we were taking the transaction that is also having fixed this is chain code meta data also there is an issue we have observed these are all issues we were observing this goes fine when it is with single channel but we were when we are trying to test with multiple channel scenario then we could able to see a lot of issues coming up so one such issue is also be found out with a chain code meta data this this win also we have fixed it and there was little change in the query blocks page nation when we are trying to fetch the records right like some of the records we were not able to fix this is with respect to the version of 2.4.7 as the first transaction wouldn't have created MSP right because of that we were there was little change so and in order to like make this code viable for both the versions like 2.2 and 2.4.7 so we have tested in both the versions and fixed this and one major issue what we have seen was like so this this issue what it is like with respect to ledger height and the status of the nodes so if we see here we have two channels in channel two we have 30 blocks and 30 transactions if I switch to network tab here I'm able to get the proper ledger height when I switch to other channel if you see in dashboard we have 52 blocks and 52 transactions but I switched to network tab whatever the ledger height that it's been picked right so this ledger height is of the peers of other channel so this is is it due to like the API not getting the right channel or like it is due to the reason the API is getting the correct input channel only but we have discovery service right so in the discovery service it is able to pick only the channel which we have mentioned as part of CCP and other thing is like so whatever the data it is being displayed it is of only one channel always and the status also if we see here so when I down one of the order in one of the channel only it is reflecting when I switch to I'll show that also better like I'll down one of the meanwhile I'll show this thing laws so from discovery results we are like the input what we are getting is channel two and when we try to bring the discovery service it is of other channel my channel so again in the discovery results the my channel be and in the discovery service my channel be this is fine so channel two input discovery service my channel be so this is this for this reason I think it is always picking one channel information so if you see here in channel two this one it is reflecting correctly but if it's switched to other channel this is not coming up and this is reflecting only if I restart the server here I'm able to get the like error it is like connected is false but when from the network if I try to get the discovery results it is always shown as true and the other channel it is false looks like we need to spend some time on the discovery service there is one common common function called get discovery result which is called by two to three functions so I thought synchronization or concurrency might be causing the issue then but everywhere it is as incubator promises are used then we try it like using mutex to lock the function but that is also it is also not working see after the server restart then only we could able to fetch the status maybe we can plan for some session on this debugging hmm somehow we could able to work around this but the problem is like we could able to get the ledger height correctly but still there is a problem in fetching the status of the nodes just I would like to show that you started the order now Archanus I have raised it okay so one good question like as a part of this release that we'll do is there any other dependency apart from the bug that you shared this discovery service bug now this is the only major thing apart from that everything we tested end to end for everything is okay so other things whatever minor issues we found right we fixed everything and we raised the pair also so this is the only issue which is like we need to decide whether we can go with the release or we need to fix this and go for a list that we have to take a decision because we tried most of the methods whatever available still we are trying to fix it but we not we not get the actual scenario like approach which we can take it to fix this one so we have changed the code and we tried okay so like if we see here we have 3030 this is updated correctly 3030 so in my channel B we have 52 right in the network also we were able to get 52 but the problem is like status is not updating so if I stop one of the then how much ever time we wait this won't get updated I think we can go with the we can go with the release and like as soon as it fixes we can have a patch release after this and we can pull out this as a known bug in the release nodes and this is absolutely working fine with one channel scenario only when we have multiple channels how that can be called out in the release node we can call this out in the release node this is updating after server eastern so what we thought was like whatever gateway instance we are using right will reinitialize a gateway and fetch the network again connect to channel and everything but thinking is that is also not working out it is throwing an error like no discovery targets are found reinitialize a network also did not work out and even discovery service we tried to like reset up that is also is not being working here we have to spend more time on this after restart server restart we could able to get the status so where this is actually going wrong we tried debugging the code but I think it's like majorly formed the issue is coming with discovery service so apart from that everything is working fine except this ledger height and status and one more update so like we need told Aditya he has tested your PR in like building the pipelines it took almost one hour 57 minutes it seems for him I know so this is not with this particular project like I saw this thing with one other project as well just taking time the build is taking time we need to check if this is the limitation from or if we can get some support from this labs account because I think the right now the all those jobs or pipelines might be scheduled on on on a on a Q base on a Q based container so it's let's talk with Rai and see if we can get something on this you're talking about that CI pipeline like GitHub CI pipeline PR which has building test yes it's not the problem with the code actually it's the problem with the data actions they are taking too much time slightly here there was an issue like this was moving out of this this model so this this has been it's a normal simple CSS fix Varma has done it so these are like Aditya and reviews we need from you oh okay now you can ping me the PRs where you need the reviews okay like like the major PRs I think there are some basic PRs like the this one which 402 389 okay you can ping me the major PRs that you have that is that I need it for this I'll I'll look into them okay thanks so these are from our side Aditya and Sathya anything more we need to discuss yeah that's all so only the now what will the plan for the release that we have to discuss Aditya around right so when we can plan for the release I think first we can close these PRs the one that I was showing and then probably we can do one final final round of testing from the main branch like once these PR are merged and then we can go ahead for the release I think by the time those the GHCR PR will also get merged and we can release those images on the on this on the GHCR so like that PR that GHCR PR like it has two features like you just call out that so one feature is like it will create the Docker images it will it will get the release whenever you will create a new release or a tag it will create a image particular corresponding to the tag number so let's say if you create a tag let's say 2.0 explorer 2.0 it will create a image with tag 2.0 and whenever you push something to the main branch there is one more job that will trigger and that will build that Docker image with the latest tag so whatever is there in the latest tag whatever is there in the latest like latest main branch that will be called out in the as a latest tag in the Docker image and the release specific or the tag specific images will be there in the they will tag along with that version so maybe next week we will try to like a she like we will share the all the PRs whatever the PRs we raised it we once this is reviewed and once this GHPR thing also completed right so we'll we can plan for a date which we can maybe release further so we'll wait till we complete all these things all the PRs merge and this one GHPR approved then we'll round we'll do one round of testing completely then we can go with the date any date we can decide on date also can someone like take like take a look on those two GHCR and the GitHub CI because I think they are also crucial PR like we're not be able to build the image with until this PR is merged and the automated CI testing will not happen with that other PR so I request uh so it's a review or any any testing is required Aditya for that those things I think uh I think it's review only uh I did one of it on my side like before is in these videos okay Arun can you uh like uh approve those things like whatever Aditya has done or he's already one round the review has happened already I think okay um Aditya can you share me the PR numbers I'll so one more thing from my side like once we merge all the PRs right uh we would try to build the images locally uh and then we would like to test with the Dockrest version also so we are doing parallely actually building the images locally and testing so we did not find major issues uh some like while building the images uh node modules are out of such type of uh errors we are getting but because of which that image building is not stopping it is building okay so Arun you're asking about from moving the project to labs to top-level project continuously like this discussion is coming up right so I think we'll have a good um steps given that we also have a meet-up coming up and then the release all of this should be a good way to prove to TUC that we are very much active project and we should be a top-level project and it will drive more contributions for sure yeah sure so the document once we are done with the release will do those activities makes sense I think it's uh so different people have done it differently in the past few people like few of the projects they created a presentation right like a ppt and they say here is the ask that was there in the TUC steps and this is what we have done to achieve that and this is what we have been following for the last few months and the few teams what they have done is they created a confluence with all those steps listed like an explanation for why they think they should be top-level project we can think of intuitive way of how we can share across our learnings or why we should be top-level project sure yeah we can we can do that we first we'll try to concentrate on the release then meet up then maybe parallely we'll do that also makes sense yeah that's all from our side maybe anything else like that other scope side we are okay that anyway user user management thing you told you're working on that one design document so apart from that I nothing we can see maybe Manoj you need anything or you are done with your setup or nothing so I tried setting expert with the text network and other network which is running on point so I didn't face any issues so I was able to successfully bring up the exposure and I saw some I perform some reflections and I saw the reflections there in the control so and I also completed the like blessing of the concepts of the KBI course so regarding this ledger height and if there is any quick fix before the release or like if I could get help from Aruna Raditya like any API is available directly from where we can fetch the ledger height or status is there anything we could get from the documentation Aditya I think there is a channel API right which gives us ledger height or current ledger height correct so in the PRCRI as well we will find that get channel get info I think get info it is like you know when we access into that PR and we execute right that is a command but okay so yeah there are APIs I was talking about from the so whatever is there in the CLI you will find definitely there should be some APIs for those options CLI is an API request to the actual peer node that's how CLI is working so there is corresponding API I think we can do that ledger height at channel level and also at individual peer level I was searching for that API I found that in the java SDK I don't know the corresponding thing in the node SDK it's available at the channel level to get ledger height information in the java SDK so one other way that I know is like you can call the CSCC chain code directly that that gives you the channel little details that can give you the channel height as well you can query that system chain code that is one of the CSCC Aditya just like you call the normal channels right you can call the CSCC chain I don't know the java SDK thing whatever you found you can just ping here so it will try to see anything available for node jays also we'll check that it's doing the channel system chain sorry chain code system chain code only it's sorry the channel system chain code one thing I would like to ask Manoj you have discord account because the way of communication I have to do only through mails so if you can drop your mobile number or discord ID then it could be like easy to communicate with you sure I already joined and sent messages on Friday regarding discord yeah this explorer blockchain explorer labs and just bring you this yeah thank you Manoj anything else Archana did you discuss oh no Satya it's good to go okay that's all from our side Arun Naditya so if you find any information on these things right getting status and all you can just pass with us meanwhile I will share the PR situation to you okay thank you all thank you thanks