[Bug]: Creating user setting on Metrics dashboard causes "Oops, something unexpected happened!" that can't be mitigated

[dnoggle]

Bug description

I modified the network interfaces section in the Metrics dashboard to change the overview dial configuration and after saving it as a user setting, the dashboard immediately crashed and now crashes with "Oops, something unexpected happened! - TypeError: i.getUI(...).getMinMax is not a function" on every load. Other rooms' Metrics dashboard work fine and the broken room's other dashboards work fine. Only the Metrics dashboard is failing.

Expected behavior

I expected to save the user setting and have it apply without failing.

Steps to reproduce

1. Find the Network Interfaces section on the Metrics dashboard
2. On the summary dial (the first one), click on labels and select type "real"
3. Change the metric from Average to Maximum
4. Click the save button, provide a name, and click Save.

Screenshots

Error Logs

Error message in Chrome Dev Tools:

6375.6df9f6e….js:2 TypeError: i.getUI(...).getMinMax is not a function at P (7866.e30da66fffe7362…c.chunk.js:2:112124) at go (npm.react.dom.cf35ec…15d43944.js:2:61134) at xi (npm.react.dom.cf35ec…5d43944.js:2:120785) at bs (npm.react.dom.cf35ec…5d43944.js:2:109891) at vs (npm.react.dom.cf35ec…5d43944.js:2:109819) at gs (npm.react.dom.cf35ec…5d43944.js:2:109682) at as (npm.react.dom.cf35ec…5d43944.js:2:106462) at ls (npm.react.dom.cf35ec…5d43944.js:2:105013) at x (6375.6df9f6e….js:2:514761) at MessagePort.M (6375.6df9f6e….js:2:515295)Caused by: React ErrorBoundary TypeError: i.getUI(...).getMinMax is not a function at P (https://app.netdata.cloud/7866.e30da66….chunk.js:2:112056) at div at C (https://app.netdata.cloud/6375.6df9f6e….js:2:547439) at E (https://app.netdata.cloud/7866.e30da66….chunk.js:2:112436) at div at C (https://app.netdata.cloud/6375.6df9f6e….js:2:547439) at M (https://app.netdata.cloud/7866.e30da66….chunk.js:2:112894) at div at C (https://app.netdata.cloud/6375.6df9f6e….js:2:547439) at https://app.netdata.cloud/7866.e30da66….chunk.js:2:114029 at https://app.netdata.cloud/7866.e30da66….chunk.js:2:154433 at https://app.netdata.cloud/7866.e30da66….chunk.js:2:153344 at div at C (https://app.netdata.cloud/6375.6df9f6e….js:2:547439) at div

Desktop

OS: Windows
Browser: Chrome
Browser Version: 134

Additional context

No response

[novykh]

@dnoggle just made a release and managed to include a fix for this. Please check if it's ok for you.
The issue is that the gauge chart you were saving settings for, was also below as a histogram. Saving the settings, was auto-selecting those same settings in the histogram (the bug was duplicate ids there) and it was failing.

If it doesn't crash for you, you should see the chart you changed, like it has no settings attached to it now, and the histogram below should have your settings (mistakenly like we said before).
Unfortunately you should manually remove the settings from the histogram (given you don't need them of course, maybe you will like a big gauge there 😄 )

Thanks for reporting, we tried to fix it as soon as possible. Feel free to reopen this if something is still weird or failing.

[dnoggle]

It works! Thanks a bunch for the quick fix!