[Wikitech-l] mwmaint1001 has been replaced by mwmaint1002

[Daniel Zahn]

PSA:  if you need access to the mediawiki maintenance server, we are back
in eqiad and mwmaint1001 was just a temporary replacement for terbium.

The correct server name to use is now:   mwmaint1002.eqiad.wmnet

The fingerprints are on:
https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/mwmaint1002.eqiad.wmnet

https://wikitech.wikimedia.org/wiki/Mwmaint1002

-- 
Daniel Zahn 
Operations Engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] New Reports in wikistats2: "top editors" (a.k.a most prolific contributors) and "top edited articles"

[Nuria Ruiz]

Hello,

The analytics team would like to announce two new metrics available in
wikistats2:

1. Top editors (a.k.a most prolific contributors)
See example for Italian wikipedia:

https://stats.wikimedia.org/v2/#/it.wikipedia.org/contributing/top-editors/normal|table|1-Month|~total

2. Top edited articles (pages with most edits, not most contributors):
Again, example for Italian wikipedia:

https://stats.wikimedia.org/v2/#/it.wikipedia.org/contributing/top-edited-pages/normal|table|1-Month|~total

Please take a look and, as always, send feedback via phab or irc
(#wikimedia-analytics)

The tasks we have in our radar for wikistats2 are metrics "per family",
that is. "edits for all wikitionary projects"  or "unique devices for all
wikipedias".

Some of these metrics are already available in the API. See for example,
the daily number of edits for all wikitionary.org projects for August 2018,
made by registered users on articles (pages in content namespace):

https://wikimedia.org/api/rest_v1/metrics/edits/aggregate/all-wiktionary-projects/user/content/daily/20180801/20180901

More info about edit data apis here:
https://wikitech.wikimedia.org/wiki/Analytics/AQS/Wikistats_2

Thanks,

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

[Wikitech-l] Breaking change: return value for OutputPage::adaptCdnTTL() removed

[C. Scott Ananian]

There are no known users of the return value of OutputPage::adaptCdnTTL()
according to
https://codesearch.wmflabs.org/search/?q=adaptCdnTTL=nope==

But our all-seeing eye does not see everything.  Be it known that
https://gerrit.wikimedia.org/r/450075, just merged, removed the return
value for OutputPage::adaptCdnTTL() and this is technically a breaking
change.

The value formerly returned by adaptCdnTTL() was arguably misleading:
callers would probably expect it to return mCdnMaxage, but instead it
(formerly) returned mCdnMaxageLimit.  Since the return value was easily
misunderstoood *and* it was unused, we've decided to remove it.

@simetrical (Aryeh) wrote the patch and should get the credit (the test
coverage for OutputPage was also significantly increased! Yay, Aryeh!).
Krinkle and I thought it was worth a C+2, so if in fact
OutputPage::adaptCdnTTL() was vital to your way of life and we've ruined it
forever, we should get the blame.
  --scott
-- 
(http://cscott.net)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] FileLinkTool

[Roul P.]

That is the smallest "tool" I've ever seen, adding a colon.  Anyway Commons
has this (since ever?) in the toolbar as button.

Am Di., 9. Okt. 2018 um 23:46 Uhr schrieb Pine W :

> Thanks, this looks like a nice addition that will cumulatively save people
> a lot of time if used widely. I'm forwarding to the Commons and Wikitech
> lists. I haven't tested it but the concept looks good.
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
>
> On Tue, Oct 9, 2018 at 10:14 AM Ananth Subray 
> wrote:
>
> > Dear All,
> >
> > We are very happy to inform you all that Indic-TechCom has made a new
> tool
> > to give a link to source file after doing the derivative work on commons.
> > We all know that how important to mention the source file correctly after
> > doing the derivative work. Based on the request of community members
> > Indic-TechCom has created. To know more about the tool visit the meta
> > page[1]. Indic-TechCom request you all to use it and spread the work to
> > your community members. In case if you have suggestions, please let us
> > know.
> >
> >
> >
> >
> > [1]. https://meta.wikimedia.org/wiki/Indic-TechCom/Tools/FileLinkTool
> > ___
> > Wikimedia-l mailing list, guidelines at:
> > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > https://meta.wikimedia.org/wiki/Wikimedia-l
> > New messages to: wikimedi...@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
> ___
> 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] Datacenter Switchback recap

[Alexandros Kosiaris]

A minor correction:

> During the most critical part of the switch
> today, the wikis were in read-only mode for a duration of 4 minutes
> and 41 seconds.

This was yesterday, not today.

-- 
Alexandros Kosiaris 

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

[Wikitech-l] Readers Monthly update for September 2018

[Chris Koerner]

Hello,

This is the monthly update from the Readers team at the Wikimedia
Foundation for September 2018.

Feedback and questions are encouraged.

==Discussions==

=== Apps===
* Work is underway to bring Wikidata description editing to the iOS app. [0]

=== Web ===
* The Advanced mobile contributions project saw an updated navigation
prototype go out to folks. We contacted ~30 people we met at Wikimania
directly, shared in Tech News, posted to 15 language specific wikis where
mobile usage was the highest, to the wikimedia-l, wikitech-l, and mobile-l
mailing lists, and to the Wikipedia Weekly Facebook group. [1] [2] [3]

=== Reading Infrastructure ===
* Made small corrections to parentheses stripping in /page/summary
endpoint: [4] [5]
* Map cluster upgrade to Debian Stretch is in progress: [6]

=== New Readers ===
* New Reader updates can be found at Meta. [7]

[0] https://phabricator.wikimedia.org/T193691
[1] https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions
[2]
https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions/Navigation_prototype_feedback
[3] https://phabricator.wikimedia.org/T197715
[4] https://phabricator.wikimedia.org/T198264
[5] https://phabricator.wikimedia.org/T202119
[6] https://phabricator.wikimedia.org/T198622
[7] https://meta.wikimedia.org/wiki/New_Readers/Updates

---

Subscribe to receive theses updates as on-wiki notifications or opt-in
email.

https://www.mediawiki.org/wiki/Newsletter:Readers_Monthly

The archive of all past updates can be found on MediaWiki.org:

https://www.mediawiki.org/wiki/Reading/Status_updates

Yours,
Chris Koerner
Community Relations Specialist
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Datacenter Switchback recap

[Alexandros Kosiaris]

Hello everyone,

Today we've concluded the successful migration of our wikis (MediaWiki
and associated services) from our secondary datacenter (codfw) back to
the primary one (eqiad). During the most critical part of the switch
today, the wikis were in read-only mode for a duration of 4 minutes
and 41 seconds. That's a significant improvement over the 7 mins and
34 seconds we achieved during the inverse process we concluded a month
ago, which was already significantly better than last year. I 'd like
to believe that it's the result of the increasing amount of experience
we are building and trust we are putting in the process and tools that
we have developed for this.

