Skip to content

DAG tags filter not showing all tags in UI #50711

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
arthur-ventura-astro opened this issue May 16, 2025 · 2 comments · May be fixed by #50732
Open
1 of 2 tasks

DAG tags filter not showing all tags in UI #50711

arthur-ventura-astro opened this issue May 16, 2025 · 2 comments · May be fixed by #50732
Assignees
Labels
affected_version:3.0 Issues Reported for 3.0 area:core area:UI Related to UI/UX. For Frontend Developers. kind:bug This is a clearly a bug priority:medium Bug that should be fixed before next release but would not block a release

Comments

@arthur-ventura-astro
Copy link

Apache Airflow version

3.0.1

If "Other Airflow 2 version" selected, which one?

No response

What happened?

When dealing with a big number of tags, the DAG tags filter appears to be "truncating" the tags list.
Even when searching for a specific tag, it doesn't appear in the filter dropdown.

The example used to test this is showcased in details below. The idea is simple, to create a DAG with a significant amount of tags. The results can be seen in the images below.

Image
Image
Image

What you think should happen instead?

All tags defined in the DAG should appear in the filter.

How to reproduce

Create a DAG with the following tags parameter setting:

...
with DAG(
    dag_id="basic_example",
    schedule="0 15 * * *",
    start_date=datetime(2024, 11, 6),
    catchup=False,
    tags=[str(i) for i in range(1000)]
) as dag:
...

Then go to the DAG tags filter and search for a tag greater than 150.

Operating System

MacOS 15.4.1

Versions of Apache Airflow Providers

No response

Deployment

Docker-Compose

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@arthur-ventura-astro arthur-ventura-astro added kind:bug This is a clearly a bug area:core needs-triage label for new issues that we didn't triage yet labels May 16, 2025
Copy link

boring-cyborg bot commented May 16, 2025

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.

@jedcunningham jedcunningham added affected_version:3.0 Issues Reported for 3.0 and removed needs-triage label for new issues that we didn't triage yet labels May 16, 2025
@dosubot dosubot bot added area:UI Related to UI/UX. For Frontend Developers. priority:medium Bug that should be fixed before next release but would not block a release labels May 16, 2025
@aritra24 aritra24 self-assigned this May 17, 2025
@aritra24
Copy link
Collaborator

Hmm, was able to repro, checking it out. Looks like it limits responses to 50 tags

@aritra24 aritra24 linked a pull request May 17, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected_version:3.0 Issues Reported for 3.0 area:core area:UI Related to UI/UX. For Frontend Developers. kind:bug This is a clearly a bug priority:medium Bug that should be fixed before next release but would not block a release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy