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

Missing stack trace on ValueError #99

Closed
mat128 opened this issue Feb 18, 2016 · 0 comments · Fixed by #101
Closed

Missing stack trace on ValueError #99

mat128 opened this issue Feb 18, 2016 · 0 comments · Fixed by #101
Assignees

Comments

@mat128
Copy link
Contributor

mat128 commented Feb 18, 2016

When a ValueError occurs (such as int('test')), no stack trace is available.

@mat128 mat128 changed the title Missing stack trace when something happens Missing stack trace when an error occurs Feb 18, 2016
@lindycoder lindycoder self-assigned this Feb 18, 2016
@mat128 mat128 changed the title Missing stack trace when an error occurs Missing stack trace on ValueError Feb 18, 2016
lindycoder pushed a commit to lindycoder/netman that referenced this issue Feb 18, 2016
This way we know what to handle and what to not handle, catching ValueError was hiding illegitimate error for which a stack trace and a 500 error was required

fixes internap#99
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants