User Details
- User Since
- Oct 15 2014, 8:27 PM (507 w, 5 d)
- Roles
- Administrator
- Availability
- Available
- LDAP User
- Tim Starling
- MediaWiki User
- Tim Starling (WMF) [ Global Accounts ]
Yesterday
We need it for the community wishlist. The idea is to mark wishes for translation in a semi-automated way, with a gadget that runs as a translation admin (T365558). I don't think we need to override the defaults for the nofuzzy checkboxes.
Or there can be a nofuzzyunits parameter and a fuzzyunits parameter, the latter subtracting from the default set.
For API usability, I think an API request with action=markfortranslation & title=Foo should be equivalent to loading the form for that title and submitting it without changing any defaults. There's a couple of things in TranslatablePageMarker that make this inconvenient, like its need to overwrite the priority languages unconditionally. But it can be done.
Fri, Jul 5
The POST branch of PageTranslationSpecialPage::onActionMark() seems simple enough, but I assume a query API similar to showPage() will also be needed, and that looks a bit bigger. Unless it's enough to expect the client to guess the unit IDs for $noFuzzyUnits.
Mon, Jul 1
Mon, Jun 24
Thu, Jun 20
Tue, Jun 18
Wed, Jun 12
There's no permissions in the gadget implementation. You can't restrict who gets to change a status.
Tue, Jun 11
@JScherer-WMF asked on Slack for image size statistics.
Jun 8 2024
Jun 6 2024
Jun 4 2024
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.
Jun 3 2024
Jun 2 2024
May 31 2024
I just discovered T224245, which is a different approach to the same problem, already implemented.
May 29 2024
Some usages of $wgBlockTargetMigrationStage remain in WMF-maintained extensions.
May 28 2024
May 24 2024
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.
May 16 2024
I suggest renaming bot.js to update-indexes.js.
May 14 2024
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.
Confirmed fix on ar.wikipedia.org
May 10 2024
Temporary repo with unreviewed code: https://github.com/tstarling/pano-projector
May 9 2024
May 7 2024
May 4 2024
May 3 2024
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.
May 2 2024
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:
May 1 2024
Apr 30 2024
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.
Apr 29 2024
Apr 26 2024
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.
Apr 9 2024
Reopening for 3rd party migration and MW core cleanup.
Apr 8 2024
There were a few duplicate key errors while the change was half-deployed, the last at 23:23:00.
Apr 7 2024
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.
Apr 5 2024
I couldn't reproduce this, with PHP 8.2.15, xdebug disabled, and excimer locally compiled from the current git master.
Apr 4 2024
CriticalSectionScope is not meant to be alive until the end of the process. That's the whole point of it, to have scope lifetime.
Apr 3 2024
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?
Apr 2 2024
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.
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.