You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a password for accessing the database that contains special characters (in this case it was @ , but others may be problematic as well) the job that initializes the database fails and Superset is never started.
Expected behavior, passwords should work regardless of which characters they contain. Also, users should not be required to escape any characters in the passwords (except maybe if they create issues with yaml).
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
No response
The text was updated successfully, but these errors were encountered:
Affected version
0.5.0
Current and expected behavior
When using a password for accessing the database that contains special characters (in this case it was @ , but others may be problematic as well) the job that initializes the database fails and Superset is never started.
Expected behavior, passwords should work regardless of which characters they contain. Also, users should not be required to escape any characters in the passwords (except maybe if they create issues with yaml).
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
No response
The text was updated successfully, but these errors were encountered: