There are currently 57 unclaimed projects on
https://wikitech.wikimedia.org/wiki/Cloud_VPS_2018_Purge. I will start
shutting down unclaimed projects at the beginning of next month, and
those projects will be left behind in the future network migration[1]
and, eventually, deleted.
If you see anything in this list that you care about, please indicate
that the project is in use on the Wikitech page. Here are the 57
projects that are currently unmarked:
aicaptcha
bots
bstorm-test
chicotestproject
ci-staging
collection-alt-renderer
contributors
deep-learning-services
discourse-wam
download
etytree
fastcci
glampipe
globaleducation
hat-imagescalers
hound
iiifls1
ircd
jupyter
maps
maps-team
matrix
mcr-dev
mediahandler-tests
mediawiki-docker
multimedia
mw-api-testing
mw-extension-ids
newsletter
nonfreewiki
openocr
orig
pagemigration
piwik
project-smtp
rdfiodev
reading-lists
redirects
reportcard
sentry
services
services-testbed
t136871
test-twemproxy
tor
traffic
wcdo
wdq-mm
wikibrain
wikidata-page-banner
wikidata-primary-sources-tool
wikidumpparse
wikifactmine
wikimetrics
wikisource-tools
wikistream
wlmjudging
[1]
https://phabricator.wikimedia.org/phame/post/view/112/neutron_is_finally_co…
_______________________________________________
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
Thank you very much for your reply and explanation. It's PWB bot actually,
which is based on Python.
And yeah, I should send such mails to the list instead of Bryan. So I'm
CCing the list, so the reply is preserved forever.
Thank you again,
Martin
Dne po 17. zář 2018 22:39 uživatel Bryan Davis <bdavis(a)wikimedia.org>
napsal:
> On Sun, Sep 16, 2018 at 11:50 PM, Martin Urbanec
> <martin.urbanec(a)wikimedia.cz> wrote:
> > Hi, STDOUT/STDERR from jobs is being added to jobname.{out,err} files
> when
> > the job is ended. Is it possible to monitor the output while the job is
> > running?
>
> I believe that the logging of stdout and stderr is actually continuous
> from the point of view of Grid Engine, but there are a couple of
> things that may make it seem to be batched from the point of view of
> you observing the files:
>
> * NFS server write aggregation and NFS client inode status updates
> cause a several seconds to several minutes delay in a write by Grid
> Engine to a log file being visible from a Toolforge bastion where you
> are trying to read it.
>
> * Your application may actually be adding additional buffering of
> writes to stdout/stderr that are not flushed through to Grid Engine to
> send on to the NFS hosted log files until program completion (or the
> buffer filling up). One common place that I have personally seen this
> is with Python scripts. See
> https://stackoverflow.com/questions/107705/disable-output-buffering
> for some ideas on how to work around this if it is a problem for you.
> If you do have a python script that does a lot of stdout/stderr output
> completely disabling write buffering may have negative impacts on
> shared NFS server performance. Finding a way to line buffer (hang on
> to writes until you see a newline) will probably be much less
> impactful on our limited shared resources than trying to write each
> byte independently.
>
> Direct inspection of the raw stdout/stderr streams of a process
> running under Grid Engine's control is technically possible, but would
> require root permissions typically. You would have to know what exec
> host the job is running on, ssh to that host, and then use `strace` or
> a similar debugging tool to inspect the stream. This is not something
> that a normal Toolforge user can accomplish themselves.
>
> Questions like this make great topics for the
> cloud(a)lists.wikimedia.org mailing list. You can get help there not
> just from me, but also from the larger Toolforge user community. It
> also makes the responses easier for others to find when they have
> similar issues.
>
> Bryan
> --
> Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
> [[m:User:BDavis_(WMF)]] Manager, Technical Engagement Boise, ID USA
> irc: bd808 v:415.839.6885 x6855
>
At 6pm UTC, we will be briefly resetting the main NFS server for tools and projects to upgrade the tooling around NFS there. This should cause a brief climb in processes waiting for IO and then that will settle out.
If things don’t operate as expected, rolling back the change could take a few minutes, but that seems unlikely. Please let us know if there are prolonged issues in the #wikipedia-cloud channel.
Brooke Storm
Operations Engineer
Wikimedia Cloud Services
bstorm(a)wikimedia.org
IRC: bstorm_
_______________________________________________
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
Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, German & Persian.
The Technical Advice IRC Meeting is a weekly support event for volunteer
developers. Every Wednesday, two full-time developers are available to help
you with all your questions about Mediawiki, gadgets, tools and more! 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 the Technical Advice IRC Meeting crew)
--
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.
All,
As you may have read about in other venues, the Wikimedia Foundation will
be conducting a switchover of datacenters on September 11 and 12, with the
switch back to occur on October 10 and 11. During the switchover and
switch-back events, the wikis will be in read-only mode.
Cloud VPS and Toolforge are not affected by these switchovers. However, if
you run bots or scripts that make edits to the wikis, they may be unable to
make edits during this time. This should appear to your bots as the
standard read-only mode which occurs unplanned on the production wikis from
time to time.
Please let me know if you have any questions.
----
James Hare
Associate Product Manager
Wikimedia Foundation
https://wikimediafoundation.org
_______________________________________________
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
<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/
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **Wednesday at 3-4 pm UTC AND
11-12 pm UTC** on #wikimedia-tech.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! 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 the Technical Advice IRC Meeting crew)
--
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.