Fixes an issue where the DashboardDS would not get the correct data from the source panels SceneQueryRunner._results because the source panel _results buffer would be empty. This affected the dashboard DS in various scenarios but was observed consistently when creating a new dashboard.
In a new dashboard, if you would create a new panel, it's _results buffer in the query runner would be empty. As soon as you saved the dashboard and refreshed the page the buffer would populate and thus the DashboardDS would also work.
The problem was in SceneQueryRunner cloning where we now emit the data in the clone so it can be picked up by the DashboardDS.
📦 Published PR as canary version: 4.5.4--canary.681.8570869587.0
:sparkles: Test out this PR locally via:
```bash
npm install @grafana/scenes@4.5.4--canary.681.8570869587.0
# or
yarn add @grafana/scenes@4.5.4--canary.681.8570869587.0
```
Fixes https://github.com/grafana/grafana/issues/84575
Fixes an issue where the DashboardDS would not get the correct data from the source panels
SceneQueryRunner._results
because the source panel_results
buffer would be empty. This affected the dashboard DS in various scenarios but was observed consistently when creating a new dashboard.In a new dashboard, if you would create a new panel, it's
_results
buffer in the query runner would be empty. As soon as you saved the dashboard and refreshed the page the buffer would populate and thus the DashboardDS would also work.The problem was in
SceneQueryRunner
cloning where we now emit the data in the clone so it can be picked up by the DashboardDS.📦 Published PR as canary version:
4.5.4--canary.681.8570869587.0
:sparkles: Test out this PR locally via: ```bash npm install @grafana/scenes@4.5.4--canary.681.8570869587.0 # or yarn add @grafana/scenes@4.5.4--canary.681.8570869587.0 ```