Trace popup closes when switching trance in trace viewer opened from dashboard

[demorgi]

HyperDX version: 2.7.1

Steps to reproduce

• Create a dashboard with a search

• Click on the search row to open details
• In the trace waterfall, click on any row
• Details view immediately closes

[pulpdrew]

Thanks for reporting this @demorgi. I am having trouble reproducing this.

Are you able to provide the following to help us debug the issue?

1. Any errors you see in the browser console just after the details view closes
2. The configuration for a dashboard that exhibits this issue? You could export the dashboard configuration using the export functionality at the top-right of the dashboard page.

[demorgi]

@pulpdrew I was able to reproduce that on local instance of hyperdx (latest image)
docker.hyperdx.io/hyperdx/hyperdx-all-in-one
0d26b215464b

Attaching dashboard json, some screenshots (you need to have 2 tables with filters to reproduce)

My Dashboard.json

also adding a link to the screen recording
https://1drv.ms/v/c/a094d25d5a05f68c/ERP8z5KgMshAmCozExwfT7IBlWq4odgtmSHlQgWOkicQkQ?e=xtCgOc

[pulpdrew]

Thanks @demorgi , I was able to reproduce the issue with the dashboard export you provided. This does appear to be a bug - thank you for reporting it! We'll try to get this fixed.

[amizyak]

Do you have an ETA?

[demorgi]

@pulpdrew, following up, this is blocking us from version updates, any ETA on this?

[pulpdrew]

Hi @demorgi, we're still looking into it. It appears that this is not specific to clicking on a span in the waterfall chart - any click in the side panel on a dashboard with >=2 search tables will result in the side panel closing.

The bug appears to have been introduced in #1171 (with that change, multiple search tables on the same dashboard results in multiple SidePanels being rendered, though only one at a time is rendered) and I believe the issue is this useClickOutside ref. I'll check with the team tomorrow if we can remove that now, as it appears that clicking outside the drawer results in the expected behavior without this hook.

[pulpdrew]

The fix has been merged and will be available in our next release. Thanks again for reporting the issue.