Hi,
we are using deadline 10.0.4.2 and have some custom jobs sent through python api that run a python plugin. They all render to complete.
But whenever we try to select one of this jobs and open the job dependency view we get in the console the following error:
2019-05-24 09:25:07: Traceback (most recent call last):
2019-05-24 09:25:07: File “UI/DisplayWidgets/JobDependencyGraph.py”, line 868, in createVisualRepresentation
2019-05-24 09:25:07: File “UI/DisplayWidgets/JobDependencyGraph.py”, line 936, in createDependencyGraph
2019-05-24 09:25:07: NameError: global name ‘validEventNames’ is not defined
On the contrary, if we choose to open the dependency view on a deadline maya or nuke job, the window opens correctly and we are able to see the dependency tree.
Our python plugin is a custom one, with some tweaks, maybe the error has to do with this?
The UI/DisplayWidgets/JobDependencyGraph.py is part of the Deadline Monitor python api so it comes compiled as pyc and im not able to see the code and spot de problem…
i think it’s something in my deadline python plugin that deadline doesnt like when showing the dependency view.
The plugin works ok, the jobs render all ok, the dependencies in the jobs are all respected when queueing them to the nodes… everything works ok except for this dependency graph view…
And since i send quite a number of inter dependent jobs, it would be very nice to be able to consult this graph…
Is there a more specific forum where i can reach out deadline programmers?
They do visit here, though it seems that lately they’ve been busy with something and not as active in the forums. Then there’s support ticket option which I assume would be faster way to contact them.
What kinds of jobs are you sending trough this custom python plugin? You might have already done this but, perhaps trying to nail down what the submission differences are with the native plugin (if exists) and the custom one?
I took a quick look at this , its trying to iterate through a list of events that hasn’t been defined yet. @eamsler.
I can repeat the error your getting, by making one of the events in the event settings to “opt-in”, then on the job mark that event as opt in.
This then causes the error your seeing, and the job dependency graph fails to build because that error is high enough up that its before it loads and displays all the other jobs.
I would try in the event settings , in the tools menu, turning off any of the events that are currently set to optin, to either globally enabled or disabled.