dosubot[bot] commented on issue #33595: URL: https://github.com/apache/superset/issues/33595#issuecomment-2913599791
<!-- Greeting --> Hi @matvey12322! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the superset team. <!-- Answer --> There is a known issue with SQL Lab in Superset 3.1.2 and 3.1.3 that can cause the "Unexpected error" popup with a TypeError like "can't convert undefined to object." This is often related to internationalization (i18n) problems, specifically involving the `messages.json` file, or to database migrations not being fully applied after an upgrade [[source](https://github.com/apache/superset/issues/27920)]. **Recommended steps to resolve:** 1. **Database Migration and Initialization** Deploy the latest Superset image for your version, then run the following commands inside your Superset environment (such as your pod or container): ``` superset db upgrade superset init ``` This has resolved the issue for others after upgrading to 3.1.x [[source](https://github.com/apache/superset/issues/31461)]. 2. **Check for i18n/message file issues** If the error persists, it may be related to a missing or corrupted `messages.json` file used for internationalization. Ensure that this file exists and is valid in your deployment [[source](https://github.com/apache/superset/issues/27920)]. 3. **Check Superset Logs** Since the error message is generic, check your Superset backend logs for any Python stack traces or more detailed error messages. This can help pinpoint the root cause if the above steps do not resolve the issue. 4. **Recent Changes** There have been recent changes to SQL Lab, such as enabling new features and improving error handling, but these are not directly related to this error. Keeping your deployment up to date with patches may help prevent similar issues in the future. If you continue to see the error after these steps, sharing the relevant log output or stack trace will help further diagnose the problem. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/45773ba0-cebd-41aa-bc84-80e325c30d0c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/45773ba0-cebd-41aa-bc84-80e325c30d0c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/45773ba0-cebd-41aa-bc84-80e325c30d0c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/45773ba0-cebd-41aa-bc84-80e325c30d0c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/45773ba0-cebd-41aa-bc84-80e325c30d0c?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/45773ba0-cebd-41aa-bc84-80e325c30d0c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/45773ba0-cebd-41aa-bc84-80e325c30d0c?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33595) -- 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]
