We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I try to submit a job with two layers, with either a frame or layer dependency I get this error:
Failed to parse job spec XML, org.jdom.input.JDOMParseException: Error on line 1: Attribute value "b'False'" of type NMTOKEN must be a name token.
A bit of digging reveals that the XML fragment received by Cuebot has a problem:
<depends> <depend anyframe="b'False'" type="LAYER_ON_LAYER"> <depjob>b858be71-6467-4e00-997a-824b32fb0e0c</depjob <deplayer>MyTaskNameTwoB</deplayer> <onjob>b858be71-6467-4e00-997a-824b32fb0e0c</onjob> <onlayer>MyTaskNameOneA</onlayer> </depend> </depends>
The 'anyframe' value is added in the build_dependencies method in outline/backend/cue.py:
build_dependencies
outline/backend/cue.py
depend = Et.SubElement(all_depends, "depend", type=dep.get_type(), anyframe=str(dep.is_any_frame()))
Looks innocuous, but str is imported from builtins, so it's of type future.types.newstr.newstr.
str
future.types.newstr.newstr
I guess xml.etree.ElementTree.SubElement is not happy with an newstr instance.
xml.etree.ElementTree.SubElement
newstr
The text was updated successfully, but these errors were encountered:
Ensure ElementTree.SubElement receives a str AcademySoftwareFoundatio…
681b14c
…n#368
Ensure ElementTree.SubElement receives a str #368 (#369)
0265e3e
donalm
No branches or pull requests
When I try to submit a job with two layers, with either a frame or layer dependency I get this error:
A bit of digging reveals that the XML fragment received by Cuebot has a problem:
The 'anyframe' value is added in the
build_dependencies
method inoutline/backend/cue.py
:Looks innocuous, but
str
is imported from builtins, so it's of typefuture.types.newstr.newstr
.I guess
xml.etree.ElementTree.SubElement
is not happy with annewstr
instance.The text was updated successfully, but these errors were encountered: