-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
No Error and exist code when using pkg/errors standard package #632
Comments
I have noticed that only the errors of type ExitCoder interface are managed and the errors from the standard library are ignored For example: return cli.NewExitError("Error message", 1) err := errors.New("errors")
return cli.NewMultiError(err) I think the standard errors should be used as well |
I encountered this issue in mac system, but it is OK in linux system. |
Hi @ehernandez-xk, Apologies for the delay. #496 added functionality which was later deemed to be backwards incompatible and less flexible for users of the library, backed out in #595. Presently, if you want to have the application exit automatically, you should use The error is bubbled up so you can still exit at the top-level if desired with something like:
Let me know if this helps! |
Thank you @jszwedko |
Hi All,
Here is the snippet to reproduce the error
Command line: (The error is not printed)
This issue was added in 9e5b048 commit
and mentioned in #496 PR
By the way, Thanks for this awesome package.
The text was updated successfully, but these errors were encountered: