[ https://issues.apache.org/jira/browse/AIRFLOW-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797668#comment-16797668 ]
ASF subversion and git services commented on AIRFLOW-2548: ---------------------------------------------------------- Commit 95cfffdaef33b85531f7b856fe5c8da643138846 in airflow's branch refs/heads/v1-10-stable from Jimmy Cao [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=95cfffd ] [AIRFLOW-2548] Output plugin import errors to web UI (#3930) > Output Plugin Import Errors to WebUI > ------------------------------------ > > Key: AIRFLOW-2548 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2548 > Project: Apache Airflow > Issue Type: Bug > Reporter: Andy Cooper > Priority: Major > Fix For: 1.10.3 > > > All, > > We currently output all DAG import errors to the webUI. I propose we do the > same with plugin errors as well. This will provide a better user experience > by bubbling up all errors to the webUI instead of hiding them in stdOut. > > Proposal... > * Extend models.ImportError to have a "type" field to distinguish from error > types. > * Prevent class SchedulerJob methods from clearing out and pulling from > models.ImportError if type = 'plugin' > * Create new ImportError records in plugins_manager.py for each plugin that > fails to import > * Prompt user in views.py with plugin ImportErrors - specifying that they > need to fix and restart webserver to resolve. > > Does this seem reasonable to everyone? I'd be interested in taking on this > work if needed -- This message was sent by Atlassian JIRA (v7.6.3#76005)