This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Graceful exit when invalid CLI flags are passed #6485
Labels
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone
Comments
ngotchac
added
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
labels
Sep 8, 2017
rphmeier
changed the title
Panic when invalid CLI flags are passed
Graceful exit when invalid CLI flags are passed
Sep 8, 2017
panicking seems a little drastic. a helpful message and exit should be fine |
I'm not sure what this ticket is about.
It always exits with a non- |
It used to work this way, but doesn't actually on |
True. |
5chdn
added
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
and removed
P5-sometimesoon 🌲
Issue is worth doing soon.
labels
Oct 11, 2017
So, this is caused by https://github.com/paritytech/parity/blob/master/parity/cli/usage.rs#L540 : .global_setting(AppSettings::AllowLeadingHyphen) // allow for example --allow-ips -10.0.0.0/8 If we remove this setting then It's strange because when we're using AllowLeadingHyphen,
edit: fix on its way |
axelchalon
added a commit
that referenced
this issue
Oct 11, 2017
debris
added a commit
that referenced
this issue
Oct 12, 2017
Graceful exit when invalid CLI flags are passed (#6485)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Parity should panic and exit with an non-0 exit code when invalid CLI flags are passed.
The text was updated successfully, but these errors were encountered: