-
Notifications
You must be signed in to change notification settings - Fork 14.1k
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Webserver returns 500 for POST requests to api/dag/*/dagrun from anonymous user #36110
Comments
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. |
Hi @eliskovets, as per my knowledge it will only affect UI access not API. But that's not the concern here. |
Hi @pateash , |
RCA ( its reproducable in main branch as well ie. 2.9-dev )user_id is coming as 'None':, |
The issue here is , user_id is a foreign key from ab_user table, Need your input @potiuk, @eladkal here. I am interested in how it used to work before 2.7 @eliskovets |
@pateash i believe before 2.7 notes weren't a separate table, that's why it worked before. |
Apache Airflow version
2.7.3
What happened
After upgrade to 2.7.3 I noticed that webserver returns 500 for POST requests with a
note
field. After some investigation it seems that None in user_id converted to str causing it:That's probably not an issue of Airflow itself, but SQLAlchemy 1.4. it's probably fixed in 2.0.
What you think should happen instead
Dagrun should be successfully registered by airflow and note should be saved into
dag_run_note
table.How to reproduce
webserver_config.py
DAGRun
APIOperating System
Debian GNU/Linux 11 (bullseye)
Versions of Apache Airflow Providers
No response
Deployment
Other Docker-based deployment
Deployment details
Docker image: apache/airflow:2.7.3-python3.9
DB: Postgresql
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: