-
Notifications
You must be signed in to change notification settings - Fork 247
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
Upgrade substrate #1198
Upgrade substrate #1198
Conversation
Updated revision to include paritytech/substrate#13372 |
Hm... storage monitor is not supported on Windows for now, I'll make it conditionally compilable and we can restore it fully once paritytech/substrate#13466 lands |
78efd83
to
6237f43
Compare
10783e7
to
9cf171c
Compare
Okay, now I see where the issue is. So yeah... waiting for paritytech/substrate#13466 now. |
9cf171c
to
4e66066
Compare
Replaced workarounds with latest Substrate ( |
Now wasmi crashes on Windows: paritytech/substrate#13487 |
Force using the wasmtime everythere in substrate-test-runtime-client.
Upgrade substrate fix
# Conflicts: # crates/subspace-archiving/Cargo.toml # domains/client/domain-executor/src/core_bundle_processor.rs # domains/client/domain-executor/src/system_bundle_processor.rs # domains/client/domain-executor/src/xdm_validator.rs
Most of the changes like last time are related to upstream refactoring from
BlockId<Block>
toBlock::Hash
. Also node storage monitor was added.Merged into out
subspace-v3
fork cleanly, continues to work with Gemini 3c without issues.Code contributor checklist: