Skip to content

configuration errors are hard to diagnose #19

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
Open
lnhrdt opened this issue Mar 14, 2018 · 1 comment
Open

configuration errors are hard to diagnose #19

lnhrdt opened this issue Mar 14, 2018 · 1 comment

Comments

@lnhrdt
Copy link

lnhrdt commented Mar 14, 2018

Unsure if handling errors gracefully is a priority for this project but I thought I'd report my experiences anyway.

When the required configuration artifact is omitted, the error is ambiguous:

screen shot 2018-03-13 at 19 34 01

When the credentials are incorrect, the error is also ambiguous:

screen shot 2018-03-13 at 19 34 13
@patrickcrocker
Copy link
Member

Thx for opening an issue. I'll incorporate some better error checking/messages in upcoming releases.

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
2 participants
@patrickcrocker @lnhrdt