canonical / canonical/data-science-stack

Feedback on implementing the dss commands with timeout

Open
#63 5 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
37
Forks
10
PR merge metrics
No merged PRs in 30d

Description

### Bug Description

Implementing the `dss initialize` and `dss create-notebook` commands with timeout affects the dss user experience, where the timeout failure logs commands are sometimes not helpful. For example as mentioned [here](https://github.com/canonical/data-science-stack/issues/44#issue-2175526056) for `dss initialize` and [here](https://github.com/canonical/data-science-stack/pull/43#discussion_r1546202201) for `dss create-notebook`.

It's necessary to consider, with the help of the UX team, whether the commands should have timeout and how to make the status of dss visible to users.

### To Reproduce

Install dss from source and run the commands
```
KUBECONFIG=~/.kube/config
pip install .
dss initialize --kubeconfig $KUBECONFIG
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.