A blocker for the upcoming Minerva deployment

Once https://phabricator.wikimedia.org/T366197 is merged, we can merge this patch. After this we'll need to QA this change

We will not be merging this ticket this sprint - next steps are to make a patchdemo, review designs, and then implement in sprint 5.

Approved

See https://phabricator.wikimedia.org/T361240 for more info on test set that was generated

This work has been completed. On April 6 we did not have any logs; for april 10 data was corrupted in the first message and this threw off remaining logs; we were able to recover messages following the first

As Daniel's manager I approve of this request!

A quick note about another thing we found when investigating this: to go directly to the view watchlist page you can go to https://en.m.wikivoyage.org/wiki/Special:Watchlist?watchlistview=feed to avoid a redirect. We are still discussing specific next steps but the above should work in any case.

We discussed this just now in task sync, and decided we don't need to take action on this until we address the logged-in user case.

As @SToyofuku-WMF 's manager I approve this request

@Jdrewniak we moved this to your plate to add more logging to catch similar issues in the future

All deploys have gone through at this point, except for donate.wikipedia and thankyou.wikimedia - we will handle these with a separate ticket

(Assigning to @Jdlrobson to verify, please reassign if inaccurate)

Thanks everyone for weighing in here and helping with this, in particular @Peter
for your assistance debugging and @Krinkle for your context.

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

Archiving tasks related to GPT plugin - See summary of the experiment and our findings here: https://commons.wikimedia.org/wiki/File:Wikipedia_ChatGPT_plugin_experiment_summary.pdf

As a few concrete examples of what this might look like:

1. There's probably something happening around this section of tableOfContents.js - scrollToActiveSection does a bunch of calculations which likely function quite differently on mobile. We could use the natively-supported scrollIntoView instead and this may just be enough to fix that particular issue, for instance.

I am closing this ticket, as our original spike as to which specific numbers were elevated has been completed. I created https://phabricator.wikimedia.org/T358380 just now to specifically handle lowering INP for MOBILE users on the DESKTOP site and added it to our upcoming sprint.

We investigated this and have the following findings - responding to the acceptance criteria above:

To clarify, for this request I would also like to create the future-audiences subgroup

Estimated at one point, but we hadn't previously anticipated this work, may need to alter sprint commitments to accommodate (CC'ing @ovasileva for context ) or consider taking this on next week - revisit at Thursday Task Sync on Oct 26

Next steps:

• Add unit testse
• Fix typescript-related build error
• @Mabualruz to review

@Jdlrobson to sync with @Mabualruz further on this re: integration testing of skins - patch and/or followup discussion