Is there a way to change my preferred shell on the Clouds to zsh? When I
try chsh -s `which zsh` it asks for a password, which I don't have of
course.
Thanks,
Huji
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
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/681/51985.
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **today, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki.org/
wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
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/681/51985.
I just can’t figure this out. Whenever I try to set the my.cnf in my personal DB instance to increase max connection and reduce max idle timeouts, they won’t appear when the DB is restarted. I always have to set them directly in the DB CLI. Can somebody explain to me what I’m doing wrong? I was meaning to address this sooner but seeing as how the instance was never in need of a reboot until Andrew did made forget to address this issue.
Cyberpower678
English Wikipedia Account Creation Team
English Wikipedia Administrator
Global User Renamer
At the Dev Summit, Birgit Müller and I will run a session on Growing the
MediaWiki Technical Community. If you're attending, we hope you will
consider joining us.
Everyone (attending the Dev Summit or not) is welcome and encouraged to
participate at https://phabricator.wikimedia.org/T183318 (please comment
there, rather than by email).
We are discussing the following questions:
* What would allow you to develop and plan your software more efficiently?
* What would make software development more fun for you?
* What other Open Source communities do we share interests with?
* How can we change our processes to take technical debt more seriously?
"Develop" means any kind of work on a software system, including design,
documentation, etc.
Our topics are:
* Better processes and project management practices, integrating all
developers and allowing them to work more efficiently
* Building partnerships with other Open Source communities on shared
interests (e.g. translation, audio, video)
* Reducing technical debt
Matt Flaschen
I usually use bash or python scrips to query data from multiple wikis at
once, but I wanted something "simple" in Quarry such as a list of users
who are active in two wikis, and I felt very stupid.
I ended up using two separate queries, a subquery and a mix of
GROUP_CONCAT, TO_BASE64 and SET SESSION group_concat_max_len (to make a
sort of temporary table in a pseudo-array string):
https://quarry.wmflabs.org/query/23956
This was reasonably fast, but is there a better way?
Federico
We have completed all of the updates and reboots for the hypervisors and
instances in https://phabricator.wikimedia.org/T184910, but there are more
maintenance events that are less invasive to come. This is being tracked
in https://phabricator.wikimedia.org/T184910
Most of this will be handled gracefully without user impact, but not all of
it.
We will reboot the `dumps` NFS server that also provides the `maps` and
`scratch` NFS shares tomorrow (1/18/2018). Note the reason this is an
outage event is that this server is a single point of failure. Efforts to
improve this are happening in https://phabricator.wikimedia.org/T168486.
More announcements will come for maintenance that is impactful.
--
Chase Pettet
chasemp on phabricator <https://phabricator.wikimedia.org/p/chasemp/> and
IRC
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Sometime soon (probably in the next day or two) we will be applying
kernel patches to all VMs and physical hosts in WMCS. This is to address
an urgent security issue[1] , so we'll be skipping the traditional 7-day
warning period -- basically as soon as proper fixes are available we'll
start patching and rebooting.
As usual, we'll do our best to re-balance Toolforge grid nodes, so
impact on Toolforge users should be minimal (worst case you may need to
manually restart interrupted tasks).
For other users: if your VPS project requires special handling or
specific notice about when a particular VM will reboot, please add a
subtask describing your need to https://phabricator.wikimedia.org/T184189 .
[1] https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
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/681/51985.
I have just merged the "stretch-migration" feature branch to master
for MediaWiki-Vagrant.
Major changes:
* Debian Stretch (Debian 9) base image
* Default PHP runtime is Zend PHP 7.0 (HHVM available via role)
* Database is MariaDB 10.1
* Puppet 4
Once you update your local MediaWiki-Vagrant clone to 59e3b49c or
later you will need to create a new VM based on the Debian Stretch
base image in order to use `vagrant provision`. Upgrading your local
VM may be as easy as using `vagrant destroy` to delete the current VM
followed by `vagrant up` to make a new one. Note that this will *not*
save the contents of any local wikis in the VM. You will need to
manually backup and restore the databases or export and import pages
you have created.
See <https://phabricator.wikimedia.org/T181353> for more information
and a few known open bugs.
I have also created a jessie-compat branch that can by used by users
who are not ready to destroy their current Jessie based virtual
machines and start over with Stretch. A simple `git checkout -b
jessie-compat` should be all that is needed to switch your local
MediaWiki-Vagrant clone to the new compatibility branch. This branch
will probably receive few updates, so you are encouraged to create new
Stretch based VMs soon.
Bryan
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Cloud Services Boise, ID USA
irc: bd808 v:415.839.6885 x6855