dosubot[bot] commented on issue #30596:
URL: https://github.com/apache/superset/issues/30596#issuecomment-2410944364

   <!-- Greeting -->
   Hey @otrebor! I'm here to help you with any bugs, questions, or 
contributions. Let's tackle this issue together!
   
   <!-- Answer -->
   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:
   
   1. **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.
   
   2. **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.
   
   3. **Dependencies:**
      Make sure all dependencies are up to date, especially those related to 
SQLAlchemy and encryption libraries.
   
   4. **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.
   
   5. **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.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
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]

Reply via email to