Skip to content

Ephesus merge mainnet liberated - #4599

Merged
mnaamani merged 159 commits into
Joystream:ephesusfrom
dobertRowneySr:ephesus-merge-mainnet-lib
Feb 7, 2023
Merged

mnaamani merged 159 commits into
Joystream:ephesusfrom
dobertRowneySr:ephesus-merge-mainnet-lib

Conversation

@dobertRowneySr

@dobertRowneySr dobertRowneySr commented Feb 3, 2023 •

Copy link
Copy Markdown
Collaborator

merge mainnet-liberated into ephesus #4556

Main points

┆Issue is synchronized with this Asana task by Unito

Lezek123 and others added 30 commits October 14, 2022 10:47
…ndVideos_fixture

fix: updating correct videoId in cliChannelsAndVideos fixture
…tring-fix

Fix computing code shasum inside docker build
…_types_package

make @joystream/types hybrid package
@vercel

vercel Bot commented Feb 3, 2023 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated
pioneer-testnet ⬜️ Ignored (Inspect) Feb 7, 2023 at 10:53AM (UTC)

@bedeho

bedeho commented Feb 3, 2023

Copy link
Copy Markdown
Member

Who else should review this?

@mnaamani mnaamani changed the title Ephesus merge mainnet lib Ephesus merge mainnet liberated Feb 4, 2023
@mnaamani

mnaamani commented Feb 5, 2023

Copy link
Copy Markdown
Member

The two flows a failing consistently in the network integration tests:

channel payouts proposal: Failed
group budget: Failed

@dobertRowneySr

dobertRowneySr commented Feb 6, 2023 •

Copy link
Copy Markdown
Collaborator Author

The two flows a failing consistently in the network integration tests:

channel payouts proposal: Failed
group budget: Failed

In the channelclaim-* fixtures there where Council budget checks. They where concurrent to the budget update logic run at each new block, that's why they where failing. Budget checks would have been nice, but implementing them is time consuming.

The other error was due to inviting members being run concurrently to the upgrade Membership Group budget fixture (so you had 2 concurrent budget updates)

@@ -8,7 +8,7 @@ const workingGroupModules = [
'contentWorkingGroup',

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can drop this entierly. It uses sudo. We forgot about it in mainnet-liberated branch

@mnaamani

mnaamani commented Feb 6, 2023

Copy link
Copy Markdown
Member

In the channelclaim-* fixtures there where Council budget checks. They where concurrent to the budget update logic run at each new block, that's why they where failing. Budget checks would have been nice, but implementing them is time consuming.

I would have assumed these were working before. Why would they stop working in this merge?

@dobertRowneySr

dobertRowneySr commented Feb 7, 2023 •

Copy link
Copy Markdown
Collaborator Author

In the channelclaim-* fixtures there where Council budget checks. They where concurrent to the budget update logic run at each new block, that's why they where failing. Budget checks would have been nice, but implementing them is time consuming.

I would have assumed these were working before. Why would they stop working in this merge?

  public async execute(): Promise<void> {
    this.expectedClaims = await getExpectedClaims(this.api, this.claimChannelRewardParams)
    const expectedClaimsSum = this.expectedClaims.reduce((sum, claim) => sum.add(new BN(claim)), new BN(0))
    const councilBudgetPre = await this.api.query.council.budget()
    await super.execute()
    const councilBudgetPost = await this.api.query.council.budget()
    assert.equal(councilBudgetPre.toString(), councilBudgetPost.add(expectedClaimsSum).toString())
  }

The execute function reads the council budget before and post execution. However there are multiple budget modifications due to the council budget bookkeeping logic (screenshot below). So the assertion checking only for the channel reward variation fails.

Screenshot 2023-02-07 at 12 02 39

I am investigating why this error has not appeared before,
Edit: the execution block for the claim_channel_reward changes at each test run. So it is possible that previous tests were fortuitous
Edit2: I can confirm that these assertions fails on ephesus @ 2676a17 at the moment

@mnaamani

mnaamani commented Feb 7, 2023

Copy link
Copy Markdown
Member

Ok thanks for investigating that, it would be good to have such assertions as part of these fixtures but it is out of scope of this PR.

@mnaamani
mnaamani merged commit c442810 into Joystream:ephesus Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants