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. Speaking of pubsub, Humbedooh mentioned the Python 3.12 deprecation of asyncore/asynchat [1] is starting to affect Infra. I doubt this is a reason (they are aware of it, so they wouldn't update to Python 3.12) but it will affect ASF in the future. I had a quick look but I don't have the time to dig into it. Anyone interested? Cheers, Daniel [1] https://lists.apache.org/thread/txcosmp5ngz6c3okrc8gno36n90qv9ft
