Hi all,
Etherpad [0], our real-time colaborative editing tool suffered an
outage due to what we only know for now was database corruption. This
was detected shortly after it happened 14:27 UTC and we (ops in charge
of the service and the database) worked to reestablish the service.
As the service continued crashing despite our efforts, we decided to
recover a database backup from 2016-06-22 01:00:01 UTC. The service is
now back up and working since 16:11 UTC, but that means that you may
have lost a day and a half of edits in the current available etherpad
[0].
I understand that that may cause a lot of inconveniences, specially
for the people at Wikimania. *We are now trying to recover more than
that*, but as the corruption could come back, or not all could be
recovered, and people need the service the plan is the following:
- Keep the current pads as is, not delete or add anything from now.
You can continue using etherpad now as usual.
- If possible, recover the last days of edits on a separate location.
See [1] for progress if you are affected.
Sorry for the inconveniences. Please, more than ever, follow the
recommendation we added at the beginning of every empty pad:
> "Keep in mind as well that there is no guarantee that a pad's contents will always be available. A pad may be corrupted, deleted or similar. Please keep a copy of important data somewhere else as well"
The reason for this is that wiki content has proper HA and redundancy,
etherpad does not.
Again, my most sincere apologies,
[0] <https://etherpad.wikimedia.org/>
[1] <https://phabricator.wikimedia.org/T138516>
--
Jaime Crespo
<http://wikimedia.org>
Hi everyone,
This week, here's the planned agenda for the ArchCom office hour:
ArchCom-RFC office hour 2016W27: 2016-06-29: E226 (E66/42)[1]
- T136866: Improve the per-programming-language listings for our
tools[2]
- Let's figure out how newcomers should identify programming
languages used on the Wikimedia cluster that align with their
interests/skills."What can I work on in language foo" or "I'm
really great with language foo, bar, and baz; anything for me to
help out with?"
- Is the [[mw:Programming_languages]][3] page a good start? Is this
the page we should easier to find? Are there better landing
pages for someone trying to answer the questions above?
The ArchCom status page[4] has these links and other information too
(e.g. last week's decision to deprecate running MediaWiki without
curl)[5]
Rob
[1]: https://phabricator.wikimedia.org/E226
[2]: https://phabricator.wikimedia.org/T136866
[3]: https://www.mediawiki.org/wiki/Programming_languages
[4]: https://www.mediawiki.org/wiki/Architecture_committee/Status
[5]: https://phabricator.wikimedia.org/T137926
Hey,
This is the 11th weekly update from revision scoring team that we have sent
to this mailing list.
*New developments:*
- ORES review tool as a beta feature is enabled in Dutch Wikipedia. More
wikis to come soon this week [1].
- We have basic edit quality model for Czech Wikipedia ready and merged.
To be deployed this week [2].
- We also have basic models for English Wiktionary too. This is the
second non-Wikipedia project we support after Wikidata [3].
- Thanks to Tar Lócesilion, we have Polish edit quality campaign
completed, We are working on building damaging and goodfaith models at the
moment [4].
*Maintenance and robustness:*
- We decreased our web capacity in order to reduce memory pressure on
scb nodes. You should not get any overload error since our capacity is
still very high but if you do, please contact us immediately and we will
bring it back up [5].
- We improved documentation on ores.wikimedia.org page a little bit. To
be deployed this week [6].
We are working on a rather big refactor on ores which will give us
performance boost on scoring multiple models at the same time [7] and
reduce memory usage [8]. Feel free to chime in and give us feedback [9].
1. https://phabricator.wikimedia.org/T139432
2. https://phabricator.wikimedia.org/T138885
3. https://phabricator.wikimedia.org/T138630
4. https://phabricator.wikimedia.org/T130269
5. https://phabricator.wikimedia.org/T139177
6. https://phabricator.wikimedia.org/T138089
7. https://phabricator.wikimedia.org/T134606
8. https://phabricator.wikimedia.org/T139407
9. https://phabricator.wikimedia.org/T139408
Sincerely,
Amir from the Revision Scoring team.
Hi,
the first image scaler based on Debian jessie is now enabled in
production. Despite other changes this also provides an update
of librsvg to 2.40.16 which fixes several long-standing bugs in
SVG rendering:
https://phabricator.wikimedia.org/T44090https://phabricator.wikimedia.org/T64987https://phabricator.wikimedia.org/T97758https://phabricator.wikimedia.org/T111815
(Please note that this currently only applies to one out of eight
systems, I'll send a followup once all scalers are migrated).
This has been tested quite a bit and no problems were found, but if
you notice anything unusual related to image/SVG scaling (e.g. due to
font changes) please drop a note in #wikimedia-operations or file a
Phabricator task and add the Operations project.
Cheers,
Moritz
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2016-06): 240
Active users (any activity) in (2016-06): 836
Task authors in (2016-06): 471
Users who have closed tasks in (2016-06): 252
Projects which had at least one task moved from one column to another on
their workboard in (2016-06): 200
Tasks created in (2016-06): 2478
Tasks closed in (2016-06): 2141
Open and stalled tasks in total: 30439
Median age in days of open tasks by priority:
Unbreak now: 11
Needs Triage: 170
High: 302
Normal: 458
Low: 773
Lowest: 584
(How long tasks have been open, not how long they have had that priority)
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 iridium at Fri Jul 1 00:00:11 UTC 2016)