Everything EOS EOS Leap Upgrade Group, 25 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: EOS MANDEL Meeting #16 (May 25th 2022)

Description

This week the ENF updates us on Mandel Platform support, the release of D.U.N.E is ready for testing and where to find the 2.0.14 release notes…. GO EOS!

🟢 In progress action items are on track:

#55
D.U.N.E., the new development environment is being tested by the team who indicated concerns about the removal of native Mac support in the platform support survey
EOS Support will reach out to the rest of the survey respondents to get their feedback on D.U.N.E. too

#41
There was a new patch released to enhance subjective billing: 2.0.14
Release notes draft is in progress and available for review and feedback: https://github.com/eosnetworkfoundation/mandel/releases/tag/v2.0.14
The block log splitting feature development is still in progress. The June deadline will be tight, but still the target.
Shout out to OCI for their great work knocking out bug fixes and enhancements and working closely with node operators to make improvements that make their lives easier.

#44
EOS Nation has deployed the latest builds on Jungle4 and has no problems to report.

#50
EOS Nation is working on publishing an article that summarizes the high level Mandel upgrade plan and consolidates developer resources

Participants (18)
Host: Daniel Keyes | EOS Nation
swatanabe
Max_Cho EdenOnEOS Member-South Korea
Kevin Heifner
Vlad
Lovejoy
cmadh | liquiid.io - Corvin Meyer auf der heide (Corvin Meyer auf der Heide)
Alysha Mims
Ted Cahall
Bucky Kittinger
Patrick - Aloha EOS (Patrick Burns)
Jeff Werner
Genie Kim - EOSeoul# NEOPLY
Randall Roland
Johnsonb - Object Computing# Inc.
junhank | NodeONE
EOSUSA Michael
cc32d9

00:00:00 Intro
00:00:07 Recap from last week by Daniel Keyes
00:01:17 Platform Support & D.U.N.E by Daniel Keyes
00:04:28 Mandel code updates by Daniel Keyes
00:05:58 Call out to the OCI team by Ted Cahall
00:08:52 Testing on Jungle 4 update by Kevin Heifner
00:13:38 2.0.14 Release notes by Daniel and Kevin
00:16:12 Wrapping it up
00:16:43 End

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://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF

A

Welcome everybody, it is, may 25th. This is our 16th uh time checking in weekly check-in quick recap. On last week we talked about dune last week. It's ready for testing. This is the new dev environment uh developed by bucky in the enf.

A

This was related to the feedback we were looking for on the changes to the platform support for mandel and, in particular, the the dropping of native mac support. uh I can give a little quick update on on there. You can see. We've uh we've got the summarized version of the results of that survey here, which we discussed. Last week uh we checked in on progress for mandel development. Everything was on track, we'll get another update today and updates on testing. Again. Everything was on track.

A

There too, um are there any new items or perhaps older items that we need to check back in on from anyone's perspective,.

A

All right, let's um dive into platform support, uh so I mentioned last call that we would reach out to some of this. So we only had uh one person who kind of raised concerns about the losing mac support and having to replace that with a docker image.

A

um I've connected with them and they're they're happy to work with their tested test dune with their team. um I've extended invite to this call, I don't think they're going to have any feedback for today. It was very very recently that they started doing the testing, but we may have them join us next week to provide any feedback.

A

The high level concerns were around unit testing environment with native tester, missed multiple environment, build by a c, make debug release version testnet and mainnet. I missed multiple contract integrations. For example, many dapps require com communication with eosio token contract and atomic assets and ci cd missed for build and test deploy of contracts. So again, this was feedback based on just general experience using docker, not using dune, so we'll we'll get updated feedback from that team after they've had a chance to to use dune.

A

Any anything to add on that topic.

A

So we'll check back in in a week and see if, uh if we get any more feedback there, but overall, like we said last week, looks pretty good.

B

We uh we pinned the dune repo at the top of eos network foundation thanks to bucky. So now it's easier to find and a little more advertised.

A

Great great and um I've only reached out to that one, no respondent. We haven't done any broader um requests for feedback from the entire um list of respondents. uh We can do that. That's something randall brought up as a opportunity. Yesterday, he's happy to send out a follow-up email, for example, just to the the respondents um is there appetite is that is that something that we would see valuable here, or are we mostly just interested in the the person who said no.

C

I mean I, I would like to see what I would like to see what the other people's um take is on it. If this is sufficient, um you know I've. I've been pushing it on.

A

C

