[jira] [Created] (AIRFLOW-1851) next/previous buttons on DAG Tree View UI

Tylar Murray created AIRFLOW-1851: - Summary: next/previous buttons on DAG Tree View UI Key: AIRFLOW-1851 URL: https://issues.apache.org/jira/browse/AIRFLOW-1851 Project: Apache Airflow Issue

[jira] [Commented] (AIRFLOW-2459) Unable to insert in log table while using MySQL

[ https://issues.apache.org/jira/browse/AIRFLOW-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474504#comment-16474504 ] Tylar Murray commented on AIRFLOW-2459: ---

[jira] [Commented] (AIRFLOW-695) Retries do not execute because dagrun is in FAILED state

[ https://issues.apache.org/jira/browse/AIRFLOW-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16491080#comment-16491080 ] Tylar Murray commented on AIRFLOW-695: -- I believe I am seeing this issue using airflow 1.9.0. What

[jira] [Created] (AIRFLOW-2535) TriggerDagRunOperator ignores max_active_runs, leading to scheduler breakdown

Tylar Murray created AIRFLOW-2535: - Summary: TriggerDagRunOperator ignores max_active_runs, leading to scheduler breakdown Key: AIRFLOW-2535 URL: https://issues.apache.org/jira/browse/AIRFLOW-2535

[jira] [Updated] (AIRFLOW-2535) TriggerDagRunOperator ignores max_active_runs, leading to scheduler breakdown

[ https://issues.apache.org/jira/browse/AIRFLOW-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tylar Murray updated AIRFLOW-2535: -- Description: `TriggerDagRunOperator` does not respect the `max_active_runs` setting. This in

[jira] [Created] (AIRFLOW-2049) Detailed documentation on airflow.cfg options

Tylar Murray created AIRFLOW-2049: - Summary: Detailed documentation on airflow.cfg options Key: AIRFLOW-2049 URL: https://issues.apache.org/jira/browse/AIRFLOW-2049 Project: Apache Airflow

[jira] [Commented] (AIRFLOW-1737) set_task_instance_state fails because of strptime

[ https://issues.apache.org/jira/browse/AIRFLOW-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581268#comment-16581268 ] Tylar Murray commented on AIRFLOW-1737: --- https://github.com/apache/incubator-airflow/pull/3754 >

[jira] [Commented] (AIRFLOW-2768) `airflow clear --upstream --only_failed` doesn't clear tasks upstream

[ https://issues.apache.org/jira/browse/AIRFLOW-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549396#comment-16549396 ] Tylar Murray commented on AIRFLOW-2768: --- It looks like `–rerun_failed_tasks` was added in `1.10`

[jira] [Created] (AIRFLOW-2768) `airflow clear --upstream --only_failed` doesn't clear tasks upstream

Tylar Murray created AIRFLOW-2768: - Summary: `airflow clear --upstream --only_failed` doesn't clear tasks upstream Key: AIRFLOW-2768 URL: https://issues.apache.org/jira/browse/AIRFLOW-2768 Project:

[jira] [Commented] (AIRFLOW-1305) This DAG seems to be exists locally.

[ https://issues.apache.org/jira/browse/AIRFLOW-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556284#comment-16556284 ] Tylar Murray commented on AIRFLOW-1305: --- After running into this myself using airflow v1.9.0 and

[jira] [Updated] (AIRFLOW-1515) Airflow 1.8.1 tasks not being marked as upstream_failed when one of the parents fails

[ https://issues.apache.org/jira/browse/AIRFLOW-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tylar Murray updated AIRFLOW-1515: -- Attachment: image-2018-04-03-21-24-58-893.png > Airflow 1.8.1 tasks not being marked as

[jira] [Commented] (AIRFLOW-1515) Airflow 1.8.1 tasks not being marked as upstream_failed when one of the parents fails

[ https://issues.apache.org/jira/browse/AIRFLOW-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424635#comment-16424635 ] Tylar Murray commented on AIRFLOW-1515: --- [~ivan.vergiliev]: I don't think the issue here is with

[jira] [Commented] (AIRFLOW-1515) Airflow 1.8.1 tasks not being marked as upstream_failed when one of the parents fails

[ https://issues.apache.org/jira/browse/AIRFLOW-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424614#comment-16424614 ] Tylar Murray commented on AIRFLOW-1515: --- Is this fixed in 1.9? I am finding this to be a big pain