-
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
Errors returned by subcommands are ignored by ExitErrHandler #736
Comments
I believe it's a bug. Subcommands are basically recursive apps, and are setup through |
Errors returned by subcommands no longer bypass the toplevel ExitErrHandler Fixes urfave#736
AppVeyer build is failing
|
I opened #763 to address the |
Errors returned by subcommands no longer bypass the toplevel ExitErrHandler Fixes urfave#736
Given that this is from last year, I think I'm comfortable closing it 🙂 feel free to re-open / open a new issue / comment in support if there's still interest here! |
A fix for this was merged here => #856 |
When a subcommand receiver outputs an error, app.ExitErrHandler is not called.
When an error is returned on firstlevel
firstlevel()
, it gets printed. However, if either sub1 or sub2 return it it is not. Not sure if this is a bug or I'm trying to do some weird things, but some insights would be appreciated anyway :)The text was updated successfully, but these errors were encountered: