Closed cartermak closed 8 months ago
@joswig I didn't see the your edit to this last week; I don't think that workaround will suffice since the problem activities have meaningful modeling which will change the generated commands and/or are part of decompositions that also include command expansion, but I'll keep it in the back of my mind in case we need to go that route.
Checked for duplicates
Yes - I've already checked
Is this a regression?
No - This is a new bug
Version
v2.2.X
Describe the bug
The Command Expansion activity loader fails to deserialize activities where "container" value schema types (struct, series) have
null
corresponding values.I'm capturing this as a bug since the Aerie UI seems to have no problem handling this, and in my opinion it makes sense for any value to be
null
and for Command Expansion to handle that case/forward that value to the expansion rule. A move towards disallowing thesenull
values may require significant rework of several complex Clipper activity parameters/mappers.Reproduction
One example: Clipper's
Optional
parameter type serializes the value asnull
if the optional is empty. This issue can be reproduced by simulating an activity with this parameter type as "empty" where the optional value is itself a list or struct.For example, given this value schema for an
Optional
parameter with a complex "struct" value:...the serialized parameter value below will cause the issue in the sequencing server:
Logs
System Info
Severity
Major
Workaround
Branch plan, delete activities with null values, run expansions on branch. This is not always a realistic option, but may work for some plans