-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Running into TypeError exception with batch_predict
component
#4430
Comments
Thank you fr your bug report. |
Fixes kubeflow#4430 The issue was introduced in kubeflow#3850. That PR has added a new parameter in the middle of the the create_job function signature which can cause breaking changes as the parameter ordering changes.
Hi @Ark-kun , Thanks for the quick response. Are you planning to release a new version of the component after merging the linked PR? I am also wondering if there are any plans to migrate these components to python3? Thanks |
Yes.
There are some plans, but they're not prioritized. I think these components already support python 3. Is these any issue with them using python 2 right now? |
For ML Engine Components, I am not running into any issue but Dataflow component is running the application code with Python2. My applications are written is python3, I am not sure if there are any workarounds for it. I am currently thinking of writing a custom component for Dataflow jobs to run application in python3. |
Hi @Ark-kun , I ran into similar issue with
Could you please change the function signature for Thanks |
…ixes #4430 (#4432) * Components - Fixed the GCP - ML Engine - Batch predict component Fixes #4430 The issue was introduced in #3850. That PR has added a new parameter in the middle of the the create_job function signature which can cause breaking changes as the parameter ordering changes. * Fixed test
…ixes kubeflow#4430 (kubeflow#4432) * Components - Fixed the GCP - ML Engine - Batch predict component Fixes kubeflow#4430 The issue was introduced in kubeflow#3850. That PR has added a new parameter in the middle of the the create_job function signature which can cause breaking changes as the parameter ordering changes. * Fixed test
What steps did you take:
I am using batch_predict component to schedule prediction job on AI platform. I was referring to steps here. https://github.com/kubeflow/pipelines/tree/master/components/gcp/ml_engine/batch_predict
ml_op = load_component_from_file(<local-path>)
ml_op(<attributes-mentioned-below>)
Job Parameters:
What happened:
Running into type error while generating the job_id.
Issue:
It is raising an exception while generating id to schedule the job. This line is failing https://github.com/kubeflow/pipelines/blob/1.0.0/components/gcp/container/component_sdk/python/kfp_component/google/common/_utils.py#L44 with this error
TypeError: expected string or buffer
. I am not passing any job_id and job_id_prefix. It is using the default values for generating the name.Error trace:
What did you expect to happen:
I was expecting the component to schedule the job with auto generated job id.
Environment:
How did you deploy Kubeflow Pipelines (KFP)?
KFP version:
1.0.0
KFP SDK version:
kfp==0.5.1
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind bug
The text was updated successfully, but these errors were encountered: