shotgun api key not saved

anon84816811 · August 26, 2014, 5:40pm

Hello… starting to test the shotgun setup in Deadline…

any help would be appreciated! thanks!

Deadline Version: 7.0.0.26 R (c53f90c95)
OSX 10.9.4

Steps to Reproduce:
(shotgun never configured on fresh repository)
Opened Deadline Monitor
Tools->Super User Mode
Tools->Configure Events…
Filled in URL, API Script Name, and API Application Key
Box and text labels turn green
Clicked ok

Result:
reopen Configure Events…
everything appears except API Application Key

Testing with Scripts->ShotgunTestConnection Returns the Following error:
Deadline’s Shotgun integration does not seem to be configured properly.
The following errors must be rectified in the Shotgun Event Plugin configuration before proceeding:
ERROR: The Shotgun Script Key has not been set.

jgaudet · August 26, 2014, 8:14pm

Hmmm, I can’t seem to reproduce this on my end

It’s weird that this is only happening for a single setting, since we’re not really doing any kind of validation on individual fields when saving. Does anything show up in the Monitor’s Console panel (View -> New Panel -> Console) after you try saving the settings?

Another thing you can do is check the contents of the ‘events/Shotgun/Shotgun.dlinit’ file; this is the text file where we store the Shotgun settings set in the dialog. I’m not sure what would be wrong with the file; maybe some garbage characters got in there somehow.

While you have the file open, try manually adding your key on the line “ShotgunScriptKey=”, after the ‘=’ sign. Make sure there are no trailing or leading whitespaces when you do this.

If, after doing that, the API key is still getting wiped, something super weird must be going on…

Hope this helps!

Jon

anon84816811 · August 27, 2014, 3:13am

I opened the Monitor’s Console panel and nothing happened when I tried it again. popping open the file… somehow a EOL /n had gotten in there and now it looks like this:

ShotgunScriptKey= 75...deba6 75...deba6= 75...deba6= 75...deba6= 75...deba6= 75...deba6= 75...deba6= 75...deba6=

long keystring replaced with … to hide my key
deleting all this and reopening monitor, then pasting in the key with no EOL now worked.

jgaudet · August 27, 2014, 7:00pm

Aaah, I see, that explains it. I’ll log an internal ticket to sanitize text input in our config forms, so stuff like this doesn’t happen =)

Cheers,
Jon

anon84816811 · September 1, 2014, 3:54am

cool thanks!

raitch · October 1, 2014, 1:06pm

Was this issue fixed in beta 4 build 36 ?
Thanks.

rrussell · October 1, 2014, 1:54pm

It was fixed in beta 3.

Cheers,
Ryan

raitch · October 1, 2014, 2:17pm

Great - thanks for the confirmation!

raitch · October 2, 2014, 3:11pm

Hmmm…
We just upgraded from build 26 to 36 across our studio.
Repo is on WIN
Client is on Mac
I did get it to work but I had to edit the text file manually; the GUI entry technique did not work.
It wasn’t a clean new install so maybe that factored into it.
Just wanted to let you know - is there a test we can try for you?

rrussell · October 2, 2014, 3:28pm

I think I know the issue. We’re sanitizing on read, not write, and since they’re on new lines, they get ignored. We’ll have to sanitize on write as well.

Thanks!
Ryan