Bug report #12745

processing python error

Added by Giovanni Manghi about 9 years ago. Updated about 9 years ago.

Status:Closed
Priority:Severe/Regression
Assignee:Victor Olaya
Category:Processing/Core
Affected QGIS version:master Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:not reproducable
Crashes QGIS or corrupts data:No Copied to github as #:20844

Description

using the GRASS r.drain module I'm getting (master and 2.8.2, Windows and Linux) the following python error that does not seems specific to the GRASS backend, but also I'm not able (at the moment) to trigger it within other modules. The error show regardless the CRS of the layers used. It was not an issue until 2.4.

Traceback (most recent call last):
  File "C:/OSGeo4W/apps/qgis/./python/plugins\\processing\\gui\\AlgorithmDialog.py", line 148, in accept
    if checkCRS and not self.alg.checkInputCRS():
  File "C:/OSGeo4W/apps/qgis/./python/plugins\\processing\\core\\GeoAlgorithm.py", line 410, in checkInputCRS
    crs = dataobjects.getObject(item).crs()
AttributeError: 'NoneType' object has no attribute 'crs'

History

#1 Updated by Giovanni Manghi about 9 years ago

  • Category changed from 94 to Processing/Core

#2 Updated by Paolo Cavallini about 9 years ago

Are we sure this is a blocker?

#3 Updated by Giovanni Manghi about 9 years ago

  • Target version changed from Version 2.10 to Future Release - High Priority

Paolo Cavallini wrote:

Are we sure this is a blocker?

a blocker is by definition a regression, and this is a regression. It was also my understanding that this does not means anymore that it should actually block a release.

#4 Updated by Paolo Cavallini about 9 years ago

In this case, better rename the category (a blocker that does not block does not make much sense, right?).
:)

#5 Updated by Giovanni Manghi about 9 years ago

Paolo Cavallini wrote:

In this case, better rename the category (a blocker that does not block does not make much sense, right?).
:)

this is not my call, I just try keep the tracker clean regardless how the tickets are classified.

#6 Updated by Martin Dobias about 9 years ago

I am unable to replicate - could you please provide a simple test project?

#7 Updated by Martin Dobias about 9 years ago

  • Status changed from Open to Feedback

#8 Updated by Giovanni Manghi about 9 years ago

  • Resolution set to not reproducable
  • Status changed from Feedback to Closed

I also cannot replicate it anymore.

Also available in: Atom PDF