avkirilishin commented on pull request #21214: URL: https://github.com/apache/airflow/pull/21214#issuecomment-1028276711
> I think by removing that then we might have undone the fix where we introduced this change in the first place I checked this. Let's reconstruct the sequence of events. - Initially next_dagrun_create_after resets only in `calculate_dagrun_date_fields` and only with other "next*" attributes (`next_dagrun`, `next_dagrun_data_interval`). It didn't control max_active_runs. - #18897: unconditional `_update_dag_next_dagruns` call introduced, now `next_dagrun_create_after` used to control max_active_runs - #19528: `_should_update_dag_next_dagruns` was added, so we don't call `_update_dag_next_dagruns` without check and we don't need `next_dagrun_create_after = NULL` anymore -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
