Open otrebor opened 1 week ago
Hey @otrebor! I'm here to help you with any bugs, questions, or contributions. Let's tackle this issue together!
The error you're encountering seems to be related to the upgrade_catalog_perms
function in the migration script, which is trying to update catalog permissions. The specific TypeError
indicates that a NoneType
is being passed where a bytes-like object is expected, likely during the encryption key update process in encrypted_type.py
.
Here are a few steps you can take to troubleshoot and potentially resolve the issue:
Check Encryption Key Configuration:
Ensure that your encryption keys are correctly configured in your superset_config.py
. A missing or misconfigured key could lead to a NoneType
being passed.
Database Integrity: Verify the integrity of your database. Ensure that all necessary tables and columns exist and are correctly populated, especially those related to catalogs and encryption.
Dependencies: Make sure all dependencies are up to date, especially those related to SQLAlchemy and encryption libraries.
Debugging:
Add logging or debugging statements in the encrypted_type.py
file to trace the value of the key being passed to digest.update
. This might help identify why a NoneType
is being encountered.
Review Related Issues: Although you mentioned that other issues might not be directly related, reviewing them could provide additional insights or workarounds.
If these steps don't resolve the issue, consider isolating the problem by creating a minimal setup to reproduce the error, which might help in identifying the root cause.
To continue talking to Dosu, mention @dosu.
Bug description
We are trying to upgrade our superset instance to 410rc2-py310
when we start superset, we get this error while the migration scripts are trying to update the catalog:
I can't really understand if it's a configuration problem or a bug. The connection string seems fine and previous tables are updated.
we see other issues like https://github.com/apache/superset/issues/29492 https://github.com/apache/superset/issues/29728 but i don't think that's the problem for us.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.10
Node version
16
Browser
Chrome
Additional context
Checklist