Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

polkadot: parachains: Fix v9 host configuration migration #2103

Merged
merged 2 commits into from
Oct 31, 2023

Conversation

alexggh
Copy link
Contributor

@alexggh alexggh commented Oct 31, 2023

We shouldn't override with their default fields that have been added in the
previous version(v8), because we are going to lose whatever values have been set.

Note, v8 & v9 seems to have landed at the same time on Rococo, probably they will
land at the same time on westend and other chains, so functionally doesn't make
much difference, but let's have this fixed for people that copy-paste :D, like me.

We shouldn't override with their default fields that have been added in
the previous version(v8), because we are going to lose whatever values
have been set.

Note, v8 & v9 seems to have landed at the same time on Rococo, probably
they will land at the same on westend and other chains, so functionally
doesn't make much difference, but let's have this fixed for people that
copy-paste :D, like me.

Signed-off-by: Alexandru Gheorghe <[email protected]>
@alexggh alexggh added A1-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). R0-silent Changes should not be mentioned in any release notes labels Oct 31, 2023
@alindima
Copy link
Contributor

my bad, copy-paste mistake 😬

Signed-off-by: Alexandru Gheorghe <[email protected]>
@alexggh alexggh enabled auto-merge (squash) October 31, 2023 16:34
@alexggh alexggh merged commit 64f4b15 into master Oct 31, 2023
114 checks passed
@alexggh alexggh deleted the alexaggh/fix_v9_migration branch October 31, 2023 16:40
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Mar 26, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 8c8adaf.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Mar 27, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit be915cb.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 8, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 8, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 8, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 8, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 8, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 9, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 9, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 9, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 9, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 9, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 9, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 10, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
serban300 added a commit to serban300/polkadot-sdk that referenced this pull request Apr 10, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (paritytech#2064)" (paritytech#2077)"

This reverts commit 62f749e.

* Adjustments
bkchr pushed a commit that referenced this pull request Apr 10, 2024
* Use wasm execution on millau and rialto

It's safer like this since here are some errors that aren't caught when
using native execution

* Revert "Revert "Fix max-size messages at test chains (#2064)" (#2077)"

This reverts commit 62f749e.

* Adjustments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A1-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants