Everything EOS EOS Leap Upgrade Group, 13 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: EOS Mandel Weekly Meeting #23 (July 13th 2022)

Description

This week the Mandel huddle group discusses DeepMind and Dfuse bug fixes, Jungle 4 Features activation, MSIG on Kylin and more!

00:00:00 Start
00:00:02 Recap from last week by Daniel
00:00:59 Mandel software development by Stephen
00:04:08 Deep Mind and Dfuse fixes by Corvin, Stephen
00:08:20 Fill-pg survey feedback by Randall, Stephen
00:12:41 D.U.N.E testing feedback by Randall, Stephene
00:16:22 Jungle 4 features activation and Hyperion by Daniel, Ross
00:34:18 MSIG on Kylin update by Daniel
00:35:32 End

Summary
🟢 In progress action items are on track:
#41
RC2 has been released and we have the green light from ENF to activate and test crypto primitives (along with all other consensus features)
CDT and contracts are released with release notes
RC3 will be required and targeting release next week (includes fix for deep mind/dfuse)
#55
D.U.N.E. will be released this Friday (was originally planned for last Friday)
We received some more feedback from someone testing D.U.N.E. on Mac
An other developer states that it is not possible to confirm whether there are remote containers. It will be great if there is support for remote container. James Mart has a video on this: Writing modern EOS smart contracts. The Fractally team supports remote container per the respondent.
#44
From a software readiness perspective, we're a go for activating consensus features on Jungle4, but we still require some additional BPs to upgrade to Mandel 3.1 RC2 and some clarity on the activation procedure before we can proceed.
EOS Nation will track upgrade progress and engage with CryptoLions and other BPs to get their Jungle4 nodes upgraded to Mandel 3.1 RC2
Kevin Heifner will confirm and document activation procedure
EOS Nation will engage with CryptoLions to propose MSIG to activate features on Jungle4
We'd like to understand how history solutions like Hyperion behave with the consensus features activated. Michael (EOS USA) has been testing Hyperion on Mandel 3.1 and we'd like an update from him on the status of Hyperion with features activated on the next call following activation.
#40
The MSIG on Kylin to update EOSIO permissions granting authority to EOS Nation and EOS USA to facilitate more rapid updates in preparation for testing has been approved and activated.
Participants (14)
Host: Daniel Keyes | EOS Nation
Matt Witherspoon
Bucky Kittinger
Stephen Diesel
Max_Cho EdenOnEOS Member-South Korea
Kevin Heifner
Ross (EOSphere)
Corvin | cmadh | Liquiid.io (Corvin Meyer auf der Heide)
Genie Kim - EOSeoul# NEOPLY
Alysha Mims
Rob - Genereos (Rob)
Randall Roland
junhank | NodeONE
Johnsonb - Object Computing# Inc.

chillsauce mentioned this issue 6 hours ago
Mandel upgrade weekly meetings #37

Everything EOS is the official media channel of the EOS Network Foundation (ENF). The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.

// EOS Network Foundation //
https://www.eosnetework.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #EOSIO #ENF

A

All right we're rolling, welcome everybody. It is july 13th. This is our 23rd week for straight meeting to discuss the mandel upgrade a quick recap. Last week when we, when we met rc2, was on the brink of being released, still required, some testing.

A

We were getting close to releasing cdt and contracts that was planned for thursday.

A

Enf was looking for feedback on phil philpg, uh we're preparing a survey for that um we've been making progress on the dune 1.0 release, including all the tester and debugging stuff that was expected on friday um and uh we're yeah getting basically getting prepared for a go no-go decision today on jungle. Four, uh so stephen, are you able to share any news on the mandel software development progress uh where we're at with rc2.

B

Yeah absolutely so um presently, rc2, of course, is available for update forever is seeking to do such a thing. um One thing that we had discussed last week was that we had an inactive feature related to uh the crypto, primitives and host functions since that time, we've given the green light for anyone to start testing that feature actively if they wish, there's an understanding from our end that that may not be the highest priority for everybody right now, but just wanted to share with this group that we have the green light there.

