DartVeDroid commented on issue #58053: URL: https://github.com/apache/airflow/issues/58053#issuecomment-3776864519
> You can **always** migrate to 3.0.LATEST - there are **only** bugfixes there (we are following semver). This is the slow migration. When you are moving to **earlier** version of major.minor you are **for sure** having all the errors that have been fixed in the later patchlevel versions of major.minor. And possibly you are taking valuable time of maintainers for things that are already fixed. > > Migrating one patchlevel at a time malkes absolutely no sense. > > Closing it. Try with latest patchlevels, ideally with latest 3.1 and report again if you stil hagve hte issue. Tried a 3.0.6 - the same problem persists. It looks very similar to https://github.com/apache/airflow/issues/50349, which is now waiting for https://github.com/apache/airflow/pull/53821. Also like https://github.com/apache/airflow/issues/49863, and there's a line in the comments "_Which means set_context needed to be called ( but it is never called in Airflow 3 )_" (https://github.com/apache/airflow/issues/49863#issuecomment-2954807262), which is kind of funny. Being honest, I tried to debug the whole thing, but it's not actually easy to do while using Windows + Docker, so I guess I'll end up monkey-patching the parts I need the different behavior from. Tried a 3.1.6 - it breaks our OAUTH-based security manager. The thing I don't understand, though, is why close an issue, which is not made by me, in response to my comment. -- 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]
