dosubot[bot] commented on issue #29289:
URL: https://github.com/apache/superset/issues/29289#issuecomment-2175583746
<!-- Answer -->
To resolve the 500 error and the unexpected keyword argument 'extra_filters'
issue, follow these steps:
1. **Check Superset Configuration**:
Ensure that `DEBUG` mode is set to `False` in your Superset
configuration. This affects error handling behavior.
2. **Review Error Handling Code**:
The error handling code in `superset/views/base.py` handles different
exceptions and returns appropriate responses. For HTTP 500 errors, it serves a
static HTML file if `DEBUG` is `False`.
3. **Verify Static Assets**:
Ensure the static HTML file for the 500 error exists at
`static/assets/500.html`:
```python
path = files("superset") / "static/assets/500.html"
return send_file(path, max_age=0), 500
```
4. **Enable Stacktrace for Debugging**:
Temporarily enable stacktrace in the configuration to get more details
about the error:
```python
def get_error_msg() -> str:
if conf.get("SHOW_STACKTRACE"):
error_msg = traceback.format_exc()
else:
error_msg = "FATAL ERROR \n"
error_msg += (
"Stacktrace is hidden. Change the SHOW_STACKTRACE "
"configuration setting to enable it"
)
return error_msg
```
5. **Check Logs**:
Review the logs for warnings or exceptions that might provide more
context about the 500 error:
```python
logger.warning("HTTPException", exc_info=True)
logger.exception(ex)
```
6. **Return JSON Error Response**:
Ensure the JSON error response is returned correctly if the request is
not for HTML:
```python
return json_errors_response(
errors=[
SupersetError(
message=utils.error_msg_from_exception(ex),
error_type=SupersetErrorType.GENERIC_BACKEND_ERROR,
level=ErrorLevel.ERROR,
),
],
status=ex.code or 500,
)
```
Additionally, there have been recent updates in the `flask` and `flask_wtf`
libraries that could affect form handling:
- `flask` updated to version 2.2.5
- `flask_wtf` updated to version 1.1.0
Review the release notes for these versions to identify specific changes
that could impact the `LoginForm_db` class
<sup>[[1]](https://github.com/apache/superset/blob/master/superset/views/base.py)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/pyproject.toml)</sup>.
Finally, ensure your `superset/config.py` file has the correct
configurations for CSRF protection:
- **WTF_CSRF_ENABLED**:
```python
WTF_CSRF_ENABLED = True
```
- **WTF_CSRF_EXEMPT_LIST**:
```python
WTF_CSRF_EXEMPT_LIST = [
"superset.views.core.log",
"superset.views.core.explore_json",
"superset.charts.data.api.data",
]
```
- **WTF_CSRF_TIME_LIMIT**:
```python
WTF_CSRF_TIME_LIMIT = int(timedelta(weeks=1).total_seconds())
```
These configurations control CSRF protection settings, which directly impact
how `LoginForm_db` interacts with `wtforms` and `flask_wtf`
<sup>[[3]](https://github.com/apache/superset/blob/master/superset/config.py)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
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]
