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.

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

Print the error detail from the cli #733

Open
d-perl opened this issue Nov 28, 2024 · 3 comments
Open

Print the error detail from the cli #733

d-perl opened this issue Nov 28, 2024 · 3 comments
Labels
bug Something isn't working
Milestone

Comments

@d-perl
Copy link
Contributor

d-perl commented Nov 28, 2024

When a user does blueapi controller run <...>, getting a message which simply says "Error 422" is not very helpful. The server does define error response detail, this should be printed in the console.

@d-perl d-perl added the bug Something isn't working label Nov 28, 2024
@callumforrester
Copy link
Contributor

@stan-dot has previously expressed a preference for terse output, maybe we should just add a --verbose flag and let the user decide?

@stan-dot
Copy link
Contributor

I believe this is the connected issue

#206

where in the comment thread we've got this

#206 (comment)

and the PR has this:
image

fwiw we could add formatting like in here: https://github.com/DiamondLightSource/blueapi/pull/527/files

@d-perl
Copy link
Contributor Author

d-perl commented Nov 29, 2024

Sure, I'm ok if it's behind a flag, I just don't want to have to run the server in a debugger just to find out how my params are wrong

@callumforrester callumforrester added this to the 1.0.0 milestone Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants