-
Notifications
You must be signed in to change notification settings - Fork 856
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
Make node syncing messages configurable. #2110
Comments
This entire |
Are you suggesting just not to use this function at all and spawn the necessary tasks separately? Or you have something else in mind? |
I hit another annoyance with The difficulty with What do you think about exposing those functions publicly? I can send a PR. |
Sounds fine to me. |
This allows to build a custom version of `spawn_tasks` with less copy-paste required. Resolves #2110 --------- Co-authored-by: Bastian Köcher <[email protected]>
This allows to build a custom version of `spawn_tasks` with less copy-paste required. Resolves paritytech#2110 --------- Co-authored-by: Bastian Köcher <[email protected]>
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Motivation
Currently, we have node syncing messages produced by the
InformantDisplay
fromsc-informant
crate withinsc-service
. There is no way to alter the messages or change their periodicity which could be suboptimal for some parachains.Request
I suggest making
InformantDisplay
configurable in thesc_service
crate.Solution
Make
SpawnTasksParams
fromsc_service
accept an optional additional parameter.There are several variants for this parameter:
sc_informant::build()
.Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered: