arobertn commented on issue #30596:
URL: https://github.com/apache/superset/issues/30596#issuecomment-2835083595
Hitting this upgrading 4.0.2 -> 4.1.2. Is there any manual workaround, to
preserve the DB while upgrading? Could I send any database extract to help
debug?
```
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
INFO [alembic.runtime.migration] Running upgrade b7851ee5522f ->
06dd9ff00fe8, add_percent_calculation_type_funnel_chart
...
INFO [alembic.runtime.migration] Running upgrade 4a33124c18ad ->
58d051681a3b, Add catalog_perm to tables
Adding column 'catalog_perm' to table 'tables'.
Adding column 'catalog_perm' to table 'slices'.
Traceback (most recent call last):
File "/usr/local/bin/superset", line 8, in <module>
sys.exit(superset())
File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1157,
in __call__
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1078,
in main
rv = self.invoke(ctx)
...
File
"/usr/local/lib/python3.10/site-packages/sqlalchemy_utils/types/encrypted/encrypted_type.py",
line 52, in _update_key
digest.update(key)
TypeError: argument 'data': a bytes-like object is required, not 'NoneType'
```
--
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]
