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
Note: The key difference of these two pipelines is the input parameter's naming for add() component. add(x,y) v.s add(x,z)!!
Click "Pipelines" menu, then click "Upload pipeline" for these two testing pipeline IR yaml
Verify "Pipeline Spec" for add(x,y)
You can find at line#6, the input parameter of "y" has changed to "true" which cause the pipeline fail.
Line#227 also indicating the same situation.
Then I try to review the IR yaml that generate by compiler "pipeline-add(x,y).yaml", and the format is correct. We can see two input parameters "x" and "y".
Verify "Pipeline Spec" for add(x,z)
I am suspect what cause the issue, so the other version pipeline just change the input parameters from "y" to "z". Checking the "Pipeline Spec" and the result is the same as "pipeline-add(x,z).yaml".
Base on this observation, I think the pipeline api backend might be the one which alter the "y" to "true".
Expected result
"Pipeline Spec" representation & structure shoud be identical as IR yaml.
The underlying issue is because gopkg.in/yaml.v2 library implements the problematic YAML 1.1 spec, and threats "y" as boolean by design: go-yaml/yaml#214
This has been fixed in gopkg.in/yaml.v3
How did you deploy Kubeflow Pipelines (KFP)?
Use https://github.com/kubeflow/manifests to deploy kubeflow.
git clone https://github.com/kubeflow/manifests.git cd manifests git checkout v1.7-branch
Modify
manifests/apps/pipeline/upstream/base/pipeline/kustomization.yaml
:Then, use one command to apply these manifest:
KFP version:
version: 2.0.0-rc.1
KFP SDK version:
version: 2.0.0-rc.1
Steps to reproduce
Create two sample pipeline (v2)
pipeline - pipeline-add(x,z)
Note: The key difference of these two pipelines is the input parameter's naming for add() component. add(x,y) v.s add(x,z)!!
Click "Pipelines" menu, then click "Upload pipeline" for these two testing pipeline IR yaml
Verify "Pipeline Spec" for add(x,y)
You can find at line#6, the input parameter of "y" has changed to "true" which cause the pipeline fail.
Line#227 also indicating the same situation.
Then I try to review the IR yaml that generate by compiler "pipeline-add(x,y).yaml", and the format is correct. We can see two input parameters "x" and "y".
Verify "Pipeline Spec" for add(x,z)
I am suspect what cause the issue, so the other version pipeline just change the input parameters from "y" to "z". Checking the "Pipeline Spec" and the result is the same as "pipeline-add(x,z).yaml".
Base on this observation, I think the pipeline api backend might be the one which alter the "y" to "true".
Expected result
"Pipeline Spec" representation & structure shoud be identical as IR yaml.
Materials and reference
I put two version of IR yaml as attachment.
pipeline-add.zip
Labels
/area backend
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: