-
Notifications
You must be signed in to change notification settings - Fork 338
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
Start minimal relay node if relay_chain_rpc_url
is set
#2042
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
librelois
added
B5-clientnoteworthy
Changes should be mentioned in any downstream projects' release notes
D3-trivial
PR contains trivial changes in a runtime directory that do not require an audit
not-breaking
Does not need to be mentioned in breaking changes
breaking
Needs to be mentioned in breaking changes
and removed
not-breaking
Does not need to be mentioned in breaking changes
labels
Jan 16, 2023
notlesh
reviewed
Jan 17, 2023
Comment on lines
+815
to
+822
info!( | ||
"Is collating: {}", | ||
if config.role.is_authority() { | ||
"yes" | ||
} else { | ||
"no" | ||
} | ||
); |
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.
This is one of my favorite use cases for the ternary operator:
Suggested change
info!( | |
"Is collating: {}", | |
if config.role.is_authority() { | |
"yes" | |
} else { | |
"no" | |
} | |
); | |
info!("Is collating: {}", config.role.is_authority() ? "yes" : "no"); | |
@purestakeoskar has tested a client based on this PR and it works! We should include it in the next client (v0.29.0) |
notlesh
approved these changes
Jan 17, 2023
imstar15
pushed a commit
to AvaProtocol/moonbeam
that referenced
this pull request
May 16, 2023
…undation#2042) * feat: start minimal relay node is relay_chain_rpc_url is set * editorconfig
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
B5-clientnoteworthy
Changes should be mentioned in any downstream projects' release notes
breaking
Needs to be mentioned in breaking changes
D3-trivial
PR contains trivial changes in a runtime directory that do not require an audit
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.
What does it do?
In #1388 we mapped the new cumulus cli option
relay_chain_rpc_url
, believing that this was enough.But it is also necessary to change the way the relay node is setup, which is the purpose of this PR.
What important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?