Although the switchback process itself has been largely automated and
went pretty smoothly, there have been some issues that we experienced:

- CentralNotice banners stayed online for a longer time than necessary
due to miscommunication issues. This has now been documented and will
be avoided in the future.

- After the switchback we 've experienced increased load to all our
mediawiki application servers. The root cause has been identified and
mitigation against it will be put in place. The summary is non working
replication of parsercache between the 2 datacenters.

- Last, but not least and probably the most important of all issues, a
data inconsistency was detected in wikidata (s8). Namely some articles
that were present in codfw but were not replicated in eqiad. We are
still investigating the root cause of this while applying corrective
actions to mitigate the user impact as quickly as possible.

All wikis are now served from our primary data center again.

Should you experience any issue that is deemed related to the
switchover process, please feel free to file a ticket in Phabricator
and tag it with the Datacenter-Switchover-2018 project tag[1]. We will
monitor this tag closely and keep any and all issues updated.

We'd like to thank everyone for their hard work in ensuring any
(potential) issues got resolved timely, for automating the process
whenever and wherever possible, and for making this datacenter
switchover and switchback a success!

-- 
Alexandros Kosiaris 

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

[Wikitech-l] 2018-09-26 Scrum of Scrums meeting notes

[Grace Gellerman]

*https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-09-26
*