That uh I kind of talk to from the community, so I just want to get there everybody's take on it see if it is sufficient enough cool.

A

So maybe we can work. I can work with randall to to get that out this week. um Did we the fact that these people responded to this survey means they're relatively engaged, so uh we can maybe get some feedback there. So that's uh we'll do that this week.

A

uh Okay, anything else on dune or platform support.

A

All right and regarding mandel code updates, I did get an update from matthew that um he's been pushing out all the late. I guess this is more testing related. These the latest update dates are the latest builds, are on jungle and everything seems seems good. No issues to report um just still waiting on the blocks.log trimming feature yeah.

C

A

Think we mentioned was where we were targeting june 1st. So that's uh we're still on track. There.

B

It's come. It's coming a little warm a little hot, we could say: matt witherspoon is working on it he's not on the call this morning, as he was probably up until 4 or 5 a.m, working on it, um so he he. Let me know that he would not make today's call, because he is uh coming in a little hot on that we we discussed it in the call yesterday that you know he's not it's not where he would like it to be. So he will probably start.

B

uh You know skipping meetings and just staying heads down because he's only got till about next tuesday wednesday to get it done.

A

Okay, so we're still still targeting that date, just that it's tight looking tighter is that right.

B

That is correct. Yes,.

A

Cool thank you um and yeah, like I said, for matthew, everything's, looking good uh from what he's seen so far, what he's tested um any anything else to add on the development side of things.

B

Just a call out to the oci team: uh they have been knocking out an amazing list of items to kind of tie up a bunch of loose ends for 3-1 make some improvements. Bug fixes just a lot of the open issues that were just hanging around that came off of both matt witherspoon's list and kevin hefner's list.

B

uh They just really knocked out an enormous amount of them. I think it's just a big fantastic job and worth a call out to that team. Brian johnson, kevin hefner and the rest of the oci folks for doing us. A tremendous job.

A

Awesome great job- I see a few of them on the call here, awesome, job and yeah. I heard matthew great great feedback from matthew as well on the work from the oci team, so yeah I'll. Second, that.

B

It's kind of nice that uh matthew has a willing group of people that are willing to improve uh life for the block producers right.

B

So instead of you know kind of just driving things that you know come from a singular vision, we're now listening to the actual block producer community and trying to close up areas that make it hard to run the chains- and I don't know if stan's on the call but stan has also been giving a lot of good feedback and any of the rest of you that are running chains that have you know, items that just make your life hard.

B

You know that's where we want issues opened up in the mandel repo, go ahead and open them up and you know send them to me: send them to kevin, or you know any of the folks here uh that have access to the mandel report.

B

We'll we'll add you into the manual repo open the issues up and then, let's start examining them and closing them down, because you know the block producer community is important and the better we make the software, for you know, ease of use and ease of reliability and operation, the better it is for everybody.

B

So um you know it's maybe a little bit of shift in policy from the old black one days, but uh uh it's great that kevin has been the that sorry that uh matthew darwin has been the vanguard, they're, really driving a lot of those issues and uh stan as well, and so please, the rest of you. I know the whole bunch of you on here that have a lot of block producer experience and please feel free to either ask for an account and we'll give you an account.

B

So you can open issues or funnel them into me or kevin or daniel or any of us and we'll get them in there and we'll start looking at them and see if we can make your lives better.

A

Yeah yeah great caulo, uh yeah matthew super appreciative of the engagement he gets from from oci and all the all the mandel developers, because yeah, like you said, making making the lives easier for him and all the other operators is, is super key.

A

Okay, anything else on code strategy or code development in general.

A

All right um testing I mentioned already that uh we've got the latest build up in jungle, four and everything's. Looking good um ross mentioned he's not gonna join, although I know he's doing some testing michael. Do you have anything to report on your side testing now, but now that matthew's done it I'll be happy to roll it out into my stuff.

A

C

A

The guinea pig has has uh yeah. I believe I just.

D

A

Up with them, yeah, whatever all good, all good uh cool, any anyone else have anything to report regarding testing.

A

Right, so maybe, unless there's any other items to discuss today, uh we we could keep it short.

A

um I guess the next thing in terms of the communication stuff, we've got that draft ready um for the the broader uh survey for eos developers and node operators, uh so that might be after maybe we'll this week, we'll we'll send out the more feedback on dune.

A

I've got a writer assigned to putting putting the other articles summarizing what's happening, mandel the upgrade the consensus we can and we can plan for maybe uh the following week a broader communication. With that other survey, that's that's uh been prepared and unless there's anything else, we could a couple cameras. A couple.

