potiuk commented on PR #23618: URL: https://github.com/apache/airflow/pull/23618#issuecomment-1443355602
> Because at the top of https://github.com/apache/airflow/issues/23497 it says Fixed by #23618 ยท May be fixed by #28336. So it seems like they are fixing the same issue. This is precisely what I missed. Next time I suggest you explain why you are asking the question. This is what I was asking about, because it's not at all obvious (it's two clicks away) so I missed that connection (it was maybe obvious for you because you looked it up but without this context it was not at all obvious). Generally - many of the issues may be related to each other and might - or might no - solve the same issues. It depends and often we are guessing and only the users who experienced the problem might confirm this. This is by sheer nature of any complex software. I think, the best way is to participate (add comments, test PRs, provide helpful feedback) to those prs that are discussing the solutions and even offer help in testing it (if you are experiencing similar problems). This is a community-driven project, most of the people participate in it as volunteers and any help from anyone who observes some problems - even testing unreleased patches is helpful. So what my point is - if you have a related problem and you see several linked issues/PRs, taking an active part in testing/reviewing of one that is being worked on and providing feedback if it fixes the problem is cool and helpful. -- 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]
