Open wz2b opened 3 months ago
Following this error message, the expanded version of the error is this:
Maximum update depth exceeded. This can happen when a component repeatedly calls setState
inside componentWillUpdate or componentDidUpdate. React limits the number of nested
updates to prevent infinite loops.
hi @wz2b I'm sorry you're running into this issue! Unfortunately, we haven't been able to reproduce it yet. A few follow up questions for you, our hope is that the answers could help us to narrow down the issue:
Thanks for reporting and for trying to test on a self hosted instance as well! If you want to try running that version of grafana locally you can by pulling down the latest of https://github.com/grafana/grafana and running git checkout 9d44c8e8cf
That said when I've done that I haven't been able to recreate the bug so I'm not sure what is not working.
That said I do see ConfigSelect
mentioned in the error message which I think is pointing to one of these components, although I don't spot the bug: https://github.com/grafana/timestream-datasource/blob/main/src/components/ConfigEditor.tsx#L80-L108 It definitely feels like an issue rendering those components, where something is causing an infinite loop of react state updates but I haven't seen yet what that is. I think if we can figure out how to easily recreate the bug it should be easier to work on.
My grafana.com instance won't load the configuration page for adding a new timestream datasource. From what I can tell, it's using plugin version 2.9.1 and the grafana version is Grafana v11.1.0-69051 (9d44c8e8cf) ... it works fine on my self-hosted grafana but I'm not on version 11.1.0.