-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
4.1.0rc1 migration fails if there is unreachable database. #29728
Labels
data:databases
Related to database configurations and connections
deploy
validation:validated
A committer has validated / submitted the issue or it was reported by multiple users
Comments
dosubot
bot
added
data:databases
Related to database configurations and connections
deploy
labels
Jul 28, 2024
This comment was marked as off-topic.
This comment was marked as off-topic.
@betodealmeida I thought we had fixed a similar issue before in the migration script. |
I'm also experiencing this when trying to start up 4.1.0, an error occurs at the same migration:
|
sfirke
added
the
validation:validated
A committer has validated / submitted the issue or it was reported by multiple users
label
Jul 29, 2024
I thought I fixed this. Let me take a look! |
9 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
data:databases
Related to database configurations and connections
deploy
validation:validated
A committer has validated / submitted the issue or it was reported by multiple users
Bug description
I'm testing version 4.1.0rc1, but migration fails due to unreachable databases, resulting in the following error:
How to reproduce the bug
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: