From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mohab Yaser <mohabyaserofficial2003(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to check if issue is solved? |
Date: | 2024-07-26 04:35:25 |
Message-ID: | 1610980.1721968525@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mohab Yaser <mohabyaserofficial2003(at)gmail(dot)com> writes:
> I wrote a simple script to get all issues from the pgsql-bugs list that are
> reported by the form (basically getting just the issues without any replies
> to them) and now while searching through these issues I can't know directly
> whether it is solved or not, just a workaround is checking any discussions
> in its thread whether there is a patch file attached or not but it is not
> accurate as submitting a patch is not related to the issue itself neither
> by mentioning the issue id or the issue itself is marked as solved or at
> least someone is working on it, so if anyone can help it will be very
> appreciated.
One way is to trawl the commit log and see if there are commits
linking to the bug thread with a Discussion: marker.
This isn't 100% accurate, because a commit could possibly mention a
bug thread without claiming to resolve the bug fully. But it's
pretty reliable for issues raised in the last half dozen years or so.
A bigger hole in what you're doing is that bug reports don't
necessarily come in via the web form.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2024-07-26 05:09:26 | Re: [Proposal] Add foreign-server health checks infrastructure |
Previous Message | Yugo Nagata | 2024-07-26 04:22:24 | Re: First draft of PG 17 release notes |