You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for all your work on the commitfest app! It has received some great improvements lately.
I created this commitfest entry to replace my previous one (since it was partly committed, and the committer asked for a new entry for post-v18 work).
I created the entry a little after sending an email to pgsql-hackers with a v50 patch series. But for some reason the app thinks
my latest patch is v49 from 2/26.
Just a guess, but maybe it's because I sent two emails on that thread very close together: first the email with the v50 patches then a reply to something else. If you look at the whole thread you can see that second reply came in later.
I still see a v49. You're right that "Stats (from CFBot)" shows "v50", and the green checkmarks look like v50, but the "Latest attachment" at the bottom shows the v49 patch file:
Activity
JelteF commentedon Mar 22, 2025
I'm not sure what happened here. But this seems to be resolved now. Because the entry now has the v50 patch listed: https://commitfest.postgresql.org/patch/5660/
Looking at the merge commit it even seems like that was more than 36 hours ago, so way before you opened this issue.
pjungwir commentedon Mar 22, 2025
I still see a v49. You're right that "Stats (from CFBot)" shows "v50", and the green checkmarks look like v50, but the "Latest attachment" at the bottom shows the v49 patch file:
JelteF commentedon Mar 22, 2025
Hmm, yeah that indeed seems like a bug then. Looking quickly at the code in question, I'm not sure why it missed this attachment.