Open JasonNS1425 opened 2 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Also hitting this issue -- curious if anyone finds a workaround
Environment
Steps to reproduce
When using the pipeline channel placeholders in formatted string and then passing it as another task input, the downstream PipelineTask often get a non-substituted version of input value. See example for details. (you may have to run the pipeline run a few times to trigger this issue)
Source codes
Pipeline run results
Kubeflow Pipeline
pipeline print-op-2
Hello Kubeflow Pipeline 2 [KFP Executor 2024-07-22 07:46:45,542 INFO]: Wrote executor output file to /tmp/kfp_outputs/output_metadata.json. I0722 07:46:45.553621 22 launcher_v2.go:705] ExecutorOutput: { "parameterValues": { "Output": "Hello Kubeflow Pipeline 2" } }
pipeline print-op-3
Hello {{$.inputs.parameters['pipelinechannel--name']}} 3 [KFP Executor 2024-07-22 07:46:42,415 INFO]: Wrote executor output file to /tmp/kfp_outputs/output_metadata.json. I0722 07:46:42.426454 24 launcher_v2.go:705] ExecutorOutput: { "parameterValues": { "Output": "Hello {{$.inputs.parameters['pipelinechannel--name']}} 3" } }
pipeline print-op-4
Hello Kubeflow Pipeline 4 [KFP Executor 2024-07-22 07:46:45,782 INFO]: Wrote executor output file to /tmp/kfp_outputs/output_metadata.json. I0722 07:46:45.794531 24 launcher_v2.go:705] ExecutorOutput: { "parameterValues": { "Output": "Hello Kubeflow Pipeline 4" } }
pipeline print-op-5
Hello Kubeflow Pipeline 5 [KFP Executor 2024-07-22 07:46:42,380 INFO]: Wrote executor output file to /tmp/kfp_outputs/output_metadata.json. I0722 07:46:42.396266 23 launcher_v2.go:705] ExecutorOutput: { "parameterValues": { "Output": "Hello Kubeflow Pipeline 5" } }
Impacted by this bug? Give it a 👍.