You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2024/09/09 15:23:55 UTC

(airflow) branch v2-10-test updated: Fix typo in plugins.rst (#42106) (#42108)

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v2-10-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/v2-10-test by this push:
     new a8187d9a1e8 Fix typo in plugins.rst (#42106) (#42108)
a8187d9a1e8 is described below

commit a8187d9a1e88eb906adb120064131e8ef16b4d0d
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 <an...@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 fcdd79028de..06195263fe9 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.