You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "James Coder (JIRA)" <ji...@apache.org> on 2019/04/20 20:54:00 UTC
[jira] [Commented] (AIRFLOW-4300) Task Modal Broken for DAGs that
have not run
[ https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822566#comment-16822566 ]
James Coder commented on AIRFLOW-4300:
--------------------------------------
fixed this in my local version with:
{code:java}
if (!(d in task_instances)) {
task_instances[d] = {try_number:0};
}
{code}
> Task Modal Broken for DAGs that have not run
> --------------------------------------------
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
> Affects Versions: 1.10.3
> Reporter: Marcus Levine
> Priority: Major
> Fix For: 1.10.4
>
>
> After upgrading to 1.10.3, the task detail modal that normally appears when clicking on a task from the graph view does not appear when the DAG has not been run yet
> This makes it impossible to see the task details and rendered template prior to running the DAG
> In the JavaScript console, it appears this issue is caused by 'try_number' being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement.<anonymous> (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)