D

Things sure uh we might uh want to just mention that we did release a 2-0-14 which was a patch on top of esio's 2-0-13, so that's out there and available. If anyone happened to miss that that that did go out. It just includes a couple of enhancements to the subjective uh billing uh feature that was called out and as as needed.

D

So that's uh that's there and the second thing is: we are starting even now to start drafting the release, notes uh for 3-1 of mandel, and so there is a draft page out there for that already, if you so, people can follow along, as that happens, and certainly feel free to uh add, suggestions, uh provide input or you know, write some numbers for that matter. um We'd be, uh would be happy for any feedback there.

A

Great and sorry, the patch release. What was that number 2.

D

2.0.14. so the last esio eos release was 2013, and so we just uh we had a couple things on top of that. There was a number of actually issues in the release: branch of 2o that had never been released, and those went out with that as well. So we uh we basically just kind of picked up that and ran with it.

A

All right, so if people want to be testing the latest and greatest, this is the build they should be testing. Is that right.

D

That would be considered the the latest uh 2-0 uh version of the software. Yes, that would be the okay version to use over uh 213. It includes a couple of fixes in the release, notes, which I don't have right in front of me: there's a there's, an additional option to um configure the subjective delay.

D

So if you don't want the default of 24 hours on your subjective, uh not delay long term the subjective decay, here's the word, I'm looking for um you can modify that with with that version and that actual that actual fix, I think, was pushed out to the block producers a while ago. But now it's in a in a you, know, semi-official release uh so yeah, that's there and then uh there's a new uh fix in the release that was just taught off uh the weekend where the um subjective um or the three strike rule.

D

um If you're not familiar with three three strike rule when when a block producer is producing a block, if it gets three failures by an account, it doesn't take any more uh transactions from that account for that block. uh That uh behavior has now been expanded across the entire block uh construction, as opposed to just of the the transactions that were in the unapplied transaction team.

D

So a little tweak to the way uh that worked, uh which was observed on some block producers over the weekend, uh they were seeing runaway cpu when that was that was put in there too. That.

A

Was that was on wax? Wasn't it.

D

It wasn't that particular yes, yeah.

A

Yeah matthew mentioned he's already applied that on in production on wax and it's and it seems to be helping so yeah awesome uh and then is there a place. I can point to for these. This release notes draft. That's it if.

D

You just go to the main manual webpage uh in the release frame the releases it's the top release. Now, because it's the last one that happened. So it's actually uh we so you won't see 305 or whatever was there before now you actually see 2014 and until we release the 315 there, you go thanks. Chad.

B

A

Oh you cut out, there ted looks like you, muted yourself, yeah.

B

My cat did sorry, are we looking to uh have the eos block producers roll it into 2014.

B

Or is that something that they just do on their own? Is their communication out to the black producers to pick this up or was mostly done for wax.

D

I mean the the issue was being observed on wax, um but I mean I think I think matthew made the point matthew's not on here. I don't believe uh made the point that you know that it's probably just a matter of time before eos might could obviously could potentially see the same sort of issue uh show up it was uh you know it was? It looked to be a particular account that was doing a particular, uh potentially arbitrage sort of thing. I don't know what exactly they were doing.

D

We didn't look into it in too much detail, but um you know so it was a particular. I won't call it an attack just a particular way of interacting with the chain that was causing issues. So um you know, but that potential is there an eos now whether block producers want to pick that up or wait until they actually observe a problem. I mean that's, obviously, a good one.

B

A

Yeah from what I understand, this is beneficial to both eos and all the other eosio chains. Just it was just. We saw the problem first on wax yeah a matter of time before the others.

B

But we would need to communicate to the eos block producers to pick it up or they they might not know to go, look and grab it right.

D

Yeah right, I assume matthew did I mean he's normally. uh He normally does with that sort of stuff, although you know I couldn't say for sure if he did or not got it, I.

A

Yeah I haven't, he hasn't confirmed that or he maybe he has. I don't remember, but I'm probably he probably has. I can confirm that with him uh make sure that that's that's been, but knowing matthew, it's likely already in progress if it hasn't happened already.

A

Awesome thanks for that update anything else to add on uh mandal development.

A

All right so we'll, uh hopefully have some feedback on dune for for next week, and uh perhaps a draft of the communication to share the broad high level communication.

A

uh So unless there's anything else, we can call it a day and see y'all in a week. Thank you, daniel. Yes, thank you thanks. Thank you.