We've been tracking down a newly discovered bug that occurs when running the l2ss>Batchee>StitchEE>CONCISE chain in UAT.
It seems like the unexpected condition may have been hidden because of a discrepancy in arguments being passed to L2SS's high-level subset() function, between command-line invocations and Harmony invocations... cut=False by default in the cli; and no argument is given in the Harmony adapter so it uses the default of cut=Truein the function definition.
In effect, I think l2-subsetter services have been (and probably want to continue) using cut=True, but for the batchee>stitchee>concise chain, we want cut=False.
It seems like to address this we might need a service- (or collection-) specific argument/configuration to be passed from Harmony to L2ss-py.
We've been tracking down a newly discovered bug that occurs when running the l2ss>Batchee>StitchEE>CONCISE chain in UAT.
It seems like the unexpected condition may have been hidden because of a discrepancy in arguments being passed to L2SS's high-level
subset()
function, between command-line invocations and Harmony invocations...cut=False
by default in the cli; and no argument is given in the Harmony adapter so it uses the default ofcut=True
in the function definition.In effect, I think l2-subsetter services have been (and probably want to continue) using
cut=True
, but for the batchee>stitchee>concise chain, we wantcut=False
.It seems like to address this we might need a service- (or collection-) specific argument/configuration to be passed from Harmony to L2ss-py.