Actions
Bug #5357
closedMany cases where an exception is caughted and printed w/o any context
Start date:
11/19/2017
Due date:
% Done:
100%
Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
All
I read the instructions above:
Description
There are many cases where an exception is caught and logged to error (log.error(e)) without any context.
This makes it harder than it could be to track down the location of problems (such as split(None) in memedit).
Actions