Thanks @JHedden I should have thought of that!

I think it may have become more urgent because new members have joined the chapter and it's not possible for the list admins to add these new members to the list. Does this qualify for increasing the priority?

I think this is now fixed and working everywhere.

It looks like it's this (unresolved) Guzzle bug, but we can maybe work around it by using a request Pool (which by default is limited to 25 concurrent requests). I've made an example patch: https://github.com/wsexport/tool/pull/186

I'm not sure there is an issue with confusing YYYY-MM with a date range, because this seems likely to be only about using this in a place where we expect a single date.

Oh, I think awstats only generates for completed years and months. So the 50x error counts are as follows, for completed months this year:

Thanks @MusikAnimal that's great. Lots of our tools suffer from the 1- to 9-minute outages, so if we leave them out we get the following counts of longer ones:

If we go with the revision tag idea, it'd of course only be possible to show talk page feedback added since this new feature becomes active. Is that okay?

A preliminary patch, to make it possible to have custom config for tests, is https://github.com/wsexport/tool/pull/185 — it's ready for review.

PR: https://github.com/wsexport/tool/pull/184

I think adding a new large instance to that project would be sufficient. It's still got space:

When the toolbar is turned on, it makes an API request to get the metadata about the page, but the pagetriagelist endpoint doesn't return info about pages that aren't in the queue. So we have the option of either extending that endpoint (e.g. with an additional includeall flag), or having the toolbar make a second request to get the missing metadata (it's looking for creator, creation date, redirect status, etc. — all the ones that are independent of the review queue). This metadata is mainly used on the 'info' flyout tab, as well as for e.g. leaving comments for the page creator. It then uses other PageTriage API endpoings such as pagetriagetagging to submit the data, and these also only work for pages in the queue.

I like the idea of creating a new instance and migrating the data of discourse1002.discourse.eqiad.wmflabs :-) (And thanks for sorting out the upgrade there the other day, by the way.)

Thanks Dom!

I've been meaning to upgrade the wiki anyway. Will do that and see how it goes on 1.32.

Log entry is:

Thanks @StevenCrossin — I'll look into this soon I hope.

This file seems to be working correctly with the new version of svgtranslate.

PR: https://github.com/wikimedia/eventmetrics/pull/298

I've created https://translatewiki.net/wiki/Translating:SVG_Translate

@dom_walden you're now a maintainer: https://toolsadmin.wikimedia.org/tools/id/svgtranslate-test

This patch is merged, and the test site is updated with the new /tmp config. The cleanup script cronjob (on the test site) has also been removed.

Who should see the "Curate this article" link in the sidebar? Every logged in user? Every extendedconfirmed user?

Ready for QA.

PR117 is now in production, so the redirect pattern above should work.

Sorry, good point: I didn't look into this in enough detail. I've added support for these in PR117 (it was only supporting file page URLs).

The PSR4 patch is merged now.

It doesn't seem worth fixing the search page to work on mobile if the translate page doesn't also work. But maybe we should add a small-screen-only message telling people not to try using narrow devices?

Merged and live on the test site.

Partial implementation of this: https://github.com/wikimedia/svgtranslate/pull/116 (just to record the bits I did this morning while we were talking about this). This can still be estimated, because the tricky bits of making it all look right are still to be done.

Good points.

This is being done at the same time as T223337.

This is ready for review. Note that you might need to nuke local temp files and docker-compose down if you've tried this patch already.

This is nearly functioning properly: https://github.com/wikimedia/svgtranslate/pull/48