potiuk commented on issue #17977: URL: https://github.com/apache/airflow/issues/17977#issuecomment-1842469420
> I still got same issue on airflow v2.4.3, Is there any updates regarding this? Well. It was also reported for 2.1.3. The issue was closed because no activity from the user. Airflow is Open Source Project - with no guarantees that all problems in all version will be addressed and fixed (in fact it comes with no guarantees at all if you look at the licence and the fact tha you pay exactly 0 for it). Many issues look similar to others but might be different. Many issues are solved without closing the issues because we have many 100s of isses, only volunteers working on it and we don't track which issues are solved by every single PR - that's why it has been closed due to inactivity. But If you care about your issue being looked at, then the best thing you can do is to open new issue, where you decribe in detail what are YOUR problems, provide all teh evidences, and make yourself available as issue author to provide more evidences if your issue will be detailed enough that someone will decide to spend their time on looking at it (it's on you to provide enough evidences so that someone will have it easy to reproduce the issue and diagnose it). So rather than asking about "update" on closed issue, I suggest you to take a more active approach and open issue, provide evidences and generally be proactive in making sure you follow up. Additionally - I'd also suggest to upgrade Airflow - there are likely many 100s of issues solved even since 2.4.3 (we are at 2.7.3) so it's likely the problem you have is already fixed (and you miss on not having all those 100s of issues fixing also possibly other problems). -- 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]
