[GitHub] [airflow] syun64 commented on pull request #13265: Dispose connections when running tasks with os.fork & CeleryExecutor

2023-04-04 Thread via GitHub
syun64 commented on PR #13265: URL: https://github.com/apache/airflow/pull/13265#issuecomment-1496631859 Just following up on my own bug report on this PR for anyone who's facing a similar issue: I wasn't able to find the root cause for my issue, but I was able to resolve the issue by disab

[GitHub] [airflow] syun64 commented on pull request #13265: Dispose connections when running tasks with os.fork & CeleryExecutor

2023-03-28 Thread via GitHub
syun64 commented on PR #13265: URL: https://github.com/apache/airflow/pull/13265#issuecomment-1487492931 Actually, after some more debugging it looks like this issue isn't specific to happening when processing the executor events. This is a error traceback that happened when the sched

[GitHub] [airflow] syun64 commented on pull request #13265: Dispose connections when running tasks with os.fork & CeleryExecutor

2023-03-28 Thread via GitHub
syun64 commented on PR #13265: URL: https://github.com/apache/airflow/pull/13265#issuecomment-1487202191 Hi @kaxil, I'm running an Airflow cluster with v2.5.0, CeleryExecutor and SQLAlchemy 1.4.4, and I actually ran into the same error noted on this PR. ``` Traceback (most recent call