B

On thursday, we did successfully release both contracts and cdt. Those release notes are available in their respective repos, and we do still require a mandel rc3 release coming up right now, we're working through about four outstanding issues. um Most of them aren't too new, but one thing that's kind of emerged. Well, there's two things that have emerged: we've had just a couple of issues um in some of the integration tests that have been occurring, but then also, I know, there's just been some issues with deep mind.

B

uh We've been collaborating with matthew darwin as well as I want to say a guy named fred who's been doing some testing for that team. We've got one of our oci tech leads helping support that effort.

B

um I think that they had pushed a solution to the first bug, but I think that it's likely there's going to be just a couple of them along the way uh right now, we're optimistically targeting likely rc3 happening next week, I'll be able to provide an update, of course, in this next meeting, that we have um that's kind of the gist of it outside of um I guess it may or may not have been discussed last week, but dune. um We had originally thought that we may be releasing dune last friday.

B

It's looking more like this friday, just as we're working out a few issues, there um covered a lot of stuff all at once, though, so any questions about any of those updates.

C

B

D

A

D

The high level.

A

Here, right, green light from the enf to activate and test crypto, primitives um cdds and contracts were released, with release. Notes on thursday is that right.

B

That's correct.

A

And rc3 will be required, we're targeting release next week.

B

Yep, that's the hope um and we'll, of course, have an update as we move along again right now. It's about four issues that we're cranking through uh some of them: we've just not gotten our hands wrapped around too much yet to feel totally confident uh that next week's the date, but that's what we're shooting for right now and then um dune we're shooting for releasing this friday.

D

Okay june will be this friday: okay, yeah any.

C

Questions for anyone, yeah yeah regarding deep mind and diffuse. Where are these these discussions happening with matthew, because we are we're also working on a deep mind: consumer deepmind based application, and currently we are still working with 305 rc1, but if there are breaking changes and stuff like that, it would be good if I know about them.

B

Yeah, so it it was kind of something that was hot off the press in our internal discussion yesterday around release. um Thank you. Kevin kevin just shared the first bug that was surfaced. um I think that we've probably just identified an opportunity of how better we can collaborate in tracking any of these uh issues that emerge. So um I think always.

B

We should be seeking to create issues in the respective repo that it's applicable for and then in terms of the escalation pathway in which we actually surface it to the internal enf team, I think is probably still to be determined, but I think um you know making mention of it in mandel dev, if you're a part of that by chance or um even dming, someone like me directly or at mentioning um any of the core team developers so that they can surface it to us as I'm continuing to learn the specific subject matter that we're working through here are all places where I think we can experiment until we find something that sticks.

B

I, of course, am acknowledging in that statement that we don't have a cohesive plan. Yet for tracking these things that we don't specifically oversee and test to its full extent, since you're kind of ingesting those changes and having to work through them, but happy to continue that discussion outside of this call, if you've got any leading thoughts there um really just. I always want to set up process where we can make it easy for people to just plug in and surface the issue and feel confident that it will get addressed.

B

C

A

This is an issue. Fred is testing heavily right now, heads on our team, so in preparation for the activation testing making sure defuse is working. uh This was a bug that fred had discovered and and reported directly to to the enf. So thank you kevin for sharing the github issue. Here I see there's a second one here.

A

C

I think it would be easier to follow deep mind diffuse, related things if we had a deep mind label.

C

Just yeah spontaneous side note.

B

Yeah, I think that that's a fair thought. um Let me bring that back to the team and just see where the appetite is there. um I think, typically for us, we want to constrain as many fields or attributes that we're assigning in github as possible, just so that it doesn't turn into too much manual work. But yeah. We've already got a pattern here of a couple deep mind issues, so I I see the value in what you're asking for.

