-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Closed
Labels
area:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.area:corekind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yetpriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release
Description
Apache Airflow version
3.0.1
If "Other Airflow 2 version" selected, which one?
No response
What happened?
It seems like the 3rd and 4th label on a dag get smashed together but should be comma separated.
What you think should happen instead?
Should be comma separated like the rest.
How to reproduce
Seems to be the standard display on DAGs in the current version, just add labels.
@dag(
dag_id="bronze_bbsav_schedule_pro_final_v1",
schedule="0 0 * * *", # midnight daily
start_date=datetime(1901, 1, 1, tzinfo=pendulum.timezone("America/Los_Angeles")),
catchup=False,
default_args=default_dag_args,
dagrun_timeout=timedelta(minutes=10),
tags=["events", "bronze", "download", "mlb"],
)
Operating System
Debian GNU/Linux 12 (bookworm) (k3s)
Versions of Apache Airflow Providers
((env) ) natesinger@tank:~/Core/data/dags$ k exec -n airflow pod/airflow-api-server-745656884c-kjtrq -it -- cat /etc/os-release
Defaulted container "api-server" out of: api-server, wait-for-airflow-migrations (init)
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
((env) ) natesinger@tank:~/Core/data/dags$ k exec -n airflow pod/airflow-api-server-745656884c-kjtrq -it -- bash
Defaulted container "api-server" out of: api-server, wait-for-airflow-migrations (init)
airflow@airflow-api-server-745656884c-kjtrq:/opt/airflow$ pip freeze | grep apache-airflow-providers
apache-airflow-providers-amazon==9.7.0
apache-airflow-providers-celery==3.10.6
apache-airflow-providers-cncf-kubernetes==10.4.3
apache-airflow-providers-common-compat==1.6.1
apache-airflow-providers-common-io==1.5.4
apache-airflow-providers-common-messaging==1.0.1
apache-airflow-providers-common-sql==1.27.0
apache-airflow-providers-docker==4.3.1
apache-airflow-providers-elasticsearch==6.2.2
apache-airflow-providers-fab==2.0.2
apache-airflow-providers-ftp==3.12.3
apache-airflow-providers-git==0.0.2
apache-airflow-providers-google==15.1.0
apache-airflow-providers-grpc==3.7.3
apache-airflow-providers-hashicorp==4.1.1
apache-airflow-providers-http==5.2.2
apache-airflow-providers-microsoft-azure==12.3.1
apache-airflow-providers-mysql==6.2.2
apache-airflow-providers-odbc==4.9.2
apache-airflow-providers-openlineage==2.2.0
apache-airflow-providers-postgres==6.1.3
apache-airflow-providers-redis==4.0.2
apache-airflow-providers-sendgrid==4.0.1
apache-airflow-providers-sftp==5.2.1
apache-airflow-providers-slack==9.0.5
apache-airflow-providers-smtp==2.0.3
apache-airflow-providers-snowflake==6.3.0
apache-airflow-providers-ssh==4.0.1
apache-airflow-providers-standard==1.1.0
airflow@airflow-api-server-745656884c-kjtrq:/opt/airflow$
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else?
Thanks!
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
Metadata
Metadata
Assignees
Labels
area:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.area:corekind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yetpriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release
