[REMINDER] Policies around Publicity & Press

All Podlings, In recent days I've been contacted about several publicity issues that have gone a bit off kilter. I wanted to remind podlings two very import policies. 1. Podlings MUST coordinate with the Public Relations Committee with all publicity activities. 2. The Press Team MUST review any

Re: Inputs and Node object context for python and shell scripts

Interesting, can you describe exactly the scenario? including the service template and the operation you are trying to run On Mon, Jul 31, 2017 at 6:12 PM, D Jayachandran wrote: > Hi, > > I got the below error when I tried assigning values as like a dict. It >

RE: Inputs and Node object context for python and shell scripts

Hi, I got the below error when I tried assigning values as like a dict. It seems to fail when it tries to remove the existing value and triggering a change event. ObjectDereferencedError: Can't emit change event for attribute 'Node.attributes' - parent object of type has been garbage

Re: Inputs and Node object context for python and shell scripts

>From within any operation or workflow you don't need to use the ".value" notation. In order to access the attribute use ctx.node.attributes['test'], and in order to assign the attribute just use ctx.node.attributes['test'] = "abc". Using this (hopefully simplified) notation does all the model

RE: Inputs and Node object context for python and shell scripts

Hi Max, Adding to this , I can access the attributes in my plugin only as below. ( I have defined the attribute test in my node type ) ctx.node.attributes['test'].value And to update the value ctx.node.attributes['test'].value = "abc" But this does not update the db. Am I missing something