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

Docker exceptions are very nondescript since v0.6.0 #55

Closed
vilhelmprytz opened this issue Apr 14, 2020 · 0 comments
Closed

Docker exceptions are very nondescript since v0.6.0 #55

vilhelmprytz opened this issue Apr 14, 2020 · 0 comments
Labels
new-feature New feature

Comments

@vilhelmprytz
Copy link
Member

Is your feature request related to a problem? Please describe.
If something goes wrong when Wilfred tries to create a new server (e.g. create the Docker container) and something goes wrong, Wilfred will exit with a very nondescript exception message since v0.6.0. This makes it hard to debug what caused the issue.

Describe the solution you'd like
By default, Wilfred should be a little bit more specific when it comes to printing what went wrong. Then I'd also like to have a verbose argument (-v) and Wilfred can just do the normal Python traceback.

Describe alternatives you've considered
None.

Additional context
This issue was introduced in v0.6.0. Prior versions handle exceptions differently.

@vilhelmprytz vilhelmprytz added the new-feature New feature label Apr 14, 2020
vilhelmprytz added a commit that referenced this issue Apr 15, 2020
(with #55 fixes)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-feature New feature
Projects
None yet
Development

No branches or pull requests

1 participant