This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a commit to branch sync_v2_10_test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit fc1d46265fa77d9cf229e88b991e9d1befe5b763
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Mon Sep 9 08:23:47 2024 -0700
Fix typo in plugins.rst (#42106) (#42108)
I'm not sure if my change is correct but I'm assuming the word `until` was
missing in the sentence.
Otherwise that would mean that the plugin changes are never used right?
(cherry picked from commit b70e3d098576d0313f058951c98878f37854fbcc)
Co-authored-by: Andres Lowrie <andres.low...@gmail.com>
---
docs/apache-airflow/authoring-and-scheduling/plugins.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/apache-airflow/authoring-and-scheduling/plugins.rst
b/docs/apache-airflow/authoring-and-scheduling/plugins.rst
index fcdd79028d..06195263fe 100644
--- a/docs/apache-airflow/authoring-and-scheduling/plugins.rst
+++ b/docs/apache-airflow/authoring-and-scheduling/plugins.rst
@@ -80,7 +80,7 @@ automatically loaded in Webserver). To load them at the
start of each Airflow process, set ``[core] lazy_load_plugins = False`` in
``airflow.cfg``.
This means that if you make any changes to plugins and you want the webserver
or scheduler to use that new
-code you will need to restart those processes. However, it will not be
reflected in new running tasks after the scheduler boots.
+code you will need to restart those processes. However, it will not be
reflected in new running tasks until after the scheduler boots.
By default, task execution uses forking. This avoids the slowdown associated
with creating a new Python interpreter
and re-parsing all of Airflow's code and startup routines. This approach
offers significant benefits, especially for shorter tasks.
