You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "rajsatha01 (via GitHub)" <gi...@apache.org> on 2025/03/20 17:56:47 UTC
[I] I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. GitHub action is working fine but when I am deploying that version into argocd showing MySQL creation and initialization error [superset]
rajsatha01 opened a new issue, #32777:
URL: https://github.com/apache/superset/issues/32777
### Bug description
Superset -- exceptions.py-- line no. 333
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
--
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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. ci workflow working fine but using latest version into kubernetes cluster showing MySQL creation and initialization error [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #32777: I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. ci workflow working fine but using latest version into kubernetes cluster showing MySQL creation and initialization error
URL: https://github.com/apache/superset/issues/32777
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. GitHub action is working fine but when I am deploying that version into argocd showing MySQL creation and initialization error [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #32777:
URL: https://github.com/apache/superset/issues/32777#issuecomment-2741845193
That's... quite an issue title.
Can you give us any form of repro steps or error logs? This doesn't seem very actionable.
ALso, it says you're using latest master and Node 16. You should be using Node 20 if you're on latest.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. ci workflow working fine but using latest version into kubernetes cluster showing MySQL creation and initialization error [superset]
Posted by "rajsatha01 (via GitHub)" <gi...@apache.org>.
rajsatha01 commented on issue #32777:
URL: https://github.com/apache/superset/issues/32777#issuecomment-2747576749
I rollback previous version getting this msg
We haven't found any Content Security Policy (CSP) defined in the configurations. Please make sure to configure CSP using the TALISMAN_ENABLED and TALISMAN_CONFIG keys or any other external software. Failing to configure CSP have serious security implications. Check https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP for more information. You can disable this warning using the CONTENT_SECURITY_POLICY_WARNING key.
2025-03-22 10:56:29,071:WARNING:superset.initialization:We haven't found any Content Security Policy (CSP) defined in the configurations. Please make sure to configure CSP using the TALISMAN_ENABLED and TALISMAN_CONFIG keys or any other external software. Failing to configure CSP have serious security implications. Check https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP for more information. You can disable this warning using the CONTENT_SECURITY_POLICY_WARNING key.
/usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:67: SAWarning: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with relationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
for prop in class_mapper(obj).iterate_properties:
INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
logging was configured successfully
2025-03-22 10:56:36,542:INFO:superset.utils.logging_configurator:logging was configured successfully
But if I am trying to use apache-superset locally getting this
2025-03-17 10:11:07,258:INFO:superset.initialization:Setting database isolation level to READ COMMITTED
/app/.venv/lib/python3.11/site-packages/flask_limiter/extension.py:333: 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(
2025-03-17 10:11:07,303:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (MySQLdb.OperationalError) (3159, 'Connections using insecure transport are prohibited while --require_secure_transport=ON.')
(Background on this error at: https://sqlalche.me/e/14/e3q8)
[2025-03-17 10:11:07 +0000] [133] [INFO] Worker exiting (pid: 133)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. ci workflow working fine but using latest version into kubernetes cluster showing MySQL creation and initialization error [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #32777:
URL: https://github.com/apache/superset/issues/32777#issuecomment-2978373994
Thanks for the issue. Seens like this should have been moved to a Helo Discussion, but it's been silent for a long while now, so I'll close as inactive/not-planned, but we're happy to reopen/revisit if needed.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. GitHub action is working fine but when I am deploying that version into argocd showing MySQL creation and initialization error [superset]
Posted by "mistercrunch (via GitHub)" <gi...@apache.org>.
mistercrunch commented on issue #32777:
URL: https://github.com/apache/superset/issues/32777#issuecomment-2744667798
We don't support any kind of argocd portability of our GHA, seems like an issue on the argocd/your side (?)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] I have cloned apache superset repo into my local repo, When I am using that local repository path into my GitHub workflow. GitHub action is working fine but when I am deploying that version into argocd showing MySQL creation and initialization error [superset]
Posted by "rajsatha01 (via GitHub)" <gi...@apache.org>.
rajsatha01 commented on issue #32777:
URL: https://github.com/apache/superset/issues/32777#issuecomment-2742983624
superset.initialization:Setting database isolation level to READ COMMITTED
/app/.venv/lib/python3.11/site-packages/flask_limiter/extension.py:333: 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(
2025-03-21 10:24:52,467:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (MySQLdb.OperationalError) (3159, 'Connections using insecure transport are prohibited while --require_secure_transport=ON.')
(Background on this error at: https://sqlalche.me/e/14/e3q8)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org