Error while plotting meshfill plot

[vvpalav]

Exception is caught while plotting mesh fill plot. Entire application crashes after this.

Traceback (most recent call last):
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/vistrails/vistrails/core/modules/vistrails_module.py", line 327, in update
    self.compute()
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/vistrails/vistrails/packages/uvcdat_cdms/init.py", line 1276, in compute
    self.cellWidget = self.displayAndWait(QCDATWidget, input_ports)
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/vistrails/vistrails/packages/spreadsheet/basic_widgets.py", line 247, in displayAndWait
    return spreadsheetWindow.displayCellEvent(e)
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/vistrails/vistrails/packages/spreadsheet/spreadsheet_window.py", line 490, in displayCellEvent
    sheet.setCellByType(row, col, e.cellType, e.inputPorts)
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/vistrails/vistrails/packages/spreadsheet/spreadsheet_tab.py", line 320, in setCellByType
    newCell.updateContents(inputPorts)
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/vistrails/vistrails/packages/uvcdat_cdms/init.py", line 1450, in updateContents
    self.canvas.plot(cgm,*args,**kwargs)
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/vcs/Canvas.py", line 2617, in plot
    a = self.__plot( arglist, keyargs )
  File "/Users/vinayakpalav/Documents/uvcdat_2_2/15-05-05/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/vcs/Canvas.py", line 2730, in __plot
    arglist[1]=MV2.array(g.getMesh())
UnboundLocalError: local variable 'g' referenced before assignment

GUI:

[remram44]

No, I don't see this error

[vvpalav]

Just tried again, same exception. FYI - I have a fresh build of UVCDAT from master.
@aashish24 @doutriaux1 can you please try this one.

[remram44]

You built the wrong branch, release has the fix (#1247)

[vvpalav]

👍 .. I built from master

[doutriaux1]

@aashish24 we should really merge release PR into master as well.

[remram44]

Release branches are usually merged into development... Git really intends for 'master' to be the latest.

[doutriaux1]

I agree.

[doutriaux1]

@aashish24 should I go "dirty" and merge release into master? Or do you (or anyone else) want to take the time to do this cleanly.

[remram44]

If you do, there'll be exactly no difference between release and master... I don't know why there are two branches to begin with.

[doutriaux1]

things are going to go into master soon that shouldn't go into release.