Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Bump MAX_CODE_SIZE to 10MiB#7105

Closed
ggwpez wants to merge 1 commit intomasterfrom
oty-bump-consts
Closed

Bump MAX_CODE_SIZE to 10MiB#7105
ggwpez wants to merge 1 commit intomasterfrom
oty-bump-consts

Conversation

@ggwpez
Copy link
Copy Markdown
Member

@ggwpez ggwpez commented Apr 19, 2023

The current Polkadot HostConfiguration does not pass its consistency_check since it is using 10MiB max code size and the hard-limit is set to 3MiB. I dont know how that happened, but I am now bumping MAX_CODE_SIZE to make the consistency check pass again.
Note: without this bump the consistency_check will stay broken, since it has the assumption: "You cannot break something that is already broken" and thereby future HostConfig upgrades would not get checked.

MIN_BANDWIDTH_BYTES will probably also need a bump.

Signed-off-by: Oliver Tale-Yazdi <[email protected]>
@ggwpez ggwpez added A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. D5-nicetohaveaudit ⚠️ PR contains trivial changes to logic that should be properly reviewed. labels Apr 19, 2023
@paritytech-cicd-pr
Copy link
Copy Markdown

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/2704599

@bkchr
Copy link
Copy Markdown
Member

bkchr commented Apr 20, 2023

Good find! The actual solution is that we should decrease the max code size on chain.

By accident @eskimor and me spoke about the max code size on Tuesday. This value should not be bigger than the max block size of Polkadot, as otherwise we will not be able to build blocks which would try to add a parachain upgrade that is 10MiB big.

@bkchr
Copy link
Copy Markdown
Member

bkchr commented Apr 20, 2023

Opened an issue: #7108

@bkchr
Copy link
Copy Markdown
Member

bkchr commented Apr 20, 2023

So, I would close this pr.

@bkchr bkchr closed this Apr 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. D5-nicetohaveaudit ⚠️ PR contains trivial changes to logic that should be properly reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants