Re: [I] 🐛 Report Schedule execution failed when user who created is not active (but current owner is active) [superset]

["rusackas (via GitHub)" <gi...@apache.org>]

rusackas commented on issue #33584:
URL: https://github.com/apache/superset/issues/33584#issuecomment-5127295333

   I think I've confirmed on `master`: `get_executor` picks a username without checking `is_active`, and `login_user()` in `MachineAuthProviderUser.get_auth_cookies` isn't called with `force=True`, so an inactive executor silently fails to authenticate instead of raising anything useful, and that's what surfaces as this screenshot failure. `get_executor` needs to skip inactive owners/creator/modifier and only raise `ExecutorNotFoundError` if none are active. 


-- 
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