Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Better error reporting on the command line #889

Closed
szabgab opened this issue Feb 7, 2013 · 3 comments
Closed

Better error reporting on the command line #889

szabgab opened this issue Feb 7, 2013 · 3 comments

Comments

@szabgab
Copy link
Contributor

szabgab commented Feb 7, 2013

By mistake I ran dancer -a Name in a read-only directory. It gave me the options, but it did not tell me why did it fail. Spending 10 frustrated minutes on this was not fun.

Could there be more specific error messages explaining why did the command fail?

There is a -message flag for pod2usage(). I think that could be used for this.

(encountered in Dancer 1.311)
@mokko
Copy link
Contributor

mokko commented Apr 3, 2013

Might be related to GH #706

@mokko
Copy link
Contributor

mokko commented Apr 3, 2013

seems already fixed, see GH #897. Close this issue?

@xsawyerx
Copy link
Member

xsawyerx commented Apr 3, 2013

@mokko thanks again! I owe a beverage for all the triage you've done! :)

@xsawyerx xsawyerx closed this as completed Apr 3, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@szabgab @xsawyerx @mokko