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

update BaseXcmWeight to match Kusama #3911

Merged
1 commit merged into from
Sep 24, 2021
Merged

Conversation

xlc
Copy link
Contributor

@xlc xlc commented Sep 23, 2021

Why they are different? This makes testing impossible because testing environment is not same as production environment (Kusama).

Code works on Westend / Rococo means nothing if it is going to work on Kusama.

There are no way to access those value from parachain runtime so we need to hardcode the number and this just makes everything harder for parachains with zero benefits.

@shawntabrizi shawntabrizi changed the title update BaseXcmWegiht to match Kusama update BaseXcmWeight to match Kusama Sep 23, 2021
@shawntabrizi shawntabrizi added C1-low PR touches the given topic and has a low impact on builders. B0-silent Changes should not be mentioned in any release notes D3-trivial 🧸 PR contains trivial changes in a runtime directory that do not require an audit. labels Sep 23, 2021
Copy link
Member

@shawntabrizi shawntabrizi left a comment

Choose a reason for hiding this comment

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

This is fine, but I will say, that probably whatever end to end experiences you are building, you will need to have some system to actually read the weight of the corresponding XCM functions, since they may change over time.

So hard coding any values may not be the right long term thing.

But I agree, no reason for this to be different in the context of the different runtimes.

@xlc
Copy link
Contributor Author

xlc commented Sep 23, 2021

I think Gav have some plan on exposing some weight crates? But otherwise currently I don't see how we can do that. We definitely need a better long term solution.

@jacogr
Copy link
Contributor

jacogr commented Sep 23, 2021

There is this issue logged for an xcm payment_queryInfo-like hook - paritytech/polkadot-sdk#969

@shawntabrizi
Copy link
Member

bot merge

@ghost
Copy link

ghost commented Sep 24, 2021

Trying merge.

@ghost ghost merged commit 5d4cd4c into paritytech:master Sep 24, 2021
@xlc xlc deleted the update-xcm-base-weight branch September 24, 2021 04:38
ordian added a commit that referenced this pull request Sep 28, 2021
* master: (24 commits)
  Added multisig in Rococo (#3873)
  Fix bin-substrate toml (#3939)
  Bump tracing from 0.1.27 to 0.1.28 (#3937)
  XCM Benchmarks for Asset Transactor w/ Fungible Asset (#3818)
  Bump libc from 0.2.101 to 0.2.102 (#3933)
  Do not compile `wasm_api` module when not needed. (#3934)
  Bump syn from 1.0.76 to 1.0.77 (#3932)
  Fix spelling (#3845)
  Bump tokio from 1.11.0 to 1.12.0 (#3910)
  Ignore `generate-bags` by dependabot (#3930)
  Update logging in paras_inherent (#3927)
  Bump libsecp256k1 from 0.6.0 to 0.7.0 (#3909)
  Remove BEEFY repo dependency (#3923)
  Substrate Companion for rust 1.54 (#3807)
  Fix broken links (#3919)
  update BaseXcmWegiht to match Kusama (#3911)
  add parachains pallets to Polkadot runtime (#3815)
  Add a `force_unfreeze` extrinsic to the disputes module (#3906)
  Add new rococo chainspec (#3905)
  Ensure all parachain configuration extrinsics are operational (#3912)
  ...
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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. D3-trivial 🧸 PR contains trivial changes in a runtime directory that do not require an audit.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants