Number of DAGs on Tabs not Match

[catbig]

Apache Airflow version

2.7.0

What happened

Number of DAGs in tabs not match with number of records

Data statistic on dag table

all1	is_active2	is_paused3
113	55	58

¹ select count(*) from dag
² select count(*) from dag where not is_paused
³ select count(*) from dag where is_paused

Record number on the page, count manually

all	is_active	is_paused
52	48	4

What you think should happen instead

The number on tabs should follow number of record

all1	is_active2	is_paused3
52	48	4

Proposed Solution

The query should add filter active

¹ select count(*) from dag where is_active
² select count(*) from dag where not is_paused and is_active
³ select count(*) from dag where is_paused and is_active

Code need to change

File path: https://github.com/apache/airflow/blob/main/airflow/www/views.py
Class: Airflow(AirflowBaseView)
Function: def index(self)

How to reproduce

Requirement

1. DAGs populate with gitSync
2. wait: 1 (1 second to sync)

Steps

1. Add new DAGs
   a. filename: hello_world.py
   b. dagId: hello_world1
2. Go to DAGs page (/home)
   a. check number of DAGs in tab and take note
   b. count records of DAGs for each tab and take note
3. Change the dagId
   a. dagId: hello_world2
   b. wait for 5 seconds
   c. dagId: hello_world3
   d. wait for 5 seconds
   e. dagId: hello_world4
   f. wait for 5 seconds
   g. dagId: hello_world5
4. Go to DAGs page (/home)
   a. check number of DAGs in tab and take note
   b. count records of DAGs for each tab and take note

Operating System

Linux

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

Deploy on kubernetes cluster using helm chart

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[potiuk]

Thank you for the report . Yes. We know and Yes, there are few issues about it already and Yes. It's already fixed and wll be released in 2.7.1 See #33912 #33698 and fix in #33778.

BTW. Delicate suggestion: Search before submit :)