No - it tells the source wiki to export a template and all its dependencies, then processes them all at once.

This error message probably means that you are trying to import too much content at once - exporting full history with templates (off-topic, something I generally recommend against doing since it will clobber the history of common templates like {{documentation}} ) can easily be very large.

Minimum reproducible wikitext:

<score vorbis="1">
{a}
</score>
[[File:Example.ogg]]

What would it mean to log out if you're automatically authenticated without ever having logged in?

Working on this for now to fix most of the above. Probably won't call this resolved when I'm done, though, since it's kind of a grab-bag of many people's ideas.

From duplicate T363517:

In T363538#9748082, @jhsoby wrote:

Sounds doable, but how will interwiki links to the Mossi Wikipedia be added to enwiki then? AFAIK, "under the hood" Wikibase still inserts interwiki links with the [[old:syntax]], it's just that it happens out of sight.

Presumably the same way interwikis to Swedish Wikisource are currently handled, with a "mos-x-foo" interwiki existing and being used. I admittedly haven't looked into this locally, and don't feel like setting up Wikibase locally to do so.

Removals proposed in duplicate T337358, reposted without comment:

Also related: T71997

This appears to be only on Meta's interwiki map (not tracked on Phabricator), not the default interwiki map. Meta's entry now points to https://iso639-3.sil.org/code/$1 (https://iso639-3.sil.org/code/fro), which is still working.

This appears to have been resolved in core's interwiki list. Updates to interwiki map for wikimedia wikis are handled on Meta, not Phabricator, and it appears to have been done there too.

Related/duplicate: T33951

Related: T337358, T337357

This seems to work now.

Please do see my notes at T318763 on how the deployment process works, though, so it will probably be a while before the next deploy.

Wow - never thought this would get anywhere near as much attention as it did.

I tried to do the same thing on this task itself - did it generate another instance of the same error?

I think I clicked on the wrong token, and then while the page was still processing that request clicked on the token I meant to award - the first (dislike) token went through, the second (like) token failed, and then I rescinded the dislike token and added a like token.

Duplicate of T234743?

This appears to be a past hackathon project that has now concluded, and as a goal outside the context of the hackathon (as it now is), it would be outside Phabricator's scope.

Anything left to do here?