Re: [Wikitech-l] Where are the logs?

[Michael Holloway]

Hi Arthur,

In MediaWiki-Docker the MediaWiki log files are created by default in the
cache subdirectory. This is controlled by the MW_LOG_DIR

setting in docker-compose.yml.

Best regards,
Michael

On Wed, Feb 10, 2021 at 11:51 AM Arthur Smith 
wrote:

> I tried setting MW_DOCKER_UID and MW_DOCKER_GID both to 0, and that at
> least allows me to see the various files - it looks like the apache log
> files are on the -web container under /tmp/, I hadn't noticed that before.
> So that's at least part of the answer. On the main mediawiki container
> there is a log file in /tmp/php7.2-fpm.log but it doesn't seem to log very
> much there; I'm still getting 500 server errors when I try to set
> $wgDebugLogFile and can't find any trace of what the problem is.
>
>   Arthur
>
> On Wed, Feb 10, 2021 at 11:17 AM Arthur Smith 
> wrote:
>
>> 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
>>
>> docker-compose logs
>>
>> 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!
>>
>> Help!
>>
>>Arthur
>>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Maps on wikidata

[Michael Holloway]

Hi Strainu,

It's probably best if a Wikibase dev confirms, but I think this is what
you're looking for:
https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Wikibase/+/master/lib/includes/Formatters/CachingKartographerEmbeddingHandler.php#198

-mdh

On Fri, May 8, 2020 at 12:44 PM Strainu  wrote:

> Hey folks,
>
> Can someone point me to the code that decides which zoom to use for
> the maps that are displayed in the items with coordinates?
>
> Thanks,
>Strainu
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] 14 January 2020 security incident on Phabricator

[Michael Holloway]

Do those of us using Phabricator 2FA need to take any action?

On Fri, Jan 17, 2020 at 7:38 AM Greg Grossmeier  wrote:

> Keeping this thread on-list to help others who might be unsure.
>
> Hello Pine,
>
> On Thu, Jan 16, 2020 at 4:23 PM Pine W  wrote:
>
> > The way that I log into Phab is by using
> > https://phabricator.wikimedia.org/auth/start/?next=%2F, and then logging
> > into MediaWiki and authorizing Phab to access my credentials. The
> MediaWiki
> > login including the 2FA is the same that I use for many other Wikimedia
> > sites.
> >
>
> Correct, you are logging into your MediaWiki account with your 2FA token,
> then you are logging into Phabricator via OAuth.
>
> None of those logins nor 2FA tokens were affected by this.
>
>
> > So, although this 2FA allows logins to Phabricator, it sounds like there
> is
> > a separate 2FA for some people for Phabricator access, perhaps for people
> > with LDAP logins, and that is the 2FA that is affected. Is this correct?
> >
>
> Correct. Phabricator has its own 2FA system for people to use.
>
> You can see if you use it via your Account Settings, then clicking on
> "Multi-Factor Auth". That is the 2FA that is affected in this incident.
>
> Best,
>
> Greg
>
> --
> | Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
> _______
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Michael Holloway
Software Engineer, Product Infrastructure
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] REST API /page/summary: proposed change to content_urls and api_urls

[Michael Holloway]

The Wikimedia REST API's /page/summary response contains content_urls and
api_urls keys that provide convenience lists of various URLs of potential
interest to the consumer.  These lists appear in other endpoint responses
as well, as the page summary response is transcluded in various places
throughout the REST API.

Currently, these URL strings are constructed erroneously using unencoded
page title strings.  A proposed patch (
https://gerrit.wikimedia.org/r/#/c/mediawiki/services/mobileapps/+/489329/)
applies encodeURIComponent to encode these before including them in URLs.

Since this endpoint is advertised as stable[1], I'm announcing the change
here in advance.  Barring any objections, the change will be deployed late
next week.

[1]
https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title

-- 
Michael Holloway
Software Engineer, Reading Infrastructure
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] problematic use of "Declined" in Phabricator

