Hi everybody,
on Thursday Sept 13th (EU morning) I am planning to reboot the stat hosts
(stat1004, stat1005 and stat1006) and the notebook hosts (notebook1003,
notebook1004) for Linux kernel upgrades. Please let me know if this impacts
your work in https://phabricator.wikimedia.org/T203165 or on IRC (elukey -
#wikimedia-analytics).
Thanks!
Luca
Hi everybody,
just wanted to let you know that tomorrow morning EU time I'll stop Hive
and Oozie on analytics1003 (Hadoop Cluster) to allow the host to be
rebooted. I don't plan to kill any job but to wait for their completion.
While the maintenance happens some errors might happen to your jobs. The
reboot should take some minutes to complete if everything goes as planned.
Tracking task: https://phabricator.wikimedia.org/T203165
Please let me know on IRC or in the task if this affects you :)
Luca (on behalf of the Analytics team)
<tl;dr>: Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors and
add your name to the mentors table and start tagging #GCI-2018 tasks.
We'll need MANY mentors and MANY tasks, otherwise we cannot make it.
Google Code-in is an annual contest for 13-17 year old students. It
will take place from Oct23 to Dec13. It's not only about coding:
we also need tasks about design, docs, outreach/research, QA.
Last year, 300 students worked on 760 tasks supported by 51 mentors.
For some achievements from last round, see
https://blog.wikimedia.org/2018/03/20/wikimedia-google-code-in-2017/
While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and fix 2 PHP7 issues from
the list in https://phabricator.wikimedia.org/T120336" style).
We also have more than 400 unassigned open #easy tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Can you mentor some of those tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2018#List_of_Wikimedia_mentors
(If you have mentored before and have a good overview of our
infrastructure: We also need more organization admins! See
https://www.mediawiki.org/wiki/Google_Code-in/Admins )
Thanks (as we cannot run this without your help),
andre
--
Andre Klapper | ak-47(a)gmx.net
https://blogs.gnome.org/aklapper/
Forwarding to Analytics and Research in case this is of interest.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Amir Sarabadani <amir.sarabadani(a)wikimedia.de>
Date: Thu, Sep 6, 2018 at 9:19 PM
Subject: [Wikitech-l] Change tag reading from the new column in the beta
cluster
To: Wikimedia developers <Wikitech-l(a)lists.wikimedia.org>
Hello,
As part of normalizing change tag schema [1] I just switched on reading
from the new column (ct_tag_id in change_tag table, a foreign key to ctd_id
from change_tag_def table) in beta cluster [2] which means new rows will
have empty string as their value of ct_tag. [3]
We are not rushing to flip the switch in production but I just wanted to
send this email asking people who test in beta cluster to file a
phabricator ticket if they see anything unexpected in there that might be
related change tags. This table is being read if someone checks history,
recent changes, watchlist, user contributions, or whole lot of other
special pages plus lots of API queries. I checked anything I could think of
but I might have missed something. Any extra pair of eyes would be
extremely appreciated.
[1]: https://phabricator.wikimedia.org/T185355
[2]: https://phabricator.wikimedia.org/T196671
[3]: For example:
MariaDB [enwiki]> select ct_id, ct_rc_id, ct_rev_id, ct_tag, ct_tag_id from
change_tag order by ct_id desc limit 10;
+--------+----------+-----------+-----------------------+-----------+
| ct_id | ct_rc_id | ct_rev_id | ct_tag | ct_tag_id |
+--------+----------+-----------+-----------------------+-----------+
| 217824 | 633991 | 384018 | | 3 |
| 217823 | 633990 | 384017 | | 3 |
| 217822 | 633989 | 384016 | | 3 |
| 217821 | 633988 | 384015 | | 3 |
| 217820 | 633987 | 384014 | | 3 |
| 217819 | 633986 | 384013 | mw-undo | 2 |
| 217818 | 633985 | 384012 | mw-undo | 2 |
| 217817 | 633984 | 384011 | visualeditor-wikitext | 29 |
| 217816 | 633983 | 384010 | mobile web edit | 16 |
| 217815 | 633983 | 384010 | mobile edit | 15 |
+--------+----------+-----------+-----------------------+-----------+
10 rows in set (0.00 sec)
Thank you!
Best
--
Amir Sarabadani
Software Engineer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi all,
On Wednesday September 5th at around 13:30 UTC we will be taking
stats.wikimedia.org and analytics.wikimedia.org offline for a server
upgrade. We expect this downtime to take about an hour.
You can follow along (and report any issues) at
https://phabricator.wikimedia.org/T192641.
Thanks!
-Andrew Otto
Systems Engineer
Wikimedia Foundation