-
Notifications
You must be signed in to change notification settings - Fork 131
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
Generalize error text #1388
Generalize error text #1388
Conversation
Right now, each time there is an error while executing `substrate-relay` it will be reported as: ERROR bridge Failed to start relay: <Actual cause of error> This is the case even if the invoked command did not have anything to do with starting a relayer. Thus this removes this text. Now something like this would be written: ERROR bridge <Actual cause of error>
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.
Imo it's more about binary (which is called substrate-relay
), not the subcommand that actually perform relay-related tasks. I'll approve - feel free to merge if you think it's better than what we have now
ah, it's the same as in
well, that was not obvious. Also, I think it still does not have anything to do with "starting". |
Perhaps, 1260f5d makes more sense? |
* Companion: Bump syn * Update Substrate & Polkadot
* Generalize error text Right now, each time there is an error while executing `substrate-relay` it will be reported as: ERROR bridge Failed to start relay: <Actual cause of error> This is the case even if the invoked command did not have anything to do with starting a relayer. Thus this removes this text. Now something like this would be written: ERROR bridge <Actual cause of error> * Use substrate-relay prefix
* Generalize error text Right now, each time there is an error while executing `substrate-relay` it will be reported as: ERROR bridge Failed to start relay: <Actual cause of error> This is the case even if the invoked command did not have anything to do with starting a relayer. Thus this removes this text. Now something like this would be written: ERROR bridge <Actual cause of error> * Use substrate-relay prefix
Right now, each time there is an error while executing
substrate-relay
it will be reported as:
This is the case even if the invoked command did not have anything to do
with starting a relayer. Thus this removes this text. Now something like
this would be written: