Refs T244108 which followed up a few years later.

FYI I got an error message while trying to upload PDF from https://archive.org/details/da-capo-press-camera-notes-v-3-4-1899-1901

In T115563#4945918, @Tgr wrote:

@Jwpat7 you need to refresh the page, then enter the code before opening any images in MediaViewer, then try opening an image. Apart from that what you do with the console doesn't matter (although if you leave it open there's a chance it gives you some useful error message when opening the image fails).

...

@Jwpat7 you need to refresh the page, then enter the code before opening any images in MediaViewer, then try opening an image. Apart from that what you do with the console doesn't matter (although if you leave it open there's a chance it gives you some useful error message when opening the image fails).

Regarding the problem with an error screen appearing after clicking a small image (with message "Sorry, the file cannot be displayed" "There seems to be a technical issue"): This message occurs when I click on images on the page https://en.wikipedia.org/wiki/Dilution_refrigerator using browser "Chromium Version 71.0.3578.98 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit)".

@Aklapper Understood.

@Thedonquixotic : This task is resolved (see top bar). If something does not work for you, see https://www.mediawiki.org/wiki/VisualEditor/Portal for where to discuss issues. Thanks!

Hey, just curious if this feature is actually in Visual Editor or not? I can't seem to find it, or figure out how to use it.

Change 242422 abandoned by Mooeypoo:
[wip] Add browser test to "mark all as read" in Echo notifications

I assume this can be closed as resolved, as https://gerrit.wikimedia.org/r/248568 is merged.

Change 178864 abandoned by Hashar:
Replace some of deprecated WfMsg and friends

Based on the long gap between responses on this bug, I'm going to guess that it's no longer an issue - especially since seemingly none of the examples still cause problems (at least for me).

I think this got worse on failover- the query planer gets confused between page_user_timestamp and page_timestamp, they are too similar indexes, but the wrong one causes a fileshort (and even worse performance when a page has many revisions).