8000 Timeline click feature is unusable after snapshot · Issue #93 · oslabs-beta/K8Mate · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Timeline click feature is unusable after snapshot #93

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.

Sign up for GitHub

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

Jump to bottom
Open
1 task
jon-si opened this issue Sep 13, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jon-si
Copy link
Collaborator
jon-si commented Sep 13, 2024

Description

On the tree page, after loading up a tree and taking a snapshot to send to the cluster history table, the page rerenders to add the new cluster into the timeline. However, upon this change, the user can no longer click on specific clusters to view them, but is still able to navigate the timeline using the arrow buttons provided under it. Refreshing the page does allow the user to use the timeline buttons again, unless the take snapshot button is clicked again.

Reproduction

  1. Open up the tree page through the sidebar navigation
  2. Click load cluster to load your most recent cluster and open up the tree structure (this also sets the firstload state as false)
  3. (Optional) Play around with the timeline on the bottom to see how the functionality should work. (Clusters displayed on the tree should change accordingly to whatever version you clicked on)
  4. Click take snapshot to send a new, current cluster data to the history database and wait for the timeline to show that newly added cluster.
  5. Try clicking around on the timeline: there should be no changes displayed on the tree.
  6. Try using the buttons to navigate across the timeline: your tree should change accordingly to the cluster version selected

System information

System:

OS: Windows 11 10.0.22631
CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
Memory: 2.01 GB / 15.34 GB

Binaries:

Node: 20.15.0 - C:\Program Files\nodejs\node.EXE
npm: 10.8.3 - C:\Program Files\nodejs\npm.CMD

Additional information

No response

👨‍👧‍👦 Contributing

  • 🙋‍♂️ Yes, I'd love to make a PR to fix this bug!
@jon-si jon-si added the bug Something isn't working label Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jon-si
0