[Michael Holloway]

I think I can provide some context here, because this really seems to be
about something specific.  The Reading Infrastructure team recently
inherited maintenance responsibility for the Wikimedia maps stack,
resourced on a very limited basis.  Along with that, we inherited a backlog
of many hundreds of tasks, many of which have seen no activity for years.
For the past couple of months, a few of us have spent an hour each week
trying to work through the backlog trying to triage all of these.  In the
course of these grooming meetings, we have closed more than a few tasks
based on a combination of not having the resources to work on them, and it
not seeming likely that anyone else will, either; the theory here is that
it can better reflect reality to openly decline a task than to let it
languish in a backlog indefinitely.

If this contravenes the relevant norms, I apologize.  If you were upset by
the closing of what you believe to be a valid maps ticket, please feel free
to reopen.  Thanks.

On Tue, Oct 2, 2018 at 10:06 PM Brian Wolff  wrote:

> Declined = WONTFIX (e.g. if some talented developer wrote a patch, and the
> patch was perfect, you would still -2 it because the functionality is not
> wanted/stupid/etc)
>
> Invalid = not a real bug. That should include things like spam, stuff where
> the reporter is mistaken ( can't reproduce or if someone say reports a
> sharepoint bug)
>
> I think the defining difference is its possible to write a patch for a
> declined bug, even though it would be rejected, where an invalid bug by
> definition is unfixable.
>
> Just my 2 cents, others may have different definitions.
>
> --
> Brian
>
> p.s. ive never liked the "need volunteer" term for lowest priority - I have
> always felt it had offensive implications as if volunteer time isnt as
> important so they get the low priority bugs.
>
> On Tuesday, October 2, 2018, Joe Matazzoni 
> wrote:
> > I agree with Amir’s understanding. "Declined” is basically for ideas
> whose proper timing is never.  Valid ideas that we just aren’t going to
> work on any time soon should go in a backlog or freezer or some such, where
> they can await until some future project or other development makes them
> relevant (at least theoretically).
> >
> > All of which does raise a slightly different question: I am much less
> clear on what the exact difference is between “Invalid” and “Declined.”
> Thoughts?
> >
> > Best,
> > Joe
> > _
> >
> > Joe Matazzoni
> > Product Manager, Collaboration
> > Wikimedia Foundation, San Francisco
> > mobile 202.744.7910
> > jmatazz...@wikimedia.org
> >
> > "Imagine a world in which every single human being can freely share in
> the sum of all knowledge."
> >
> >
> >
> >
> >> On Oct 2, 2018, at 9:31 AM, Amir E. Aharoni <
> amir.ahar...@mail.huji.ac.il>
> wrote:
> >>
> >> Hi,
> >>
> >> I sometimes see WMF developers and product managers marking tasks as
> >> "Declined" with comments such as these:
> >> * "No resources for it in (team name)"
> >> * "We won't have the resources to work on this anytime soon."
> >> * "I do not plan to work on this any time soon."
> >>
> >> Can we perhaps agree that the "Declined" status shouldn't be used like
> this?
> >>
> >> "Declined" should be valid when:
> >> * The component is no longer maintained (this is often done as
> >> mass-declining).
> >> * A product manager, a developer, or any other sensible stakeholder
> thinks
> >> that doing the task as proposed is a bad idea. There are also variants
> of
> >> this:
> >> * The person who filed the tasks misunderstood what the software
> component
> >> is supposed to do and had wrong expectations.
> >> * The person who filed the tasks identified a real problem, but another
> >> task proposes a better solution.
> >>
> >> It's quite possible that some people will disagree with the decision to
> >> mark a particular task as "Declined", but the reasons above are
> legitimate
> >> explanations.
> >>
> >> However, if the task suggests a valid idea, but the reason for declining
> is
> >> that a team or a person doesn't plan to work on it because of lack of
> >> resources or different near-term priorities, it's quite problematic to
> mark
> >> it as Declined.
> >>
> >> It's possible to reopen tasks, of course, but nevertheless "Declined"
> gives
> >> a somewhat permanent feeling, and may cause good ideas to get lost.
> >>
> >> So can we perhaps decide that such tasks should just remain Open? Maybe
> >> with a Lowest priority, maybe in something like a "Freezer" or "Long
> term"
> >> or "Volunteer needed" column on a project workboard, but nevertheless
> Open?
> >>
> >> --
> >> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> >> http://aharoni.wordpress.com
> >> ‪“We're living in pieces,
> >> I want to live in peace.” – T. Moore‬
> >> ___
> >> Wikitech-l mailing list
> >> Wikitech-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> > 

