From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
---|---|
To: | Nikolay Samokhvalov <nik(at)postgres(dot)ai> |
Cc: | pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: commitfest – hard to create entries after system upgrade |
Date: | 2025-06-22 21:44:39 |
Message-ID: | CAGECzQTjv5Fp2+MEEXeL6SwLy6KvK5gg4-wDG4SymtFm3URXeg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 22 Jun 2025 at 23:05, Nikolay Samokhvalov <nik(at)postgres(dot)ai> wrote:
>
> Tried to create a new entry for someone's patch that was already commented by Peter E as looking good, but:
>
> 1) when I went to the "PG19-1" commitfest, I couldn't find a button/link to open new entries there.
Could it be that you were/are not logged in? It seems the button is
hidden. I created an issue for that now, but this is not new
behaviour: https://github.com/postgres/pgcommitfest/issues/74
> 2) at homepage, there is a link in the bottom, https://commitfest.postgresql.org/open/new/ – but it doesn't work does't work, redirects to home page with these words:
>
> > More than one open commitfest exists, redirecting to startpage instead.
Yeah, that was a dumb bug which I also noticed quickly after I had
deployed to prod. That's fixed now.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Lind | 2025-06-22 21:55:56 | Re: Per-role disabling of LEAKPROOF requirements for row-level security? |
Previous Message | Nikolay Samokhvalov | 2025-06-22 21:22:48 | Re: fix: propagate M4 env variable to flex subprocess |