[19:12:09] SMalyshev: hey! i saw you enabled ElasticSearch on Wikidata! Cool! [19:12:33] can you drop a note about this to the wikidata mailing list, and tell people where to report any issues? [19:34:11] DanielK_WMDE: I've added it to the news. I wondered if I should write on the list since it was supposed to be birthday thing? [19:49:12] DanielK_WMDE: If you're still about...just spotted T179038 in wmf.5 [19:49:12] T179038: DomainException / NullResult holds no constraint - https://phabricator.wikimedia.org/T179038 [19:51:49] no_justification: Lucas is probably the go to person for this. Assigned him. [19:52:58] ty [19:58:18] Also spotted Warning: Wikibase\Rdf\DispatchingValueSnakRdfBuilder::getValueBuilder: No RDF builder defined for data type globe-coordinate nor for value type bad. [Called from Wikibase\Rdf\DispatchingValueSnakRdfBuilder::getValueBuilder in /srv/mediawiki/php-1.31.0-wmf.5/extensions/Wikidata/extensions/Wikibase/repo/includes/Rdf/DispatchingValueSnakRdfBuilder.php at line 75] in [19:58:20] /srv/mediawiki/php-1.31.0-wmf.5/includes/debug/MWDebug.php on line 309 [19:58:53] Unrelated: Fatal error: Class undefined: ProofreadPage\Index\MultilineTextInputWidget in /srv/mediawiki/php-1.31.0-wmf.5/extensions/ProofreadPage/includes/index/EditIndexPage.php on line 107 [19:58:58] James_F: I thought we fixed that last one ^ [19:59:30] no_justification: We… did? [19:59:44] Well there was a similar thing with multiline input widget things [19:59:44] no_justification: Ultra-cached PHP somehow? [20:00:12] Definitely more than one apache reporting it [20:00:16] You sure? [20:00:16] https://github.com/wikimedia/mediawiki-extensions-ProofreadPage/commit/1b12648e0e5a52ce31248235d390b4e8d635f42e [20:00:16] So not like a single one outta sync [20:00:22] Came in 6 days ago [20:00:40] Phpstorm can't seem to find it in the extension/core [20:01:21] Has that version of OOJS/UI been deployed? [20:01:23] I can only see a js MultilineTextInputWidget [20:01:40] no_justification: Yeah, two weeks ago. [20:02:25] Reedy: Github says that commit's only in master [20:02:57] Specifically it's in OOjs UI v0.23.4 which was merged into MW master on 2017-10-11. [20:03:20] no_justification: You back-ported it? [20:03:36] no_justification: https://gerrit.wikimedia.org/r/#/q/I81e50d9585bac8323adf7b8fe7f2e0f662c556e6 [20:03:50] https://github.com/wikimedia/mediawiki-extensions-ProofreadPage/commits/wmf/1.31.0-wmf.5 [20:03:52] It's in .5 [20:03:53] Ok yeah it's in wmf.5 [20:03:57] So it's in wmf.4/.5 and master. [20:04:05] We're not running wmf.3 somewhere? [20:04:06] And .4 [20:04:06] https://github.com/wikimedia/mediawiki-extensions-ProofreadPage/commits/wmf/1.31.0-wmf.4 [20:04:09] But...it can't find the code? [20:04:35] Did it get reverted in production somehow? [20:05:03] Hah [20:05:05] ProofreadPage\Index\MultilineTextInputWidget in /srv/mediawiki/php-1.31.0-wmf.5/extensions/ProofreadPage/includes/index/EditIndexPage.php on line 107 [20:05:16] Namespace code lacked a use [20:05:25] Ooooh. [20:05:26] Meh. [20:05:44] One second. [20:05:58] There's already OOUI imports at the top too! [20:07:33] no_justification: https://gerrit.wikimedia.org/r/386478 [20:09:14] +2'd and cherried to wmf.5 [20:24:27] James_F: Live. Seems to be disappearing from logs [20:24:51] Ouch: Notice: Cannot access property on non-object in /srv/mediawiki/php-1.31.0-wmf.5/extensions/GlobalBlocking/includes/api/ApiGlobalBlock.php on line 53 [20:25:30] 53, 56, 59 [22:50:51] legoktm: Thinking about a sniff that would require a PHPUnit test*() method to have a doc block with at least 1 @covers. [22:50:52] Thoughts? [22:51:15] .. optionally tolerated if the class has one already. [22:51:35] Just finding quite often that when fixing code coverage for an older area, there are actually tests, but just forgotten to add @covers [22:52:37] opt-out via @coversNothing, although I don't think we need it. We typically do include coverage from integration tests, but when strict we'd specify only the entry method, not the indirect ones. [22:58:07] Krinkle: how do you determine whether the class is a phpunit test? [22:58:15] otherwise that seems like a decent idea to me [23:55:08] should each separate test have @covers? [23:55:49] I put it on class but specific tests would probably just duplicate the class one often. They frequently use more than one method from the class...