MediaWiki does support now JSON content model files. As far as I remember, it lints the file before saving it so some mistakes can be avoided. That's what I meant.
Thu, Nov 16
Yep, every time.
Compact language links is special, because we override both the language name and the tooltip from what is present in the interlanguage list.
Wed, Nov 15
git bisect says b8a10e6dcf00da3519ccb9e43d1c2ce0db422557 is the first bad commit.
This only affects the new filters, not the old filters. The issue seems that the URL is not updating when the limit is changed. If I add it manually to the URL it works.
In this screenshot taking in Farsi (fa) language, we see that in the following placed the numerals are not localised:
- The numbers on Y-axis (should use mw.language.convertNumber from MediaWiki)
- The days on X-axis (should likely use a proper date formatting from MediaWiki
- The data on the tooltip (as above)
- The number on the toolip
It's more effort the delete them and they are harmless.
The path is configurable on our side, so feel free to use whatever is simplest.
Tue, Nov 14
Next automatic dump will happen on Friday. I'll assume @ArielGlenn will post an update here after that.
I have accepted the invite. If you are willing, do feel free to give a shot on making the patch, but I just noticed I linked the config for datavalues even though you were speaking of datatypes, which means it needs to be moved from regular mediawiki extensions, which is a bit more complicated than what I said above.
Make sure that @translatewiki GitHub user has push rights to the master? branch of that repository.
There is no "JSON editor". Some work will always be needed to have these even synced to and from in translatewiki.net, even without a special editor.
I am not sure I understand the question. If you are asking about whether the translations should be deleted in translatewiki.net, we never do that.
Mon, Nov 13
contributionsmenu entry point should only be accessible when CX is enabled, hence it is not listed in the campaigns.
I am not sure my fix is enough. What is the best way to test it? Get it merged and SWAT deployed and wait for next run?
Maybe I should add some output the script.
Unfortunately this was not fully resolved yet:
2017-11-13 09:25:45 web1.translatewiki.net translatewiki_net-bw_: Translation service TTMServer problem: (curl error: 28) Timeout was reached [Mon Nov 13 10:25:46 2017] [hphp] [17218:7fcfc87ff700:18538:000001]  \nWarning: Invalid operand type was used: array_merge expects array(s) in /srv/mediawiki/tags/2017-11-13_08:35:02/extensions/Translate/translationaids/TTMServerAid.php on line 77 [Mon Nov 13 10:25:46 2017] [hphp] [17218:7fcfc87ff700:18538:000002]  \nCatchable fatal error: Argument 1 passed to TTMServer::sortSuggestions() must be an instance of array, null given in /srv/mediawiki/tags/2017-11-13_08:35:02/extensions/Translate/translationaids/TTMServerAid.php on line 80
Happened for ULS too: https://integration.wikimedia.org/ci/job/mediawiki-extensions-qunit-jessie/45051/console
@ArielGlenn Is it possible to check which of the export commands this is? Like, if it is the XML version, then maybe I shouldn't spend time looking for streaming json encoders.
Sun, Nov 12
Sat, Nov 11
I have to check how it was done. I suppose serializing into one big JSON (or XML) is problematic. Could use streaming approach and/or split into multiple files.
Fri, Nov 10
There has been no recent changes to the code. 32825933824 is 30G and the latter number is just huge. Might be just regular growth exposing the memory inefficiency that has been present since beginning.
Thu, Nov 9
Any other prefixes missing?
Another problem I observed is that mergeMessageFiles.php doesn't pick up the i18n files from SMW (because of late registration?).
Wed, Nov 8
Still present in master, in fact none of the SMW special pages work at all if $wgShortUrlTemplate is set.
A few more. It wouldn't solve the issue for Northern Sami though.
Tue, Nov 7
The reason is that the language does not meet the default export threshold of 35%. The question is what should we do? Lower the threshold for portals?
This has apparently fixed itself at some point.
It looks like a permanent debug mode has been turned on. @KartikMistry ?
Mon, Nov 6
Some additional observations:
- ULS trigger does not work in mobile view. This requires changes in ULS. A new task?
- In minerva the personal tools are formatted in ugly way. But @Petar.petkovic is working on re-doing them, so I guess that's fine.
I'm declaring my workaround stable for now, and re-purpose this task as general MediaWiki issue.
It turns out the warning is pretty much unrelated to the actual issue that some modules were not marked to be compatible with mobile view. I will fix that first.
Sat, Nov 4
We don't want a separate version of CX that would compete and differ from CX. The only webapp specific feature I can think of is full support for doing work while offline. But offlines requirements are in conflict with how CX works. Anything else should be possible to improve in CX itself.
Yeah it's RTL ui selecting Finnish pages.
Fri, Nov 3
Is this the expected display?
Memcached seems to be filling much slower with memcached-pecl, unless something else changes. Will consider this fix stable if it runs without any issues to next week.
Thu, Nov 2
I would recommend filing a separate issue for each point and linking them from here.
I made few tweaks to the task in codein.
@Petar.petkovic I believe this is coming from your patch. Want to have a look at it?
Wed, Nov 1
Nothing to do from our side, as far as I can see.
One possible cause is https://gerrit.wikimedia.org/r/#/c/383918/
Those PHP errors went away when I restarted memcached – I suppose those clients use a slightly different way to serialize data.
Tue, Oct 31
@Nemo_bis Are you planning to create the babels?
The calls to Yandex are made server side. You would need to add debug statements to lower level of code to see the actual URL and parameters.
@Volker_E The things in the task description are still valid. Some cleanups have been done but the major things are still pending.