The 1.35.0-wmf.27 version of MediaWiki is blocked[0].
The new version is not deployed to any group[1], and can proceed no
further until these issues are resolved:
* Call to undefined method WikiPageMessageGroup::getKeys() -
https://phabricator.wikimedia.org/T249258
* Wikidata's wb_items_per_site table has suddenly disappeared, creating
DBQueryErrors on page views - https://phabricator.wikimedia.org/T249565
Once these issues are resolved train can resume. If these issues are
resolved on a Friday the train will resume Monday.
Thank you for your help resolving these issues!
-- Your humble train toiler
[0]. https://phabricator.wikimedia.org/T247774
[1]. <https://tools.wmflabs.org/versions/>
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation
Hello,
https://www.mediawiki.org/wiki/API:Revisions mentions "revision slots"
multiple times, but fails to explain what it is?
I noticed that some queries that were running fine in the past now
have warning: "Because "rvslots" was not specified, a legacy format
has been used for the output. This format is deprecated, and in the
future the new format will always be used."
Which is interesting, but not very descriptive. What are revision
slots? Why are they needed? What is difference between "legacy format"
and "new format"? If rvslots are so important, why they aren't part of
some of the examples?
So far I googled this: https://www.mediawiki.org/wiki/Manual:Slot it
seems like some new "work-in-progress" feature, that isn't very useful
yet, as there is only 1 slot in existence.
Is it necessary to pay attention to this? Can I simply silence this
warning by providing parameter rvslots=*? Or should I pay it some
deeper attention?
Thanks
Hi All,
I am trying to convert an old extension into a module which I can use from
other extensions. After configuring with something like below:
"ResourceModules": {
"ext.myExtension": {
"packageFiles": [
"resources/ext.myExtension/index.js",
"resources/ext.myExtension/core.js",
"resources/ext.myExtension/foobar.js"
],
"styles": "resources/ext.myExtension.css",
"messages": [
"myextension-hello-world",
"myextension-goodbye-world"
],
"dependencies": [
"oojs"
]
}}
mw.loader.using('ext.myExtension')... results into a module not found error
What could be missing here?
Hey,
I am maintainer of the Maps extension for MediaWiki.
https://github.com/JeroenDeDauw/Maps#maps
Recently I worked on improving integration with Visual Editor. Maps used to
not show up as a grey box [0] since their initialization JavaScript was not
being run. I got things working but am not happy with the solution and hope
there is a better approach.
After some searching I found that if I ran the initialization code in a
handler to the ve.activationComplete hook, the maps would get initialized
as desired [1]. That is not a complete solution though, since you can edit
the maps with Visual Editor [2]. This causes an API request that parses the
new wikitext to HTML, which then replaces the old HTML of the initialized
map. So initialization needs to happen again.
An hour or two searching through the docs and Visual Editor code did not
yield any usable hook/event. (This was quite surprising to me. Has no one
ever done something similar to what I am doing here?) So I settled on just
running initialization once every second with setInterval(). I found the
ve.deactivationComplete hook which I then used to stop the code running
every second on saving and existing the visual editor. Turns out that when
opening the visual editor after that does not result in a new
ve.activationComplete event, hence I had to remove termination of the
repeating initialization.
Surely there is a better way to run my code once per second (ad infinitum)
starting with Visual Editor activation? The perfect event for my usecase
would be "visual editor rendered a parser function". A broader event (ie
"something got rendered") would still be better than nothing.
You can see my current code here [3], including a few commented out bits
which I left in so you can see some of what did not work.
[0]
https://user-images.githubusercontent.com/146040/78461765-18d15780-76cc-11e…
[1]
https://user-images.githubusercontent.com/146040/78461769-21299280-76cc-11e…
[2]
https://user-images.githubusercontent.com/146040/78461779-369ebc80-76cc-11e…
[3]
https://github.com/JeroenDeDauw/Maps/blob/7.17.1/resources/leaflet/LeafletL…
Cheers
--
Jeroen De Dauw | www.EntropyWins.wtf <https://EntropyWins.wtf>
Professional wiki hosting and services: www.Professional.Wiki
<https://Professional.Wiki>
Entrepreneur | Software Crafter | Open Source | Wikimedia | Speaker
~=[,,_,,]:3
Hi,
I've written down some observations, thoughts and ideas for
ResourceLoader's debug mode.
See https://phabricator.wikimedia.org/T85805.
Do you like how it works today? Have suggestions for how it could be
better? Let me know here, or on-task :-)
I plan for it to be an iterative process. Mainly I'm looking to make sure
that we don't diverge the paths if we don't need to, and that if we do
split, that the new path is good enough for most use cases.
-- Timo
The 1.35.0-wmf.26 version of MediaWiki is blocked.[1]
The new version is deployed to group0,[2] but can proceed no further until
these issues are resolved:
* High rate of timeouts on jsonTruncated channel -
https://phabricator.wikimedia.org/T249162
Once these issues are resolved, train can resume. If these issues are
resolved on a Friday, the train will resume on Monday.
Thank you for your help in resolving these issues!
-- Your humble train toiler
[1]: https://phabricator.wikimedia.org/T247773
[2]: <https://tools.wmflabs.org/versions/>
--
Dan Duvall
Senior Software Engineer, Release Engineering
Wikimedia Foundation <http://wikimediafoundation.org>
Hi,
for HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-04-01
Željko
--
= 2020-04-01 =
== Callouts ==
* Release Engineering
** [All] Review guidance at [[wikitech:Deployments/Covid-19]] and Code
Deployment Office Hour at 17:00UTC in #wikimedia-office
== Product ==
=== iOS native app ===
* Updates:
** 6.6 release out on public beta (mobile-html integration) -
[[phab:project/view/4273]]
*** bug fixing and working towards code freeze on that
=== Android native app ===
* Updates:
** Beta candidate with mobile-html and Suggested Edits V4 features is being
tested for a shortly coming release.
** Actively working on tech debt on Android and some analytics work for the
release candidatesCurrent board P: [[phab:project/view/4645/]]
=== Web ===
* Updates:
** Summary: Vue.js iterations planning and continuing desktop improvements
project (DIP).
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector
/ DIP)]]:
*** [[phab:T244481|<nowiki>Provide basic FeatureManagement in Vector
codebase</nowiki>]]
*** [[phab:T243281|<nowiki>Build opt-out link for logged-in users with new
vector on</nowiki>]]
*** [[phab:T248399|<nowiki>Document Skin API and their stability, if any
(including Vector)</nowiki>]]
*** [[phab:T246419|<nowiki>Build collapsible sidebar and sidebar button
</nowiki>]]
*** [[Vue.js|Vue.js]] iterations planning.
** Mobile website (MinervaNeue / MobileFrontend):
*** [[phab:T248415|<nowiki>Regression: MediaWiki:Minerva.css is being
loaded on mobile site</nowiki>]]
*** [[phab:T248500|<nowiki>Replace $wgMobileFrontendLogo with
$wgLogos</nowiki>]]
*** [[phab:T248141|<nowiki>Regression: MobileFrontend overrides
non-existent user page handling in desktop view</nowiki>]]
*** [[phab:T248360|<nowiki>Phan warning in
"includes/specials/SpecialMobileDiff.php" - working around by
disabling</nowiki>]]
*** [[phab:T237230|<nowiki>Long edit summary/titles/user breaking AMC
special pages</nowiki>]]
** Miscellaneous
*** [[phab:T248133|<nowiki>WebInstallerOutput should more elegantly load
Vector stylesheet rather than hardcoding a reference</nowiki>]]
*** [[phab:T212521|<nowiki>RFC: Reconsider how we run QUnit unit
tests</nowiki>]]
=== Product Infrastructure ===
* Updates:
** /page/summary endpoint: updating the list of api_urls endpoints.
Removing references to removed endpoints. Is anyone even using this?
[[[phab:T247991]]]
** upcoming OSM data re-import in codfw [[[phab:T243609]]]
** Wikimedia Push Notification Service RFC published: [[phab:T249065]]
=== Structured Data ===
* Updates:
** minor updates to MachineVision
** failed attempt to get wikibase constraints deployed to production
commons :/
** experimenting with Vue.js on frontend
** media search prototype
== Technology ==
=== Fundraising Tech ===
* Updates:
** Fixes to backup payment processor NL bank transfer integration
[[phab:T247885]], [[phab:T248712]]
** Code cleanup and PHP7 updates for payment library
** Looking for alternatives to 3rd party cookies for hiding CentralNotice
banners across projects
** Determining how to get 'drush' on debian buster - might have to bug
releng for repo reset
** Reviewing contractor work on CentralNotice
** Improving email CC, BCC handling in core CiviCRM
** CiviCRM contact deduplication fixes: [[phab:T247377]]
** Testing migrating recurring card donations from main processor's old API
to new API
** Starting work on matching gifts database sync: [[phab:T247878]]
=== Core Platform ===
* Blocking:
** Search Platform: MW Job consumers sometimes pause for several minutes
[[phab:T224425]]
* Updates:
** API gateway designs
** Finished Core REST API MVP epic [[phab:T229662]]
** New backwards-compatible hooks interface coming
=== Engineering Productivity ===
==== Release Engineering ====
* Updates:
** [All] Deployments/Covid-19 [[wikitech:Deployments/Covid-19]]
** Train Health
*** Last week: 1.35.0-wmf.25 - [[phab:T233873]]
*** This week: 1.35.0-wmf.26 - [[phab:T247773]]
*** Next week: 1.35.0-wmf.27 - [[phab:T247774]]
=== Search Platform ===
* Blocked by:
** Core: MW Job consumers sometimes pause for several minutes
[[phab:T224425]]
* Updates:
** Data for events from wdqs needs to be deleted after 90 days and/or
sanitized [[phab:T247034]]
* Stuff no one else cares about:
=== Site Reliability Engineering ===
* Updates:
** TLS 1.3 support being rolled out gradually to cache-upload.
** After some routing changes, traffic to codfw will be routed more
consistently and geographically correct.
