On Thu, Nov 28, 2024 at 1:43 AM Daniel Sahlberg <daniel.l.sahlb...@gmail.com> wrote:
> Den ons 27 nov. 2024 kl 08:40 skrev Daniel Sahlberg < > daniel.l.sahlb...@gmail.com>: > >> Den ons 27 nov. 2024 kl 06:42 skrev Nathan Hartman < >> hartman.nat...@gmail.com>: >> > A little while ago I committed r1922147 at site/staging to catch-up >>> merge from site/publish. However, it appears the site continues to >>> serve older content. >>> >>> It doesn't appear to be a browser caching issue on my end. >>> >>> A few hours earlier I committed r1922136 and r1922133; those changes >>> are showing up in the browser as expected. >>> >>> Since r1922147 was kind of a hairy manual merge, I'm tempted to think >>> something got messed up there, but I don't see anything wrong in the >>> diff. >>> >>> Any ideas? >>> >> >> Sorry, nope. I think we need to involve Infra in this question. It should >> be picked up by pubsub, but I don't know what happens if a notification is >> missed. >> > > It seems it was updated later that day, probably after the r1922147 > (catchup) or r1922183 (1.15) revisions. > I forgot to circle back... I talked to Infra yesterday and Infra said a system was offline at the time of my catchup merge, but things are back to normal... I reviewed r1922136 (mailing lists) and it looks good, so I merged to > publish and it appeared on the website immediately. > Thanks! Cheers, Nathan
