[
https://issues.apache.org/jira/browse/AIRFLOW-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301449#comment-15301449
]
Chris Riccomini commented on AIRFLOW-168:
-----------------------------------------
The comment in [this|https://github.com/apache/incubator-airflow/pull/1506]
pull request from [~bolke] reads:
{quote}
This creates dagrun from a Dag. It also creates the TaskInstances from the
tasks known at instantiation time. By having taskinstances created at dagrun
instantiation time, deadlocks that were tested for will not take place anymore
(@jlowin, correct? different test required?). *For now, the visual consequence
of having these taskinstances already there is that they will be black in the
tree view.*
{quote}
> schedule_interval @once scheduling dag atleast twice
> ----------------------------------------------------
>
> Key: AIRFLOW-168
> URL: https://issues.apache.org/jira/browse/AIRFLOW-168
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
> Affects Versions: Airflow 1.7.1.2
> Reporter: Sumit Maheshwari
> Attachments: Screen Shot 2016-05-24 at 9.51.50 PM.png,
> screenshot-1.png
>
>
> I was looking at example_xcom example and found that it got scheduled twice.
> Ones at the start_time and ones at the current time. To be correct I tried
> multiple times (by reloading db) and its same.
> I am on airflow master, using sequential executor with sqlite3.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
