potiuk commented on issue #33647: URL: https://github.com/apache/airflow/issues/33647#issuecomment-1801324111
There is no other source of information for that than public issues if there are no updates, it means that there are no updates, generally. Possibly at some point in time before the next release all similar performance related issues might be look at by somene, but since it is volunteer driven effort, it may or might not happen. But if somene would like to look at it and try to apply a remedy - it is open for anyone to look at and fix it. But since you asked, here is my advice and a bit of context There is no "support" or "someone to fix it" in OSS project like this. The sofware you get is free, you pay 0 for it and you get it without any promises and guarantees of things being fixed or even looked at. If some people will dedicate some of their free time on fixing it, they will take a look and might attempt to diagnose and fix it, but there is no SLAs or promises it will be fixed. Often when issues relate to previous versions of airlfow and there are no signs of similar issues being common and affectng more people, it might not drag attentions of thsoe who are trying to prioritize where they spend their free time after hours and on weekends. However this also means that new versions of Airflow often solve similar problems because they are fixed while fixing other issues. So the most rreasonable approach if you would like to "refresh" an issue and increase a chance it will be looked at and time spent on it is to upgrade your installation to the latest release (we just released 2.7.3 so I recommend that) and report back - if you still observe the issue there, maybe there are addional logs and observation you have maybe more evidences you might find, or maybe (hopefully) you will upgrade and the issue will be solved in latest version (then you can report it back and we can close the issue. That would by my recommendation for you. -- 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]
