* fix: docs/api won't render
fix: docs/api won't render
It's unclear to me exactly why, but docz is flimsy with the way
things are named and runs into odd collision and error messages.
Somehow renaming the route seem to help. Jut rolling with it after many
`gatsby clean`
* kill paths-ignore on github-actions
* trigger
* style(sqllab): make database errors more clear and render as monospace
In SQL Lab, when a database error message is returned, generally because
of a user error in the SQL, it's identified as an "Unexpected Error" and
some of the text formatting of the error message (\n, spaces, tabs, ...)
are lost as they are rendered in html.
This PR identifies the error as a "Database Error", and renders like
more like a <pre>, using a monospace font.
* fix the build
* addressing comments
* addressed comments
* lint + removing cruft
* addressing comments
* fix: enable consistent etag across workers
* Use CACHE_DEFAULT_TIMEOUT instead of 0
* Change timeout to 0 and set expires header even for no-cache
* Reduce number of if branches to appease Pylint
* Fix mypy error
* docs: typo
* docs: consistent two-line gap before sections in README
this is merely to touch something outside of docs/ to work around a CI
issue (comment in #11152), while not creating diff-noise only
* rescinding htaccess rewrite
* Changing License link title to make Apache happy
* Revert "rescinding htaccess rewrite"
This reverts commit 0ee153ef08.
* changing url in asf.yaml
* fix: alembic migration fails by deleting non existent constraint on tables
* Revert "fix: alembic migration fails by deleting non existent constraint on tables"
This reverts commit 3a359b0577.
* mantain migration but just for MySQL and add downgrade procedure
* skip the downgrade
Recently a change related to emotion styling not properly working through
react-bootstrap's popover broke the SpatialControl.
This PR makes SpatialControl use antd's equivalent, and addresses the
issue as a result: emotion's styling context is preserved through
this superior popover.
* fix: Disabling timezone of dataframe before passing Prophet
While running forecasting with Druid. Prophet throws the following exception. This PR removes the timezone info.
ValueError: Column ds has timezone specified, which is not supported. Remove timezone
https://github.com/apache/incubator-superset/issues/11106
@villebro
* Update pandas_postprocessing.py
* Update superset/utils/pandas_postprocessing.py
Co-authored-by: Ville Brofeldt <33317356+villebro@users.noreply.github.com>
Co-authored-by: Ville Brofeldt <33317356+villebro@users.noreply.github.com>
* Fix table existance validation function
* Drop left over table name index in mysql db
* Do not modify model
Co-authored-by: bogdan kyryliuk <bogdankyryliuk@dropbox.com>
* fix(api): unable to delete virtual dataset because of wrong permission name
* Still delete the dataset even when no permission was found
* migration script to fix possible existing faulty permissions on the db
* black
* fix db migration and one more test
* add more comments to the migration script
* freeze a partial schema of the model on the migration step
* fix mig script
* Update superset/migrations/versions/3fbbc6e8d654_fix_data_access_permissions_for_virtual_.py
Co-authored-by: Ville Brofeldt <33317356+villebro@users.noreply.github.com>
Co-authored-by: Ville Brofeldt <33317356+villebro@users.noreply.github.com>