Bug report #20609

Error in Processing modeller

Added by Paolo Cavallini about 5 years ago. Updated almost 5 years ago.

Affected QGIS version:3.4.1 Regression?:Yes
Operating System:Debian Sid Easy fix?:No
Pull Request or Patch supplied:No Resolution:fixed/implemented
Crashes QGIS or corrupts data:No Copied to github as #:28429


when creating a model in Processing (QGIS 3.4.1), if one param is missing (band number in gdal contour), an error is thrown [0] before showing the proper error message.


An error has occurred while executing Python code: 


Traceback (most recent call last):
  File "/usr/local/src/qgis/QGIS/build-qgis341/output/python/plugins/processing/gui/wrappers.py", line 208, in widgetValue
    return self.value()
  File "/usr/local/src/qgis/QGIS/build-qgis341/output/python/plugins/processing/gui/wrappers.py", line 1764, in value
    return self.comboValue(validator)
  File "/usr/local/src/qgis/QGIS/build-qgis341/output/python/plugins/processing/gui/wrappers.py", line 174, in comboValue
    raise InvalidParameterValue()

Python version: 3.6.7 (default, Oct 21 2018, 08:08:16) [GCC 8.2.0] 
QGIS version: 3.4.1-Madeira Madeira, f7bba750bc 

Python Path:

    /home/paolo/.local/share/QGIS/QGIS3/profiles/Ghent course/python
    /home/paolo/.local/share/QGIS/QGIS3/profiles/Ghent course/python/plugins
    /home/paolo/.local/share/QGIS/QGIS3/profiles/Ghent course/python


#1 Updated by Giovanni Manghi about 5 years ago

  • Regression? changed from No to Yes
  • Priority changed from Normal to High
  • Category changed from Processing/GDAL to Processing/Modeller

#2 Updated by Victor Olaya almost 5 years ago

  • Status changed from Open to Feedback

Cannot reproduce.

I create a model and add a raster layer. When later I add the contour algorithm, the band parameter is populated with "1". I delete that value, leaving the box empty, and try to add the algorithm, but it correctly shows the warning message

Checking the code, the exception that you report is being correctly catched. The corresponding code is there since 2017...

Can you provide a more detailed explanation on how to reproduce the error?

#3 Updated by Paolo Cavallini almost 5 years ago

  • Resolution set to fixed/implemented
  • Status changed from Feedback to Closed

I can confirm, now the correct error is displayed.

Also available in: Atom PDF