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

error uploading pipeline from github URL #2922

Closed
amygdala opened this issue Jan 28, 2020 · 11 comments
Closed

error uploading pipeline from github URL #2922

amygdala opened this issue Jan 28, 2020 · 11 comments
Assignees
Labels
area/backend help wanted The community is welcome to contribute. kind/bug lifecycle/frozen needs more info status/triaged Whether the issue has been explicitly triaged

Comments

@amygdala
Copy link
Contributor

I'm using whatever kfp version is Build commit: ca58b22.

When I try to upload a pipeline version, I get the following error. I double checked that I could 'wget' the URL and unarchive the result. (Am I misinterpreting what "Package Url means?)

Screenshot 2020-01-28 10 08 00

Related: why doesn't this UI support browsing to upload a file, rather than requiring a URL? That makes things much less convenient IMO.

@amygdala
Copy link
Contributor Author

amygdala commented Feb 3, 2020

Update: it looks like github URLs are problematic somehow. With a url like this:
https://raw.githubusercontent.com/amygdala/pipelines/automl_client_update/components/gcp/automl/tables_eval_pipeline.py.tar.gz , which downloads okay via curl or wget, I see the error above.
If I try with this URL, which points to the same archive file:
https://storage.googleapis.com/aju-btest2/arghh/tables_eval_pipeline.py.tar.gz
things work okay.

IMO this issue with github urls is particularly problematic since we apparently can not upload an archive file from the local machine via the version UI, unlike the case with a (non-version) Pipeline upload.

cc @jingzhang36

@jingzhang36
Copy link
Contributor

jingzhang36 commented Jun 22, 2020

We now have another api method UploadPipelineVersion that works with local files. Examples are at
https://www.kubeflow.org/docs/pipelines/tutorials/sdk-examples/#creating-a-pipeline-and-a-pipeline-version-using-the-sdk

Also, if using CreatePipelineVersion with url, there is some known issue regarding which types of urls are supported. We recommend using https://storage.googleapis.com/ <gcs bucket name>/ <file name>

@amygdala
Copy link
Contributor Author

/reopen

I'm sorry, I don't view this as fixed-- it's pretty important that GitHub URLs are supported IMO.

@k8s-ci-robot k8s-ci-robot reopened this Jun 22, 2020
@k8s-ci-robot
Copy link
Contributor

@amygdala: Reopened this issue.

In response to this:

/reopen

I'm sorry, I don't view this as fixed-- it's pretty important that GitHub URLs are supported IMO.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@amygdala
Copy link
Contributor Author

Just pinging on this... it continues to annoy me each time I would like to load from a github URL and it breaks (since that's really the only remote URL source I normally use for pipelines). I expect that if it annoys me so often, it is surely annoying other users too.

I think there just needs to be some frontend support for handling redirects. Does the js package being used support that?

@Bobgy Bobgy added the help wanted The community is welcome to contribute. label Sep 2, 2020
@Bobgy Bobgy assigned jingzhang36 and Bobgy and unassigned jingzhang36 Sep 2, 2020
@Bobgy
Copy link
Contributor

Bobgy commented Sep 2, 2020

Thanks, this sounds useful. I've put it to triage track, but if any contributor is willing to jump in. You are welcome to do so.

@amygdala amygdala changed the title error uploading pipeline version error uploading pipeline from github URL Sep 30, 2020
@stale
Copy link

stale bot commented Dec 31, 2020

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.

@stale stale bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Dec 31, 2020
@amygdala
Copy link
Contributor Author

amygdala commented Jan 5, 2021

let's keep this open, we really should fix it.

@stale stale bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jan 5, 2021
@amygdala
Copy link
Contributor Author

amygdala commented Jan 5, 2021

/lifecycle frozen

@zijianjoy
Copy link
Collaborator

Hello @amygdala , thank you for providing the sample for reproducing the issue! I went through the steps as below:

Environment

I am using v1.3.0 for backend image: gcr.io/ml-pipeline/api-server:1.3.0. And I am using the latest change of frontend code on GitHub.

Observation

I have no problem uploading a revision of pipeline using raw github content URL as you provided (https://raw.githubusercontent.com/amygdala/pipelines/automl_client_update/components/gcp/automl/tables_eval_pipeline.py.tar.gz ). And below is a screenshot of a successful upload UI and the network requests:

Screen Shot 2021-02-02 at 12 05 31 PM

From this screenshot, you can see that a revision of pipeline request is sent to {domain}/apis/v1beta1/pipeline_versions endpoint, with query parameter of the githubusercontent URL. And on the right hand side is a graph of pipeline after successful response.

Action

This issue might have been fixed already. You can try redeploying your KFP with new version. If the issue persists or resolves, please reply back here and I am happy to dig in further with you. Reference: KFP release note

@zijianjoy
Copy link
Collaborator

Received response from user that the issue has been fixed, and new UI allows you to upload pipeline revision file from local.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend help wanted The community is welcome to contribute. kind/bug lifecycle/frozen needs more info status/triaged Whether the issue has been explicitly triaged
Projects
None yet
Development

No branches or pull requests

6 participants