thatguyatgithub commented on issue #37842:
URL: https://github.com/apache/superset/issues/37842#issuecomment-3877876473

   The bot missinterpreted the output. The `re-encrypt-secrets` did NOT throw 
any errors, it finished with exit code 0 and no errors, as shown before:
   ```
   # superset --debug re-encrypt-secrets
   Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
   2026-02-10 13:15:28,470:DEBUG:superset.utils.logging_configurator:logging 
was configured successfully
   2026-02-10 13:15:28,537:DEBUG:root:Configured event logger of type <class 
'superset.utils.log.DBEventLogger'>
   2026-02-10 13:15:28,543:DEBUG:superset.initialization:Setting database 
isolation level to READ COMMITTED
   /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:324: 
UserWarning: Using the in-memory storage for tracking rate limits as no storage 
was explicitly specified. This is not recommended for production use. See: 
https://flask-limiter.readthedocs.io#configuring-a-storage-backend for 
documentation about configuring the storage backend.
     warnings.warn(
   2026-02-10 13:15:29,181:INFO:alembic.runtime.migration:Context impl 
PostgresqlImpl.
   2026-02-10 13:15:29,181:INFO:alembic.runtime.migration:Will assume 
transactional DDL.
   2026-02-10 13:15:29,714:INFO:superset.app:Syncing configuration to 
database...
   2026-02-10 13:15:29,724:DEBUG:superset.commands.theme.seed:Updated system 
theme: THEME_DEFAULT
   2026-02-10 13:15:29,733:DEBUG:superset.commands.theme.seed:Updated system 
theme: THEME_DARK
   2026-02-10 13:15:29,735:INFO:superset.app:Configuration sync to database 
completed successfully
   2026-02-10 13:15:30,516:INFO:superset.utils.encrypt:Collecting info for re 
encryption
   2026-02-10 13:15:30,517:INFO:superset.utils.encrypt:All tables processed
   ```
   
   The errors raise at the main superset node process when any operation from 
the webui attempts to gather either DB connections or anything like that.
   
   If I go back and restore the superset_config.py with the original 
SECRET_KEY, everything goes back to normal, meaning 
   It looks like `superset re-encrypt-secrets` is not performing any actions at 
all from the get go.


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