Monitor slave window not showing slaves

Deadline
1

Hello,

We have a big issue, since a few hours ago (while I was setting up power management, but not sure it is related).
The Slave panel is not displaying all our slaves, or not all the information about it (see the screenshot).
I restarted pulse, I restarted my monitor, my computer, but nothing change and it does happen to everyone who restart the monitor now.
Sometimes when I restart it, it does not even show any slaves. What should I do ?

bug_slave_window.jpg
bug_slave_window.jpg1108×357 102 KB

thanks

F.

2

I guess it is related to the power management scheduling (which I already had some kind of issue with not updating slave status correctly, see here : viewtopic.php?f=11&t=11653).

Because, by restarting all the slaves, did update the slave panel correcly.

Any suggestions ?

3

Hello Francois,

Could I have you open up the console from the view/new panels menu, and paste anything you find in there into here for me? Thanks.

4

This is what happen when I open the slave panel and have some issue to display everything :

2014-04-24 10:36:32:  Traceback (most recent call last):
2014-04-24 10:36:32:    File "DeadlineUI\UI\Models\SlaveListProxyModel.py", line 45, in invalidate
2014-04-24 10:36:32:    File "DeadlineUI\UI\Models\SlaveListProxyModel.py", line 124, in onModelReset
2014-04-24 10:36:32:  KeyError: u''
2014-04-24 10:36:39:  Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
2014-04-24 10:37:53:  Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
5

Ah, this is the same issue as before with how we handle the decimal point.

Le virgule nous cause des problèmes!

6

Is there any quick fix I can do in the python script. This is a big issue for us.

7

This is within compiled Python, so it can’t be patched without our build system.

There is the temporary solution mentioned in your other thread here:
viewtopic.php?f=11&t=11689

I’ll e-mail the guy who fixed this and ask if it’s possible to replace the PYC file somehow without breaking everything.

8

A follow up here. I was reminded that while this error is happening within the Python code, the actual cause of this is deeper, within our compiled code.

We can get you on the beta though. Can you e-mail me at edwinamsler@thinkboxsoftware.com so I can get the ball rolling on getting you ready with 6.2?