-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Fix circular import error when Kubernetes executors are dynamically loaded with Sentry #55809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
c3e47c3 to
7cb2ad6
Compare
jedcunningham
approved these changes
Sep 17, 2025
hussein-awala
approved these changes
Sep 17, 2025
Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
7cb2ad6 to
48cb640
Compare
78 tasks
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Sep 30, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 1, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 2, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 3, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 4, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 7, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 8, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 9, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 10, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 11, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 12, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 14, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 15, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 17, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 19, 2025
…e#55809) Resolves circular import that occurs when KubernetesExecutor is dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization. Root cause: The import chain executor → version_compat → BaseOperator → taskinstance → sentry → executor creates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported. Changes: - Remove BaseOperator and BaseSensorOperator from version_compat.py module-level imports - Add conditional imports directly in operator/sensor files that need these classes - Maintain compatibility across Airflow 2.x and 3.x versions This prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading. Files affected: - version_compat.py: Removed BaseOperator/BaseSensorOperator imports - operators/job.py: Added conditional BaseOperator import - operators/kueue.py: Added conditional BaseOperator import - operators/pod.py: Added conditional BaseOperator import - operators/resource.py: Added conditional BaseOperator import - sensors/spark_kubernetes.py: Added conditional BaseSensorOperator import Fixes apache#55803
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves circular import that occurs when
KubernetesExecutoris dynamically loaded during Airflow startup. The issue manifests as 'cannot import name from partially initialized module' errors during scheduler/triggerer initialization.Root cause: The import chain
executor→version_compat→BaseOperator→taskinstance→sentry→executorcreates a circular dependency when sentry is enabled, as sentry initialization attempts to load the executor while it's already being imported.Changes:
BaseOperatorandBaseSensorOperatorfromversion_compat.pymodule-level importsThis prevents the circular import by breaking the chain at version_compat, ensuring sentry initialization doesn't trigger recursive executor loading.
Fixes #55810
To Reproduce:
Error log: