-
Notifications
You must be signed in to change notification settings - Fork 25
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
fix: hrmp #278
base: main
Are you sure you want to change the base?
fix: hrmp #278
Conversation
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## main #278 +/- ##
==========================================
- Coverage 70.47% 69.91% -0.56%
==========================================
Files 54 55 +1
Lines 9250 9325 +75
Branches 9250 9325 +75
==========================================
+ Hits 6519 6520 +1
- Misses 1737 1811 +74
Partials 994 994
|
729b5b6
to
6beb4ba
Compare
1df2ea6
to
063b598
Compare
063b598
to
3bc1881
Compare
* dispatch kill tx * paseo-local metadata * chore: address hrmp channels at creation * clean unnecessary deps * fix: don't wait for finalisation * Provide documentation
3bc1881
to
deffdbd
Compare
Rebased. |
I noticed that when I build the chain-spec-generator and used it to spin up a local network the parachains were not producing blocks. Used the release binary and it worked. Not 100% sure I did something wrong or it is the chain spec generator. Just put it here so that we are aware. |
Ensures hrmp channels work seamlessly via
pop-cli
.Note that it currently requires a build of the
chain-spec-generator
from https://github.com/r0gue-io/paseo-network-runtimes. See open questions below.Test using:
cargo run -- up parachain -f ./tests/networks/pop.toml --verbose
Open question: