@leila I expect to have a near-final preview within three weeks and will proceed with items (2) and (3). I’ve created a new task to track the upgrade.

In T415725#11563856, @Wargo wrote:

In T415725#11563488, @brennen wrote:

I've seen it claimed that ?action=purge for a given page fixes the error, but @Lucas_Werkmeister_WMDE says not always, so maybe people are seeing a coincidence with something dropping out of cache?

Yes, it (or null-edit) helps only once for a page and after revisit (same user or another) the error returns.

In the context of T311945, I’m migrating the Design site to a Codex + VitePress stack. Next, I plan to migrate the Research site, reusing the same theme, since the two sites have similar content structures.

Since the site repositories have been migrated to GitLab and a new deployment infrastructure has been put in place, this task is no longer relevant.

@leila https://research.wikimedia.org/report.html?date=2025-12-18

@leila I've made the adjustments.

All ported. Preview:

Apologies for that. At the time of deployment the canary check was fine but I can see the spike on Logstash now. I believe I should've observed it further.

1210729 pre-deployed the non-enwiki surveys with 0 coverage.

Debug URL

@TAndic I can try to deploy it on Monday afternoon backport window and otherwise on the late window. Anyway it wouldn't be useful for this survey as I'm deploying it on Monday as well.

In T410696#11396160, @TAndic wrote:

@YLiou_WMF I checked the skip patterns for the survey and all looks fine on this end.
Methodological note: temp users (previously IP editors/anon) are now categorized with user/editors (see QuickSurvey documentation). If you see a drop in previous editing experience, this may be a result of the population change. (Alternatively, we could target all and then use the userInGroup setting to only display to temp for users, but having never used this and working on a short timeline, it may be risky as I believe there are still some open questions about the temp group functionality.)

@YLiou_WMF I'm available for deployment on Monday.

Debug URL

@Dragoniez thanks!

I wasn't able to create the link message on jawiki due to an automatic malicious edit filter.

I just deployed the survey with coverage set to 0. I missed a space on the config so the survey question is not displaying. Will deploy fix.

Test URL

@Isaac CDN has some information on how caching works on Wikimedia projects. I have the same issue. Users are served by different servers based on their IP. What probably is happening is that some caching servers have an outdated cache while others don't. I don't know if I can improve that from my side but if you trigger a cache miss the caching server will retrieve the latest version of the page. You can do that by adding a fake parameter to the page and it can be anything as the site is static. It just need to be a new URL. e.g. https://research.wikimedia.org/report.html?r=12

@Isaac Just published it.

@Isaac

@Isaac I've finished moving the sections that were stable.

@Isaac The redirect is in place.

@Isaac acknowledged!

@Jelto it happens, no problem.

@Isaac it appears that a patch from T398303 accidentally rolled back the images to older versions.

Readers of English Wikipedia (global) excluding active editors (5+ edits in past month)

@YLiou_WMF Yes.

@diego I updated the citation to match the existing style.

We decided to increase coverage to 25% to ensure that the survey reaches its goal.

@DKumar-WMF Done.

We're increasing coverage to 7% to adjust for a slower than expected response rate.

Survey was pre-deployed with 0 coverage. Looks good to me.

Thanks @Isaac! Changes are live.

@Isaac & @leila I'm done.

@Isaac Porting the content is more repetitive than difficult. :) I can share a page capture here to save you some extra steps and so Leila can also preview it.

@Aklapper owner perms are needed to archive the project. @Dzahn can you do it?