This extension only adds this link once (via SidebarBeforeOutput hook).

Seemingly fixed in T266681.

In T331228, this error happens inside $parser->recursiveTagParseFully( $row->text )
(where $parser is Parser object, and $row->text is the value of text.old_text field in the MediaWiki database).

I don't know. VisualEditor is maintained by WMF's Editing team: https://www.mediawiki.org/wiki/Editing_team

In T285176#7379175, @Yaron_Koren wrote:

Are you sure this isn't fixed already? I would like, if possible, to get confirmation that this is still a problem with the latest Cargo code (version 3.0).

Pull request to modify the library: https://github.com/nyurik/mw-graph-shared/pull/4

it depends how much original code is left?

Implemented, backported to REL1_37.
Closing as resolved.

Closing, as this issue doesn't seem to exist now.
(I updated one of the extensions yesterday, and "Version Breakdown" is showing correct version already)

@daniel Do you have any objections to reverting T283146?

Unknown. Can only be tested by updating the version of some extension on some wiki, and then checking the WikiApiary page of that wiki in a few days after Bumble Bee run.
Let's close this ticket and reopen it later if the problem is observed again.

1. Its removal should be reverted. It was removed without understanding of its usecase (see above), and there is no benefit to it being removed.
2. Even without --reuse-db, a second issue ("due to tables now being deleted, --use-normal-tables now can't be used for inspecting the database after a failed test") still remains.
3. T283146 incorrectly implies that --use-normal-tables was useless due to table truncation. This is wrong, because phpunit can be called with --stop-on-failure, which ensures that no other tests run after the failed test (meaning that tables won't be truncated: they are truncated at the beginning of tests).

Extension:AWS is on GitHub, so it uses GitHub issues as bugtracker: https://github.com/edwardspec/mediawiki-aws-s3/issues?q=is%3Aissue

Slots can still be accessed via RenderedRevision object:

I haven't looked into Moderation yet, it may or may not have to use this mechanism.

This impacts Extension:Moderation (see https://github.com/edwardspec/mediawiki-moderation/issues/56#issuecomment-659131221 ),
which calls invalidateCache() method of its service in the end of LoadExtensionSchemaUpdates hook.

The following hooks (although unused now) have valid usecases where they can be needed (private corporate wikis, etc.):

Note: Extension:Moderation uses "master" compatibility policy (its master branch is backward compatible with MW 1.31), so it doesn't need this change yet. (not until hard deprecation of IP class)

@daniel @CCicalese_WMF Is there anything I can do to get this merged before 1.35 (LTS) gets released?

Uploading extra screenshot for code review of gerrit:569107, showing the "Previous page" thumbnail and URL of its link.

There was an UI bug that caused clicks on "Previous page" thumbnail on Page 2 to point to page=0 (incorrect) instead of page=1 (correct).
It is fixed by https://gerrit.wikimedia.org/r/569107

Not applicable to the latest version of CreateRedirect.
Closing as resolved.

"DeletedUser123" or something.

A colon is correctly prepended in the latest version (after T28898).

people were accidentally tagging it instead of the correct account,

The following change fixes this: https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VEForAll/+/523976/

See also: https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/CreateRedirect/+/562647/

Hello,
I cleaned/rewrote the extension, please see https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/CreateRedirect/+/562647/

See also T205982. If/when MultiContentSave hook is merged (https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/467308/), it will be possible to use the following:

public static function onMultiContentSave( $title, $user, $slots, $summary, $flags, $status ) {
    $slots->setContent( 'main', ContentHandler::makeContent( "Another text", $title ) );

Also https://wikiapiary.com/wiki/User:Audit_Bee claims that it "Makes websites inactive [...] if they have not had any edits in 12 weeks".
But on 23 December it marked this wiki as inactive - https://wikiapiary.com/w/index.php?title=%D0%9C%D0%B0%D1%82%D0%92%D0%B8%D0%BA%D0%B8&diff=4801798&oldid=4721089 - where the latest edit was on 21 December.

500 is almost always temporary.
There is no reason not to retry in 6 hours, unless the site returned 500 on all past attempts for weeks.

As convenient as it would be for WMF to say "just go install your own Mathoid, Restbase, etc.",
the facts are:

1. Math is an extension of immense importance. It's used on many third-party wikis, including scientific wikis operated by small groups or individuals.
2. In the past, Math didn't have all those complex dependencies. You just placed texvc executable where needed and it worked.
3. Later Math was rewritten to require Mathoid server and (apparently) Restbase server. Those are memory-consuming daemons that run always (even if the wiki has like 30 formulas overall) and require adding NodeJS (not the least memory-leaky thing in the world) to the stack.
4. An experienced engineer can setup that, but let's be honest about it, most noncommercial third-party wikis won't be able to.
5. ... so wikis who have like 30 formulas use the default configuration, with enwiki as Restbase and WMF's beta mathoid as Mathoid. This is reflected by default settings.
6. Breaking those default settings, either by blanking them or by shutting down the public Mathoid server that WMF has been operating, would just break Extension:Math on many sites, and prevent many more from using it.

I used force push to import existing revision history from the Github repository.
The repository on Gerrit was just created and had no code, so there was no reason not to overwrite it. Two commits by @MarcoAurelio were things like placeholder README, copied codesniffer config, etc., so nothing meaningful was lost.

@DeepBlue Looks like BumbleBee bot is not running: https://wikiapiary.com/wiki/Special:Contributions/Bumble_Bee

mathoid.testme.wmflabs.org returns 502 Bad Gateway again.

Closing as resolved, as Extension:AWS works with latest MediaWiki and is covered by automatic tests.
https://www.mediawiki.org/wiki/Extension:AWS

Investigating. But it uses standard