FYI: the PHP RFC to deprecate dynamic property assignment is now in
the voting stage. If this RFC is accepted, dynamic property assignment
will raise E_DEPRECATED in PHP 8.2 unless the
#[AllowDynamicProperties] attribute is set on the class.
I'm voting no on this, on account of the amount of migration work I
think it will create for us.
https://wiki.php.net/rfc/deprecate_dynamic_properties
-- Tim Starling
Hello,
One of the CI Jenkins jobs running for MediaWiki repositories had a
faulty npm cache being restored. That caused some dependencies to not be
properly installed and lead to a faulty build.
The issue apparently started yesterday Nov 8th around 17:30 UTC and
should be now resolved as of 8:30 UTC after I have deleted the faulty cache.
The affected job is quibble-vendor-mysql-php72-selenium-docker which
runs the Selenium browser test. If a change made to an extension or skin
fails mysteriously, please try rechecking the CI change by commenting
`recheck` on the change or using:
recheck due to npm cache corruption - T295341
It has hit us a few times in the recent time:
* https://phabricator.wikimedia.org/T294426
* https://phabricator.wikimedia.org/T293937
* https://phabricator.wikimedia.org/T295341
I have filed a generic task to further investigate the issue:
* https://phabricator.wikimedia.org/T295351
--
Antoine "hashar" Musso
Hi all,
The 1.38.0-wmf.7 train is currently deployed to all wikis albeit in a
regressive state due to UBN T295187.[1][2]
From the UBN summary: "Since yesterday, multiple users have reported
that Chinese conversion no longer functions in ToC on Chinese
Wikipedia."
A rollback to 1.38.0-wmf.6 was performed, initially to group1 before
rolling back from all wikis, before a further report that the parser
cache had already been polluted in a backwards incompatible way
causing the TOC to completely disappear from many wikis. All wikis
were again rolled forward to 1.38.0-wmf.7 to avoid the broader of the
two regressions.[2]
The train is not blocked, but cannot be safely rolled back either to
fix UBN T295187.[2] Some fine folks are already helping to resolve
this issue before the weekend, but any further assistance is
appreciated as always.
To keep up with the most current status please watch the train blocker
task in Phabricator.[1]
--
- 💕🚂🌈 - Your loving train conductor.
[1] https://train-blockers.toolforge.org/
[2] https://phabricator.wikimedia.org/T295187
How’d we do in our strive for operational excellence last month? Read on to find out!
Incidents
There were 4 documented incidents last month. This is currently on average, compared to the past five years (per Incident graphs <https://codepen.io/Krinkle/full/wbYMZK>).
2021-10-08 network provider <https://wikitech.wikimedia.org/wiki/Incident_documentation/2021-10-08_netwo…>; Impact: For upto an hour, some regions experienced a partial connectivity outage. This primarily affected the US East Coast for 13 minutes, and Russia for 1 hour. It was caused by a routing problem with one among several network providers.
2021-10-22 eqiad networking <https://wikitech.wikimedia.org/wiki/Incident_documentation/2021-10-22_eqiad…>; Impact: For 40 minutes clients that are normally geographically routed to Eqiad experienced connection or timeout errors. We lost about 7K req/s during this time. After initial recovery, Eqiad was ready and repooled in 10 minutes.
2021-10-25 s3 db replica <https://wikitech.wikimedia.org/wiki/Incident_documentation/2021-10-25_s3_db…>; Impact: For 30min MediaWiki backends were slower than usual. For 12 hours, many wiki replicas were stale for Wikimedia Cloud Services such as Toolforge.
2021-10-29 graphite <https://wikitech.wikimedia.org/wiki/Incident_documentation/2021-10-29_graph…>; Impact: During a server upgrade, historical data was lost for a subset of Graphite metrics. Some were recovered via the redundant server, but others were lost as the redundant was also upgraded since then and lost some in a similar fashion.
Remember to review and schedule Incident Follow-up work <https://phabricator.wikimedia.org/project/view/4758/> in Phabricator, which are preventive measures and tech debt mitigations written down after an incident is concluded. Read about past incidents at Incident status <https://wikitech.wikimedia.org/wiki/Incident_status> on Wikitech.
Trends
**Norwegian blue** 🐦
*298 bugs were up on the board.
We solved 20 of those over the past thirty days.*
*How many might now be left unexplored?
We also added new bugs to our database.*
*Half those bugs are pining for their fjord.
The other 23 carry on, with their dossiers.*
*All in all, 301 bugs up on the board.*
In October, 49 new tasks <https://phabricator.wikimedia.org/maniphest/query/3A8rqYpefUFF/#R> were reported as production errors. Of these, we resolved 26, and 23 remain unresolved and carry forward to the next month.
Previously, the production error workboard held an accumulated total of 298 still-open error reports. We resolved 20 of those. Together with the 23 new errors carried over from October, this brings us to 301 unresolved errors on the board.
Figure 1: Unresolved error reports by month. <https://phabricator.wikimedia.org/phame/post/view/260/production_excellence…>
For the month-over-month numbers, refer to the spreadsheet data <https://docs.google.com/spreadsheets/d/e/2PACX-1vTrUCAI10hIroYDU-i5_8s7pony…>.
Outstanding errors
Take a look at the workboard and look for tasks that could use your help:
View Workboard <https://phabricator.wikimedia.org/tag/wikimedia-production-error/>
Issues carried over from recent months:
Apr 2021:
9 of 42 issues left.
May 2021:
16 of 54 issues left.
Jun 2021:
9 of 26 issues left.
Jul 2021:
12 of 31 issues left.
Aug 2021:
12 of 46 issues left.
Sep 2021:
11 of 24 issues left.
Oct 2021:
23 of 49 new issues <https://phabricator.wikimedia.org/maniphest/query/3A8rqYpefUFF/#R> are carried forward.
Thanks
Thank you to everyone who helped by reporting, investigating, or resolving problems in Wikimedia production. Thanks!
Until next time,
– Timo Tijhof
🔗 Share or read later via https://phabricator.wikimedia.org/phame/post/view/260/
This email is a summary of the Wikimedia production deployment of
1.38.0-wmf.6
- Conductor: Mukunda Modell
- Backup Conductor: Antoine "hashar" Musso
- Blocker Task: T293947 <https://phabricator.wikimedia.org/T293947>
- Current Status <https://versions.toolforge.org>
🔢 Numbers
Current Stats + Sparklines comparing the relative stats for the last 5
trains.
- 284 Patches █▁▂█▃
- 1 Rollbacks ▃█▁▁▃
- 1 Days of delay ▁█▁▁▃
- 3 Blockers █▇█▁▁
🥰 Trainbow Love 🌈 Thanks to folks who reported or resolved blockers,
including:
- Taavi Väänänen
- Samuel
- Zabe
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2021-10): 311
Active Maniphest users (any activity) in (2021-10): 995
Task authors in (2021-10): 524
Users who have closed tasks in (2021-10): 286
Projects which had at least one task moved from one column to another on
their workboard in (2021-10): 298
Tasks created in (2021-10): 2442
Tasks closed in (2021-10): 2047
Open and stalled tasks in total: 48692
* Only open tasks in total: 47793
* Only stalled tasks in total: 899
Median age in days of open tasks by priority:
Unbreak now: 2
Needs Triage: 717
High: 937
Normal: 1544
Low: 2161
Lowest: 2227
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2021-10): 9
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1001 at Mon 01 Nov 2021 12:00:23 AM UTC)