stretch was easier than I expected, patched packages are at https://people.debian.org/~legoktm/doxygen-stretch/ - please test :)

Marking this as verified, is there a separate ticket for the flickering issue? @Petar.petkovic/@Esanders.

In T217616#5038738, @Volker_E wrote:

Do we agree that we should treat non-Arabic numeral ordered lists equal to Arabic numeral (all Latin scripts to my knowledge) ones?
If we don't set decimal as default, ordered lists fall back to decimal. Which we should override with better treatment for serving our communities (we do this in other skins already).

In Beta the button appears to bleed into the right edge of the screen. The expectation is that it is right aligned.

Yeh your screenshot definitely looks better but right now i'm seeing bleeding on enwiki too.

Four Wikipedias are protesting against EU Copyright Directive - https://wikimediafoundation.org/2019/03/20/four-wikipedias-to-black-out-over-eu-copyright-directive/

• German
• Danish
• Czech
• Slovak

Black boxes in CX will go away after the blackout ends. It is supposed to last 24 hours on March 21.

@hashar I built patched debs for buster at https://people.debian.org/~legoktm/doxygen/, could you test those out before I build fixed versions for stretch (assuming the defacto Debian maintainer is OK with my plan)?

It turned out to be an action on dewiki - https://de.wikipedia.org/wiki/Wikipedia:Hauptseite

I verified this is happening in production, on dewiki.

Tested, now fixed.

Mentioned in SAL (#wikimedia-operations) [2019-03-20T23:49:24Z] <jforrester@deploy1001> Synchronized php-1.33.0-wmf.22/resources/lib/ooui/oojs-ui-core.js: SWAT T218722 T218830 Bring forward UBN OOUI fix (duration: 00m 57s)

Change 497949 merged by jenkins-bot:
[mediawiki/core@wmf/1.33.0-wmf.22] OOUI: Bring forward UBN fix for DropdownInputWidget with MenuSectionOptionWidget

Change 497949 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[mediawiki/core@wmf/1.33.0-wmf.22] OOUI: Bring forward UBN fix for DropdownInputWidget with MenuSectionOptionWidget

Change 497947 merged by jenkins-bot:
[mediawiki/core@master] OOUI: Bring forward UBN fix for DropdownInputWidget with MenuSectionOptionWidget

(Also affects core Special:Block)

Change 497947 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[mediawiki/core@master] OOUI: Bring forward UBN fix for DropdownInputWidget with MenuSectionOptionWidget

Possibly same as T218722?

In T218233#5036593, @Krinkle wrote:

Looks like all the Debian channels (jessie, stretch, buster, sid) are still on 1.8.13. Last update was last year (1.8.13-10) indicating that the package no longer has a Debian maintainer (discussion).

I can force the client to timeout, but I can't seem to reproduce the problem with displaying the response on screen. It seems plausible that display_errors was the problem, and is now fixed. I'm willing to call this complete and we can re-open if it is seen again.

From: Antoine Musso
Date: Wed, 20 Mar 2019, 22:24

From: Paolo Greppi
Date: Wed, 20 Mar 2019 18:52:04 +0100

In T218535#5041247, @Beeswaxcandle wrote:

I would rather deal with my five scores on enWS myself. Even if a bot amends them, I'll still have to go back into the pages to do other tasks. I would be surprised if there were any other enWS scores affected as I'm the principal editor of such and I would have been contacted by anyone else seeing the problem.

In T218535#5040598, @Ebe123 wrote:

@Ankry: It would be helpful, thanks! I didn't know about this quarry-ing :) Would be good to group by page, but also make sure that content in the score tag was modified in the timeframe, and include all wikis)

In T218535#5040528, @Ankry wrote:

In T218535#5040209, @Ebe123 wrote:

Impossible to have a full list of broken scores, but they can be fixed by adding a comment to the scores, which will force regeneration.

No true. This is possible. Only pages with the "score" property edited in specific time period are affected and number of wikis that use score effectively is limited. Basing on such a query:
https://quarry.wmflabs.org/query/34588
I can likely provide a full list of broken score images.

Will it be helpful?

In T218535#5040598, @Ebe123 wrote:

@Lydia_Pintscher: I understand that you have your processes, that was not the concern. It was more asking why Wikidata has taken an interest in this bug, seeing that it did not affect Wikidata (some sort of taking responsibility as the cause of the bug?)

@Lydia_Pintscher: I understand that you have your processes, that was not the concern. It was more asking why Wikidata has taken an interest in this bug, seeing that it did not affect Wikidata (some sort of taking responsibility as the cause of the bug?)

In T218535#5040209, @Ebe123 wrote:

Impossible to have a full list of broken scores, but they can be fixed by adding a comment to the scores, which will force regeneration.

Seeing the indicator again! Thanks @NHarateh_WMF!

@Ebe123 This is handled by the Wikidata team and the Wikidata team has a specific process about how tickets flow through the pipeline. A part of that is product management and community communications testing the feature or bugfix to make sure everything is ok. So please leave the ticket open when someone reopens it when their team is the one working on it.

Impossible to have a full list of broken scores, but they can be fixed by adding a comment to the scores, which will force regeneration.

I think, this still needs some maintenance to regenerate broken score images, created while the wrong configuration was actice.