Thread: Re: Commitfest URL
Greetings, * Bruce Momjian (bruce@momjian.us) wrote: > I usually use this URL to find the current commitfest: > > https://commitfest.postgresql.org/action/commitfest_view/inprogress > > It used to work, but now returns a "Not found" error. Is there a better > URL for this? Short answer is, yes: https://commitfest.postgresql.org/inprogress The old URL had been a redirect set up when we were running lighttpd but wasn't carried over when we switch go nginx, I suspect since it was always intended to be there to have things continue to work while folks transistioned to the /inprogress link. We can certainly add it back if folks would like. Thanks, Stephen
Attachment
Stephen Frost <sfrost@snowman.net> writes:
> The old URL had been a redirect set up when we were running lighttpd but
> wasn't carried over when we switch go nginx, I suspect since it was
> always intended to be there to have things continue to work while folks
> transistioned to the /inprogress link.
Huh. I wonder why it was still working for me?
> We can certainly add it back if folks would like.
I just switched my bookmark to the new one, so I don't care anymore.
regards, tom lane
Greetings, * Tom Lane (tgl@sss.pgh.pa.us) wrote: > Stephen Frost <sfrost@snowman.net> writes: > > The old URL had been a redirect set up when we were running lighttpd but > > wasn't carried over when we switch go nginx, I suspect since it was > > always intended to be there to have things continue to work while folks > > transistioned to the /inprogress link. > > Huh. I wonder why it was still working for me? All I can guess is a really long cache, maybe because the browser hadn't been restarted since the last time you used it..? There's very clearly not a redirect in the nginx config for that, while there was in the lighttpd config, and that change was made back in February.. > > We can certainly add it back if folks would like. > > I just switched my bookmark to the new one, so I don't care anymore. Ok. Thanks! Stephen
Attachment
On Wed, Mar 17, 2021 at 05:07:36PM -0400, Stephen Frost wrote: > Greetings, > > * Bruce Momjian (bruce@momjian.us) wrote: > > I usually use this URL to find the current commitfest: > > > > https://commitfest.postgresql.org/action/commitfest_view/inprogress > > > > It used to work, but now returns a "Not found" error. Is there a better > > URL for this? > > Short answer is, yes: > > https://commitfest.postgresql.org/inprogress > > The old URL had been a redirect set up when we were running lighttpd but > wasn't carried over when we switch go nginx, I suspect since it was > always intended to be there to have things continue to work while folks > transistioned to the /inprogress link. > > We can certainly add it back if folks would like. No, thanks, the new one is fine. I just needed it for: https://pglife.momjian.us/ -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
On Wed, Mar 17, 2021 at 10:14 PM Stephen Frost <sfrost@snowman.net> wrote: > > Greetings, > > * Tom Lane (tgl@sss.pgh.pa.us) wrote: > > Stephen Frost <sfrost@snowman.net> writes: > > > The old URL had been a redirect set up when we were running lighttpd but > > > wasn't carried over when we switch go nginx, I suspect since it was > > > always intended to be there to have things continue to work while folks > > > transistioned to the /inprogress link. > > > > Huh. I wonder why it was still working for me? > > All I can guess is a really long cache, maybe because the browser hadn't > been restarted since the last time you used it..? There's very clearly > not a redirect in the nginx config for that, while there was in the > lighttpd config, and that change was made back in February.. In fact, the change was made already back in December, not sure here you got February from? :) That said, I don't think it was *intentional* to drop them, that was a mistake. But it seems that if we made it from December until March before people noticed, we're probably fine, and can just leave it out :) -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
On Wed, Mar 17, 2021 at 11:21:47PM +0100, Magnus Hagander wrote: > On Wed, Mar 17, 2021 at 10:14 PM Stephen Frost <sfrost@snowman.net> wrote: > > > > Greetings, > > > > * Tom Lane (tgl@sss.pgh.pa.us) wrote: > > > Stephen Frost <sfrost@snowman.net> writes: > > > > The old URL had been a redirect set up when we were running lighttpd but > > > > wasn't carried over when we switch go nginx, I suspect since it was > > > > always intended to be there to have things continue to work while folks > > > > transistioned to the /inprogress link. > > > > > > Huh. I wonder why it was still working for me? > > > > All I can guess is a really long cache, maybe because the browser hadn't > > been restarted since the last time you used it..? There's very clearly > > not a redirect in the nginx config for that, while there was in the > > lighttpd config, and that change was made back in February.. > > In fact, the change was made already back in December, not sure here > you got February from? :) > > That said, I don't think it was *intentional* to drop them, that was a > mistake. But it seems that if we made it from December until March > before people noticed, we're probably fine, and can just leave it out > :) Agreed. I already made the one-line change to fix it for Pglife. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.