team @bvibber / @TheDJ / @Jdforrester-WMF ;)

@jcrespo and @Ladsgroup does any of this still occur ? There's been several changes to the job since that 2017 state, but i have no idea if this is still a thing.

And also a reminder that this is expected every once in a while. It even has it's own page https://en.wikipedia.org/wiki/Wikipedia:Replication_lag

we do seem to check partially if the file still exists

/ Do a quick check to confirm the job was not restarted or removed while we were transcoding
// Confirm that the in memory $jobStartTimeCache matches db start time

It means that a request was sent but then the server didn't respond within x seconds and the servers cut off the connection, failing the request.

Hmm this attribute was also not documented. https://www.mediawiki.org/w/index.php?title=Help:Extension:Kartographer&diff=prev&oldid=6471835

This messing with the focus events is sloppy though (always has been). You are basically moving the cursor... IF this is a problem for CM6, an alternative is to add a named event and have charinsert listen to that perhaps.

The gadget directly uses the storage item api, and does not account for the fact that the storage allowed for the website by the browser might be full. This is a bug in the gadget.

Ive been thinking about this, do we really need a column for this ? We can just log it as a field in the error. Not pretty, but a lot less duplication of servernames.

We are no longer generating ogg/oga derivatives. everything is webm or mp4 now.

@bvibber if we are going to run db updates anyways. Perhaps we should add a column for the file size of the derivs to the table as well ? Those are currently unknown and there's been a desire in the past to get better insight into that information. T57942: Expose file sizes of transcoded assets in API

Both fields are a requirement for GPS exif coordinates.

In T361465#9691865, @Andyrom75 wrote:

@TheDJ, this buggy code is on server side o it's in a local gadget?
I suppose the first one, but I ask to avoid misunderstanding.

@Arlorla how do i configure my wiki to use native parsoid rendering ? i can't find that anywhere in the documentation.

I forgot about database latency of course. I should probably do findfile with the latest: true annotation.

If anyone is interested in improving this, the code is here: https://github.com/wikimedia/mediawiki/blob/master/resources/src/jquery/jquery.textSelection.js

Yes, this is a known issue, because the textSelection plugin we use doesn't support that, because it is from a time before multiple selections were supported in browsers.

Yeah I also don't really understand this. margins are predictable. Trying to bypass collapsing seems like an attempt to break a behaviour because it was in the way somewhere, but it just creates more problems because now you are doing something that nothing else is expecting.

We will have to merge the two diverting versions https://github.com/wikimedia/getID3/compare/master...JamesHeinrich%3AgetID3%3Amaster

We would still have to trigger a GlobalUsageCachePurgeJob for interwiki purges. Same as for T241901.

I'm calling this resolved, though some follow up work is required on some of the messages, which is T361754 and T361756

Solved like this:

Charinsert has a function that determines the last focused text input.

hmm. or not. I moved this file https://test.wikipedia.org/wiki/File:Bear_av1_renamed.webm

Due to changes in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TimedMediaHandler/+/986519
Possibly happens when both the timed text page AND the corresponding file do not exist.

possibly for non-existing timed text page + non-existing File page...

Remainder should be in https://gerrit.wikimedia.org/r/986519

This should be fixed once the change rolls out this week.

@bvibber i wonder if this is because of findfile following the redirect...

I feel this was already 'mostly' fixed a while ago, but with https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TimedMediaHandler/+/1015413 I think the final holes should be plugged ?

I guess we can introduce a dependency on GlobalUsage extension and re-use GlobalUsageCachePurgeJob. might take a look next week.

In T343081#9664580, @Watchduck wrote: It would be useful to figure out what went wrong.

I was inspecting the epub, and I noticed that it sets:

In T345723#9664487, @Samwilson wrote:

but it does seem like the wrong thing to do.

The point of display:table on the figure is so that the caption stays left aligned and doesn't extend beyond the width of the figure, without having to set an explicit width. With display:block any caption becomes too wide.

In T345723#9664621, @Xover wrote:

I would also argue that since the thumb chrome is a function of the skin (which is exactly why we don't use it in content), which is not present and won't work in ePub output, this would also be a reasonable limitation to impose in WS Export.

In T360384#9662874, @Base wrote:

How many freeform javascripts do you get to install in your Facebook or Instagram page again?

If your point is that WMF is a for-profit corporation just like Meta Platforms is, and thus it should not hold its userbase in any regard, then I would agree with you.

Don't forget about @1.5 and @2 sizes for hidpi/retina screens

Also asking the user which software was used to make this clip, that might be helpful for any other clips generated with a similar path.

@bvibber I believe we run our own version of getID3 ? If so we can update.

https://github.com/JamesHeinrich/getID3/issues

This file throws:

In T360384#9660135, @Base wrote:

Another additional work paid "improved" vector WMF staff is putting on unpaid projects' volunteers.

I've done some checkups in the logs and brought @Bawolff 's patches up to date. I think they are still fine to merge and move forward with, at the very least initially towards wikipedia/test resources.

In T97233#9656083, @Tercer wrote:

Yet another file hit by this bug: https://commons.wikimedia.org/wiki/File:Quadratic_function_graph_key_values.svg

Everybody knows that it's pointless to list more files here. Spamming this task is an expression of our frustration.

In T134455#9512045, @Jonathanischoice wrote:

Should we close this ticket, given we now have wgSVGNativeRendering and related settings merged to master on T208578?