airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] GabrielNicolasAvellaneda opened a new pull request #4214: Better instructions for airflow flower
Date Tue, 20 Nov 2018 19:18:50 GMT
GabrielNicolasAvellaneda opened a new pull request #4214: Better instructions for airflow flower
URL: https://github.com/apache/incubator-airflow/pull/4214
 
 
   It is not clear in the documentation that you need to have flower installed to successful
run airflow flower. If you don't have flower installed, running airflow flower will show the
following error which is not of much help:
   
   airflow flower                                                                        
              
   [2018-11-20 17:01:14,836] {__init__.py:51} INFO - Using executor SequentialExecutor   
                                                  
   Traceback (most recent call last):                                                    
                                                  
     File "/mnt/secondary/workspace/f4/typo-backend/pipelines/model-pipeline/airflow/bin/airflow",
line 32, in <module>                     
       args.func(args)                                                                   
                                                  
     File "/mnt/secondary/workspace/f4/typo-backend/pipelines/model-pipeline/airflow/lib/python3.6/site-packages/airflow/utils/cli.py",
line
    74, in wrapper                                                                       
                                                  
       return f(*args, **kwargs)                                                         
                                                  
     File "/mnt/secondary/workspace/f4/typo-backend/pipelines/model-pipeline/airflow/lib/python3.6/site-packages/airflow/bin/cli.py",
line 1
   221, in flower                                                                        
                                                  
       broka, address, port, api, flower_conf, url_prefix])                              
                                                  
     File "/mnt/secondary/workspace/f4/typo-backend/pipelines/model-pipeline/airflow/lib/python3.6/os.py",
line 559, in execvp              
       _execvpe(file, args)                                                              
                                                  
     File "/mnt/secondary/workspace/f4/typo-backend/pipelines/model-pipeline/airflow/lib/python3.6/os.py",
line 604, in _execvpe            
       raise last_exc.with_traceback(tb)                                                 
                                                  
     File "/mnt/secondary/workspace/f4/typo-backend/pipelines/model-pipeline/airflow/lib/python3.6/os.py",
line 594, in _execvpe            
       exec_func(fullname, *argrest)                                                     
                                                  FileNotFoundError: [Errno 2] No such file
or directory
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - In case you are fixing a typo in the documentation you can prepend your commit with
\[AIRFLOW-XXX\], code changes always need a Jira issue.
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed
multiple commits if they address the same issue. In addition, my commits follow the guidelines
from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use
it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
   
   ### Code Quality
   
   - [ ] Passes `flake8`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message