[MXS-4449] Query Editor GUI Same connection is mapping to two work sheets Created: 2022-12-13  Updated: 2023-01-11  Resolved: 2023-01-09

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 22.08.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Naresh Chandra Assignee: Duong Thien Ly
Resolution: Won't Fix Votes: 0
Labels: None

Attachments: PNG File image-2022-12-13-23-42-03-207.png    
Sprint: MXS-SPRINT-173, MXS-SPRINT-174

 Description   

I see that same connection is mapping to work sheets. Even after refreshing the browser alos its like that only.

 Comments   
Comment by Duong Thien Ly [ 2022-12-28 ]

naresh.chandra@copart.com By any chance, do you have steps to reproduce this issue?

Comment by Naresh Chandra [ 2022-12-28 ]

Duong, I am unable to reproduce but its randomly happening.

Comment by Duong Thien Ly [ 2022-12-30 ]

Were you using multiple browser tabs for the GUI?

Comment by Naresh Chandra [ 2022-12-30 ]

May be sometimes we are using multiple browser tabs but not all the time.

Comment by Duong Thien Ly [ 2023-01-09 ]

naresh.chandra@copart.com Sorry for the late response, I was on vacation.
If you're using multiple browser tabs simultaneously and one or some browser tabs are opening the query editor, then it's expected to have
odd behaviors. This is because the query editor app data is persisted in browser storage, changes in one browser tab may override the others.
In other words, for now, we don't support multiple browser tabs.
I'll update the limitation in the documentation soon. So I'll close this ticket as won't fix.

Comment by Duong Thien Ly [ 2023-01-09 ]

The bug occurs when maxgui is opened in multiple browser tabs. If one or some of those tabs are opening the query editor, changes to one browser tab may override the other browser tabs and leads to some weird bugs. This is a limitation for the query editor, so it will be documented later.

Comment by Naresh Chandra [ 2023-01-11 ]

Thanks, Duong, for the confirmation.

Generated at Thu Feb 08 04:28:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.