Since all the subtasks are resolved, can this be resolved?

If the code for QuickSurveys loads AFTER MobileFrontend, the hook will be registered too late and the survey will never show.

The task that led to the introduction of the mobile.betaoptin event: T111188

• Data for clicks to all new links can be collected using https://meta.wikimedia.org/wiki/Schema:MobileWebMainMenuClickTracking

@Jdlrobson: Would changing the message require that any existing workflows are updated or would folk still have to refer to the tag by its name when querying the DB or specifying it as an argument for the tagfilter parameter in an MW API call, for example? That is, would the tag look like it was called "mobile web action" but still actually be called "mobile web edit"?

As for on-wiki uses by the general public:

Would replacing the textarea with a div if the page is protected work? This would be cleaner than manipulating the DOM in JS IMO.

In T217526#5024391, @Jhernandez wrote:

@ovasileva This is probably a bug on mobile web too?

This appears to have been fixed in https://en.wikipedia.org/w/index.php?title=Calculus&type=revision&diff=887407355&oldid=886050145, which is the fix that @Tacsipacsi proposed in T217526#5012719.

@mforns: I'm pretty sure this is deployed and (re)started as there are log lines appearing in Kibana for the following query: https://logstash.wikimedia.org/goto/36329f5fd2348e181177ff879800d9c0

In T217142#4997724, @Ottomata wrote:

Unless we have a generic schema for client error logs! :) Might not be a bad idea.

CC @LarsWirzenius per https://lists.wikimedia.org/pipermail/engineering/2019-February/000689.html :)

Also CCing @dr0ptp4kt

CC @Jhernandez, @Tgr, @faidon, @fgiunchedi, @herron for visibility. My apologies in advance for the description churn, y'all.

1. Nice find, @Jdlrobson!
2. Should we discard surveys that required CentralNotice to be loaded if it isn't?

@Tbayer pointed me at this task during our 1:1 yesterday.

@nray: See @Krinkle's detailed explanation here: T208980#4792762

@ovasileva: This is in Triaged but Future in our backlog but doesn't appear to have a priority.

Following @Tbayer's advice, I did a little digging in wmf.webrequest:

In T216063#4953716, @phuedx wrote:

AFAICT the function that should be decoding and parsing the QSON (Querystring-encoded JSON) string is expecting that character to not be encoded but it is (it's the %3B at the end of the raw event).

The "Extra data:" error is raised by json.loads as it encounters the ; character at the end of the JSON string:

@Edtadros and I worked through testing the 4th 5th acceptance criterion together during our 1:1 today.

In T215477#4949367, @Jdlrobson wrote:

I guess such a generic hook for log events would need to run inside $logEntry->insert()?

In T210652#4948279, @phuedx wrote:

@ovasileva: Could you update https://phabricator.wikimedia.org/project/profile/2960/ accordingly?

I've removed this from our (Readers Web's) kanban board as Proton has been handed over to Readers Infrastructure.

In T214444#4946376, @Edtadros wrote:

1. Are you expecting an HTTP 204 status in the last QA step for the requests that appear after filtering?

@ovasileva: Could you update https://phabricator.wikimedia.org/project/profile/2960/ accordingly?

Per our (@Jhernandez, @Tgr, @pmiazga, and me) conversation in last Thursday's Audiences Platform Sync, Proton has officially been handed over to Readers Infrastructure for ongoing maintenance. I'll follow up with an email to readers-web-team@wikimedia.org and ri-team@wikimedia.org to confirm this.

Drop proton-staging as it is not used (chromium-pdf.reading-web-staging.eqiad.wmflabs) - can be done after the handoff

@Capt_Swing: Thanks for the additional detail. Given that, I think it's reasonable to keep both tasks separate.

In T63737#4944679, @Jdlrobson wrote:

@alexhollender the click to cancel functionality is now live on beta cluster and ready for this weeks train.

To minimize the traffic sent to the stats endpoint we should track MinervaClientError counter only once after the request is done, not on every error occurrence.

@Joe: Yes. That's correct. Do note that this is the current behaviour for the beta mode of the mobile site (visit https://m.mediawiki.org/wiki/Special:MobileOptions and enable "MediaWiki ß"). I think it's worth wondering how caching best works for both that and this new opt-in feature.

Thanks for hashing this out, y'all. FWIW I think the proposed interim solution seems reasonable.

@Joe: Here's the task I promised to create during the Readers Web/Readers Infra/Services/SRE interlock meeting on Wednesday, 23rd January /cc @ggellerman

FeaturesManager::isFeatureAvailableInContext will need to be updated to take a User object and check the stored value of AMC. This is needed for the talk tab task (T212216).

☝️ I pulled out the very technical AC from the AC section and into the Developer notes section as:

I apologise for not including an approver on the task. I wasn't actually sure who should approve access in this case but realise now that @Nuria would've been the sensible choice.

Thanks!

In T198218#4322957, @Tbayer wrote:

Here is the same limited to desktop, but for five months (January-May) instead of one. It confirms that the high number for RecentChangesLinked above wasn't an outlier - it got 13x as much traffic as RecentChanges, which I would have expected to be much more relevant and useful.

_c0 views
https://en.wikipedia.org/wiki/wiki.phtml 61495

What's the rationale for this skipping Needs QA (the first time it moved to Ready for Signoff, I guess)?

In T214444#4905420, @phuedx wrote:

This should only involve changing https://github.com/wikimedia/mediawiki-extensions-WikimediaEvents/blob/db66eac96fb29beffd89cc40edda1aae99eaee0e/modules/all/ext.wikimediaEvents.readingDepth.js#L21 from dependencies = [ 'schema.' + SCHEMA_NAME ], to dependencies = [],.

AFAICT there's no instrumentation about how (or how frequently) our various overlays are being interacted with. Nevertheless, it's a production feature, so we should do our best to make sure that we don't introduce regressions while doing this refactoring. With that in mind, could we add tests so that this can go through Needs QA.

I'll add a note as to why my proposed change should work and testing instructions for reviewing engineers and @Edtadros.

In T214724#4928097, @Niedzielski wrote:

There is also a main page stylesheet.

Is there any chance that you did get time to look at this during All Hands, @hashar? I know it was very busy.