-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Exceptions are not super helpful #3107
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
Comments
Good point on the message. Related to one of the sub-items raised by #2514. I disagree however that reproducing the information already in the stack trace is the job of an exception message. The facility for telling where an exception was thrown is the stacktrace. So I don't view it as problematic that the only thing that shows where an exception was thrown is the stack trace, since that is more or less the entire purpose why the stack trace exists and is part of every exception. |
Do you know why it says 'Boolean' at the end? |
Yep. Properly it should be |
A) would be nice to have space between type and sentence.
B) this exception happened in Concat transform and only indication of that is stack trace.
The text was updated successfully, but these errors were encountered: