The 1.35.0-wmf.2 version of MediaWiki is blocked[0].
The new version is deployed to group(s) 0 & 1[1], but can proceed no
further until these issues are resolved:
* Some revisions' contents are incorrect in the cache - wrong contents
shown in history & diffs - https://phabricator.wikimedia.org/T235188
Once these issues are resolved train can resume. If these issues are
resolved on a Friday the train will resume Monday.
Thank you for your help resolving these issues!
-- Your humble train toiler
[0]. <https://phabricator.wikimedia.org/T233850>
[1]. <https://tools.wmflabs.org/versions/>
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation
Hi,
for HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-10-16
Željko
--
= 2019-10-16 =
== Callouts ==
* Language team ->Core(?): Blocked on [[phab:T235188#5574342]]
* SRE DBAs
** requested read-only time for enwiki 14th Nov to switchover the primary
database master - [[phab:T234801]], already done
** s6 primary master switchover (read-only required) 19th Nov 05:00 AM UTC
* DBAs, Performance: Heads up that PI will be pinging for reviews/review
updates for the MachineVision extension later this week, as soon as the
code settles a bit (DBA review: [[phab:T227355]], Perf review:
[[phab:T230813]] )
== Product ==
=== Editing ===
* Updates:
** Catch errors during document initialization
** Enforce that some files must not use the `ve` global (task
[[phab:T228684]])
** Parse relative hrefs on image nodes like on regular links (task
[[phab:T193253]])
** Fix Vector wikitext surface padding overrides when using custom browser
font-size (task [[phab:T222217]])
=== Growth ===
* Updates:
** Initial structure for Suggested Edits module
** Do not align the bottom of the homepage columns (task [[phab:T232420]])
** StartEditing: Remove special message for add-change response (task
[[phab:T232419]])
=== iOS native app ===
* Updates:
** 6.5 in active development - [[phab:project/view/4245]]
***bug fixes
*** History & diffs feature
**** Core Platform working on Rest APIs for this
=== Android native app ===
* Updates:
** Working actively towards completion of Suggested edits V3
** Working with the PI team to update backend support for the same.
=== Product Infrastructure ===
* Updates:
** MachineVision extension work in progress, still aiming to deploy to prod
by end of month
** Still working to resolve [[phab:T229286]] ("'worker died, restarting'
mobileapps issue")
=== Structured Data ===
* Blocked by:
** Wikidata/WMDE: [[phab:T229280]] following up on [[gerrit:534536]]
** Wikidata/WMDE: [[phab:T223792]]
* Blocking:
** Search: RecentChange support for SDC: [[phab:T230862]] (actually the
higher level task on which we are blocked: [[phab:T221917]])
* Updates:
** Machine Vision, bugfixing/tidy up on WikibaseMediaInfo
=== Parsing ===
* Updates:
** Fixing bugs in Parsoid/PHP based on HTML string compasion between
Parsoid/JS & Parsoid/PHP. ~1% pages still have diffs that need
investigation / bug fixing.
** Will sync with Services (CPT) and SRE to finalize deployment plans for
initial deployment (no live client traffic) to identify any last lingering
Parsoid crashers OR performance problems in a production context.
=== Language ===
* Blocked by:
** Language->Core(?) Blocked on [[phab:T235188#5574342]]
* Updates:
** CX going out of beta in some Wikipedias next week.
=== UI Standardization ===
* Updates:
** OOUI v0.35.0 and 0.35.1 with one small revert released eo last week,
latter already on this week's train
** Design Style Guide:
*** Progressing “Components“ section
*** Change to Git lfs for large binary files. If you've cloned the dir,
throw away your current clone, re-clone it.
https://github.com/wikimedia/WikimediaUI-Style-Guide In your repo directory
type `git lfs pull`. If the lfs app is not installed follow
https://github.com/git-lfs/git-lfs/wiki/Installation
== Technology ==
=== Analytics ===
* Blocking:
** Search: [[phab:T229882]]
=== Fundraising Tech ===
* Updates:
** Refining annual summary receipt for recurring donors: [[phab:T195907]]
** Restoring data lost during manual merges: [[phab:T232636]]
** Looking into reconciliation file discrepancies from S. Amer / India
processor: [[phab:T235212]]
** Might need to add more params to CentralNotice banner hide cookies:
[[phab:T235204]]
** Refining treatment of opt in and opt out data: [[phab:T234925]]
** Looking into errors on Amazon Pay donation form: [[phab:T234538]]
== Core Platform ==
* Blocked by:
** SRE [[phab:T235478]]
* Blocking:
** Wikidata/WMDE: In the Data Bridge work (editing Wikidata items from
Wikipedia) we have encountered problems with Special:EntityData serving
stale (old) data. The problem is quite old: [[phab:T128486]]. We are
looking for a team/person with whom we could get some clarity on the
current state of the cache solutions on WMF cluster, and figure out how to
get [[phab:T128486]] unstuck.
** Scoring: Review of Jade API [[phab:T199834]] (Can we get a high level
review in the short term? We want to build on this but not dig a hole.)
** Language->Core(?) Blocked on [[phab:T235188#5574342]]
* Updates:
** history API done
** working on stretch goals
** echo notification storage
=== Engineering Productivity ===
==== Performance ====
* Blocked by:
** SRE
*** PHP7 fatal-error reports missing from type:mediawiki in Logstash. –
[[phab:T234283]]
*** mwdebug1002 might need to be reprovisioned, failing to report messages
to Logstash. – [[phab:T214734]]
==== Release Engineering ====
* Updates:
** v3 of CI arch document for new CI wants review and feedback
[[User:LarsWirzenius/NewCI]]
** Train Health
*** Last week: 1.35.0-wmf.1 - [[phab:T233849]]
*** This week: 1.35.0-wmf.2 - [[phab:T233850]]
*** Next week: 1.35.0-wmf.3 - [[phab:T233851]]
=== Scoring Platform ===
* Blocked by:
** CPT: Review of Jade API [[phab:T199834]]
* Updates:
** Cleanup for Jade API components and working through review
[[phab:T199834]]
*** Naming conflicts [[phab:T235003]]
*** Central Auth (Found CentralAuth.lookup()!)
** Jade
*** Continuing iterations on Jade designs (based on Design Review feedback)
[[phab:T212370]]
*** Reached out to Front-End Arch. WG. for recommendations for Jade UI.
We got a response from Mark Holmquist and will be going to Eric Gardner for
specific advice and reviewing SDC code (WikibaseMediaInfo)
** Completed second major review of Revscoring refactoring for Session
orientation [[phab:T231214]]
** Firmed up cross-team deliverables for Topic Modeling work.
[[phab:T235181]]
** Merged new features for Basque Language [[phab:T223788]]
** ORES celery workers struggling in Cloud VPS. Still looking into it.
[[phab:T234926]]
=== Search Platform ===
* Blocked by:
** Structured Data: RecentChange support for SDC: [[phab:T230862]]
(actually the higher level task on which we are blocked: [[phab:T221917]])
** Analytics: [[phab:T229882]]
* Updates:
** Error when searching for exact phrase on English Wikipedia:
"Precondition failed: Must have a resultset set": [[phab:T234445]]
** Deploy A/B Test for Glent Method 0 [[phab:T233211]]
** Optimize the Sanitizer to produce a single job if all elasticsearch
clusters are to be updated: [[phab:T233587]]
=== Security ===
* Updates:
* In Progress:
** GRC Tool Eval
** MachineVision extension review
** FileImporter extension review
** Data Map update submission review
=== Site Reliability Engineering ===
* Blocking:
** Performance
*** PHP7 fatal-error reports missing from type:mediawiki in Logstash. –
[[phab:T234283]]
*** mwdebug1002 might need to be reprovisioned, failing to report messages
to Logstash. – [[phab:T214734]]
** Core Platform SRE [[phab:T235478]]
* Updates:
** Started working on new goals
** Helping CPT get restrouter rate limiting working, deploying echostore
== Wikimedia DE ==
=== Wikidata ===
* Blocked by:
** Not sure who, Core Platform? Mentioned 2 weeks ago already with no
result: : In the Data Bridge work (editing Wikidata items from Wikipedia)
we have encountered problems with Special:EntityData serving stale (old)
data. The problem is quite old: [[phab:T128486]]. We are looking for a
team/person with whom we could get some clarity on the current state of the
cache solutions on WMF cluster, and figure out how to get [[phab:T128486]]
unstuck.
* Blocking:
** Structured Data: [[phab:T229280]] following up on [[gerrit:534536]]
coming up this week
** Structured Data: [[phab:T223792]] - also expect to unblock this week
Hello,
We have requested a 30 minutes read-only window for s5 wikis (T234303) for
the 15th October from 05:00-05:30 AM UTC to switchover that section primary
database master (T234300)
db1070 is an old host and out of warranty that will be decommissioned
(T217396). The new master will be db1100.
We are going to do this on Tuesday 15th Oct from 05:00 to 05:30 AM UTC (we
do not expect to use the 30 minutes window, if everything goes as expected).
Impact: Writes will be blocked on the following wikis
cebwiki
dewiki
enwikivoyage
mgwiktionary
shwiki
srwiki
Reads will remain unaffected.
Communication will happen at #wikimedia-operations
If you are around at that time and want to help with the monitoring, please
join us!
Thanks
Hello, everyone!
My name is Ilana, and I'm the product manager for the Community Tech team.
We’re excited to share an update on the Community Tech 2020 Wishlist Survey
<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020>. This will
be our fifth annual Community Wishlist Survey, and for this year, we’ve
decided to take a different approach. In the past, we've invited people to
write proposals for any features or fixes that they'd like to see, and the
Community Tech team has addressed the top ten wishes with the most support
votes. This year, we're just going to focus on the *non-Wikipedia content
projects* (i.e. Wikibooks, Wiktionary, Wikiquote, Commons, Wikisource,
Wikiversity, Wikispecies, Wikidata, Wikivoyage, and Wikinews), and we're
only going to address the top five wishes from this survey. This is a big
departure from the typical process. In the following year (2021), we’ll
probably return to the traditional structure.
So, why this change? We’ve been following the same format for years — and,
generally, it has lots of benefits. We build great tools, provide useful
improvements, and have an impact on diverse communities. However, the
nature of the format tends to prioritize the largest project (Wikipedia).
This makes it harder to serve smaller projects, and many of their wishes
never make it onto the wishlist. As a community-focused team, we want to
support *all* projects. Thus, for 2020, we want to shine a light on
non-Wikipedia projects.
Furthermore, we’ll be accepting five wishes. Over the years, we’ve taken on
larger wishes (like Global Preferences
<https://meta.wikimedia.org/wiki/Community_Tech/Global_preferences> or Who
Wrote That
<https://meta.wikimedia.org/wiki/Community_Tech/Who_Wrote_That_tool>),
which are awesome projects. At the same time, they tend to be lengthy
endeavors, requiring extra time for research and development. When we
looked at the 2019 wishlist, there were still many unresolved wishes.
Meanwhile, we wanted to make room for the new 2020 wishes. For this reason,
we’ve decided to take on a shortened list, so we can address as many wishes
(new and remaining 2019 wishes
<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Results>)
as possible.
Overall, we look forward to this year’s survey. We worked with lots of
folks (engineering, product management, and others) to think about how we
could support underserved projects, all while preserving the dynamic and
open nature of the wishlist. *Please let us know your thoughts
<https://meta.wikimedia.org/wiki/Talk:Community_Wishlist_Survey_2020>* related
to this change. In addition, we’ll begin thinking about the guidelines for
this new process, so *we want your feedback
<https://meta.wikimedia.org/wiki/Talk:Community_Wishlist_Survey_2020>* (on
what sorts of processes/rules we may want to consider). Thank you, and
we’re very curious to see the wishes in November!
Thanks,
Ilana Fried
Product Manager, Community Tech
<https://meta.wikimedia.org/wiki/Community_Tech>
Hello,
I'm being logged out from gerrit basically every other day, I'm pretty sure
I use "Remember me" and because my passwords are secure, It's cumbersome to
login (not that much but it piles up the frustration).
Is it just me? My colleagues and some other people I personally know have
this issue too but I'm not sure if it's universal.
Best
--
Amir (he/him)