A

So is this also a deep mind issue, or is this just another issue related to rc3.

E

This is the pit; this is the fix. This is the pull request.

A

B

In in conversations yesterday, just to clarify uh when discussing with matthew darwin and a few other people on the call, there was a suspicion that this may just be the the first bug, and there may be a couple more that emerged from it. um So the goal was just to resolve this so that it was easier to test and break through to any other additional changes that may need to be made. I don't know that we've confirmed any additional issues at this time, though,.

A

C

E

But we are eager to hear.

A

Okay, anything else on the topic of rc3.

D

A

Beautiful thank you for the update steven. uh I will mention this in our platform, support notes here, so we don't lose track.

A

uh And I believe I'm I'm not if randall, if you're able to speak, I know I um you've got a survey prepared, I'm not sure if it's been sent yet for the feedback on phil pg. Are you able to share any updates on that.

F

Yes, um we were able to send it out. We have only one feedback that came in um a developer will say that they are using um hyperion history api, because uh phil pg they can't manage to filter and retrieve data that they want to show to um their customers in a smart way like um they feel like.

F

The solution is mostly them um uploading, all the history and then filtering instead, so um they have been using a hyperion and they are hoping that maybe a lot of people can um run notes for hyperion and other um um history notes, so that we can have like a stable history on eos.

F

That's what they said, um but that that was it. That was the only um um feedback that we've received so far. It seemed like people are not using it um based on what we are gathering.

A

Great, so you that was that survey so far, just one response: it was only sent what a couple days ago or something last week.

F

Last week um we sent it our thing on last week, tuesday, okay,.

D

What happened to my notes.

B

And just one quick question from me on that and um just with the design of the survey since I've not seen it is there any opportunity for uh respondents to just be like nope, I don't use phil pg in the story. I don't want to answer any more questions just to remove any friction for getting those results, but also maybe validating the hypothesis that phil pg is not in widespread uses at the moment.

F

um We we were trying to do that, but I think I discussed with uh daniel and daniel wanted us to make in the way that okay, we are trying to find out if um people.

E

F

It in their projects, but that's something that we can you can add to, we can add to it. It's.

A

F

A

I correct me from it's like basically it's one question basically around: do you are you using phil pg or do you plan to use phil pg in any of your projects and that's basically, it yeah yep.

B

Cool. Thank you for the clarification.

A

Hear me all right, I think I'm probably talking through my monitor now, but that's okay.

A

uh I can't hear you guys, though, but maybe that's just because no one's talking this is me talking.

B

All right, I can.

A

Hear you um so I'm not sure what happened. Did I forget to come and post my comment on this issue with the notes. That's okay, I'll, go! Fill it up I'll, go review the recording later and update this uh this issue with the notes that are have disappeared, um and I will also add that update so so far, not much feedback from the survey for phil pg we'll continue to monitor if any other feedback comes in, but the feedback that has come in so far, no one no one's going to miss it.

A

If we stop supporting it, it sounds like.

F

Yeah, that's that's about about right! Yeah!.

A

Eating, let's move on then to.

A

We talked about doing already, testing on.

F

I want to talk about doom. um We have uh two feedbacks that came, um I think. um Last week um a gentleman set up um dune on his mac, m1 and installation worked but he's having problems or trouble starting a note. So he has opened a github issue.

F

I can post it github issue with the enf, so I can post um the link on uh maybe mandel.

A

Group chat, maybe sure yeah, either in there or in the zoom chat here and I'll. Add it to the ticket or I'll. Add it to this github issue. Here.

F

Perfect and um the second feedback, um a developer, um wants to know if we are going to have like remote containers, um the developers stated that um it would be great if there is support for remote containers, because the factory team has support for remote containers and um james mart actually had a video on youtube regarding something similar.

F

So um I also have like the youtube um link that they sent us. So maybe that's something that we can also look into.

B

