-
Notifications
You must be signed in to change notification settings - Fork 14.9k
Fix proper joining of the path for logs retrieved from celery workers #26493
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
Fix proper joining of the path for logs retrieved from celery workers #26493
Conversation
The change apache#26377 "fixed" the way how logs were retrieved from Celery, but it - unfortunately broke the retrieval eventually. This PR should fix it. Fixes: apache#26492
824ca74
to
cbdf03b
Compare
…apache#26493) The change apache#26377 "fixed" the way how logs were retrieved from Celery, but it - unfortunately broke the retrieval eventually. This PR should fix it. Fixes: apache#26492 (cherry picked from commit 52560b8)
Should we add a unit test to prevent regression? |
Yeah. I thought of that. I will add it. |
Added unit test to apache#26493
Added Unit test in #26603 not "super" valuable, but better than nothing (and this - essentially where it failed) |
* Add unit test for log retrieval url Added unit test to #26493
Thanks @potiuk I am experiencing the same problem with my CeleryExecutor setup and it is resolved by applying the trailing slash as in this PR. :) |
Cool. 2.4.1 will fix it permanently :) |
The change #26337 "fixed" the way how logs were retrieved from Celery, but it - unfortunately broke the retrieval eventually.
This PR should fix it.
Fixes: #26492
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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.