There's no permissions in the gadget implementation. You can't restrict who gets to change a status.

In T361067#9858226, @MusikAnimal wrote:

Random tech debt thing -- we have a few terms for whatever the subpage name for a wish/focus area is. Is slug a good name and if so maybe the db and backend things could be renamed? Or vice versa :)

@JScherer-WMF asked on Slack for image size statistics.

In T366824#9872926, @MarkAHershberger wrote:

I wish I understood how coroutines were disabled, but searching the Scribunto codebase found only a couple of references to the word coroutine in the tests. Fiddling ignorantly with those tests didn't seem to provide any meaningful change.

In T138933#9847347, @Sdkb wrote:

@tstarling I don't understand the gerritbot comment above. Would you be able to give an update on where this task is at?

TMH should set its own class attributes on the server side and avoid mangling unrelated content. Per my commit message comments on cf8a4f2133cb, TMH is too broken to use with Score. Requiring every other extension to set a fake TMH attribute to trick TMH into not breaking it doesn't seem like a good solution.

I just discovered T224245, which is a different approach to the same problem, already implemented.

In T201340#4508339, @Niharika wrote:

Do we want to do the row cleanup as part of this ticket? If not, let's get another ticket in.

Some usages of $wgBlockTargetMigrationStage remain in WMF-maintained extensions.

In T209892#9834400, @Clement_Goubert wrote:

@tstarling @dom_walden Is it possible to test an election on the mw-debug deployment of MW-on-K8s using XWD, or are we missing some configuration to try this in production?

In T352499#9813708, @Jdlrobson wrote:

FWIW We need some more background on why these messages were selected in the first case.

It seems to me that it should be possible to represent all powers of two up to the limit of the exponent, since the mantissa is just 1 for those numbers. So 2^53+1 is the lowest positive integer which needs to be rounded in order to fit in a double.

I suggest renaming bot.js to update-indexes.js.

In T361067#9790933, @MusikAnimal wrote:

Proposed implementation plan:

• Use sqlite3 for data persistence, using the filesystem to avoid the need for an SSH tunnel to a Cloud Services database (or local MySQL-like dependency)

This was fixed.

@aaron disabled it on 2013-03-14 and re-enabled it for Commons only on 2013-03-29. But there was no UI for it on wikis other than Commons, and that remains the case.

In T354949#9790843, @Ligliotoi wrote:

Hallo,

https://panoviewer.toolforge.org/ does not work. Error 403 "Forbidden". Can somebody fixed it maybe?

Confirmed fix on ar.wikipedia.org

In T346293#9785650, @matmarex wrote:

Looking here: https://gerrit.wikimedia.org/g/mediawiki/core/+/bc11d8072a47fdc2f9d3a60f78c09716948b626e/includes/block/DatabaseBlockStore.php#336 tables does not list block_target, but it refers to bt_* fields from that table.

The query definition a few lines below: https://gerrit.wikimedia.org/g/mediawiki/core/+/bc11d8072a47fdc2f9d3a60f78c09716948b626e/includes/block/DatabaseBlockStore.php#367 does list block_target when using fields from that table.

I'm not sure if that's a mistake, but it looks suspicious.

Temporary repo with unreviewed code: https://github.com/tstarling/pano-projector

In T363891#9762699, @tstarling wrote:

In T363891#9760677, @TheDJ wrote:

Panellum falls back to a low resolution full size image if the results are not yet ready. The toolforge tool also renders on the fly i believe and it will 'fill in' results as they arrive based on a JS poll.

There's no Pannellum support for that, it's only in the panoviewer tool.

I did a rough prototype of this in C++, and I got it down to 5.9 seconds for single-threaded extraction of a single cube face. So I think this is the way to go. I'll write a custom cube face extractor, and Thumbor will run it on demand, no need for a job.

The frequency of these errors before March 6 g1008752 reflected the frequency of Redis connection timeout errors. About 1 in every 160 errors raised by excimerFlushToArclamp() would fail with "HookRunner not found". So following Timo's patch, we can expect this to be very rare indeed. In logstash since that date, there has only been one such error. So I think it is a low priority.

DENIVIP's panorama converter shows how simple it can be. It does all 6 cube faces in 67 seconds, single threaded. They messed up the interpolation somehow, the CImg library they used is weird and scary, and the dependencies are wrong (it doesn't really need xorg-dev), but it's certainly inspiring. It's basically doing the thing we need in 229 lines of code.

