[jira] [Created] (SUBMARINE-668) Experiment output is Null
Kevin Su created SUBMARINE-668:
--
Summary: Experiment output is Null
Key: SUBMARINE-668
URL: https://issues.apache.org/jira/browse/SUBMARINE-668
Project: Apache Submarine
Issue Type: Bug
Components: Backend Server
Affects Versions: 0.6.0
Reporter: Kevin Su
Fix For: 0.6.0
When I used minikube v14.2 or v18.0 with the latest submarine installed by the
helm chart, the experiment output always is null.
*http://submarine:32080/api/v1/experiment/logs*
if I install Kubernetes by kind, I could successfully get experiment output.
{code:java}
minikube start --vm-driver=none --cpus 60 --memory 122880 --disk-size=120g
--kubernetes-version v1.14.2
helm install submarine ./helm-charts/submarine
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org
For additional commands, e-mail: dev-h...@submarine.apache.org
[jira] [Assigned] (SUBMARINE-668) Experiment output is Null
[
https://issues.apache.org/jira/browse/SUBMARINE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Lo reassigned SUBMARINE-668:
-
Assignee: Ryan Lo
> Experiment output is Null
> -
>
> Key: SUBMARINE-668
> URL: https://issues.apache.org/jira/browse/SUBMARINE-668
> Project: Apache Submarine
> Issue Type: Bug
> Components: Backend Server
>Affects Versions: 0.6.0
>Reporter: Kevin Su
>Assignee: Ryan Lo
>Priority: Major
> Fix For: 0.6.0
>
>
> When I used minikube v14.2 or v18.0 with the latest submarine installed by
> the helm chart, the experiment output always is null.
> *http://submarine:32080/api/v1/experiment/logs*
> if I install Kubernetes by kind, I could successfully get experiment output.
>
> {code:java}
> minikube start --vm-driver=none --cpus 60 --memory 122880 --disk-size=120g
> --kubernetes-version v1.14.2
> helm install submarine ./helm-charts/submarine
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org
For additional commands, e-mail: dev-h...@submarine.apache.org
Re: [VOTE] Submarine-0.5.0-RC1 is ready for a vote!
Hi Kevin,
Thank you so much for running this release.
Trying to follow the helm install stage, but notebook controller is failed
to start.
I downloaded RC1 source code, and follow the guidance:
https://github.com/apache/submarine/blob/master/docs/userdocs/k8s/helm.md
The pods in my system:
NAMESPACE NAME READY
STATUS RESTARTS AGE
default notebook-controller-deployment-58797bdd75-9fstx 0/1
CrashLoopBackOff 7 12m
default pytorch-operator-75fd845678-dpc52 1/1
Running0 12m
default submarine-database-54776644c6-x2zrm 1/1
Running0 12m
default submarine-server-5d846f7b4f-m2fw8 1/1
Running0 12m
default submarine-traefik-d55c689b5-cq6db 1/1
Running0 12m
default tf-job-operator-598686fd84-2fwt9 1/1
Running0 12m
And notebook-controller pod has the following information: (kubectl
describe pods notebook-controller-deployment-58797bdd75-9fstx)
Events:
Type Reason Age From Message
-- ---
Normal Scheduled 12m default-scheduler
Successfully assigned
default/notebook-controller-deployment-58797bdd75-9fstx to docker-desktop
Normal Pulling12m kubelet, docker-desktop
Pulling image "apache/submarine:notebook-controller-v1.1.0-g253890cb"
Normal Pulled 12m kubelet, docker-desktop
Successfully pulled image
"apache/submarine:notebook-controller-v1.1.0-g253890cb"
Normal Pulled 11m (x4 over 12m) kubelet, docker-desktop
Container image "apache/submarine:notebook-controller-v1.1.0-g253890cb"
already present on machine
Normal Created11m (x5 over 12m) kubelet, docker-desktop
Created container manager
Normal Started11m (x5 over 12m) kubelet, docker-desktop
Started container manager
Warning BackOff2m45s (x51 over 12m) kubelet, docker-desktop
Back-off restarting failed container
Logs: (kubectl log notebook-controller-deployment-58797bdd75-9fstx)
2020-11-02T17:11:53.159Z ERROR setup unable to create controller
{"controller": "Notebook", "error": "no matches for kind \"Notebook\" in
version \"kubeflow.org/v1beta1\""}
github.com/go-logr/zapr.(*zapLogger).Error
/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
main.main
/workspace/notebook-controller/main.go:76
runtime.main
/usr/local/go/src/runtime/proc.go:200
I guess it might be version of K8s, I'm using DockerDesktop:
kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.6",
GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean",
BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc",
Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+",
GitVersion:"v1.16.6-beta.0",
GitCommit:"e7f962ba86f4ce7033828210ca3556393c377bcc", GitTreeState:"clean",
BuildDate:"2020-01-15T08:18:29Z", GoVersion:"go1.13.5", Compiler:"gc",
Platform:"linux/amd64"}
I'm not sure what I should do now? Last time when we release 0.4.0, we
verified 1.14, 1.15, 1.16 should all work.
https://github.com/apache/submarine/blob/master/docs/userdocs/k8s/README.md
What is our recommendation for now?
Thanks,
Wangda
On Fri, Oct 30, 2020 at 8:47 PM Wanqiang Ji wrote:
> +1 for this RC1. Thanks Kevin drive this release and everyone for the great
> works.
> I've done the following tests:
> 1. Install the helm charts against the minikube
> 2. Install the helm charts against the kind
> 3. Check the UI's features, create the notebook/experiment and run work
>
> BR,
> Wanqiang Ji
>
>
> On Wed, Oct 28, 2020 at 4:52 PM Zhankun Tang wrote:
>
> > Thanks for the great efforts! Kevin!
> > I've done the below testing
> > 1. Verify the signatures (I signed Kevin's key and updated the KEYS file)
> > 2. Build from source
> > 3. Install the helm charts against Docker desktop k8s (v1.14.8)
> > 4. Check basic UI's experiment and notebook features
> >
> > And I like the built-in examples in our notebook image. It's
> > straightforward for beginners to get familiar with our SDK.
> > One minor suggestion is that we can add a link in parent readme
> > <
> >
> https://github.com/apache/submarine/blob/master/docs/userdocs/k8s/README.md
> > >
> > to our notebook.md doc. But this is not a blocker, we can improve docs
> > later since it's in GitHub for now.
> >
> > I'll give my *+1(binding)* to this RC1.
> >
> > @Wei-Chiu Chuang BTW, I can download the
> > "apache/submarine:mini-0.5.0-RC1" image on my laptop.
> >
> > BR,
> > Zhankun
> >
> > On Mon, 26 Oct 2020 at 10:21, Wei-Chiu Chuang
> > >
> > wrote:
> >
> > > Curious -- I see mini-0.5.0-RC1 and RC0 docker images, however, the
> > > operator, server, database and j
Re: [VOTE] Submarine-0.5.0-RC1 is ready for a vote!
Nevermind, please ignore the previous message. I think it is caused by
previous installation (0.4.0), I reset K8s cluster and now everything can
be installed, trying to follow other steps now.
1) Why by default Submarine sever login has maria_dev as default user name?
2) There's no doc about using Submarine UI, we need to add one, I will file
a PR later (TODO)
3) Trying to create notebook, the notebook name initially I gave is
"nb_123", but I got the error, "K8s submitter: parse Job object failed by
Unprocessable Entity, please try again"
If we have limitation of how naming of notebook should be, we should add it
to the UI (like only character or numbers are supported).
>From the doc it mentioned: "Name of the notebook server. It should be
unique and include no spaces." We need to update both of doc and UI.
4) When I choose the environment for notebook, I saw both my-submarine-env
and notebook-env. What are the differences between the two?
- I found only notebook-env works, "my-submarine-env" failed to start. We
should remove the my-submarine-env from the default helm installation.
5) Also, I found even if notebook is not fully start and running, the UI
indicate it is created:
[image: image.png]
Clicking notebook name will show you an error page, we should improve this
part.
6) After waiting for ~5 mins, the notebook started, but I still cannot
access the notebook UI, clicking the link on the Submarine UI tells me:
HTTP ERROR 404
Problem accessing /notebook/default/notebook/. Reason:
Not Found
And logs for the notebook pod tells me;
kubectl logs notebook-0
Conda current version is currentVersion=4.8.3;. Moving forward with
env creation and activation.
[I 17:45:50.056 NotebookApp] Writing notebook server cookie secret to
/home/jovyan/.local/share/jupyter/runtime/notebook_cookie_secret
[W 17:45:52.108 NotebookApp] All authentication is disabled. Anyone
who can connect to this server will be able to run code.
[I 17:45:52.144 NotebookApp] Serving notebooks from local directory:
/home/jovyan
[I 17:45:52.145 NotebookApp] Jupyter Notebook 6.1.3 is running at:
[I 17:45:52.146 NotebookApp]
http://notebook-0:/notebook/default/notebook/
[I 17:45:52.147 NotebookApp] Use Control-C to stop this server and
shut down all kernels (twice to skip confirmation).
Is it bind to a wrong port?
On Mon, Nov 2, 2020 at 9:18 AM Wangda Tan wrote:
> Hi Kevin,
>
> Thank you so much for running this release.
>
> Trying to follow the helm install stage, but notebook controller is failed
> to start.
>
> I downloaded RC1 source code, and follow the guidance:
> https://github.com/apache/submarine/blob/master/docs/userdocs/k8s/helm.md
>
> The pods in my system:
>
> NAMESPACE NAME READY
> STATUS RESTARTS AGE
> default notebook-controller-deployment-58797bdd75-9fstx 0/1
> CrashLoopBackOff 7 12m
> default pytorch-operator-75fd845678-dpc52 1/1
> Running0 12m
> default submarine-database-54776644c6-x2zrm 1/1
> Running0 12m
> default submarine-server-5d846f7b4f-m2fw8 1/1
> Running0 12m
> default submarine-traefik-d55c689b5-cq6db 1/1
> Running0 12m
> default tf-job-operator-598686fd84-2fwt9 1/1
> Running0 12m
>
> And notebook-controller pod has the following information: (kubectl
> describe pods notebook-controller-deployment-58797bdd75-9fstx)
>
> Events:
> Type Reason Age From
> Message
> --
> ---
> Normal Scheduled 12m default-scheduler
> Successfully assigned
> default/notebook-controller-deployment-58797bdd75-9fstx to docker-desktop
> Normal Pulling12m kubelet, docker-desktop
> Pulling image "apache/submarine:notebook-controller-v1.1.0-g253890cb"
> Normal Pulled 12m kubelet, docker-desktop
> Successfully pulled image
> "apache/submarine:notebook-controller-v1.1.0-g253890cb"
> Normal Pulled 11m (x4 over 12m) kubelet, docker-desktop
> Container image "apache/submarine:notebook-controller-v1.1.0-g253890cb"
> already present on machine
> Normal Created11m (x5 over 12m) kubelet, docker-desktop
> Created container manager
> Normal Started11m (x5 over 12m) kubelet, docker-desktop
> Started container manager
> Warning BackOff2m45s (x51 over 12m) kubelet, docker-desktop
> Back-off restarting failed container
>
> Logs: (kubectl log notebook-controller-deployment-58797bdd75-9fstx)
>
> 2020-11-02T17:11:53.159Z ERROR setup unable to create controller
> {"controller": "Notebook", "error": "no matches for kind \"Notebook\" in
> version \"kubeflow.org/v1beta1\ ""}
> github.com/go-logr/zapr.(
[jira] [Created] (SUBMARINE-669) notebook name contain only lowercase alphanumeric characters or '-'
Ryan Lo created SUBMARINE-669: - Summary: notebook name contain only lowercase alphanumeric characters or '-' Key: SUBMARINE-669 URL: https://issues.apache.org/jira/browse/SUBMARINE-669 Project: Apache Submarine Issue Type: Bug Components: Workbench Notebook Reporter: Ryan Lo If we create a notebook instance with name "test.a", the notebook-controller will return below error message. Reissued from statefulset/test.a: create Pod test.a-0 in StatefulSet test.a failed error: Pod "test.a-0" is invalid: [spec.containers[0].name: Invalid value: "test.a": a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name', or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?'), spec.hostname: Invalid value: "test.a-0": a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name', or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')] Object names must follow the DNS label standard as defined in [RFC 1123|https://tools.ietf.org/html/rfc1123] * contain at most 63 characters * contain only lowercase alphanumeric characters or '-' * start with an alphanumeric character * end with an alphanumeric character reference : [K8s object names and IDs|https://kubernetes.io/docs/concepts/overview/working-with-objects/names/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org For additional commands, e-mail: dev-h...@submarine.apache.org
[jira] [Created] (SUBMARINE-670) Improvements of Submarine user docs
Wangda Tan created SUBMARINE-670: Summary: Improvements of Submarine user docs Key: SUBMARINE-670 URL: https://issues.apache.org/jira/browse/SUBMARINE-670 Project: Apache Submarine Issue Type: Task Components: Doc Reporter: Wangda Tan Found the following issues during test: * Moved build Docker image from helm chart session to the build from code. * Moved Submarine Python SDK tutorial from README.md of k8s, to a separate file. * Added run experiment from UI doc. Updated contents of k8s/README.md, and make it points to all correct links. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org For additional commands, e-mail: dev-h...@submarine.apache.org
[jira] [Assigned] (SUBMARINE-670) Improvements of Submarine user docs
[ https://issues.apache.org/jira/browse/SUBMARINE-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reassigned SUBMARINE-670: Assignee: Wangda Tan > Improvements of Submarine user docs > --- > > Key: SUBMARINE-670 > URL: https://issues.apache.org/jira/browse/SUBMARINE-670 > Project: Apache Submarine > Issue Type: Task > Components: Doc >Reporter: Wangda Tan >Assignee: Wangda Tan >Priority: Major > > Found the following issues during test: > * Moved build Docker image from helm chart session to the build from code. > * Moved Submarine Python SDK tutorial from README.md of k8s, to a separate > file. > * Added run experiment from UI doc. > Updated contents of k8s/README.md, and make it points to all correct links. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org For additional commands, e-mail: dev-h...@submarine.apache.org
[jira] [Commented] (SUBMARINE-670) Improvements of Submarine user docs
[ https://issues.apache.org/jira/browse/SUBMARINE-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225033#comment-17225033 ] Wangda Tan commented on SUBMARINE-670: -- Submitted PR: https://github.com/apache/submarine/pull/444 > Improvements of Submarine user docs > --- > > Key: SUBMARINE-670 > URL: https://issues.apache.org/jira/browse/SUBMARINE-670 > Project: Apache Submarine > Issue Type: Task > Components: Doc >Reporter: Wangda Tan >Priority: Major > > Found the following issues during test: > * Moved build Docker image from helm chart session to the build from code. > * Moved Submarine Python SDK tutorial from README.md of k8s, to a separate > file. > * Added run experiment from UI doc. > Updated contents of k8s/README.md, and make it points to all correct links. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org For additional commands, e-mail: dev-h...@submarine.apache.org
Re: [VOTE] Submarine-0.5.0-RC1 is ready for a vote!
*Update:*
After restart K8s, the problem (cannot connect to notebook) is gone, I'm
not sure if there's anybody else hits the issue, it will be better if we
can add documentation to the user doc and help users to do troubleshooting.
Verified the following:
- Run example code inside the nodebook, the deepfm_example runs without any
isssue. "submarine-experiment_sdk" also runs fine, the only issue is
"submarine_client.list_experiments(status=status)" takes some time to
execute, I checked the PODs status is:
NAME READY STATUS
RESTARTS AGE
mnist-dist-ps-0 0/1 PodInitializing
0 103s
mnist-dist-worker-0 0/1 PodInitializing
0 103s
(QUESTION) I fast click "run" button from notebook page, for all paragraphs
(exclude the last one), and the experiment show in the UI after a while
(1-2 mins), I'm not sure why it takes that long. And it is hard to
understand it from both notebook and UI.
- (NEED HELP) After that, I tried to restart the notebook, I clicked the
button "Delete" on the UI, it showed a message on the UI: "Http failure
response for http://127.0.0.1:32080/api/v1/notebook/null: 404 Not Found"
- (NEED HELP) Also, I cannot launch a new notebook session, click "+ New
Notebook" doesn't have any effect, Chrome console error showed:
"ERROR TypeError: Cannot read property 'environment' of null
at Object.eval [as updateRenderer]
(ng:///NotebookModule/NotebookComponent.ngfactory.js:92)
at Object.debugUpdateRenderer [as updateRenderer] (vendor.js:88356)
at checkAndUpdateView (vendor.js:87731)"
- (QUESTION) Also, on the Notebook List UI, all Environment, Docker Image,
Resources, Status are empty for the running notebook "notebook", I
don't know if it is normal or not.
- (QUESTION) On the environment page, "my-submarine-env" is showed up, is
there any example uses the my-submarine-env? If it is introduced by some
previous test, I think we should remove it. (We should only ship usable
examples/configs during release).
- (NEED HELP) I tried to follow the notebook guide (
https://github.com/apache/submarine/blob/master/docs/userdocs/k8s/notebook.md),
run the Experiment example (see "Experiment with your notebook
"), it has error message below:
---
ApiException Traceback (most recent call last)
in
30
31 # Create experiment
---> 32 experiment =
submarine_client.create_experiment(experiment_spec=experiment_spec)
/opt/conda/lib/python3.7/site-packages/submarine/experiment/api/experiment_client.py
in create_experiment(self, experiment_spec)
57 :return: submarine experiment
58 """
---> 59 response =
self.experiment_api.create_experiment(experiment_spec=experiment_spec)
60 return response.result
61
/opt/conda/lib/python3.7/site-packages/submarine/experiment/api/experiment_api.py
in create_experiment(self, **kwargs)
75 """
76 kwargs['_return_http_data_only'] = True
---> 77 return self.create_experiment_with_http_info(**kwargs) #
noqa: E501
78
79 def create_experiment_with_http_info(self, **kwargs): # noqa:
E501
/opt/conda/lib/python3.7/site-packages/submarine/experiment/api/experiment_api.py
in create_experiment_with_http_info(self, **kwargs)
163
_preload_content=local_var_params.get('_preload_content', True),
164
_request_timeout=local_var_params.get('_request_timeout'),
--> 165 collection_formats=collection_formats)
166
167 def delete_experiment(self, id, **kwargs): # noqa: E501
/opt/conda/lib/python3.7/site-packages/submarine/experiment/api_client.py
in call_api(self, resource_path, method, path_params, query_params,
header_params, body, post_params, files, response_type, auth_settings,
async_req, _return_http_data_only, collection_formats, _preload_content,
_request_timeout, _host)
417auth_settings,
_return_http_data_only,
418collection_formats,
_preload_content,
--> 419_request_timeout, _host)
420
421 return self.pool.apply_async(
/opt/conda/lib/python3.7/site-packages/submarine/experiment/api_client.py
in __call_api(self, resource_path, method, path_params, query_params,
header_params, body, post_params, files, response_type, auth_settings,
_return_http_data_only, collection_formats, _preload_content,
_request_timeout, _host)
218 except ApiException as e:
219 e.body = e.body.decode('utf-8') if six.PY3 else e.body
--> 220 raise e
221
222 content_type = response_data.getheader('content-type')
/opt/conda/lib/python3.7/site-packages/submarine/experiment/api_client.py
in __call_api(self, resource_path, method, path_params, query_params,
h
[jira] [Updated] (SUBMARINE-668) Experiment output is Null
[
https://issues.apache.org/jira/browse/SUBMARINE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Su updated SUBMARINE-668:
---
Status: Patch Available (was: Open)
> Experiment output is Null
> -
>
> Key: SUBMARINE-668
> URL: https://issues.apache.org/jira/browse/SUBMARINE-668
> Project: Apache Submarine
> Issue Type: Bug
> Components: Backend Server
>Affects Versions: 0.6.0
>Reporter: Kevin Su
>Assignee: Ryan Lo
>Priority: Major
> Fix For: 0.6.0
>
>
> When I used minikube v14.2 or v18.0 with the latest submarine installed by
> the helm chart, the experiment output always is null.
> *http://submarine:32080/api/v1/experiment/logs*
> if I install Kubernetes by kind, I could successfully get experiment output.
>
> {code:java}
> minikube start --vm-driver=none --cpus 60 --memory 122880 --disk-size=120g
> --kubernetes-version v1.14.2
> helm install submarine ./helm-charts/submarine
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org
For additional commands, e-mail: dev-h...@submarine.apache.org
[jira] [Assigned] (SUBMARINE-668) Experiment output is Null
[
https://issues.apache.org/jira/browse/SUBMARINE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Lo reassigned SUBMARINE-668:
-
Assignee: Kevin Su (was: Ryan Lo)
> Experiment output is Null
> -
>
> Key: SUBMARINE-668
> URL: https://issues.apache.org/jira/browse/SUBMARINE-668
> Project: Apache Submarine
> Issue Type: Bug
> Components: Backend Server
>Affects Versions: 0.6.0
>Reporter: Kevin Su
>Assignee: Kevin Su
>Priority: Major
> Fix For: 0.6.0
>
>
> When I used minikube v14.2 or v18.0 with the latest submarine installed by
> the helm chart, the experiment output always is null.
> *http://submarine:32080/api/v1/experiment/logs*
> if I install Kubernetes by kind, I could successfully get experiment output.
>
> {code:java}
> minikube start --vm-driver=none --cpus 60 --memory 122880 --disk-size=120g
> --kubernetes-version v1.14.2
> helm install submarine ./helm-charts/submarine
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org
For additional commands, e-mail: dev-h...@submarine.apache.org
[jira] [Assigned] (SUBMARINE-426) [SDK] Add Convolutional Click Prediction Model
[ https://issues.apache.org/jira/browse/SUBMARINE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Chang reassigned SUBMARINE-426: Assignee: Lisa Chang > [SDK] Add Convolutional Click Prediction Model > -- > > Key: SUBMARINE-426 > URL: https://issues.apache.org/jira/browse/SUBMARINE-426 > Project: Apache Submarine > Issue Type: Sub-task > Components: SDK >Reporter: Kevin Su >Assignee: Lisa Chang >Priority: Minor > > Add TensorFlow implementation of Convolutional Click Prediction Model > [CIKM 2015][A Convolutional Click Prediction > Model|http://ir.ia.ac.cn/bitstream/173211/12337/1/A%20Convolutional%20Click%20Prediction%20Model.pdf] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org For additional commands, e-mail: dev-h...@submarine.apache.org
[jira] [Created] (SUBMARINE-671) correct the typo (parseNotebookResponseObject)
Ryan Lo created SUBMARINE-671: - Summary: correct the typo (parseNotebookResponseObject) Key: SUBMARINE-671 URL: https://issues.apache.org/jira/browse/SUBMARINE-671 Project: Apache Submarine Issue Type: Improvement Components: K8s Submitter Reporter: Ryan Lo Assignee: Ryan Lo Correct the typo "parseNotebookResponseObject" to "parseExperimentResponseObject" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org For additional commands, e-mail: dev-h...@submarine.apache.org
