[ 
https://issues.apache.org/jira/browse/AIRFLOW-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kaxil Naik resolved AIRFLOW-4841.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.4

> Doc check in master started to failed with cyclic import problem suddenly
> -------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4841
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4841
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: ci
>    Affects Versions: 2.0.0
>            Reporter: Jarek Potiuk
>            Priority: Major
>             Fix For: 1.10.4
>
>
> Doc check started to fail suddenly after merging 
> [https://github.com/apache/airflow/commit/487ad38d60dc0f43fc69e9a0cf1a9c5e04cc49f5]
>   
>  The warnings do not seem to be related to change (which was anyhow 
> [travis-CI tested|[https://travis-ci.org/apache/airflow/builds/549462029]] 
> before).
>   
>  It seems that it is triggered by latest Sphinx 2.1.2 release (released 19th 
> of June). 
>   
>  WARNING: Cannot resolve cyclic import: airflow, airflow.models, 
> airflow.models.connection, airflow
>  WARNING: Cannot resolve import of unknown module 
> airflow.kubernetes.kubernetes_request_factory in 
> airflow.kubernetes.pod_launcher
>  WARNING: Cannot resolve import of 
> airflow.contrib.hooks.qubole_hook.COMMAND_ARGS in 
> airflow.contrib.operators.qubole_operator
>  WARNING: Cannot resolve import of 
> airflow.contrib.hooks.qubole_hook.HYPHEN_ARGS in 
> airflow.contrib.operators.qubole_operator
>  WARNING: Cannot resolve import of airflow.contrib.hooks.jira_hook.JIRAError 
> in airflow.contrib.operators.jira_operator
>  WARNING: Cannot resolve import of 
> airflow.contrib.operators.jira_operator.JIRAError in 
> airflow.contrib.sensors.jira_sensor
>  
> It turns out that it was a sphinx-autoapi v 1.1.0 released 23rd of June in 
> fact.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to