The 1.35.0-wmf.19 version of MediaWiki is blocked[0].
The new version is deployed to group1[1], but can proceed no further until
these issues are resolved:
* Varnish 5xx 2k/min spike - https://phabricator.wikimedia.org/T245202
Once these issues are resolved train can resume. If these issues are
On Thu, Feb 13, 2020 at 10:56 AM Željko Filipin
wrote:
> Hi,
>
> for HTML version see
> https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-02-12
>
> Željko
>
> --
>
> = 2020-02-12 =
>
> == Callouts ==
>
> * SRE for Release engineering on Looking for scap reviewers for syslog
> support
Hello colleagues,
This is a reminder that this month's Wikimedia Café will start
approximately 48 hours from now.
--
Hello colleagues,
The February 2020 Wikimedia Café meetup will occur on 15 February 2020
at 8:30 AM PST / 11:30 AM EST / 4:30 PM UTC / 10 PM IST. The date is
earlier than usual
If your cache layer is APC, and your cached file is PHP (e.g.
load.php?querystring), then you can configure APC to always check for a
revised file in the backend (opcache.validate_timestamps=1 in php.ini) --
this may solve the issue if it wasn't set previously. Also, you can write
your own
Hey Roan,
Thank you for your response!
I did stumble upon ContentOverrideCallback. Unfortunately, it doesn’t seem to
be an exact fit for this use case.
I think I will opt for manual URL purges to ensure timely updates in this
scenario
Cheers,
Máté Szabó
SOFTWARE ENGINEER
Fandom Poland sp.
Hi,
for HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-02-12
Željko
--
= 2020-02-12 =
== Callouts ==
* SRE for Release engineering on Looking for scap reviewers for syslog
support [[gerrit:563468]]
* Parsing - Project retrospective of how Parsoid was ported to PHP:
