help us fix (or convince us not to care about):
* No atomic section is open (got LocalFile::lockingTransaction)
We've been on 1.36.0-wmf.27 for two weeks which is 1,038 changes behind
1.36.0-wmf.30 (the latest branch).
The remaining issue is: "No atomic section is open (got
We're not sure about the impact of this log message. Holding the train is
our most effective tool to ensure that the log messages that we see don't
We need to solve this by Monday or we will remain on wmf.27 for another
Any help you can provide is sincerely appreciated. Any feedback on how to
communicate about log messages more clearly so they get the attention they
need in a timely manner is also appreciated!
On Monday 02/15 I will start upgrading Quibble on the CI jobs to version
0.0.46. The notable changes for CI are:
* Run phpunit-unit stage before MediaWiki installation.
T266441 Kosta Harlan
* Fix regression which made us run linters for repositories besides
MediaWiki extensions or skins (eg: mediawiki/services/parsoid).
T263500 Antoine Musso
* Mute zuul.CloneMapper logging when running browser tests.
It opens the way to use Apache instead of the php built-in webserver.
That would make the Selenium tests slightly faster, but we have to add
Apache to the images, that will be done later.
The full changelog is:
The task tracking the upgrade is:
(feel free to forward the message as is to your friends, family members &
We would like to invite you to apply to the Outreachy and Google Summer of
Code program with the Wikimedia Foundation (a non-profit organization
About the Outreachy program
Wikimedia will be mentoring ~3 projects in the Outreachy program in the May
to August 2021 round. The initial applications are due February 22nd at 4
Apply today: https://www.outreachy.org/apply/ 
Outreachy offers three-month internships to work remotely in Free and Open
Source Software (FOSS) projects with experienced mentors. The internships
may include programming, user experience, documentation, illustration, and
graphic design, or data science.
Outreachy internships run twice a year – from May to August and December to
March. Interns are paid a stipend of $5,500 USD for the three months of
work. They also have a $500 USD stipend to travel to conferences and
events. Interns often find employment after their internship with Outreachy
sponsors or in jobs that use the skills they learned during their
Outreachy is open to both students and non-students. Outreachy expressly
invites the following people to apply:
- Women (both cis and trans), trans men, and genderqueer people.
- Anyone who faces under-representation, systematic bias, or
discrimination in the technology industry in their country of residence is
invited to apply.
- Residents and nationals of the United States of any gender who are
Black/African American, Hispanic/Latin@, Native American/American
Indian, Alaska Native, Native Hawaiian, or Pacific Islander.
About the Google Summer of Code program
Wikimedia is planning to mentor 8-10 projects in 2021’s Google Summer of
Code (GSoC) program. Beginning March 9th, pending Wikimedia’s acceptance as
a mentoring organization, applicants can begin discussing ideas with the
The student application will be due on April 13, 2021:
Google Summer of Code, now in its 17th year, is Google's summer program for
candidates participating in any academic programs who want to get involved
in open-source software. Over 6,626 students from 121 countries have
already participated in the last year’s round i.e 2020 <
. Google Summer of Code is a unique program that pairs students with
mentors who introduce them to the open-source community and provide
guidance while they work on real-world open-source projects during their
summer break from university.
This year there are some new breaking changes in the GSoC program,
- Smaller project size ~175 hr project (previously 350 hr)
- Shortened coding period ~10 weeks long (previously 3 months)
- Eligibility criteria redefined; the program is now open to candidates
participating in a variety of academic programs (previously accredited
university programs only)
Projects cover a wide range of fields including Cloud, Operating Systems,
Graphics, Medicine, Programming Languages, Robotics, Science, Security and
many more. It's a highly competitive program (and this year is expected to
be even bigger than last year), so don't wait until the last minute to
About the Wikimedia Foundation
The Wikimedia Foundation is the nonprofit organization that hosts and
operates Wikipedia and the other Wikimedia free knowledge projects. Our
vision is a world in which every single human can freely share in the sum
of all knowledge. We believe that everyone has the potential to contribute
something to our shared knowledge and that everyone should be able to
access that knowledge, free of interference. We host the Wikimedia
projects, build software experiences for reading, contributing, and sharing
Wikimedia content, support the volunteer communities and partners who make
Wikimedia possible, and advocate for policies that enable Wikimedia and
free knowledge to thrive.
* Browse through the participants’ guides, to learn more about the
application process steps:
* All the projects will be showcased here:
We hope you will help us spread the word about Wikimedia’s participation in
these programs (by sharing this email)
Looking forward to your participation!
Gopa, Srishti, Pavithra, Ankit & Mahveotm (Wikimedia organization
administrators for GSoC & Outreachy)
Gopa Vasanth <https://www.mediawiki.org/wiki/User:Gopavasanth>
Amrita Vishwa Vidyapeetham <http://www.amrita.edu/> | Blog
amFOSS <https://amfoss.in/@gopavasanth> | GitHub
<https://github.com/gopavasanth> | Gerrit
“Yesterday is not ours to recover, but tomorrow is ours to win or lose.”
I've been using mediawiki in the docker containers for a while, and I just
did a git pull to the latest, replaced the containers I was running etc,
and now I can't figure out where errors are being logged to or how I'm
supposed to see them. Help!
This may be related to the new '.env' file that seems to be required, which
sets a MW_DOCKER_UID and MW_DOCKER_GID value... If I run
I do see some "Permission denied" errors for files in /etc/php/7.2/cli and
/etc/php/7.2/fpm but those don't seem to be log files exactly
(20-xdebug.ini files ?)
If I do docker-compose exec mediawiki bash I get a login shell on the
container and I can look around, but there are no mediawiki log files in
/var/log where I would expect them, and again I don't have permission to
create a file there. Also if I docker exec into the web container I don't
have permission to look at the apache logs (but those do exist).
If I try to add a $wgDebugLogFile to LocalSettings.php the mediawiki
instance completely collapses, I can't look at anything, and I see no
errors explaining what's going on!
For python projects, tox has been upgraded from 3.10 to 3.21.4. That
was notably to address an issue when python3.9 is defined as an
environment although it is not available in our image, tox would
fallback to whatever default python 3 instead of failing (T274232).
You can read the full tox changelog at:
If there is any issue, please file a task in Phabricator against
Antoine "hashar" Musso
All wikis except testwikis are on 1.36.0-wmf.27; testwikis are running
We've rolled back to wmf.27 so that we have a stable base version from
which to roll out wmf.30.
We will proceed with rollout of wmf.30 once this cherry-pick for wmf.30 is