Warning when submitting Nuke script: Key-Value pair not supported

Deadline
1

Hello Deadline community,

I’m running into an issue after upgrading to 10.0.26.0 (from 10.0.23.4) where submissions from Nuke to Deadline are generating excessive number of warnings.

Submissions 10.0.23.4 clients to repository do not induce this issue, whereas 10.0.26.0
clients do generate these errors (Repository is at 10.0.26.0)

Any thoughts as to what might be generating this issue?

Deadline Command 10.0 [v10.0.26.0 Release (4e29e465c)]

Submitting to Repository: P:\DeadlineRepository10

Submission Contains No Auxiliary Files.

Result=Success
JobID=5d11291e9ef410254401a2f8

The job was submitted successfully, but there were some warnings:

  • Key-value pair not supported: ‘AWSAssetFile50’=’[value global.font_path]/AlrightSans-Regular-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile51’=‘P:/VFX_ELEMENTS/nuke_startup/fonts/alright-sans/’
  • Key-value pair not supported: ‘AWSAssetFile16’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/3D/Houdini/render/XXXX_XXX_010_v10/XXXX_XXX_010_v10.Redshift_ROP1.####.exr’
  • Key-value pair not supported: ‘AWSAssetFile37’=’[value global.font_path]/AlrightSans-Regular-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile11’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Renders/JPG/XXXX_XXX_010_v11.jpg’
  • Key-value pair not supported: ‘AWSAssetFile18’=‘node_camera.xpm’
  • Key-value pair not supported: ‘AWSAssetFile22’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Renders/JPG/XXXX_XXX_010_v12.jpg’
  • Key-value pair not supported: ‘AWSAssetFile21’=‘node_scene.xpm’
  • Key-value pair not supported: ‘AWSAssetFile20’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Comp/Plates/TexturesCom_LandscapeArid0149_XXL.jpg’
  • Key-value pair not supported: ‘AWSAssetFile26’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Comp/Pre_Comp/DirtPrecomp_01_V01/DirtPrecomp_01_V01.####.exr’
  • Key-value pair not supported: ‘AWSAssetFile25’=‘P:/JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Comp/Pre_Comp/boardDAMAGE/boardDAMAGE####.exr’
  • Key-value pair not supported: ‘AWSAssetFile24’=‘P:/JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Comp/Pre_Comp/boardDAMAGE_EDGE_v2/boardDAMAGE_EDGE_v2####.exr’
  • Key-value pair not supported: ‘AWSAssetFile28’=‘node_camera.xpm’
  • Key-value pair not supported: ‘AWSAssetFile45’=’[value global.font_path]/AlrightSans-Regular-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile47’=’[value global.font_path]/AlrightSans-Light-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile46’=’[value global.font_path]/AlrightSans-Regular-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile41’=‘P:/VFX_ELEMENTS/nuke_startup/gizmos/Splice_Logo.tif’
  • Key-value pair not supported: ‘AWSAssetFile40’=’[value global.font_path]/AlrightSans-Regular-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile43’=’[value global.font_path]/AlrightSans-Bold-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile42’=‘P:/VFX_ELEMENTS/nuke_startup/gizmos/Splice_Slate_BGImage.tif’
  • Key-value pair not supported: ‘AWSAssetFile49’=’[value global.font_path]/AlrightSans-Regular-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile48’=’[value global.font_path]/AlrightSans-Regular-v3.otf’
  • Key-value pair not supported: ‘AWSAssetFile3’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Comp/Plates/XXXX_XXX_010_v002_Denoise/XXXX_XXX_010_v002_Denoise.####.exr’
  • Key-value pair not supported: ‘AWSAssetFile27’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Comp/Pre_Comp/MountainsSkyPrecomp_01_v01/MountainsSkyPrecomp_01_v01.####.exr’
  • Key-value pair not supported: ‘AWSAssetFile29’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Tracking/Tracking_Export/Nuke/XXXX_XXX_010_v002.1003_Camera01LD.tif’
  • Key-value pair not supported: ‘AWSAssetFile23’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Tracking/Tracking_Export/Nuke/XXXX_XXX_010_v002.1003_Camera01RD.tif’
  • Key-value pair not supported: ‘AWSAssetFile0’=‘P:/_JOBS3/XXXXXXXX/19077_XXXXXXXX_XXXX4_XXX_042919/VFX/SHOTS/XXXX_XXX_010/Comp/XXXX_XXX_010_v020.nk’
  • Key-value pair not supported: ‘AWSAssetFile1’=‘C:/Program Files/Nuke11.3v4/plugins/OCIOConfigs/configs/nuke-default/config.ocio’
  • Key-value pair not supported:
2

We are having exactly the same issue here. After the upgrade to 10.0.26.0 every time we submit a Nuke job we get warnings.

There is a “Key-value pair not supported: ‘AWSAssetFileXX” for each file in the Nuke script. Most of the time the error/warning is so big that it will fill up the whole screen.

We have modified the submitters in the past, but no code changes have been made recently. Any suggestions on what might have triggered the issue?

3

Try submitting as a list of lists.

i noticed when we upgraded to 10.0.26.0, that jobs are now stored differntly in the db, plugin info and job environments, went from k/v pairs to list of lists.
So something that was previous:

data : {'key1':'value1','key2':'value2'}

is now represented as:

data : [['key1','value1'],['key2','value2']]

This is the data model in the database, it bit us, because we have a search api, that helps us traverse job info quicker, (read only) , but our lookups for jobs on the farm started failing, because you can no longer search based on key value pairs for imbeded job info :frowning:

On the bright side, it looks like allot of the jobs / backend is converting between the old and new way to lookup data, this one may have been missed.

Id make a support ticket, for this problem, The support folks seem pretty busy these days , no many of them get around to looking at the forums much… Eh @eamsler ?

Hope this helps.

4

Yeah, I’m only seeing this now for example while looking for something else.

To be honest, this incompatibility is why we say “don’t access the Database directly” :confused:. While the core API is stable and we put in the work to make sure it’s backward compatible, the schema can change at any time as long as we maintain that backward compatibility at the API level.