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.

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

FE[TRACES]: Query range api is triggered twice when trace explorer page is loaded. #6308

Open
nityanandagohain opened this issue Oct 29, 2024 · 1 comment · May be fixed by #6677
Open

FE[TRACES]: Query range api is triggered twice when trace explorer page is loaded. #6308

nityanandagohain opened this issue Oct 29, 2024 · 1 comment · May be fixed by #6677
Assignees
@ahmadshaheer
Labels
frontend

Comments

@nityanandagohain
Copy link
Member

Query range api is triggered twice when trace explorer page is loaded.

Screen.Recording.2024-10-29.at.3.14.50.PM.mov
@SagarRajput-7 SagarRajput-7 self-assigned this Oct 29, 2024
@maninaik
Copy link

maninaik commented Nov 2, 2024

The TracesExplorer/ListView component gets rendered multiple times and maxTime and minTime changes throughout renders. I'm thinking we could add a debounce to the queryKey of the query-range API. (idk if it's the best solution)

@YounixM YounixM assigned ahmadshaheer and unassigned YounixM and SagarRajput-7 Dec 11, 2024
This was referenced Dec 15, 2024
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ahmadshaheer ahmadshaheer

Labels
frontend
Projects
None yet
Milestone
No milestone
5 participants
@YounixM @maninaik @nityanandagohain @ahmadshaheer @SagarRajput-7