when i use my custom superset_config.py,there is an error like this,how to fix it ?

[yang472541642]

ke Gecko)  Mobile/15E148 wxwork/4.1.33 MicroMessenger/7.0.1 Language/zh ColorScheme/Light wwmver/3.26.15.613"
WARNING:superset.views.error_handling:Exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/app/superset/utils/log.py", line 303, in wrapper
    value = f(*args, **kwargs)
  File "/app/superset/views/core.py", line 894, in welcome
    if not g.user or not get_user_id():
  File "/usr/local/lib/python3.10/site-packages/werkzeug/local.py", line 318, in __get__
    obj = instance._get_current_object()
  File "/usr/local/lib/python3.10/site-packages/werkzeug/local.py", line 526, in _get_current_object
    return get_name(local())
  File "/usr/local/lib/python3.10/site-packages/flask_login/utils.py", line 25, in <lambda>
    current_user = LocalProxy(lambda: _get_user())
  File "/usr/local/lib/python3.10/site-packages/flask_login/utils.py", line 370, in _get_user
    current_app.login_manager._load_user()
  File "/usr/local/lib/python3.10/site-packages/flask_login/login_manager.py", line 364, in _load_user
    user = self._user_callback(user_id)
  File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/manager.py", line 2163, in load_user
    if user.is_active:
AttributeError: 'NoneType' object has no attribute 'is_active'
ERROR:superset.views.error_handling:'NoneType' object has no attribute 'is_active'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/app/superset/utils/log.py", line 303, in wrapper
    value = f(*args, **kwargs)
  File "/app/superset/views/core.py", line 894, in welcome
    if not g.user or not get_user_id():
  File "/usr/local/lib/python3.10/site-packages/werkzeug/local.py", line 318, in __get__
    obj = instance._get_current_object()
  File "/usr/local/lib/python3.10/site-packages/werkzeug/local.py", line 526, in _get_current_object
    return get_name(local())
  File "/usr/local/lib/python3.10/site-packages/flask_login/utils.py", line 25, in <lambda>
    current_user = LocalProxy(lambda: _get_user())
  File "/usr/local/lib/python3.10/site-packages/flask_login/utils.py", line 370, in _get_user
    current_app.login_manager._load_user()
  File "/usr/local/lib/python3.10/site-packages/flask_login/login_manager.py", line 364, in _load_user
    user = self._user_callback(user_id)
  File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/manager.py", line 2163, in load_user
    if user.is_active:
AttributeError: 'NoneType' object has no attribute 'is_active'

[dosubot[bot]]

The error you're encountering indicates that the load_user function in the Flask App Builder security manager is returning None, and the code is attempting to access the is_active attribute on this None object. This typically happens when the user ID cannot be found or the user is not properly loaded.

Here are a few steps you can take to troubleshoot and potentially fix this issue:

1. Check User ID Retrieval: Ensure that the user ID is being correctly retrieved and passed to the load_user function. If the user ID is None or invalid, the function will return None.

2. Verify User Existence: Make sure that the user exists in your database and is active. If the user does not exist or is inactive, the load_user function might return None.

3. Custom superset_config.py: Review your custom superset_config.py file to ensure that any custom authentication logic or user loading mechanisms are correctly implemented. Any misconfiguration here could lead to the user not being loaded properly.

4. Debugging: Add logging or debugging statements in your custom configuration or user loading logic to trace the flow and identify where it might be failing.

5. Session Management: Ensure that session management settings in superset_config.py are correctly configured, as they can affect user authentication and session persistence.

By following these steps, you should be able to identify the root cause of the issue and resolve it. If the problem persists, further investigation into the specific customizations in your superset_config.py might be necessary.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yang472541642]

@dosu
i delete the user before,when i login again,the error is happen,what should i do to fix it ?

[dosubot[bot]]

The error you're experiencing is likely due to the fact that the user you deleted is still being referenced in the session or authentication process. Here are some steps you can take to resolve this issue:

1. Clear Session Data: Ensure that any session data related to the deleted user is cleared. This can often be done by logging out and logging back in, or by clearing the session cookies in your browser.

2. Check for Cached Data: If your application or browser is caching user data, make sure to clear this cache to prevent it from trying to load a deleted user.

3. Database Consistency: Verify that the user has been completely removed from the database and that there are no lingering references to the user in any related tables or records.

4. Restart the Application: Sometimes, restarting the Superset application can help clear any in-memory references to the deleted user.

5. Review Custom Configurations: If you have custom logic in your superset_config.py, ensure that it handles cases where a user might be deleted and that it doesn't attempt to load a non-existent user.

By following these steps, you should be able to resolve the issue related to the deleted user.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yang472541642]

it works for me

i logout the app,and login again, it works ok

[user1500177]

@dosu

@dosu

I am also encountering the same error ,is ther a way to editsomething in the superset_config.py like session commit instead of the user clearing Cache in browser???

[dosubot[bot]]

You can automate session cleanup in Superset so users don't have to clear their browser cache after a user is deleted. In your superset_config.py, use the FLASK_APP_MUTATOR hook to add a before_request handler that checks if the current user still exists and logs them out if not. This will clear the session server-side whenever a deleted user tries to make a request, preventing the "NoneType object has no attribute 'is_active'" error.

Here's an example:

from flask import g
from flask_login import logout_user, current_user
from superset.extensions import db
from superset.models.core import User

def logout_if_user_deleted():
    if current_user.is_authenticated:
        # Check if user still exists in the DB
        user = db.session.query(User).get(current_user.get_id())
        if user is None or not user.is_active:
            logout_user()

def FLASK_APP_MUTATOR(app):
    app.before_request(logout_if_user_deleted)

Add this to your superset_config.py. Now, if a deleted user tries to use their session, Superset will log them out automatically and redirect them to the login page, no manual cache clearing needed. This is the recommended pattern for handling deleted user sessions in Superset [docs].

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[user1500177]

So would that error only arise if a deleted user is trying to login ??, means that for other users they won't experience the same issue right