fix: system parachain chain spec generator #149
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Tests have finished. BuildStatus: success Relay ChainStatus: failure System ParachainsStatus: success Integration TestsStatus: failure ❌ Some tests have failed. Please check the details above for more information. |
|
The change was introduced to avoid matching with any of the included spec ids in the sdk Let's revisit if that is not the case anymore and follow up accordingly here. |
hbulgarini
approved these changes
Oct 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running
pop up parachainwith the latest paseo release (v1.3.1) I was getting an issue generating the chain-spec. Comparing the old one generated (v1.2.6) with the new one I noticed the difference was with the id:vs
Fixed to use
asset-hub-paseo-local.