Abhi2939 opened a new pull request, #76693:
URL: https://github.com/apache/airflow/pull/76693
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
closes: #76549
The Calendar tab skipped planned runs whenever the requested range had no
historical runs. `get_calendar_data` passes only the in-range runs as the
baseline for `_get_planned_dag_runs`, and `_should_calculate_planned_runs`
returns `False` for an empty baseline. Daily mode requests a whole year, so it
nearly always has history; Hourly requests one month, so a month without past
runs showed "No runs" even though the Dag has planned runs there.
When the range has no historical runs, the baseline now falls back to the
Dag's latest run overall (`_get_latest_dag_run_state`). The existing
planned-run calculation is unchanged: it already skips dates outside the
requested range. The extra query only runs when the range is empty, so other
requests keep their query count.
Tests:
- a cron Dag with one November run now shows 31 planned entries for an
hourly December request
- a Dag whose `end_date` is before the viewed month still shows no planned
runs
- one existing expectation changed: the hourly case with exclusive
`logical_date_gt`/`logical_date_lt` on Jan 2 excluded the Jan 2 00:00 run from
the range, so it previously returned no planned runs. It now returns the Jan 2
01:00 planned run, matching the neighbouring case.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (Claude)
Generated-by: Claude following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