By specifying bilinear interpolation I was able to reduce the time taken by PTmender to extract a cube face from 42 to 33 seconds. By default it uses a cubic polynomial on a 4x4 region of the input image, but I think that's excessive given we're only upscaling by a factor of between 1 and 2.

I made subtasks for what I see as the three main components of spherical panorama support:

In T363891#9760677, @TheDJ wrote:

Where would we store the results ? Make a new file storage subspace like score-render ?

In T345334#9752173, @Ladsgroup wrote:

That'd work on overall hits, as you said "sort images by popularity". That's not the case here. Front caches absorb all of the hits and collapse the power law distribution.

In T363885#9760636, @TheDJ wrote:

In my experiments so far, i've noticed that we also have a LOT of images that do NOT have GPano metadata.

In T363885#9760140, @AntiCompositeNumber wrote:

It only supports TIFF output, so it's necessary to pass the resulting image through ImageMagick to convert it to a JPEG.

What input formats are supported?

Following the merge of https://gerrit.wikimedia.org/r/1003091 it would be good if @dom_walden could do a test election using the new OpenSSL encryption method. See my local test log comment on PS5 for information about generating keys and creating an election.

We can't, due to T196132: wikidiff2 binaries are not distributable due to PHP / GPL license incompatibilities

In T345334#9654752, @Ladsgroup wrote:

If we do extrapolation after 10,000th hit. The Theil-Sen extrapolation becomes more useful:
So the simplest is to see is boundary problem and say it's 130 hits at zero and zero at 200M and draw a line.

Should be fixed in Shellbox 4.0.1 which is required by MediaWiki 1.42.

If there is some aspect of this that is not addressed by https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1010344/ , feel free to reopen.

Reopening for 3rd party migration and MW core cleanup.

There were a few duplicate key errors while the change was half-deployed, the last at 23:23:00.

Thanks for the report @labster. I can accept a Gerrit patch along these lines. It looks like you do have an account in Gerrit already.

I couldn't reproduce this, with PHP 8.2.15, xdebug disabled, and excimer locally compiled from the current git master.

CriticalSectionScope is not meant to be alive until the end of the process. That's the whole point of it, to have scope lifetime.

This should only happen if your IP address is in a /24 subnet (or /64 for IPv6) that hasn't been used for login in the past 80 days. Can you comment on whether that is likely to be the case?

Note that the other classes extended by GlobalPreferences (DefaultPreferencesFactory, PreferencesFormOOUI and SpecialPreferences) are also not marked stable to extend.

MaxSem refactored ApiOptions to allow GlobalPreferences to extend it. He just didn't add @stable to extend because his work predated the introduction of those annotations.

In T323076#9678101, @tstarling wrote:

As such, it seems to me that the apiwarn-globally-overridden warning should have been an error.

In T323076#8394346, @Jdlrobson wrote:

(unless we resort to hacky string indexOf checks on the warning).

Shortcuts for zoom will be provided to avoid clicking and repositioning: shift+scroll and "+" and "-" keys will increase/decrease the zoom level centering the zoom area to the current mouse position.

On T198913 we had multiple engineers arguing that users should be informed of global preference updates or overrides, so the default behaviour of action=options, where there is a non-overridden global preference and the extension has not suitably informed the user, should be to fail. As such, it seems to me that the apiwarn-globally-overridden warning should have been an error.

I found 1.20.6 on a random website. I think the only one we're missing is 1.20.7.

It's unlikely the Internet Archive or any crawler would have files that were generated in September 2013 and reported missing in December 2013. Maybe community members would have them, but the right time to ask was December 2013.

OK, well if they were already missing in 2014, I'm not going to find them in a 2018 archive.

In T349462#9667721, @Pppery wrote:

Anything left to do here?

Legoktm uploaded all MediaWiki tarballs from releases.wikimedia.org to the Internet Archive in 2018. I should be able to recover the remaining missing tarballs from there.

I can set up a wall time limit, but it seems abusive to queue unlimited Transkribus jobs without any plans to check their responses.

I uploaded the following release tarballs from my personal archives, which mostly derive from a copy I made of the SourceForge files section in 2009. I retroactively designated the dated snapshots of 2003 as "1.0" for clarity when navigating the top-level directory. There was no other 1.0 and they immediately preceded 1.1 in the release notes. For files which already existed on releases.wikimedia.org, I confirmed that the MD5 hash was the same before removing them from the following list.