LeiZhangImo opened a new issue #17206:
URL: https://github.com/apache/superset/issues/17206
A clear and concise description of what the bug is.
#### How to reproduce the bug
1. Go to swagger/v1 scroll down to post dataset
2. Click on 'Try it out'
3. Input following:
`{
"database": 1,
"owners": [
1
],
"schema": "testschema",
"table_name": "tenant002"
}`
4. See an error in the error log
`
{
"errors": [
{
"message": "400 Bad Request: The CSRF token is missing.",
"error_type": "GENERIC_BACKEND_ERROR",
"level": "error",
"extra": {
"issue_codes": [
{
"code": 1011,
"message": "Issue 1011 - Superset encountered an unexpected
error."
}
]
}
}
]
}
`
### Expected results
get 200 without error
### Environment
- browser type and version: Chrome/94.0.4606.61
- superset version: superset docker: apache/superset:1.3.2
- python version: Python 3.8.12
- node.js version: not know
- any feature flags active: connected to aws Anthena
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [x] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [x] I have reproduced the issue with at least the latest released version
of superset.
- [x] I have checked the issue tracker for the same issue and I haven't
found one similar.
### Additional context
I'm using the Admin user, even after this error occurred the GET /dataset
API still working.
--
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]
