-
Notifications
You must be signed in to change notification settings - Fork 91
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
Update to Polkadot v0.9.29 #1041
Conversation
151f160
to
a74f58e
Compare
a74f58e
to
4449b14
Compare
I'm pulling my hair out for this getrandom issue 🤯 all I find online suggests adding an explicit dependency on that crate, like so:
I've tried that + adding When I do that, then the error becomes (in short):
I was trying following the same logic and playing with the default-features and /std for secp256k1 but just spinning my wheels at this point. @mikiquantum @branan do you maybe have some cue on how to tackle this one? Edit: I have updated our internal repos that also depend on the parity repos with Edit 2: interesting lead: interlay/interbtc#504 (comment) |
e74d77b
to
b5fcafb
Compare
Got it! So get around the Past that point I bumped into the At this point I built each runtime separately and realised that cc @gruberb |
@gruberb I've just cleaned up the changes I added for the |
runtime/centrifuge/src/lib.rs
Outdated
@@ -1252,8 +1252,8 @@ impl_runtime_apis! { | |||
let weight = Executive::try_runtime_upgrade().unwrap(); | |||
(weight, RuntimeBlockWeights::get().max_block) | |||
} | |||
fn execute_block_no_check(block: Block) -> Weight { | |||
Executive::execute_block_no_check(block) | |||
fn execute_block(block: Block, state_root_check: bool, try_state: TryStateSelect) -> Weight; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: Have to figure out how this is actually used vs. and if we used execute_block_no_check
in the past.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ASAIR the no-check prevents digest checks for block building. Do not think we can anything about the change and hopefully parity has this correctly ^^
1fd7b10
to
f59d6e9
Compare
This PR is finally ready for review! I am currently trying to figure out why one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some questions and some feature flags that must be set true in dev. Furthermore, there are a few lines that need to be changed in the integrations-tests for instanciating a timestamp.
But damn, this was a lot of work! Thanks, @gruberb!!
Let's commit this and see if the CI gets the same build error.
This moves the issue down to failed to run custom build command for `secp256k1-sys v0.6.1`. This GH issue suggests it may be an issue with M1 support: tomusdrw/rust-web3#543
Having it on the root Cargo.toml is enough :)
I just realized that we probably only needed this because we were importing dependencies from pallet-claims with the default-features enabled, which caused getrandom from being pulled with enabled std WHILE trying to build it for wasm, which caused the failing compilation error. Now that those dependencies are imported correctly with default-features = false, we in fact don't need this getrandom workaround anymore :)
* loans benchmarks: ensure generated rates match our rules * integration tests: Do not create duplicate NFT class I have no idea how either of thesee was working before ¯\_(ツ)_/¯
395f53c
to
db83730
Compare
All green now, and comments from @mustermeiszer resolved! Should we try to merge this soon? @branan @NunoAlexandre |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gruberb Just a small change needed. Then I will make this green ^^
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for adapting.
Description
Upgrading
centrifuge-chain
to the latest Polkadot version,v0.9.29
Fixes #976
Changes and Descriptions
This change also includes the upgrade to
v0.9.28
: https://github.com/paritytech/polkadot/releases/tag/v0.9.28Type of change
Please delete options that are not relevant.
How Has This Been Tested?
cargo build --release
cargo test --workspace --release --features test-benchmarks,try-runtime,runtime-benchmarks
Checklist:
parachain
branch