Pie charts display bad data on mouse-over

[jrmuizel]

Issue Summary

A summary of the issue and the browser/OS environment in which it occurs.

Steps to Reproduce

1. Mouse over the 41.7% and 44.6% slices of "webrender why not release?" on https://sql.telemetry.mozilla.org/dashboard/webrender

2. The popups say "0.01% (2,341)" "1.14% (529,596)" which makes no sense give the percentages on the actual pie-chart

Technical details:

• Redash Version: 9.0.0+alpha
• Browser/OS: Firefox + macOS
• How did you install Redash: N/A

[susodapop]

Please provide more detail. There's nothing actionable here because we can't see your private Redash instance. Stated another way: how can we reproduce the issue?

[jrmuizel]

Ah sorry. I didn't realize it wasn't public. Here's the dashboard: https://sql.telemetry.mozilla.org/public/dashboards/Zo3A3uEtmUIEyhA5hRpSHPFtNXJ0BzPxtTKPUxSJ?org_slug=default

[susodapop]

Sorry to be a stickler but that's still not enough. While it's clear something is out of whack it's impossible to tell what that might be. We need to see the actual data behind the chart so we can reproduce it on our end. You can paste the CSV data in your issue description.

[jrmuizel]

x-column is count, y-column is wr_qualified

count,webrender,wr_qualified
31,disabled,blocked-screen-too-large
19471339,opt-in,denied
3,disabled,blocked-vendor-unsupported
14,disabled,blocked-has-battery
10849,unavailable,blocked
20275114,opt-in,blacklisted
2,unavailable,blocked-release-channel-battery
76,disabled,blocked-release-channel-battery
1456,unavailable-no-angle,blocked-has-battery
152,unavailable-no-gpu-process,blacklisted
788,blocked,blocked
260,unavailable-no-gpu-process,denied
5,unavailable,blocked-device-too-old
11,unavailable,blacklisted
552081,opt-in,blocked
1,opt-in,blocked-screen-unknown
141703,unavailable,available
4,unavailable-no-gpu-process,blocked-vendor-unsupported
8,unavailable-no-gpu-process,blocked-has-battery
6,unavailable-no-gpu-process,blocked-device-too-old
11,unavailable-no-gpu-process,blocked-screen-too-large
1224720,opt-in,blocked-device-too-old
4057,unavailable-no-angle,blocked-device-too-old
623682,opt-in,blocked-screen-too-large
15,unavailable-no-gpu-process,blocked-release-channel-battery
1091966,,
2162,disabled,blacklisted
210499,opt-in,blocked-vendor-unsupported
48,disabled,blocked-device-too-old
388,unavailable-no-gpu-process,available
42,unavailable,denied
2341,disabled,denied
5431,disabled,available
1231,unavailable-no-angle,blocked-vendor-unsupported
529596,unavailable-no-angle,blacklisted
2182169,opt-in,blocked-release-channel-battery
87366,opt-in,available
6,disabled,blocked
235547,opt-in,blocked-has-battery

[susodapop]

This isn't a bug. What's happening is your query returns more than one Y for every X, which we would expect to cause issues. It's a different version of this behavior.

The solution in our docs applies here:

You can resolve this by filtering out the doubled entries on the X axis. Or revise the query to include a grouping field...

See the screenshots below.

Current

Grouping on wr_qualified field

There was a similar discussion on the user forum late last year.

[jrmuizel]

Ok, that's sort of surprising behaviour, but thanks for your help.