-
Notifications
You must be signed in to change notification settings - Fork 136
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
Error messages not fully captured #157
Comments
Also causes #162 |
Similar problem today: Terjadi kesalahan perhitungan: 2 Toggle traceback...
The problem here is to do with key error in the dictionary damage_curves |
See also issue #174 |
Reopenied as we still have the 'toggle twice issue'' |
Still not seeing the error message in relation to issue #174 - maybe there isn't one? E.g. either Calculation Error: Input layers did not overlap |
Ok I believe this is all neat and tidy now with no double exceptions and the second tier exception being reported as a string. I am going to have one more little pass at beautifying the stringified exception that is pulled over from SAFE by putting the trace items into an html list. |
Looks good! |
If an error occurs, it is currently reported in the GUI and there is an option to see the stack trace.
However, the error message is not the full Python message.
For example if an impact function has a key error (e.g non existing key 'public_building' in a dictionary), the GUI reports:
No impact layer was calculated. Error message: Calculation error encountered: Problem:
'public_building'
It should have said:
KeyError: 'public_building'
The stack trace is great except that the label Toggle traceback appears twice (and so does the Problem tag)
This is not urgent, but would be good to sort out as it helps development.
The text was updated successfully, but these errors were encountered: