Jeremy Lewi

That image looks pretty old. Jan 23 2019.

https://github.com/kubeflow/fairing/blob/736c025e6d77f135bda345e5030398d5d2ef654a/examples/prediction/README.md Looks like maybe we should be using: seldonio/seldon-core-s2i-python3:0.4

Looks like that fixed that problem. Now I get a different error ``` 2019-04-10 04:12:01,837 - seldon_core.microservice:main:261 - INFO: Starting microservice.py:main 2019-04-10 04:12:01,839 - seldon_core.microservice:main:292 - INFO: Annotations: {} Traceback...

I think this might be fixed by https://github.com/kubeflow/fairing/pull/207

@karthikv2k Any update on the status of this work? I think one way to test this would be to use the demo notebook I used for kubecon https://github.com/jlewi/kubecon-demo/blob/master/ames-xgboost-build-train-deploy.ipynb I was...

@karthikv2k Any update on this?

It looks like this still isn't fixed. Code is still using gcr.io/kubeflow-images-public/fairing:dev https://github.com/kubeflow/fairing/blob/87c1185cde356939494ff4e9631c0b490b27153a/fairing/constants/constants.py And that image is still very old January 22, 2019 It looks like the code in the...

I think we also need to override the files returned https://github.com/kubeflow/fairing/blob/08c81437fd9ed720cf4b780e25097fef9fa16cd6/fairing/preprocessors/converted_notebook.py#L57

Here's the preprocessor I created for my kubecon demos. https://github.com/jlewi/kubecon-demo/blob/master/fairing_util.py Should we get that checked into fairing?

One idea would be to * Selectively trigger tests specific to plugins when the plugin changed * Use purposely designed kustomize applications and KFDef files to test the bulk of...