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

Secondary dashboards not staying active. #404

Open
birdman3131 opened this issue Apr 5, 2023 · 3 comments
Open

Secondary dashboards not staying active. #404

birdman3131 opened this issue Apr 5, 2023 · 3 comments

Comments

@birdman3131
Copy link

I recall us talking about this a few months back but I figured I would bring it back to your mind.

Secondary dashboards often lose their identity. Often times I am switched back to what I believe is the original dashboard (Windhart Gaming) created with my account.

A couple observations.

  1. I have never been switched from windhart to another dashboard. Only back to windhart
  2. I did not have a default dashboard before this. While testing I set my default to Youtube Test, logged out and back in directly to youtube test and it never switched me to windhart. As soon as I switched to windhart and then back to youtube test it would start throwing me back to windhart.

In the video below watch how the moment I click on the server it switches me back if you watch the dashboard name.

bug1.mp4
@mvaessen
Copy link
Contributor

mvaessen commented Apr 5, 2023

Hi,

Thanks for reporting!

This is an issue that I came across in the passed too but is quite hard to fix due to how GSA is working on some pages.
I spent quite some time trying to figure out what caused it and it turns out it's the AJAX calls for the overview & game server blocks! When the ajax calls haven't finished yet, and you switch to another dashboard, the session data isnt properly stored / overwritten by the existing requests.

You can test this by switching to another dashboard on a page where there are no ajax calls or wait for the ajax calls to finish.

I'm not entirely sure why that happens, but the solution might be forcing the browser to wait for all calls to finish before it can use the dashboard switcher.

@github-actions github-actions bot added the status: backlog This item is on the backlog for future releases label Apr 5, 2023
@mvaessen
Copy link
Contributor

I haven't been able to reproduce this issue anymore recently. Does it still happen for you @birdman3131 ?

@github-actions github-actions bot added status: needs more info This item did not come with enough info to pick it up. and removed status: backlog This item is on the backlog for future releases labels Mar 22, 2024
@birdman3131
Copy link
Author

Just checked and it will still do it.

@github-actions github-actions bot added status: backlog This item is on the backlog for future releases and removed status: needs more info This item did not come with enough info to pick it up. labels Mar 22, 2024
@mvaessen mvaessen moved this from Inbox to Backlog in GSA Development Jul 2, 2024
@mvaessen mvaessen removed the status: backlog This item is on the backlog for future releases label Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

2 participants