Plotly error on pipeline restart

[brollb]

I executed a pipeline, opened a job and viewed a plot, then restarted the pipeline and got the following error:

I suspect the plot was still trying to update and wasn't properly destroyed (maybe ignoring the "embedded" value)?

[brollb]

Technically, you could split this into 2 issues:

• plotly visualizer shouldn't be updating when I am viewing the pipeline again
• plotly graph should probably handle this more gracefully. That is, it shouldn't throw an error if I have it open when the execution is restarted

[umesh-timalsina]

Do you have the operation that caused this error? Like if matplotlib is in interactive mode vs regular mode?

[brollb]

I was using the Train operation from the cifar10 example. However, I suspect it is an issue at the UI level rather than matplotlib. (Since I was viewing the execution when it occurred, I didn't expect that code to be running at all.) Here is a more detailed list of the actions I took:

• execute a training pipeline
• an operation after the training operation failed (no other operations had any plotting)
• opened the "Train" job and viewed the training loss
• went back to the execution view and restarted it

Since the Plotly JSON was valid when I viewed it and the Train operation had finished, I suspect this is just an issue at the visualizer level.

[umesh-timalsina]

I discovered a new error while working to resolve this issue:

Replication steps using devProject:

1. Go to ScatterPlots3D operation in devProject
2. Execute PlotsPipeline operation, view the graph and restart the execution from the console output view
3. Go back the ExecutionView, which will result in the following error:

Uncaught (in promise) TypeError: node.getId is not a function
    at ExecutionViewControl.Execute.runExecutionPlugin (Execute.js:52)
    at Execute.js:404
    at _fulfilled (q.js:1121)
    at q.js:1150
    at Promise.promise.promiseDispatch (q.js:1083)
    at q.js:891
    at runSingle (q.js:404)
    at flush (q.js:392)
    at onNextTick (q.js:252)
    at Item.run (q.js:154)
Execute.runExecutionPlugin @ Execute.js:52
(anonymous) @ Execute.js:404
_fulfilled @ q.js:1121
(anonymous) @ q.js:1150
Promise.promise.promiseDispatch @ q.js:1083
(anonymous) @ q.js:891
runSingle @ q.js:404
flush @ q.js:392
onNextTick @ q.js:252
Item.run @ q.js:154
drainQueue @ q.js:124
setTimeout (async)
runTimeout @ q.js:42
process.nextTick @ q.js:144
exports.setImmediate @ q.js:245
nextTick @ q.js:447
(anonymous) @ q.js:890
(anonymous) @ q.js:530
become @ q.js:889
deferred.resolve @ q.js:905
(anonymous) @ APIClient.js:68
Request.callback @ superagent.js:1723
(anonymous) @ superagent.js:1550
Emitter.emit @ superagent.js:134
xhr.onreadystatechange @ superagent.js:1817
XMLHttpRequest.send (async)
Request._end @ superagent.js:1884
Request.end @ superagent.js:1788
APIClient._request @ APIClient.js:63
JobOriginClient.getOrigin @ JobOriginClient.js:41
Execute._onOriginBranch @ Execute.js:382
(anonymous) @ Execute.js:402
_fulfilled @ q.js:1121
(anonymous) @ q.js:1150
Promise.promise.promiseDispatch @ q.js:1083
(anonymous) @ q.js:891
runSingle @ q.js:404
flush @ q.js:392
onNextTick @ q.js:252
Item.run @ q.js:154
drainQueue @ q.js:124
setTimeout (async)
runTimeout @ q.js:42
process.nextTick @ q.js:144
exports.setImmediate @ q.js:245
nextTick @ q.js:447
Promise.then @ q.js:1143
Promise.nodeify @ q.js:2320
CoreQ.loadChild @ coreQ.js:32
loadChildrenPattern @ client.js:351
baseLoaded @ client.js:374
loadPattern @ client.js:382
ThrottleListener.execute @ tasync.js:630
(anonymous) @ tasync.js:672
Client.updateTerritory @ client.js:1922
updateDeepForgeNamespace @ globals.js:167
triggerEvents @ backbone.js:371
triggerApi @ backbone.js:356
eventsApi @ backbone.js:155
Events.trigger @ backbone.js:346
set @ backbone.js:516
_WebGMEState.set @ StateManager.js:187
(anonymous) @ WebGME.History.js:59
dispatch @ jquery.js:5183
elemData.handle @ jquery.js:4991