[
https://issues.apache.org/jira/browse/AIRFLOW-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Meickle updated AIRFLOW-4589:
-----------------------------------
Description:
If I enter Graph View and click on a newly deployed task with no TI history, I
get this JS error:
{code:java}
graph?dag_id=XXX:1092 Uncaught TypeError: Cannot read property 'try_number' of
undefined at SVGGElement.<anonymous> (graph?dag_id=XXX:1092) at
SVGGElement.__onclick (d3.min.js:1)
(anonymous) @ graph?dag_id=XXX:1092
(anonymous) @ d3.min.js:1{code}
The popup modal does work on the "Tree View" page, so there is a workaround,
but it's irritating because there is only a JS error in the console and no
visual indicator of what's happening.
was:
If I enter Graph View and click on a newly deployed task with no TI history, I
get this JS error:
{code:java}
graph?dag_id=XXX:1092 Uncaught TypeError: Cannot read property 'try_number' of
undefined at SVGGElement.<anonymous> (graph?dag_id=XXX:1092) at
SVGGElement.__onclick (d3.min.js:1)
(anonymous) @ graph?dag_id=XXX:1092
(anonymous) @ d3.min.js:1{code}
The popup modal does work on the "Task View" page, so there is a workaround,
but it's irritating because there is only a JS error in the console and no
visual indicator of what's happening.
> Graph View modal is broken for new tasks with no history
> --------------------------------------------------------
>
> Key: AIRFLOW-4589
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4589
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
> Affects Versions: 1.10.3
> Reporter: James Meickle
> Priority: Minor
>
> If I enter Graph View and click on a newly deployed task with no TI history,
> I get this JS error:
> {code:java}
> graph?dag_id=XXX:1092 Uncaught TypeError: Cannot read property 'try_number'
> of undefined at SVGGElement.<anonymous> (graph?dag_id=XXX:1092) at
> SVGGElement.__onclick (d3.min.js:1)
> (anonymous) @ graph?dag_id=XXX:1092
> (anonymous) @ d3.min.js:1{code}
>
> The popup modal does work on the "Tree View" page, so there is a workaround,
> but it's irritating because there is only a JS error in the console and no
> visual indicator of what's happening.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
