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

Facing issues with connecting to SQL lab after updating to superset 3.1.2 #27920

Open
3 tasks done
Kabeer001 opened this issue Apr 5, 2024 · 5 comments
Open
3 tasks done

Comments

@Kabeer001
Copy link

Bug description

Facing issues with connecting to SQL lab after updating to superset 3.1.2. I have checked the superset logs also but it's not available .
Screenshot (561)

How to reproduce the bug

I have updated the superset 3.0.0 to 3.1.2

Screenshots/recordings

Screenshot (561)

Superset version

master / latest-dev

Python version

3.10

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
@rusackas
Copy link
Member

rusackas commented Apr 5, 2024

Does your browser's console provide any additional information/errors?

@Henryz0928
Copy link

This is caused by internationalization.

@rusackas
Copy link
Member

rusackas commented Apr 8, 2024

@Henryz0928 can you elaborate a bit on what you mean?

@Kabeer001
Copy link
Author

I have updated the version; it has been updated successfully, but sql lab is not working; it shows an unexpected error. I can't check the console because, for immediate purposes, I have degraded the version to 3.0.0. Now it's alright, but I do not know what's the problem with my update.

@Henryz0928
Copy link

@rusackas Hello, the issue raised by the author came up when I accidentally modified messages.json and then ran the front-end project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants