Feature request #10773
Processing: more meaningful error messages
|Pull Request or Patch supplied:||No||Resolution:||fixed/implemented|
Can we have a more user friendly error message for many of the processing stuff? e.g. I get the following
Error executing algorithm 3 'NoneType' object has no attribute 'dataProvider' See log for more details
1 - see log for more details seems to be out of place since the error is displayed on the log itself
2 - In this case the error is due to Grass Installation directory not set correctly. Would be better if the message would be something like
Error executing algorithm 3, Grass Directory not found please install or set path (or something along that line)
The cryptic message wouldn't be easy to debug why algorithm fails
#2 Updated by Giovanni Manghi over 3 years ago
- Priority changed from Normal to Low
- Target version set to Future Release - Nice to have
- Subject changed from Processing Log Error to Processing: more meaningful error messages
- Tracker changed from Bug report to Feature request
I guess that potentially any tool can throw a different error, catching all them and returning a specific error message could not be easy to do. Eventually we can try put together a list of the most common/similar ones and return the same messages.
please try choose more meaningful subjects, otherwise it is hard to understand what is about the ticket.
#3 Updated by Victor Olaya over 3 years ago
Please, notice that there are errors that are due to some wrong user interaction (like the one you mention with the GRASS installation) and other that are real errors, real bugs in Processing. The one that you are seeing is clearly one of them, since the variable in the modeler should never get that None value.
When the message tells you to see the log, it is because in the log you will find the full error trace, which is helpful to find and fix the bug. That is not maybe user friendly, but if it is a bug, there is nothing that the user can do, except providing the developers all the information that is possible to fix it. The message is, instead, dev-friendly.
Hope this helps.
BTW, if you can open a new issue with that problem you are having with the modeler, providing more detail, it would be great. Thanks!