Re: [Wikitech-l] My Phabricator account has been disabled

[Michael Holloway]

What I think has people talking past one another here is that the "final
straw" that led to the ban wasn't a per se ban-worthy offense, *and* there
is no clear standard or process for determining when past patterns of
behavior can be taken into account in determining whether a given action
crosses the line.  In legal contexts we account for past behavior with
things like repeat-offender rules/"three-strikes" rules, point systems (as
with driver's licenses), and so on.  Without such rules or processes in
place, banning someone for conduct that is permitted of others risks at
least the appearance of arbitrariness.

On Tue, Aug 14, 2018 at 4:04 PM Brian Wolff  wrote:

> Thanks Amir for clarifying this. This is the first I remember hearing this
> was the reason for the sactions against mcbride, and differs significantly
> from what I assumed was the reason.
>
> However, MZMcbride has also claimed his comment was in exasperation after
> facing the same breach of the CoC you have cited, from varnent. Given that
> there is a narrative going around that the CoC is unfairly biased in favour
> of staff, would you mind sharing what deliberations took place that
> resulted in sactions against only one of the participants in a dispute
> where both participants are alleged to have committed the same fault. To be
> clear, im not neccesarily sugesting (nor am i neccesarily suggesting the
> converse) that the CoC is wrong in this - only that it seems full
> disclosure of the rationale seems like the only method to heal this rift
> that has opened up.
>
> Thank you
> --
> Bawolff
>
> On Tuesday, August 14, 2018, Amir Ladsgroup  wrote:
> > Hey Petr,
> > We have discussed this before in the thread and I and several other
> people
> > said it's a straw man.
> >
> > The problem is not the WTF or "What the fuck" and as I said before the
> mere
> > use of profanity is not forbidden by the CoC. What's forbidden is
> "Harming
> > the discussion or community with methods such as sustained disruption,
> > interruption, or blocking of community collaboration (i.e. trolling).".
> > [1]  When someone does something in phabricator and you *just* comment
> > "WTF", you're not moving the discussion forward, you're not adding any
> > value, you're not saying what exactly is wrong or try to reach a
> consensus.
> > Compare this with later comments made, for example:
> > https://phabricator.wikimedia.org/T200742#4502463
> >
> > I hope all of this helps for understanding what's wrong here.
> >
> > [1]: https://www.mediawiki.org/wiki/Code_of_Conduct
> > Best
> >
> > On Tue, Aug 14, 2018 at 9:29 PM Petr Bena  wrote:
> >
> >> I am OK if people who are attacking others are somehow informed that
> >> this is not acceptable and taught how to properly behave, and if they
> >> continue that, maybe some "preventive" actions could be taken, but is
> >> that what really happened?
> >>
> >> The comment by MZMcBride was censored, so almost nobody can really see
> >> what it was and from almost all mails mentioning the content here it
> >> appears he said "what the fuck" or WTF. I can't really think of any
> >> language construct where this is so offensive it merits instant ban +
> >> removal of content.
> >>
> >> I don't think we need /any/ language policy in a bug tracker. If
> >> someone says "this bug sucks old donkey's " it may sounds a bit
> >> silly, but there isn't really any harm done. If you say "Jimbo, you
> >> are a f retard, and all your code stinks" then that's a problem,
> >> but I have serious doubts that's what happened. And the problem is not
> >> a language, but personal attack itself.
> >>
> >> If someone is causing problems LET THEM KNOW and talk to them. Banning
> >> someone instantly is worst possible thing you can do. You may think
> >> our community is large enough already so that we can set up this kind
> >> of strict and annoying policies and rules, but I guarantee you, it's
> >> not. We have so many open bugs in phabricator that every user could
> >> take hundreds of them... We don't need to drive active developers away
> >> by giving them bans that are hardly justified.
> >>
> >> P.S. if someone saying "WTF" is really giving you creeps, I seriously
> >> recommend you to try to develop a bit thicker skin, even if we build
> >> an "Utopia" as someone mentioned here, it's gonna be practical for
> >> interactions in real world, which is not always friendly and nice. And
> >> randomly banning people just for saying WTF, with some cryptic
> >> explanation, seems more 1984 style Dystopia to me...
> >>
> >> On Tue, Aug 14, 2018 at 4:08 PM, David Barratt 
> >> wrote:
> >> >>
> >> >> Again, this isn't enwiki, but there would be a large mob gathering at
> >> the
> >> >> administrators' doorstep on enwiki for a block without that context
> and
> >> >> backstory.
> >> >>
> >> >
> >> > That seems like really toxic behavior.
> >> >
> >> > On Tue, Aug 14, 2018 at 6:27 AM George Herbert <
> george.herb...@gmail.com
> >> >
> >> > wrote:

Re: [Wikitech-l] Patchsets by new Gerrit contributors waiting for code review and/or merge

[Michael Holloway]

On Thu, Jul 5, 2018 at 9:46 AM Andre Klapper  wrote:

> *
> https://gerrit.wikimedia.org/r/#/c/mediawiki/services/mobileapps/+/441517/
> ** Metadata: Adds per-variant display_title
> ** 2018-Jun-25
> ** Maintainers/Stewards: Reading Infrastructure / Services ?
>

This patch is on RI's radar but blocked on a product decision.

That said, thanks for sending out these notices!

-mdh
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] O'Reilly free books

[Michael Holloway]

That's fantastic, thanks very much for the heads-up, Amir!

On Mon, Oct 10, 2016 at 11:24 AM, Bináris  wrote:

> Of course, your mail is very useful, thanks a lot!
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Mobile][Engineering] Java 8 now required to build the Android app

[Michael Holloway]

Forwarding from mobile-l:


Dear Mobile Wikimedians,

The Android app recently upgraded to the latest version (24.0.0) of the
Android support library, which requires Java 8 in order to build.
Accordingly, Java 8 is now required to build the Android app.

As of about an hour ago, our CI jobs have moved from using Java 7 to Java
8.   Details are here: https://phabricator.wikimedia.org/T138506

Big thanks to @hashar for making the CI change!

Warmly,
Michael
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] Update: Upload to Commons Android app

[Michael Holloway]

Nice work, Josephine, congratulations!

On Mon, Jun 20, 2016 at 2:39 AM, Florian Schmidt <
florian.schmidt.wel...@t-online.de> wrote:

> Congratulations Josephine! :) It’s awesome to see an app which is
> maintained by volunteers only! :)
>
>
>
> *Von:* Mobile-l [mailto:mobile-l-boun...@lists.wikimedia.org] *Im Auftrag
> von *Josephine Lim
> *Gesendet:* Montag, 20. Juni 2016 07:18
> *An:* wikitech-l@lists.wikimedia.org; mobile-l <
> mobil...@lists.wikimedia.org>; common...@lists.wikimedia.org
> *Betreff:* [WikimediaMobile] Update: Upload to Commons Android app
>
>
>
> Hi all,
>
>
>
> A quick update re: the Upload to Commons Android app:
>
>
>
> - We are now considered an 'official' app and have been granted permission
> by WMF to use the Wikimedia Commons logo and name. As such, the app is now
> named "Wikimedia Commons" <
> https://play.google.com/store/apps/details?id=fr.free.nrw.commons>
> instead of "Upload to Commons", and its icon has been changed to the
> Commons logo. Ownership of the app should also soon be transferred to the
> WMF Google Play account. On a practical basis, there should be no change in
> the use of the app and it will still be maintained by volunteers.
>
>
>
> - I am happy to announce that my IEG proposal for further work on the app <
> https://meta.wikimedia.org/wiki/Grants:IEG/Improve_%27Upload_to_Commons%27_Android_App>
> has been selected. :) I will be starting work on it shortly, so there will
> be regular releases planned for the next 6 months. Bug/crash reports and
> feedback are welcome on our Google Groups forums <
> https://groups.google.com/forum/#!forum/commons-app-android> and GitHub
> page  as
> always.
>
>
>
> Have a great day!
>
>
>
>
>
> Cheers,
>
> Josephine
>
>
>
>
>
> ___
> Mobile-l mailing list
> mobil...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Engineering] [ANNOUNCEMENT] MathML/SVG as the default rendering mode on all projects

