Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected error occur when make a new query in panel. #493

Closed
karl-sh80 opened this issue Nov 5, 2024 · 7 comments · Fixed by #526
Closed

Unexpected error occur when make a new query in panel. #493

karl-sh80 opened this issue Nov 5, 2024 · 7 comments · Fixed by #526
Assignees

Comments

@karl-sh80
Copy link

karl-sh80 commented Nov 5, 2024

What happened:
I am using grafana 9.5.21 with the opensearch plugin 2.21.1
I created a new panel with opensearch darasource, but an error occurred from the first query.

"An unexpected error happened
TypeError: (0, unexpected.isAction) is not a function

  • from plugin v2.20.0, this type error occur.

What you expected to happen:
The window where you can register the query normally should be visible.

How to reproduce it (as minimally and precisely as possible):
Create a new panel and select opensearch datasource.

Anything else we need to know?:

Environment:

  • Grafana version: 9.5.21
  • OpenSearch version: 2.17.1
  • Plugin version: 2.21.1
@caviliar
Copy link

caviliar commented Nov 5, 2024

have also encountered this issue. we worked around it by pinning the version back to 2.19.1.

grafana-opensearch-datasource 2.19.1

(looks like upgrading to the latest 11.3.0 also fixes the bug)
#488

(previous) Environment:
Grafana version: v10.4.11
OpenSearch version: 2.13
Plugin version: 2.21.1

@idastambuk idastambuk moved this from Incoming to Next in AWS Datasources Nov 5, 2024
@idastambuk
Copy link
Contributor

Hi @karl-sh80, we're taking a look and we'll update when we have more info. In the meantime, are you able to apply the workaround(s) suggested by @caviliar?
Thanks for the info @caviliar!

@karl-sh80
Copy link
Author

Hi @idastambuk, I have already applied the workaround to my grafana suggested by @caviliar.
Thank you @caviliar.

@psauvage0
Copy link
Contributor

Hi, we encountered this problem with grafana 10.1.8 when working on this : #483
We found that the problem came from the upgrade of @redux/toolkit in this commit : d701c1c
@idastambuk Can we consider a downgrade of this package to allow for more versions of grafana to work with the plugin ?

@sfisli
Copy link

sfisli commented Dec 9, 2024

any updates ?

@iwysiu iwysiu self-assigned this Dec 13, 2024
@iwysiu iwysiu moved this from Next to In Progress in AWS Datasources Dec 13, 2024
@iwysiu iwysiu removed their assignment Dec 13, 2024
@iwysiu iwysiu moved this from In Progress to Next in AWS Datasources Dec 13, 2024
@kevinwcyu kevinwcyu self-assigned this Dec 18, 2024
@kevinwcyu kevinwcyu moved this from Next to In Progress in AWS Datasources Dec 18, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in AWS Datasources Dec 20, 2024
@forrejam
Copy link

forrejam commented Jan 14, 2025

I'm still getting this issue.

Grafana 11.0
Plugin 2.22.2

Has this fix made its way into release yet?

EDIT: Upgrading Grafana to 11.4 has fixed this issue for me.

@kevinwcyu
Copy link
Contributor

This should be fixed in Plugin version 2.22.3 which was just released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

8 participants