My pleasure 😃

I think this ticket can be marked as resolved as the main issue has been solved (the feature commit has been merged long long ago)

@Urbanecm I think this has been resolved by https://github.com/wikimedia/labs-tools-watch-translations/commit/0e698c31fc2eaa376d39e18d5b287b7fc34dafaf#diff-b91f3d5bd63fcd17221b267e851608e8 and can be closed right?

Alright, just updated the patch to use uca-it-u-kn for napwikisource's $wgCategoryCollation

According to the manual, there are collations specific for each language; nap is not there but I guess the Italian collation should be pretty fine. It would be interesting to know which collation it.wikisource uses.

@StevenJ81 (or someone from Neapolitan Wikisource), Hi, I wanna ask about what $wgCategoryCollation (https://www.mediawiki.org/wiki/Manual:$wgCategoryCollation) will be used in the wiki. I guess it would be the default one (since Neapolitan Wikipedia uses the default one), but .. I'm kinda not sure, that's why I'm asking here to verify about that

@hashar No worries :)

@Legoktm . From (https://phpunit.de/getting-started/phpunit-6.html) since PHPUnit 6 is going to be not supported in February 2019. Would it be a good idea if we start using PHPUnit 7 for this task. (Just a suggestion, honestly I'm not too familiar with php)

I think this can be marked as resolved now. Thanks @Arcayn ! :)

Thanks! I think this can be marked as resolved now

Alright, I'll choose to ignore W504 as wikimetrics's codebase already used "line break after binary operator" style.

@Nuria no problem. This isn't a big issue anyway, this can be fixed very easy anytime.
We only need the answer to this question:

When I fix the W504 it creates some new W503 warnings (https://integration.wikimedia.org/ci/job/tox-docker/4694/console). I think we need to select which rule we wanna comply in this case (W504 or W503). In my opinion, I think it's better to stick with W503 and ignore all W504 warnings. What do you think?

Okay, no problem.

@MarcoAurelio When I fix the W504 it creates some new W503 warnings (https://integration.wikimedia.org/ci/job/tox-docker/4694/console). I think we need to select which rule we wanna comply in this case (W504 or W503). In my opinion, I think it's better to stick with W503 and ignore all W504 warnings. What do you think?

@Shreyasminocha no problem :)

@hashar I wanna work on this, could you give me some examples on how it can be done? (from an old commit, etc)

@Pipix51 are you still working on this? I still can see the GCI task for this task in my GCI interface

@Shreyasminocha are you still working on this? I can see the task for this in my GCI interface (https://codein.withgoogle.com/tasks/4984021353234432/?sp-organization=4956074911203328&sp-search=python). I'm afraid if someone would claim it and you still working in this task

👍 for this. I'd like to support this nomination

In T189982#4757969, @Amire80 wrote:

@rafidaslam , @Zoranzoki21 - your changes were deployed, and you can now see "Wiki Love - API" and "Cirrus Search - API" at https://translatewiki.net/wiki/Special:Translate?filter=!translated&action=translate&group=wikimedia-technical . Thanks for your help! If you can do this for more extensions in the list, it would be very nice ;)

I'll work on this

I'll work on this

I think it's accepted as heading 1, but the text is = Babovky =, am I right?

Btw, @Dvorapa, is header like below is accepted also in Mediawiki?

=<!-- comment-->= Heading ==

I'll work on this (claimed on gci)

I'll do this (claimed on gci)

Yes, I think so.
I think the culprit is the apt, since when I did a chmod a=rwx cache/apt/partial, and then I did a sudo apt-get install git (or any package) in my vagrant through a ssh session, the apt got stuck (didn't prompt a yes/no question), and then when I check cache/apt/partial directory again, its permission changed to 0700 again..

Merged :)

Yes, I think this happened after https://gerrit.wikimedia.org/r/#/c/404448/ merged.

I think it'd be neat if this tool was using a library like GitPython instead of calling git from shell. We could get some advantages like increased test coverages (especially for this task which we need to make a test with repository that the remote upstream is from gerrit and another repository that the remote upstream is not from gerrit such as GitHub). Just a suggestion though.. :)

I'll work on this

@Samwilson is there any another link to the failure log? since I just got No log available. in those 3 links..

@jayvdb yes I can.

I've just retested this task.

I've just retested this bug.

@jayvdb Ah, yes, I can reproduce it locally by deleting the apicache directory

In https://travis-ci.org/refeed/pywikibot/jobs/324761540

A possible long term solution for this is https://phabricator.wikimedia.org/T184081