8.0 Monitor error in Manage User Group dialog

Deadline
1

8.0.10.4 on Fedora 19

When I open the Manage User Groups dialog and click on a user group other than Everyone (that I’ve made menu or script permission changes to), I get this in the console:

2016-10-25 10:10:36: Traceback (most recent call last): 2016-10-25 10:10:36: File "DeadlineUI/Forms/PermissionManagementForm.py", line 565, in comboValueModified 2016-10-25 10:10:36: File "DeadlineUI/Forms/PermissionManagementForm.py", line 260, in UpdateColor 2016-10-25 10:10:36: File "DeadlineUI/Forms/PermissionManagementForm.py", line 256, in UpdateColor 2016-10-25 10:10:36: KeyError: <Deadline.Permissions.Feature object at 0x7f8a08372dd0>

2

I’m waiting on getting a Fedora 19 VM up in OpenStack so that I can spin off VMs for each of these problems. Keep them coming.

3

This doesn’t really seem like a platform-specific issue… It looks like a bug in the UI code.

4

Hmm… You’re likely right that it’s not Linux specific.

I can’t reproduce it over here though. I made a handy video of me poking at stuff. Note that I’ve got a half-done event script that’s throwing its own fuss that’s not related to this at all.

youtu.be/Tq8WVu3MfAY

Do you have layouts specified in the user groups or anything that’s not defaults? I’m not quite sure how to reproduce over here. I’ll take a quick look at the Python code in question too.

5

Update here, it looks like we hit this back in May 2015 internally here, but again weren’t able to reproduce it either. Tips and tricks for reproducing would be great.

6
  1. Tools -> Manage User Groups, and add a new group (say, “test”).
  2. Go to the Scripts tab.
  3. Change the “General Scripts” pulldown from Enabled to Disabled. I see the error.
  4. Now, if I re-open the Manage User Groups dialog and just click on the “test” group, I see the error.
7

Thanks! I can reproduce. Logged as bug to be fixed.

8

Huh. I can’t over here (OS X 10.10.5)… Mike, want to compare notes tomorrow morning?

9

I made a video and shared internally to demonstrate the issue. I think the winning combo is to also have one or more custom scripts located under the /custom/ directory structure.

10

This one also got fixed today.