Scheduler should not crash when executor_config is provided with CE #47375
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.
closes: #47349
Ideally, it isn't correct to pass
executor_configwithpod_overridefor CE as it makes no sense to do that. It is generally a config for KE / EDGE etc. Whenexecutor_configis passed to an executor, with AF 3, it is present as part of the TI model & is serialised as a workload and sent to the supervisor to run. We do not need to ever pass it down to the supervise function as it these are "decorators" used to set the "environment" for execution for the task. Example: they are used to pick right image, volumes etc for KE.Ignoring the config for executor_config while performing a serialisation.
Testing:
Logs:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.