seanghaeli opened a new pull request, #68864:
URL: https://github.com/apache/airflow/pull/68864

   Reverts #68840.
   
   #68840 ("Do not leak threads from `InProcessExecutionAPI`") moved the 
background event-loop + thread cleanup into a `weakref.finalize` keyed on the 
`InProcessExecutionAPI` instance. Callers build a sync `Client` from 
`InProcessExecutionAPI().transport` and drop the factory object, so the 
instance is garbage-collected while the transport is still in use — the 
finalizer then stops the loop and every later request hangs on the dead loop.
   
   This is currently red on `main`: the latest scheduled canary fails ~24/31 
serialization-core jobs with `Error while closing in-process execution API 
lifespan -> TimeoutError` (e.g. 
`test_processor.py::TestDagFileProcessor::test_top_level_variable_*`, 
`test_triggerer_job.py::test_trigger_can_*`). It blocks CI on every open PR 
that touches core test scope.
   
   This is a **temporary revert to unblock `main`**. The proper forward-fix 
(finalize on the transport rather than the instance) is @potiuk's #68855, which 
should supersede this once it is green and reviewed. Reverting first restores a 
green `main` for everyone in the meantime; the original thread-leak #68840 
addresses can be re-landed via #68855.
   
   related: #68840, #68855
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
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