- Does the Android app expect TFA to be present in the response?
When looking at the RESTBase dashboard, the 504s seem pretty clearly to result from the 12/3 security update.
Same as T184128, in which the errors were suppressed for the Graph extension but not Kartographer. There's an open patch for this that I'll take another look at and see if it's mergeable.
Wed, Dec 12
I would suspect the internal promisification stuff, but that wasn't deployed until 12/6.
I suppose for MediaWiki to parse text extracts for 12 pages might not be a particularly fast operation.
Tue, Dec 11
@Tgr Is this what you're seeing?
Mon, Dec 10
I spent a good chunk of time on Friday and over the weekend attempting to reproduce this in MW-Vagrant, but could not; the dynamic map content loads and displays as expected. There must be some quirk in the Wikimedia production environment causing this. If anyone does manage to reproduce this locally, please add some steps in the description and I'll be very grateful!
Fri, Dec 7
Ping @Jhernandez ^
Thu, Dec 6
@Yuriy_kosygin When was the last time you saw this working correctly?
(The page looks fine with JS disabled.)
I can't see any backend errors and it looks like the pieces are all being loaded (scroll down to see them, out of place) but something is broken in the frontend JS.
Wed, Dec 5
The response change is now live.
bearND removed a project: Reading-Infrastructure-Team-Backlog (Kanban).
Tue, Dec 4
Mon, Dec 3
Fri, Nov 30
Node 10 is only supported in node-mapnik >= 4.0.0.
Wed, Nov 28
Nothing else from me. 👍
Tue, Nov 27
Per https://incubator.wikimedia.org/wiki/Special:Version, Kartographer is enabled.
PR to remove it from the service template: https://github.com/wikimedia/service-template-node/pull/110
Mon, Nov 26
Thanks @Aklapper for the updates, and thanks to Platonides (not subscribed) for review assistance so far!
Thu, Nov 22
Wed, Nov 21
Also, considering the image Kartotherian is using as its favicon is an official OSM logo subject to its trademark policy, for as long as we continue to use it, we should include a notice as specified in the policy in some appropriate location:
Tue, Nov 20
Notes for future reference: this file lives at https://github.com/kartotherian/server/blob/master/static/favicon.ico and is referenced from index.html in the same directory. maps.wikimedia.org is mapped to kartotherian.discovery.wmnet which resolves to a kartotherian backend via DNS Discovery.
I can mentor this.
The xmldoc dep was dropped in favor of libxmljs in T177019.
wmf1256:Desktop mholloway$ curl -sO https://maps.wikimedia.org/osm-intl/1/1/1.png wmf1256:Desktop mholloway$ file 1.png 1.png: PNG image data, 256 x 256, 8-bit colormap, non-interlaced
I'll keep this tagged with Mobile-Content-Service for now, but note that this might actually be appropriate as an addition to the Recommendation-API (see also my notes on T206504#4754767). Needs discussion with the Core Platform team and possibly others.
It's live on https://en.wikipedia.org/api/rest_v1/feed/announcements.
@Gehel, do you mean specifically the additional EventBus load generated by activating resource_change events sent from Tilerator (T109776: Tilerator should purge Varnish cache)? Otherwise it's not clear to me where EventBus is implicated here.
Created https://www.mediawiki.org/wiki/Specs/Announcements/0.3.0 reflecting the recent iOS updates. Thanks @JoeWalsh for your work on this!
Mon, Nov 19
@bearND I'd be inclined to agree, except that the mobile site handles the initial language selection menu very poorly, and requires scrolling down (on almost any device, I'd think) to get to the policy text...
I believe this is correct but the app teams should confirm.
Fri, Nov 16
I had a chat with @phuedx about this yesterday after the Audiences-Platform sync, and he pointed out that there are a couple of projects extant and running in production that already do something very close to this: