This is an automated email from the ASF dual-hosted git repository.
shahar1 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new b9a9b4f4c02 Fix syntax error and typos in FAQ doc (#73088)
b9a9b4f4c02 is described below
commit b9a9b4f4c02773a3f6ccc011b7233900926f4d5a
Author: Justin Pakzad <[email protected]>
AuthorDate: Sun Sep 13 17:10:05 2026 -0400
Fix syntax error and typos in FAQ doc (#73088)
---
airflow-core/docs/faq.rst | 18 ++++++++----------
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/airflow-core/docs/faq.rst b/airflow-core/docs/faq.rst
index 46c783317db..a694f83e53d 100644
--- a/airflow-core/docs/faq.rst
+++ b/airflow-core/docs/faq.rst
@@ -41,7 +41,7 @@ There are very many reasons why your task might not be
getting scheduled. Here a
``airflow`` and ``DAG`` in order to prevent the DagBag parsing from
importing all python
files collocated with user's Dags.
-- Is your ``start_date`` set properly? For time-based Dags, the task won't be
triggered until the
+- Is your ``start_date`` set properly? For time-based Dags, the task won't be
triggered until
the first schedule interval following the start date has passed.
- Is your ``schedule`` argument set properly? The default
@@ -81,7 +81,7 @@ There are very many reasons why your task might not be
getting scheduled. Here a
how many ``running`` concurrent instances of a Dag there are allowed to be.
You may also want to read about the :ref:`scheduler` and make
-sure you fully understand how the scheduler cycle.
+sure you fully understand how the scheduler cycle works.
How to improve Dag performance?
@@ -181,8 +181,7 @@ until ``min_file_process_interval`` is reached since Dag
Parser will look for mo
:caption: dag_loader.py
:name: dag_loader.py
- from airflow.sdk import DAG
- from airflow.sdk import task
+ from airflow.sdk import DAG, task
import pendulum
@@ -192,7 +191,7 @@ until ``min_file_process_interval`` is reached since Dag
Parser will look for mo
dag_id,
schedule=schedule,
default_args=default_args,
- pendulum.datetime(2021, 9, 13, tz="UTC"),
+ start_date=pendulum.datetime(2021, 9, 13, tz="UTC"),
)
with dag:
@@ -514,7 +513,7 @@ represents data in the date of ``2016-02-19``, this date is
also called the
run's *logical date*, or the date that this Dag run is executed for, thus
*execution date*.
-For backward compatibility, a datetime value ``execution_date`` is still
+For backward compatibility, a datetime value ``execution_date`` is still
available
as :ref:`Template variables<templates:variables>` with various formats in Jinja
templated fields, and in Airflow's Python API. It is also included in the
context dictionary given to an Operator's execute function.
@@ -627,7 +626,7 @@ What does ``TemplateNotFound`` mean?
-------------------------------------
``TemplateNotFound`` errors are usually due to misalignment with user
expectations when passing path to operator
-that trigger Jinja templating. A common occurrence is with
:class:`~airflow.providers.standard.operators.BashOperator`.
+that trigger Jinja templating. A common occurrence is with
:class:`~airflow.providers.standard.operators.bash.BashOperator`.
Another commonly missed fact is that the files are resolved relative to where
the pipeline file lives. You can add
other directories to the ``template_searchpath`` of the Dag object to allow
for other non-relative location.
@@ -812,7 +811,7 @@ How can I test a connection or use a Canary Dag?
------------------------------------------------
For security reasons, the test connection functionality is disabled by default
across the Airflow UI,
-API and CLI. This can be modified by setting
ref:`config:core__test_connection`.
+API and CLI. This can be modified by setting
:ref:`config:core__test_connection`.
You can utilize a Dag to regularly test connections. This is referred to as a
"Canary Dag" and can detect and
alert on failures in external systems that your Dags depend on. You can create
a simple Dag that tests connections
@@ -820,8 +819,7 @@ such as the following Airflow 3 example:
.. code-block:: python
- from airflow import DAG
- from airflow.sdk import task
+ from airflow.sdk import DAG, task
with DAG(dag_id="canary", schedule="@daily", doc_md="Canary Dag to regularly
test connections to systems."):
