Bug report #16656

python error in Processing result viewer

Added by Giovanni Manghi over 4 years ago. Updated over 4 years ago.

Assignee:Victor Olaya
Affected QGIS version:2.18.9 Regression?:Yes
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:not reproducable
Crashes QGIS or corrupts data:No Copied to github as #:24556


Traceback (most recent call last):
File "C:/OSGEO4~1/apps/qgis-rel-dev/./python/plugins\processing\ProcessingPlugin.py", line 166, in openResults
dlg = ResultsDialog()
File "C:/OSGEO4~1/apps/qgis-rel-dev/./python/plugins\processing\gui\ResultsDialog.py", line 57, in init
File "C:/OSGEO4~1/apps/qgis-rel-dev/./python/plugins\processing\gui\ResultsDialog.py", line 77, in loadResults
content = f.read()
File "C:\OSGEO4~1\apps\Python27\lib\codecs.py", line 671, in read
return self.reader.read(size)
File "C:\OSGEO4~1\apps\Python27\lib\codecs.py", line 477, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xc1 in position 209: invalid start byte

Seen this on 2.18.9 (nightly) on Windows.


#1 Updated by Alexander Bruy over 4 years ago

  • Status changed from Open to Feedback

Can you provide sample? As I can see, it already opens file using unicode. Probably some algorithm writes results without proper encoding or output file is broken.

#2 Updated by Giovanni Manghi over 4 years ago

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

Cannot replicate in a consistent way. Will reopen if is the case (it was happening sometimes with a specific postgis layer, but not with its shapefile counterpart, and was using the "v.report" module).

Also available in: Atom PDF