You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A custom tool I'm developing has an optional input defined in the XML file, so that the user could override the data that would normally come from that input connector using the HTML inputs. However, running the workflow with this custom tool as the 'first' tool in a data stream causes the debug workflow to end without processing the python main.py.
As you can see from the image, the first inv debug run completes even though there is a pdb.set_trace() in the code, and the "ToolId ..." output is missing.
The second inv debug run is after I updated the debug workflow to include an Text Input tool before the custom tool, and you can see that it stops at the trace point and allows me to inspect the code objects to confirm behavior is as expected.
To create this test tool, I simply copied the ExampleBatchTool into a new tool, renamed all the files, updated the places where the name is referenced in the code, and created a simple debug workflow. I've attached a ZIP of the YDMD and YXI files.
Re-reading my comments above I realized that I left out something important ...
The additional change I made to the ExampleBatchTool project was to change the XML file to make the input connection optional: Optional="True". Hopefully that was clear from the attached files, but just wanted to make sure! :)
A custom tool I'm developing has an optional input defined in the XML file, so that the user could override the data that would normally come from that input connector using the HTML inputs. However, running the workflow with this custom tool as the 'first' tool in a data stream causes the debug workflow to end without processing the python main.py.
As you can see from the image, the first
inv debug
run completes even though there is apdb.set_trace()
in the code, and the"ToolId ..."
output is missing.The second
inv debug
run is after I updated the debug workflow to include an Text Input tool before the custom tool, and you can see that it stops at the trace point and allows me to inspect the code objects to confirm behavior is as expected.To create this test tool, I simply copied the
ExampleBatchTool
into a new tool, renamed all the files, updated the places where the name is referenced in the code, and created a simple debug workflow. I've attached a ZIP of the YDMD and YXI files.TestOptionalInput.zip
The text was updated successfully, but these errors were encountered: