bbovenzi opened a new pull request, #38310: URL: https://github.com/apache/airflow/pull/38310
If you had a Dag that ran extremely often, like every minute, it would take a long time to fetch the data for the calendar view. And seeing that many planned events isn't too useful anyways. The easy fix is to put a max count we are willing to calculate and then include an info tooltip for the user explaining the issue. <img width="903" alt="Screenshot 2024-03-19 at 5 09 56 PM" src="https://github.com/apache/airflow/assets/4600967/cbc18d3d-0d72-44d6-be65-5cb0efd70bd8";> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
