You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "MaluNoPeleke (via GitHub)" <gi...@apache.org> on 2026/01/12 09:46:34 UTC
[D] Sentry fixed wasn't really merged in 3.1.4 [airflow]
GitHub user MaluNoPeleke created a discussion: Sentry fixed wasn't really merged in 3.1.4
We want to implement Sentry for Airflow and it seems like the latest SDK hasn't been merged in 3.1.x ([#57032](https://github.com/apache/airflow/issues/57032)) yet: https://github.com/cern-sis/issues-inspire/issues/1084#issuecomment-3714465323
Is there a way to implement it sooner with a custom image?
GitHub link: https://github.com/apache/airflow/discussions/60401
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Sentry fixed wasn't really merged in 3.1.4 [airflow]
Posted by "MaluNoPeleke (via GitHub)" <gi...@apache.org>.
GitHub user MaluNoPeleke added a comment to the discussion: Sentry fixed wasn't really merged in 3.1.4
Problöem still persists with Airflow 3.1.6
GitHub link: https://github.com/apache/airflow/discussions/60401#discussioncomment-15507759
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Sentry fixed wasn't really merged in 3.1.4 [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk added a comment to the discussion: Sentry fixed wasn't really merged in 3.1.4
Correct - as mentioned in https://github.com/cern-sis/issues-inspire/issues/1084#issuecomment-3714465323 and as you can see in the PR, this change is not back-ported to 3.1 (it's just to big and too risky to backport) - it will be fixed in 3.2.
You can follow the [Release Plan](https://cwiki.apache.org/confluence/display/AIRFLOW/Release+Plan) and subscribe to devlist or attend our regular dev calls See [Airflow 3.x](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.x) to keep yourself updated on when it will be ready for alpha/beta/rc testing and participate in those tests.
Of course if you **really** want to have it in 3.1 - you can propose a PR back-porting the change, making sure it's green and convincing maintainers that it is safe-enough to backport it - for example building a test package containing the fix and trying it in your case and providing logs confirming the backport is working fine.
Airflow has > 3500 and you can eeasily become one by backporting it and leading such backport PR to completion. We have detailed guide on backporting https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-github-actions (and the following chapters) and quite comprehensive contributor's guidelines https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst that you can follow (or anyone you will find who can do it if you don't feel like you can do it yourself.
GitHub link: https://github.com/apache/airflow/discussions/60401#discussioncomment-15508009
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Sentry fixed wasn't really merged in 3.1.4 [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk edited a comment on the discussion: Sentry fixed wasn't really merged in 3.1.4
Correct - as mentioned in https://github.com/cern-sis/issues-inspire/issues/1084#issuecomment-3714465323 and as you can see in the PR, this change is not back-ported to 3.1 (it's just to big and too risky to backport) - it will be fixed in 3.2.
You can follow the [Release Plan](https://cwiki.apache.org/confluence/display/AIRFLOW/Release+Plan) and subscribe to devlist or attend our regular dev calls See [Airflow 3.x](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.x) to keep yourself updated on when it will be ready for alpha/beta/rc testing and participate in those tests.
Of course if you **really** want to have it in 3.1 - you can propose a PR back-porting the change, making sure it's green and convincing maintainers that it is safe-enough to backport it - for example building a test package containing the fix and trying it in your case and providing logs confirming the backport is working fine.
Airflow has > 3500 contributors and you can eeasily become one by backporting it and leading such backport PR to completion. We have detailed guide on backporting https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-github-actions (and the following chapters) and quite comprehensive contributor's guidelines https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst that you can follow (or anyone you will find who can do it if you don't feel like you can do it yourself.
GitHub link: https://github.com/apache/airflow/discussions/60401#discussioncomment-15508009
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org