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

Internal error reporting should be better #4

Open
LionsPhil opened this issue May 23, 2015 · 0 comments
Open

Internal error reporting should be better #4

LionsPhil opened this issue May 23, 2015 · 0 comments
Assignees
@LionsPhil
Labels
enhancement
Milestone
v0.3: No more SSH

Comments

@LionsPhil
Copy link
Owner

At the moment, when a web service API call fails, Plumage generally just throws and ends up displaying a 500 error, with some detail in the logs. While semi-appropriate for a public-facing system, this is a technical internal one, and having "contacting the Master component failed", or "Master reports Client failed to spawn plumage_run" or such is more useful.
@LionsPhil LionsPhil added this to the v0.3: No more SSH milestone Jul 3, 2015
@LionsPhil LionsPhil self-assigned this Jul 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LionsPhil LionsPhil

Labels
enhancement
Projects
None yet
Milestone
v0.3: No more SSH
Development

No branches or pull requests
1 participant
@LionsPhil