You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/07/25 21:00:22 UTC
[jira] [Commented] (AIRFLOW-359) `bool object not callable` when
running CI due to flask-login 0.3
[ https://issues.apache.org/jira/browse/AIRFLOW-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392659#comment-15392659 ]
ASF subversion and git services commented on AIRFLOW-359:
---------------------------------------------------------
Commit edce741234d86c05e11d3fd6a76bc8e83dabade2 in incubator-airflow's branch refs/heads/master from [~xuanji]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=edce741 ]
[AIRFLOW-359] Pin flask-login to 0.2.11
Closes #1679 from zodiac/xuanji_pin_ci_flask_login
> `bool object not callable` when running CI due to flask-login 0.3
> -----------------------------------------------------------------
>
> Key: AIRFLOW-359
> URL: https://issues.apache.org/jira/browse/AIRFLOW-359
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Li Xuanji
> Assignee: Li Xuanji
>
> Because our CI's requirements.txt entry for flask-login is not pinned (https://github.com/apache/incubator-airflow/blob/master/scripts/ci/requirements.txt#L17), it installed flask-login 0.3 for me, while airflow normally installs flask-login 0.2. The is_authenticated function was changed to a property in 0.3, leading to the same error reported here https://github.com/miguelgrinberg/flasky/issues/74 while running CI (eg https://travis-ci.org/zodiac/incubator-airflow/jobs/147009407)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)