Fix for failing Training Job on py 3.8+

[izapolsk]

I've encountered the issue similar to described in #452.
It occurs when user uses function preprocessor + cloudpicke version containing cloudpickle_fast.py + python 3.8+.

The root cause is that newer versions of cloudpickle contain cloudpickle_fast.py and that file isn't copied by preprocessor during image preparation.

So, this PR aims to append mentioned above file along with the rest of cloudpickle package.

By the way, what's the reason for copying that package into image ? Wouldn't it be better to copy egg there f.e. and install it on start up ?

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[kubeflow-bot]

This change is 

[k8s-ci-robot]

Hi @izapolsk. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[izapolsk]

@googlebot I signed it!

[izapolsk]

/assign @xauthulei

[xauthulei]

/test

[k8s-ci-robot]

@xauthulei: The /test command needs one or more targets.
The following commands are available to trigger jobs:

• /test kubeflow-fairing-presubmit

Use /test all to run all jobs.

In response to this:

/test

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.

[xauthulei]

/ok-to-test

[xauthulei]

Thanks @izapolsk

[xauthulei]

Currently it report this issue:

Files with lint issues: /build/lib/kubeflow/fairing/preprocessors/function.py, /kubeflow/fairing/preprocessors/function.py

You could install the Pylint checking plugin in your python development env to catch the errors/warning here.

[jinchihe]

@izapolsk This is caused by line-too-long, easy to fix. Thanks

INFO|2020-09-10T01:45:19|util.py:72| ************* Module kubeflow.fairing.preprocessors.function
INFO|2020-09-10T01:45:19|util.py:72| C: 69, 0: Line too long (118/100) (line-too-long)
INFO|2020-09-10T01:45:19|util.py:72| 
INFO|2020-09-10T01:45:19|util.py:72| -----------------------------------
INFO|2020-09-10T01:45:19|util.py:72| Your code has been rated at 9.77/10

[izapolsk]

sorry, my default setting is =<120

[xauthulei]

/lgtm

[xauthulei]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xauthulei

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:

• OWNERS [xauthulei]

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