Also in emails, e.g., regarding failed puppet runs

I just changed https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikiqlever to include that other page. Maybe we can document that, and is that good enough?

Ah the SAL subpage page is already at the place where I would have expected it to be https://wikitech.wikimedia.org/wiki/Nova_Resource:5238620953c040e7a9effbe47d4e0932/SAL

The stupidest thing I can think of is moving https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikiqlever to https://wikitech.wikimedia.org/wiki/Nova_Resource:5238620953c040e7a9effbe47d4e0932. One can then use displaytitle, etc to make it look nicer. I guess there was a reason for changing from semantic identifiers to identifiers with different desired properties. If we don't enforce uniqueness in project names anymore, it would be hard for the bot the guess the right project.

yes, at the first try (without the volume mounted at /srv) I created the puppet folder manually, but it didn't solve the problem. And I ran into permission issues, regardless of what I changed.

In T379030#10291065, @bd808 wrote:

https://openstack-browser.toolforge.org/project/5238620953c040e7a9effbe47d4e0932 is the UUID named page for the "wikiqlever" project. Stashbot thinks that @Physikerwelt should have used !log 5238620953c040e7a9effbe47d4e0932 start setting up puppet master following https://wikitech.wikimedia.org/wiki/Help:Project_puppetserver based on the LDAP lookup data. This is really poor user experience (same for the UUID in the openstack-browser URL honestly) that we should figure out how to fix.

The Cloud-Services project tag is not intended to have any tasks. Please check the list on https://phabricator.wikimedia.org/project/profile/832/ and replace it with a more specific project tag to this task. Thanks!

I reviewed the remaining tickets, submitted patches for the issues I understand, and commented on the rest. In summary, if the submitted patches are merged. We should be done.

Firefox left, Safaria 18 right. to me both look good.

In T375346#10166157, @SalixAlba wrote:

SVG mode is also generous with space

I can not reproduce that with Safari 18.1

In T375337#10307085, @Krinkle wrote:

@Physikerwelt What happens if, after we roll this out, one of the browsers picks up the change in spec. Does that conflict in any way? If not, I suppose if could go ahead with our overwrite in the mean time.

@Krinkle This is a mistake in the spec, which is going to be fixed upstream https://github.com/w3c/mathml-core/issues/260#issuecomment-2444013254 . Should we still overwrite the defaults or wait until browsers eventually pick up the change in the spec?

Fixing by adding ! to mo

The problem is that \rangle is a delimiter and | is an operator. Thus | doesn't stretch even if we stretch all delimiters.

@SalixAlba I submitted a patch for :

\begin{align}
\int \limits_x ABC \\
\int \nolimits_x ABC \\
\operatorname{sn} \limits_x \\
\operatorname{sn} \nolimits_x \\
\operatorname{\int} \limits_x \\
\sum \limits_x \\
\operatorname{\Sigma} \limits_x \\
\Sigma\limits_x %throws a warning
\end{align}
renders as

There are actually two problems.

1. TeX and texvc ignore \limits and \nolimits commands when they are not used after an operator
2. texvc currently does not recognize \operatorname{x} as something that can be followed by an \limits command

In T166369#10291112, @Ladsgroup wrote:

We do have a bloat problem in user_properties table: T54777: user_properties table bloat not one single property is problematic but they are adding up. There is a maint script that can drop the property if it's all useless now but this has valid cases I think?

The website does no longer exist.

Even 1.36 is no longer supported https://www.mediawiki.org/wiki/Version_lifecycle

I think it boils down the question if we want to extend the set of whitelisted macros and allow \emph as part of the Wikimedia LaTeX syntax. I personally think we don't really need it, but we can also make if poll on this.

@brion Is this still a relevant bug or should we close?

Someone with db access needs to take care of that. It's a simple task to clean old user preferences. Theoretically, one could also load and save all user preferences from time to time (not only for math) and store them again to eliminate invalid values. But why would one care? The math extension assumes the content can be invalid and returns to a default value, so this is not an issue from the Math extension perspective.

The new MathML rendering mode supports it now again.

That should work by now.

There is no image rendering anymore.

I am so unhappy about this solution that I can barely sleep.

The special page won't be needed after svg deprecation.

is no longer supported

This is now part of the module, wd. Also custom parsing functions exist for special types of Math markup in [[ portal.mardi4nfdi.de/wiki/module:wd | non-wmf-hosted ]] wikis:

function Config:getValue(snak, raw, link, short, anyLang, unitOnly, noSpecial, type)
...

is no longer supported.

By default, there are now native MathML and MathJax rendering modes. Restbase is no longer required.

I am running mediawiki 1.25 wmf 16

In T377655#10289317, @aborrero wrote:

Maybe we can create the project with the default quotas, and you can ask for whatever quota bump later once the data is clear to you?

I think for a preview one can jus tender the input using the rendering functionality described in the hook. From this point, math should not need special treatment and should be handled like other complex types.

In T377197#10267684, @ArthurTaylor wrote:

Looks like I missed at least one use of TempUserTrait in CheckUser. I've uploaded a patch now which should resolve the issue in https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php74-noselenium/49533/console ( https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Math/+/1083452 / https://phabricator.wikimedia.org/T377167 )

This is probably similar to https://phabricator.wikimedia.org/T352536 caused by https://github.com/w3c/mathml/issues/61

Current test on https://en.wikipedia.beta.wmflabs.org/wiki/T375907

ok. So it renders fine with ClientSide MathJax (this ticket). The chrome problem would be rather T375861 I think.

What settings do you use in MathJax. For Chromium on Mac it works with MathJax SVG rendering.

If it's sometimes, I was not lucky.