*= 2018-09-26 =*
== Callouts ==

Release Engineering:

* *Deployments of MediaWiki with scap cause a spam of "web request took
longer than 60 seconds and timed out"*
** https://phabricator.wikimedia.org/T204871

** Scap is checking canary servers in dormant instead of active-dc*
** Switchover process needs an update. Long term the list of canaries
should be in conftool.
** https://phabricator.wikimedia.org/T204907

* ComTech:
**  We're starting to work on showing SVGs in page language -
https://phabricator.wikimedia.org/T205040

== Audiences ==
=== Readers ===
 iOS native app 
* Blocked by:
* Blocking:
* Updates:
**Planning to be feature complete for 6.1 (
https://phabricator.wikimedia.org/tag/ios-app-v6.1-narwhal-on-a-bumper-car/) by
the end of this week
** Apps offsite next week,

 Android native app 
* Blocked by:
* Blocking:
* Updates:
**Working on productionising new navigation
**Apps offsite next week.



 Readers Web 
* Blocked by:
* Blocking:
* Updates:
** Mobile website (MinervaNeue / MobileFrontend):

*** SkinMinerva.php file logs "Undefined variable: returntoquery` error
T205449

*** Invest in the MobileFrontend & MinervaNeue frontend architecture
https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture
 Continue Webpack and test transition of mobile.startup T203817
 Add more tests to mobile.startup files T203818
 Simplify CategoryOverlay T191987
 Add Sinon.JS configuration T204885
 Update test file naming T197884
 Bundle Hogan.js T205128 T205129
 Enable client side error reporting T167699

*** Page issues
https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues
 Limited A/B test in progress T204609
 ReadingDepth logging sometimes initializes before PageIssues T204144
 Add new treatment opt-in query parameter override T204746
 Don't cache config flag with HTML T205355
 What % of pages feature issues? T201123
 Increase sampling ratio for ReadingDepth T205176

*** Working with editing
*** Add share icon to beta T181195
*** Lighten default theme color T204691
*** Maintenance and bug fixes T199066 T204584 T197105 T198018 T205321

*** Advanced mobile contributions
https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions
 Generate list of most used special pages T198218
 Design and product continuing special pages work in Minerva

*** Data working on "better use of data" requirements

** PDF rendering (Proton)
https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality
*** Remaining work tracked in T186748
*** Working with Services on a Grafana dashboard T201158 T204055
*** Chromium-render doesn't handle browser connection abort well T181623
*** Miscellaneous maintenance and bug fixes

** Supporting Multimedia/Test hiring processes



 Readers Infrastructure 
* Blocked by:
* Blocking:
* Updates:
** PCS: Continue work on mobile-html endpoint.
** Maps
*** maps1004 migrated to stretch successfully
 It will now receive OSM data load to start generating tiles T205462
*** Investigation of tilerator crash in eqiad has an workaround but still
need permanent fix T204047

 Parsing 
* Blocked by: None
* Blocking: None
* Updates: All code review requests from last week have been handled, thanks
** Will pass along: (Parsing) T205497 [Regression pre-wmf.23] REST API on
Beta cluster returns content of different pages than requested (breaks VE)



 Multimedia 
* Blocked by:
* Blocking:
* Updates
**


=== Contributors ===
 Community Tech 
* Blocked by:
* Blocking:
* Updates:
** We're starting to work on showing SVGs in page language -
https://phabricator.wikimedia.org/T205040 *Ping Parsing and SRE*


 Anti-Harassment Tools 
* Blocked by:
* Blocking:
* Updates:
**

 Editing 
* Blocked by:
* Blocking:
** Updates:
** Removed dedicated annotation operation types in the VE data model and
instead model annotation transactions using replacements
** Improved mobile dialogs in the visual editor
** Completed move of MobileFrontend's VisualEditor styles back to
MobileFrontend from Minerva



 Growth 
* Blocked by:
* Blocking:
* Updates:
**


 Language 
* Blocked by:
* Blocking:
* Updates:
** Preparing for ContentTranslation v2 continue.


=== Audiences Design ===
* Blocked by:
* Blocking:
* Updates:
**


 UI Standardization 
* Blocked by:
* Blocking:
* Updates:
** Special:Preferences OOUI rollout
** Resolving remaining typography/imagery quests on Design Style Guide
** Accessibility work on wikimediafoundation.org website


== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
- Analytics team off-site
- Replacement of hadoop cluster node managers without issues
- 2 new metrics for Wikistats2: pages to date (total article count) and top

[Wikitech-l] 2018-10-03 Scrum of Scrums meeting notes

[Grace Gellerman]

*https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-10-03
*

*=2018-10-03=*
== Callouts ==
* Fundraising campaigns
https://meta.wikimedia.org/wiki/CentralNotice/Calendar
* Actively working to eliminate ongoing messages from the mediawiki-errors
logging channel.  Your team may be tagged on those, please take a look
if/when you are.
* SRE:

Switchover/Switchback dates reminder.* It's next week!*

Switchback:

Traffic: Wednesday, October 10th 2018 09:00 UTC
MediaWiki: Wednesday, October 10th 2018: 14:00 UTC
Services: Thursday, October 11th 2018 14:30 UTC
Media storage/Swift: Thursday, October 11th 2018 15:00 UTC

* Release Engineering
** Next week: No train next week, DC switchover

* Reading Infrastructure:
We would like to ask the Security Team how is the security review of
"JsonConfig and Kartographer interaction" (T163827) going and if they
need any help with that (It's not blocking anything, but we would like to
know the current status)

* Research
** [Services]: Setting up a connection from the recommendation API service
to MySQL: https://phabricator.wikimedia.org/T205452

* UI Standardization
** OOUI v0.29.0 released yesterday with 8 possible breaking changes, among
those PHP 7 requirement and removal of CapsuleMultiselectWidget
*** Please consider if these changes might affect your code
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v0.29.0

* 5 Minute Demo - taking your sign-ups now! Next meeting on Oct 11
** https://www.mediawiki.org/wiki/5_Minute_Demo#Recordings_and_Presenters

* Parsoid
Services (Core Platform) and Parsing team deployed code this week that
implements HTML version (content) negotiation protocol alongwith a major
version bump of Parsoid HTML from 1.8.0 to 2.0.0 (
https://www.mediawiki.org/wiki/Specs/HTML/2.0.0 ). As part of this,
RESTBase + Parsoid will enforce the HTML version requested in the Accept
header. If a version is requested that is different (^ semantics) than what
is available in storage, RESTBase will ask Parsoid to get the appropriate
version. If Parsoid cannot do that, it will return a HTTP 406. What does it
mean for Parsoid clients? If you are requesting a really old version in
your Accept header, you are very likely going to get a HTTP 406. If you
request an older version (1.7 or 1.8), you will see an additional latency
to your requests while Parsoid downgrades the HTML from the more up to date
version. So, Parsoid clients should provide an accept header with the most
up-to-date version of Parsoid HTML you can handle. Subsequently, you should
update your code to handle the newer versions in a timely manner. A longer
announcement and wiki docs will be coming out soon.


== Audiences ==


=== Contributors ===
 Community Tech 
* Blocked by:
* Blocking:
* Updates:
**

 Anti-Harassment Tools 
* Blocked by:
* Blocking:
* Updates:
**

 Editing 
* Blocked by:
* Blocking:
** Updates:
**

 Growth 
* Blocked by:
* Blocking:
* Updates:
**

 Language 
* Blocked by: None
* Blocking: None
* Updates:
** Content Translation v2 released!
https://wikimediafoundation.org/2018/09/30/content-translation-version-two/

=== Readers ===
 iOS native app 
* Blocked by:
* Blocking:
* Updates:
**

 Android native app 
* Blocked by:
* Blocking:
* Updates:
**


 Readers Web 
* Blocked by:
* Blocking:
* Updates:
** Mobile website (MinervaNeue / MobileFrontend):

*** Invest in the MobileFrontend & MinervaNeue frontend architecture
https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture
 Add unit tests for util and mfExtend T203818
 Bundle widgets and models with Webpack; enable headless Page and View
tests T204867 T204786
 Make test set up explicit T204885
 Lint unsupported JavaScript in build products T203976
 Move MainMenu click tracking schema from MobileFrontend to Minerva
T204584
 Merge skin option modules into a single ResourceLoader module and move
enabled logic to client T167713

*** Page issues
https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues
 A/B test in progress T204609
 Lots of cross-wiki QA and A/B test discussions

*** Maintenance and bug fixes T205449 T202756

*** Advanced mobile contributions
https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions
 Design and product continuing special pages work in Minerva

** PDF rendering (Proton)
https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality
*** Remaining work tracked in T186748
*** Html2pdf route should return promise T201158 T204055 T181623
*** Consistently represent asynchronous code execution T204055

** SEO: where should Schema property 'sameAs' live? T204070
*** The Performance team is going to be deploying a second set of sitemaps
next week, they will also be testing the indexing on mobile in parallel.
Mikhail has analyzed the data from the 

[Wikitech-l] 2018-10-10 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-10-10

*=2018-10-10=*
== Callouts ==
* Fundraising campaigns
https://meta.wikimedia.org/wiki/CentralNotice/Calendar
*
* SRE:
** Switchover week, no train. Up to now traffic and mediawiki switchovers
have succeeded

* Release Engineering
** Blocked by: need review from SRE/services [
https://gerrit.wikimedia.org/r/#/c/461457/ Support a literal body for POST
requests in `fetch_url`]
** Train Health: no train due to DC switchover - T191071 1.32.0-wmf.25
deployment blockers
** Log Health: T204871 Deployments of MediaWiki with scap cause a spam of
"web request took longer than 60 seconds and timed out"

* Research
** *Services* please help with "Setting up a connection from the
recommendation API service to MySQL":
https://phabricator.wikimedia.org/T205452


* Parsoid



== Audiences ==


=== Contributors ===
 Community Tech 
* Blocked by:
* Blocking:
* Updates:
**

 Anti-Harassment Tools 
* Blocked by:
* Blocking:
* Updates:
**

 Editing 
* Blocked by: Partially blocked by Performance on T176262.  We want to
preload code in the visual editor to improve loading times (T202720) and we
need to understand the priority and timeline for T176262 to plan
accordingly.
* Blocking:
** Updates:
**

 Growth 
* Blocked by:
* Blocking:
* Updates:
**We've released PageTriage/ORES integration.
**Will release PageTriage/Copyvio integration in about a week.
***We are working on interventions for Understanding first day (
https://phabricator.wikimedia.org/T205754) and

 Language 
* Blocked by: None
* Blocking: None
* Updates:
** Work on polishing ContentTranslation v2 continue. Received positive
feedback so far.

=== Readers ===
 iOS native app 
* Blocked by:
* Blocking:
* Updates:
**Working on closing out 6.1 for beta (
https://phabricator.wikimedia.org/tag/ios-app-v6.1-narwhal-on-a-bumper-car/),
changes to cookie handling in progress

 Android native app 
* Blocked by:
* Blocking:
* Updates:
** Offsite last week; focusing on releasing navigation updates.


 Readers Web 
* Blocked by:
* Blocking:
* Updates:
** Mobile website (MinervaNeue / MobileFrontend):

*** Invest in the MobileFrontend & MinervaNeue frontend architecture
https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture
 Transition Gruntfile tasks to NPM scripts T206069
 Follow-ups from last week

*** Page issues
https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues
 A/B test rollout increased on Farsi, Japanese, Russian, and English
wikis T200792

*** Enable Dynamic Type in iOS 9+ browsers T204807
*** Maintenance and bug fixes T206274 T206174 T204835 T206337 T205582

*** Advanced mobile contributions
https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions
 Design continuing special pages work in Minerva

** PDF rendering (Proton)
https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality
*** Remaining work tracked in T186748
*** Testing concurrency
*** chromium-render naming is being updated to proton

** SEO: add Schema sameAs property pointing to Wikidata entries T198946

** Management supporting Multimedia hiring processes

** Design continuing work on reference previews
https://reference-previews.firebaseapp.com/.

** Product continuing 3-5 year planning.


 Readers Infrastructure 
* Blocked by:
** none
* Blocking:
** none known
* Updates:
** RI offsite next week, very limited availability
** Maps:
*** Load OSM data into maps1004 continues this week, we expected to start
generating tiles next week



 Multimedia 
* Updates
** Working on hiring, interviewing candidate this week
** All of the SDoC multi-lingual file captions work is merged - some small
security fixes and we can deploy to beta (crosses fingers)
** lots of discussion/design on prototypes for adding 'depicts' to files
containing artworks

 Parsing 
* Blocked by:
* Blocking:
* Updates:


 UI Standardization 
* Blocked by:
* Blocking:
* Updates:
** OOUI v0.29.2 released with a hotfix on consistent document listeners
from breaking change in v0.29.0
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v0.29.2
** Design Style Guide “Resources” section inclusion – preparing patches
** wikimediafoundation.org priority accessibility issues successfully
resolved https://phabricator.wikimedia.org/T201682

== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Putting finishing touches on new metrics on wikistats, see for example
“top editors” in italian wikipedia. We just added ability to split by
bots/anonymous:
https://stats.wikimedia.org/v2/#/it.wikipedia.org/contributing/top-editors
(as always all metrics are available programmatically via APIs)
** Working with security in prioritizing items to work on as part of
security’s review of analytics’ stack.
** Ingesting data from eventlogging for easy visualization 

Re: [Wikitech-l] [Wikidata-tech] Normalization of change tag schema

[Amir Sarabadani]

Hello,
One other update regarding this: We just set reading to use the new change
tag backend (and stop writing to ct_tag column) in mediawiki.org, test
wikis and several other small wikis. This means if you are depending on
ct_tag column, your tool/service will be broken soon.

Also, since this changes queries of recentChanges, watchlist, User
contributions, history action, a handful of API modules and some other
special pages, let us know if anything in that regard doesn't look right to
you. Dear developers, keep this in mind if something pops up in logs or
tendril.

We are planning to move forward on bigger wikis next week.

Best

On Tue, 31 Jul 2018 at 09:19, Jon Robson  wrote:

> 
>
> On Tue, Jul 31, 2018, 3:42 AM Derk-Jan Hartman <
> d.j.hartman+wmf...@gmail.com>
> wrote:
>
> > That is an impressive difference !
> >
> > On Mon, Jul 30, 2018 at 6:22 PM Amir Sarabadani <
> > amir.sarabad...@wikimedia.de> wrote:
> >
> > > And this is the load on vslow database nodes on s7:
> > >
> > >
> >
> https://grafana.wikimedia.org/dashboard/db/mysql?panelId=3=1=1532794373712=1532967173714=eqiad%20prometheus%2Fops=db1090=13317
> > >
> > > You can see similar drops on other sections from exactly the moment it
> > got
> > > deployed:
> > > s1:
> > >
> > >
> >
> https://grafana.wikimedia.org/dashboard/db/mysql?panelId=3=1=1531757700702=1532967300702=eqiad%20prometheus%2Fops=db1106=9104
> > > s2
> > > <
> >
> https://grafana.wikimedia.org/dashboard/db/mysql?panelId=3=1=1531757700702=1532967300702=eqiad%20prometheus%2Fops=db1106=9104s2
> > >
> > > :
> > >
> > >
> >
> https://grafana.wikimedia.org/dashboard/db/mysql?panelId=3=1=1532794561870=1532967361872=eqiad%20prometheus%2Fops=db1090=13312
> > >
> > > Best
> > >
> > > On Mon, 30 Jul 2018 at 13:13, Amir Sarabadani <
> > > amir.sarabad...@wikimedia.de>
> > > wrote:
> > >
> > > > Hey,
> > > > Using the new table as backend of Special:Tags (and similar APIs) is
> > now
> > > > enabled everywhere. Contact me if there's any issues with that.
> > > >
> > > > Best
> > > >
> > > > On Wed, 25 Jul 2018 at 19:17, Amir Sarabadani <
> > > > amir.sarabad...@wikimedia.de> wrote:
> > > >
> > > >> Hello,
> > > >> One update regarding this.
> > > >> We enabled using the new table for Special:Tags in several large
> wikis
> > > >> which caused a massive improvement in the performance of the page.
> For
> > > >> example loading Special:Tags on Wikidata used to take around a
> minute
> > > and
> > > >> now it takes less than a second. English Wikipedia is down from ten
> > > seconds
> > > >> to less than one and so on.
> > > >>
> > > >> There is a lot of work needs to be done and maintenance scripts is
> > being
> > > >> ran to backpopulate the ct_tag_id column in change_tag table (If you
> > > want
> > > >> to follow the progress, see
> https://phabricator.wikimedia.org/T193873
> > )
> > > >> and then we need start reading from the new table in mediawiki and
> > > finally
> > > >> we can drop ct_tag column entirely. If you want to help in review,
> > > writing
> > > >> code or anything, just let me know.
> > > >>
> > > >> Best
> > > >>
> > > >> On Wed, 27 Jun 2018 at 15:15, Léa Lacroix  >
> > > >> wrote:
> > > >>
> > > >>> Hello all,
> > > >>>
> > > >>> Our team is refactoring some code around the change tags on Recent
> > > >>> Changes. This can impact people using the database on ToolForge.
> > > >>>
> > > >>> Currently, the tags are stored in the table change_tag in the
> column
> > > >>> ct_tag.
> > > >>>
> > > >>> In the next days, we will add a column ct_tag_id with a unique
> > > >>> identifier for these tags. A new table change_tag_def that will
> store
> > > >>> the tag id, the message, and more information like how many times
> > this
> > > tag
> > > >>> is used on the local wiki.
> > > >>>
> > > >>> On the long term, we plan to drop the column ct_tag since the tag
> > will
> > > >>> be identified with ct_tag_id.
> > > >>>
> > > >>> This change will happen on:
> > > >>> - French Wikipedia: Monday July 2nd
> > > >>> - All other wikis: from July 9th
> > > >>>
> > > >>> If there is any problem (trouble with saving edits, slow down of
> > recent
> > > >>> changes…) please  create a subtask of T185355
> > > >>>  or contact Ladsgroup
> > > >>> .
> > > >>>
> > > >>> Cheers,
> > > >>> --
> > > >>> Léa Lacroix
> > > >>> Project Manager Community Communication for Wikidata
> > > >>>
> > > >>> Wikimedia Deutschland e.V.
> > > >>> Tempelhofer Ufer 23-24
> > > >>> 10963 Berlin
> > > >>> www.wikimedia.de
> > > >>>
> > > >>> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens
> e.
> > V.
> > > >>>
> > > >>> Eingetragen im Vereinsregister des Amtsgerichts
> Berlin-Charlottenburg
> > > >>> unter der Nummer 23855 Nz. Als gemeinnützig ane
> >  >rkannt
> > durch das
> > > Finanzamt
> > > >>> für Körperschaften I Berlin,