Skip to content

Conversation

@ashb
Copy link
Member

@ashb ashb commented Apr 4, 2025

Prior to 984c61d this code looked like:

        result = task_to_run.apply_async(args=[command], queue=queue)

Closes #47781


^ 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 airflow-core/newsfragments.

Prior to 984c61d this code looked like:

```python
        result = task_to_run.apply_async(args=[command], queue=queue)
```

Closes apache#47781
@potiuk
Copy link
Member

potiuk commented Apr 4, 2025

Let me test it

@potiuk
Copy link
Member

potiuk commented Apr 4, 2025

Works ! Tested with 2.10.5!

Screenshot 2025-04-04 at 20 32 28

@potiuk potiuk requested a review from eladkal April 4, 2025 18:34
@potiuk
Copy link
Member

potiuk commented Apr 4, 2025

I think we should yank 3.10.1 -> 3.10.4 after releasing 3.10.5. They will neither work on 2 nor on final 3 (I guess)

@ashb
Copy link
Member Author

ashb commented Apr 4, 2025

Ah you beat me to testing it, thanks.

@ashb
Copy link
Member Author

ashb commented Apr 4, 2025

3.10.2+ would work on Airflow 3, but yeah lets yank

@eladkal
Copy link
Contributor

eladkal commented Apr 4, 2025

Lets not yank if they work on Airflow 3.. it will give Airflow 3 users the option to run with Celery 5.4 should they want to

@potiuk
Copy link
Member

potiuk commented Apr 4, 2025

Some of 3.1-3.4 might not work on any 3 versions. There were multiple changes implemented since 3.10.1 and some of them look really bad if you look at the changelog - so while 3.10.4 might work, I am pretty sure 3.10.1 -> 3.10.3 won't ... It's safer to yank them all I think rather than loose time on checking which one works and which one does not. Especially that 3.10.5 also has the higher celery version which fixes another issue, it's likely safer to say "Please don't use 3.10.1 -> 3.10.4" IMHO.

But feel free to decide.

@potiuk
Copy link
Member

potiuk commented Apr 4, 2025

BTW: We don't loose anything by yanking... We can only risk some issues if we don't :)

@potiuk potiuk merged commit a61cb1b into apache:main Apr 4, 2025
63 checks passed
@ashb ashb deleted the celery-compat-fix branch April 4, 2025 18:56
nailo2c pushed a commit to nailo2c/airflow that referenced this pull request Apr 4, 2025
Prior to 984c61d this code looked like:

```python
        result = task_to_run.apply_async(args=[command], queue=queue)
```

Closes apache#47781
diogotrodrigues pushed a commit to diogotrodrigues/airflow that referenced this pull request Apr 6, 2025
Prior to 984c61d this code looked like:

```python
        result = task_to_run.apply_async(args=[command], queue=queue)
```

Closes apache#47781
simonprydden pushed a commit to simonprydden/airflow that referenced this pull request Apr 8, 2025
Prior to 984c61d this code looked like:

```python
        result = task_to_run.apply_async(args=[command], queue=queue)
```

Closes apache#47781
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3.10.3 apache-airflow-providers-celery release is broken

3 participants