Skip to content
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

Active sessions do not always show up in the dashboard #2593

Closed
olevski opened this issue Jun 7, 2023 · 0 comments · Fixed by #2608
Closed

Active sessions do not always show up in the dashboard #2593

olevski opened this issue Jun 7, 2023 · 0 comments · Fixed by #2608
Labels
bug status/triage Issue needs to be triaged

Comments

@olevski
Copy link
Member

olevski commented Jun 7, 2023

To replicate:

  1. start a few sessions in different projects
  2. navigate to the page that shows all active sessions in a specific project
  3. from here navigate straight to the renku home page by clicking the renku logo
  4. no sessions will show up at all (even though there are several active)
  5. click the refresh button, now active sessions will show up

See the video.

Tested on Mac, with Chrome browser.

The ui version used is from commit sha 3bfe4f24 on the master branch. This was tested in a ci deployment that targeted the master of the ui. And when this was deployed the head of master was that commit.

See video:
https://github.com/SwissDataScienceCenter/renku-ui/assets/16360283/c6218b49-8552-4a7f-9793-87b9640ebd54

@olevski olevski added bug status/triage Issue needs to be triaged labels Jun 7, 2023
leafty added a commit that referenced this issue Jun 19, 2023
leafty added a commit that referenced this issue Jun 21, 2023
Fixes #2593.

Explanation: the current version of the code runs `notebookCoordinator.fetchNotebooks()` only the first time the Dashboard component is rendered.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug status/triage Issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant