Skip to content
New issue

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

SDK - Compiler - Validating Argo validator #3874

Conversation

Ark-kun
Copy link
Contributor

@Ark-kun Ark-kun commented May 29, 2020

Fixes #3859

@kubeflow-bot
Copy link

This change is Reviewable

try:
has_working_argo_lint = _run_argo_lint('')
except:
pass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we log a warning message here? So it doesn't feel lost for end users why sometimes argo lint is there, but sometimes not

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think most our users do not have argo CLI installed. I'm not sure we want to show warnings for those users.
WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we move this check after checking if argo exists in PATH? That seems to solve this case.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, if linting with argo is a useful feature (sounds to me, it's very useful). If argo is not in path, can we log an info message suggesting users to do so?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we move this check after checking if argo exists in PATH? That seems to solve this case.

We have some bug reports from people who either have different programs called argo in path or have recent versions of argo that cannot work inside container. In both cases the executable exists in path, but is not suitable.
This is why we first validate it on empty input (maybe we should use a small pipeline).

Copy link
Contributor

@Bobgy Bobgy Jun 12, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think moving this check after checking argo in PATH is a better UX for the cases you mentioned.
e.g. when user has a later argo cli version, they will see an info message that kfp cannot use the argo cli for linting, because "xxx".

Then they know:

  • kfp sdk can use argo cli to lint argo workflow (that's a really useful feature)
  • how they can enable the feature (by switching to an argo cli of suitable version)
  • if they don't want use this feature, just ignore this info message, it won't block execution

@Ark-kun
Copy link
Contributor Author

Ark-kun commented May 29, 2020

/retest

1 similar comment
@Ark-kun
Copy link
Contributor Author

Ark-kun commented Jun 12, 2020

/retest

@Bobgy
Copy link
Contributor

Bobgy commented Jul 10, 2020

Thanks! This looks great

/lgtm

@Ark-kun
Copy link
Contributor Author

Ark-kun commented Jul 11, 2020

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Ark-kun

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit bbc9ff5 into kubeflow:master Jul 11, 2020
Jeffwan pushed a commit to Jeffwan/pipelines that referenced this pull request Dec 9, 2020
* SDK - Compiler - Validating Argo validator

* Added warning if argo is available, but not working
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compilation of KFP fails if no .kube/config present
7 participants