Yeah also, if you want to connect uh our team with that respondent just so, we can understand uh why they would want those remote containers. I I would greatly appreciate it.

F

A

Awesome, thank you. So randy you'll share the link to that issue in the youtube. After this call. Yes,.

C

Isn't is remote containers just the functionality of visual studio code.

F

um So when you have uh visuals to your code, um you can actually write smart contracts uh in a way when you have uh the docker remote container um syncs to it, and um I think that's how fractally builds the applications they have. They use that tool.

F

So um I'm guessing that's what the developer is asking for. Maybe.

A

Looks like this is the issue. Is that right, randall say it again looks like I don't know. If you can see my screen right now, uh kevin shared the what looks like.

F

A

Be referring to.

F

Yes, that's the issue.

A

And then, and there's a separate feed from someone else, or is that the same, the same respondent who shared the youtube video about that was, that was a.

F

Separate um okay, um give us that feedback, I'm actually going to put um paste it on uh the zoom color right now,.

A

A

Okay, anything else to add um platform support.

A

Great I'll I'll come back to update this. uh These notes, when we have the other feedback, um all right. Let's move on to jungle, so the question is: are we ready to give a go to activate features? I guess which features would we would we be activating and uh what what needs to happen in order to make that happen?

A

um So I understand from enf's perspective, the crypto primitives is ready to activate. um Is that is that right, stephen? Would there would there be any other features beside that?

A

B

The only one that I'm aware of at this time that we had advised not to activate that we have now approved for activating okay.

A

So so everything is, and now is from from ens perspective, good to go for activation.

A

um One of the questions around activation is: do we have a viable history solution um once we activate, we will lose diffuse on jungle based on our our testing. Defuse is going to stop working.

A

Do we have anyone who can speak to the status of hyperion.

A

I did I don't see, michael on the line. I think I saw some some notes from him that he's testing it. It seems to be working.

A

um In any, is there anyone else go ahead.

C

I would assume that it just continues working while just throwing one or two exceptions that these these features are not known right and then it would try to to deserialize any actions transactions deltas that it receives through chip. As always, but there's there's no change. I would expect it to just.

G

Work, I'm sure michael said that he tested it and it actually carried on ingesting.

A

Yeah, I'm not sure if he's tested with features activated, probably not but yeah,.

A

Without the features activated, yeah yeah.

C

Yeah, but but except the feature, activation notification transaction, whatever uh there's no difference in what chip returns so anything else, everything that should still work.

A

Okay, um assuming a worst case scenario, and it doesn't work- is there anyone on the call who has any?

A

um Can we live in a world with jungle, not having block explorers for now and and what's the worst case scenario, I guess we could roll back start using jungle, three relaunch jungle, for what would what what would happen in that case, I.

G

Reckon that um if we had to ping eagle, he would put some more focus on it with the rio team to just try and figure out exactly why it wasn't working on the hyperion side of things. I I mean, I'm speaking out of terms just for him to comment on, but obviously they want to keep hyperion going with mandel or you know, going forward with the new branch of code, so um it'll actually be good. It'll be a good thing.

G

If, if um you know we can see what's happening right, then a couple of people testing it type thing rather actually just get it going. I reckon.

A

Yeah, it adds a little a identifies. If there is a problem b puts a little pressure on making getting the attention to getting it.

G

Yeah yeah yeah yeah and we're talking jungle. Four right, that's right! I don't know what the uptake was of jungle four to date compared to what jungle three was in the past right. So you know I don't think, there's any any mission, critical stuff running on the test net on jungle. Four, but then again, that's just right! It's just me, thinking about it. Yeah.

A

Yeah agreed, um I don't think, there's anything I know: there's they're testing evm on jungle, four, that's one of the reasons where we're looking to get crypto primitives activated sooner rather than later. So we can start benchmarking, um let's see where we're at with jungle.

A

For in terms of uh so it looks like we have more lots of folks upgraded all the way up to rc2. That's good aloha is still an rc1.

A

um So what needs to be true to activate? We need 21 upgraded to rc2 right. The rc1 is not good enough.

A

So we'll we're not there yet.

G

Well then, of course, that's also dependent on your bp json. So that's.

A

G

I'm not not sure what the actual upgrade list looks like.

A

Is there anyone who, on the call, who is upgraded but not on this list,.

G

One of the most important would be crypto lions yeah, uh even in the last um mc. I think they had like 10 or so of their producers in there.

A

uh Okay, so we need I'm not. I I'm not confident to say that ever we have 21 upgraded at this time. I don't think we do yeah um so that we, but we have rc2. Now we have go, go ahead from enf that everything should be working, so we should be making a big effort to get 21 vps upgraded.

A

So we can make a push in the jungle channel for the next coming days. Make sure people are upgraded, make sure if they're, not if their bp json is not updated. At least they give us give us confirmation, verbally that they're, updated.

G

I think what I'm saying is that if you had to look at the top 21, most of them are crypto lines.

A

Right, so, if we just get crypto lines that probably pushes us over the edge yeah yeah, we have anyone from crypto lines on the call.

G

Okay, that's that's the view yeah, so that they're not actually here.

A

Yeah yeah, but but we can uh get the word out to them and hopefully relatively quickly, get the crypto line, nodes upgraded to mandel rc2, and that should get us.

A

That should get us to 21.

B

Okay, I'm just gonna ask: is there an action item there uh that someone on the call should carry to completion? I mean it sounds like maybe you reach out to sudeep or someone else from the team. um I don't presently work with them very closely, but I've had some interactions in the past, but.

A

Yeah so I'll I can reach out in the jungle channel to cryptolines.

D

Excellent thanks.

G

Yeah, if we got them on board- and you might even find that that you know all of those producers are one node- they can just you know, get us moving forward.

A

Right: okay, what else needs to happen before we hit? So if I remember, if I'm thinking back to 1.8, upgrade.

A

If I recall correctly, we had to like set the a time. I don't know if it was in the msig or was it in the configuration on the.

H

um Yeah there was a config.

G

There was configuration.

H

You know there was a.

G

Separate uh json files to configure- I don't know kevin, maybe you can just fill us in what the latest process is.

G

I'm sorry, I didn't hear the question I would when you want to upgrade or enable the features, at least what is the process like technical process? Do you have to like change some config and restart the node, or was it.

A

For one point, for example, we had to agree to a time and configure everyone had to set the same time. Yeah. Is there anything like that for from the mandel feature, activations.

E

That that's a good question. I I don't even remember it's been so long. I'd have to get back to you, yeah, okay, cool.

A

um So can I add that, as an action kevin um we'll look into activation.

H

Procedure, thanks kevin you just volunteered there. I love that uh sure.

G

I think I think before there was like a safeguard, it was a safeguard and like a json configuration file, it was separate and it said that you can't actually execute the enablement of these features until this date right. I think that's what it was.

E

If in tests, it's just, uh um you know it's just a a curl command to do it, but yeah there's no great guards and turns like. I know there is like a like. You said: a json configuration as well yeah, that's uh involved in it, but yeah the exact details. I'd have to check on again, I know in uh and what we'll be in 3.2 we've actually added support to kleos, uh or maybe that's still in pr, but we're adding the ability to.

E

We can do it with chaos instead of a curl command, but uh anyway, yeah we'll definitely get those uh directions uh as part of uh something yeah. They should be in the release, notes, probably to make.

G

That audience and there might be there just none of us- have looked at that. No, I don't regret it, but uh yeah we should. We should get that somewhere, where it's clear.

A

Okay, so uh these this activation procedure will also be added to the release. Notes is that right.

E

I'm not necessarily saying that, but we'll definitely get them somewhere and okay.

G

E

