Skip to content

Generalize error text#1388

Merged
svyatonik merged 2 commits intomasterfrom
pep-generic-error
May 5, 2022
Merged

Generalize error text#1388
svyatonik merged 2 commits intomasterfrom
pep-generic-error

Conversation

@pepyakin
Copy link
Copy Markdown
Contributor

@pepyakin pepyakin commented May 4, 2022

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>

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>
@pepyakin pepyakin added the A-chores Something that has to be done, as part of regular maintenance label May 4, 2022
Copy link
Copy Markdown
Contributor

@svyatonik svyatonik left a 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

@pepyakin
Copy link
Copy Markdown
Contributor Author

pepyakin commented May 5, 2022

ah, it's the same as in

find not-exists
find: ‘not-exists’: No such file or directory

well, that was not obvious. Also, I think it still does not have anything to do with "starting".

@pepyakin
Copy link
Copy Markdown
Contributor Author

pepyakin commented May 5, 2022

Perhaps, 1260f5d makes more sense?

@svyatonik svyatonik merged commit 4eb5db7 into master May 5, 2022
@svyatonik svyatonik deleted the pep-generic-error branch May 5, 2022 12:52
svyatonik pushed a commit that referenced this pull request Jul 17, 2023
* Companion: Bump syn

* Update Substrate & Polkadot
serban300 pushed a commit to serban300/parity-bridges-common that referenced this pull request Mar 27, 2024
* 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
serban300 pushed a commit to serban300/parity-bridges-common that referenced this pull request Apr 8, 2024
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-chores Something that has to be done, as part of regular maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants