shahar1 commented on issue #70355:
URL: https://github.com/apache/airflow/issues/70355#issuecomment-5080427574

   > `apache-airflow-providers-openlineage==2.20.0rc1`
   > 
   > PR [#69109](https://github.com/apache/airflow/pull/69109): During manual 
testing, it was discovered that `DagRunInfo.team_name() `was creating a new 
SQLAlchemy session via `@provide_session`, resulting in an unexpected commit 
within the scheduler's `on_dag_run_running` callback and triggering the HA lock 
protection (`RuntimeError: UNEXPECTED COMMIT - THIS WILL BREAK HA LOCKS!)`. 
Fortunately, the fix is relatively simple i.e. use the existing session used by 
the `DagRun` ORM object and pass it into `DagBundleModel.get_team_name`.
   > 
   > `apache-airflow-providers-celery==3.23.0rc1`
   > 
   > PR [#69092](https://github.com/apache/airflow/pull/69092): The scenario 
needed to trigger the emission of `celery.task_timeout_error` is difficult to 
reproduce deterministically. Given this is simply passing the existing 
`team_name` attribute into the metric tags, unit tests should be sufficient.
   > 
   > `apache-airflow-providers-snowflake==6.15.0rc2`:
   > 
   > PR [#68942](https://github.com/apache/airflow/pull/68942) & PR 
[#69731](https://github.com/apache/airflow/pull/69731): Changes are working as 
expected with no observed regressions. PR 
[#68597](https://github.com/apache/airflow/pull/68597) & PR 
[#68549](https://github.com/apache/airflow/pull/68549): Changes are working as 
expected with no observed regressions.
   > 
   > I would recommend that a second release candidate (RC2) be prepared for 
`apache-airflow-providers-openlineage==2.20.0`. This will include the fix for 
the issue described above for PR 
[#69109](https://github.com/apache/airflow/pull/69109).
   
   Thanks! OL will be excluded from this release :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to