Let you guys know but yeah that seems like we've. uh It seems like. We definitely need to get that documented somewhere.

G

He cannot confirm or deny that they'll be in the release, notes. It's.

A

And then I guess do we need to. If do we need to agree on a time? I guess that if there is a indeed a configuration, a time required to configure that everyone aligns on, um do we want to talk about what that time would be, or is it too? Maybe it's not even necessary? uh Maybe this procedure has changed to it's just as simple as activating the mc and that's it is that possible.

A

The time is when the execution of the nsaid occurs.

G

To be decided, I guess.

A

Okay, so I guess, pending the upgrade of crypto lines, nodes to mandel, rc2 and clarity on the activation procedure.

A

D

Anybody have any.

A

Red flags- or um I guess, objections to activating features on jungle four, uh once once we have that.

A

No, I'm good, I'm good and uh again, assuming there's nothing that comes out of the activation procedure. It's just a matter. I guess of posting an m sig on jungle. Four, do we have a volunteer who wants to create that end? State.

G

I can uh I can I would I would suggest we might get the crypt alliance guys to look at that. Okay, maybe just put that as part of your request, then.

G

Typically, before anything happens on jungle, bowden has looked at it and like yeah. Is it.

A

Okay, I will I will discuss that with crypto alliance buddha.

A

uh Okay, so it looks like we're at the activation point, pretty pretty close a couple of couple last boxes to tick, but the software is ready from from our perspective and uh just a matter of of getting the bps on jungle four set and and the in crypto lines thumbs up to uh just post that mc anything else that we should be considering before going ahead with the activation on jungle. Four.

A

Okay, so we'll uh I don't know if I'll say it's a go for activation, we still haven't, but I think it's a go to proceed. Preparation for activation.

D

B

Yeah yeah is there anybody throughout the next week that will just passively be able to discover and verify uh whether a state history solution is in a good enough place uh to move forward.

G

I think michael said it was at least running and the database database has been built, so it it appears to be working, and I think he actually ingested into a hyperion from there. So at least we know that uh it can build the database and it can be queried.

G

We know that you know I, I suppose, as everybody starts, to really use it rather than just test it we'll.

B

Figure that out agreed yeah, I just didn't know if he wanted to say hey. This person is going to give us an eloquent response next week about the status quo, but no words we can say.

G

That, usually, usually, is almost cool. I don't know why he's not I'm not here this evening, but.

A

Yeah normally, maybe he will so maybe I'll make that as another action item for myself. Talk to michael about uh so we'd like to get an update from michael on the next call about this state of hyperion, um with the features activated.

A

A

Okay, anything else so I'll catch up with michael and the crypto lines team offline um kevin. If you do dig anything up on the activation procedure, maybe you can share it in the telegram channel, we'll get it added here.

A

um In the meantime, we'll start kind of tracking our progress towards 21 bps on jungle, four I'll um I'll, maybe start another github issue. For that to you know we can keep keep track of where we're at in terms of top 21 activated good to go and um and share the the end sig when it's ready.

A

um Thank you randall. I I see you've uh shared your feedback.

D

A

Whoops, I didn't mean to do that, um but I'll add it to our.

A

Dune platform support here we go.

A

uh Okay, anything else on testing.

A

Okay, um we've, the m-sig has passed on kylin and been activated um so now. Eos, nation and eos usa basically have the authority to get kylian in an upgradable state. um I think there's still some progress to be made before we're ready to even update mandel, so I'll don't have much to share. Besides the fact that we've we're going to be able now to update kylian more rapidly uh and that's in progress right now. So hopefully we'll have some more news to share on next week on the state of manville on kylin.

A

Are there any other items anyone want to discuss today.

A

Okay, so we'll uh we'll see you all in the chat look forward for uh msig on jungle and um yeah, good luck with testing everybody. Thank you for joining.

G

Thanks everyone, everyone cheers bye, bye,.

F