[Michael Holloway]

Awesome work, Physikerwelt and all involved!

On Mon, Jun 6, 2016 at 9:46 AM, Marko Obrovac 
wrote:

> Hello,
>
> On Tuesday, May 31 we have deployed a change to the production cluster
> that sets MathML with SVG fall-back as the default rendering mode for
> mathematical formulae for all Wikimedia projects~[1]. This change brings
> scaleable and selectable formulae to the whole Wikimedia community, not
> just logged-in users, thus opening new perspectives for better rendering,
> accessibility, search, equation sharing, font and unicode support, styling,
> line breaking…
>
> We are very excited about this feature seeing the light of day, not only
> because of the visible improved experience for our reader and editors, but
> also because this project has been carried out in collaboration with the
> community. In particular, this achievement would not have been possible
> without Moritz Schubotz (aka User:Physikerwelt), who has been the lead
> developer of Mathoid, the rendering service responsible for producing the
> MathML and SVG code that the end-users see on the web-site.
>
> You can read more about this awesome feature on the MathML Association’s
> web-site~[2].
>
> Best,
> The WMF Services Team
>
> [1] https://phabricator.wikimedia.org/T131177
> [2] http://mathml-association.org/announcement/2016/05/31/wikipedia.html
>
>
> --
> Marko Obrovac, PhD
> Senior Services Engineer
> Wikimedia Foundation
>
> ___
> Engineering mailing list
> engineer...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] (no subject)

[Michael Holloway]

Nice work, Josephine!

On Wed, Feb 17, 2016 at 12:43 AM, Josephine Lim 
wrote:

> Hi all,
> I've been working on a project to improve the categorization of pictures in 
> the Upload to Commons Android app  
> as part of the Outreachy Dec '15 program, which is soon drawing to an end. To 
> summarize, 3 new features have been implemented in this app:
>
> 1. If a picture with geolocation is uploaded, nearby category suggestions are 
> offered (based on the categories of other Commons images with similar 
> coordinates)
>
> 2. If a picture with no geolocation is uploaded, nearby category suggestions 
> are offered based on the user's current location. This is optional and only 
> works if enabled in Settings.
>
> 3. Category search (when typing in the search field) has been made more 
> flexible, whereas previously this was done solely by prefix search. E.g. now 
> searching for 'latte' should be able to return 'iced latte'.
>
> The latest version of the app is v1.11 and can be downloaded at 
> . Please 
> feel free to leave feedback or bug reports at 
> .
>
> I have had an amazing time working on this app as part of the Outreachy 
> program, and I greatly appreciate all the support and help that the WMF 
> community has given me. :)
>
>
> Cheers!
>
>
> --
>
> Regards,
> Josephine
>
> ___
> Mobile-l mailing list
> mobil...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l