nicholaslimck commented on PR #27360: URL: https://github.com/apache/superset/pull/27360#issuecomment-2519289340
> @michael-s-molina We're running [Superset `3.1.3`](https://github.com/apache/superset/releases/tag/3.1.3) deployed in Kubernetes [using the official Helm chart](https://superset.apache.org/docs/installation/kubernetes/) and still encountering this bug. > > Are there any migration scripts that need to be run or any way to verify this fix is still applied in the compiled JS? Currently running Superset 4.1.1 deployed on Helm and was experiencing the same issue with incorrect ordering:  Checked this MR and realised that the fix was only applied for the Heatmap (Legacy) chart, but I'm using the newer Heatmap chart defined [here](https://github.com/apache/superset/tree/4.1.1/superset-frontend/plugins/plugin-chart-echarts/src/Heatmap). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
