[00:00:11] it has /$ZUUL_PROJECT -m checkstyle [00:00:13] which becomes /mediawiki/extensions/PdfHandler -m checkstyle [00:00:28] oh [00:00:29] that's inside the docker container [00:00:31] mounting [00:00:38] mhm [00:00:54] src/extensions/$EXT_NAME/... should work [00:01:56] https://gerrit.wikimedia.org/r/#/c/429367/3/jjb/mediawiki-extensions.yaml [00:07:48] :D [00:07:51] are you going to deploy it? [00:08:41] I... can [00:09:00] * Reedy looks for the instructions again [00:11:37] * Reedy waits for ../.local/bin/jenkins-jobs --conf etc/jenkins_jobs.ini test config/ -o output/ [00:12:14] if [ ! -f "src/extensions/$EXT_NAME/tests/phan/config.php" ]; then [00:12:14] echo "Phan config not found\n" [00:12:14] exit 0 [00:12:14] fi [00:12:53] seems right [00:13:16] mmm [00:14:04] * Reedy rechecks some jobs [00:15:08] 00:14:50 [mwext-php70-phan-docker] $ /bin/bash -eu /tmp/jenkins4697845656797878585.sh [00:15:08] 00:14:50 + '[' '!' -f src/extensions/PdfHandler/tests/phan/config.php ']' [00:15:08] 00:14:50 + echo 'Phan config not found\n' [00:15:08] 00:14:50 Phan config not found\n [00:15:09] 00:14:50 + exit 0 [00:15:11] 00:14:50 Finished: SUCCESS [00:15:14] :D [00:15:22] Not really a success [00:15:25] But we'll take it ;) [00:15:28] test a job that should ran phan too? [00:15:44] I've rechecked brion's master patch too [00:15:55] I did think of htat :P [00:16:19] https://integration.wikimedia.org/ci/job/mwext-php70-phan-docker/5475/console [00:16:38] LGTM [00:16:45] :D [00:16:53] \o/ [00:17:06] Could almost switch the phan job on everywhere now ;) [00:17:18] phan-tastic! [00:25:37] brion: I did the other backports, but as they're slightly modified, I'm not self merging them [00:25:45] Did 1.31 as it's the same as master [00:25:51] https://gerrit.wikimedia.org/r/#/q/Ib4ee9cf12ac04304c576087727eff5dc521ae751 [00:25:59] sounds good [00:26:01] thanks! [00:28:25] i'll test and merge down the branch ones tomorow [14:43:04] hello everyone.. If anyone has a few minutes, this PR needs some love. It modify blocks/autoblocks. Any comment/suggestion is more than welcome [14:43:06] https://gerrit.wikimedia.org/r/#/c/425313/ [18:51:04] dmaza: in https://gerrit.wikimedia.org/r/#/c/425313/10/includes/user/User.php does loadFromSession() still need trackBlockWithCookie()? [18:59:24] I don't like the list of open bugs for 1.31 still :\ [18:59:32] A little much for me to cut a non-broken rc [19:01:31] MaxSem: well that was one of my questions in gerrit. We were setting the cookie before on every session load for logged in users. But I think it is an overkill [19:46:02] dmaza: so right now the workflow is like: you get cookies when you try to edit, create an account AND whenever MW decides it needs a session [19:48:08] yes [19:49:07] MaxSem: I don't think we need to set the cookie when we load from session, 'cause we don't use the block anywhere unless you either try to edit or create an account [19:50:34] Unless I'm missing something something, I believe we can remove it from loadFromSession. [20:11:33] dmaza: I think removing it would also resolve T180050 [20:11:33] T180050: [Russian] [Chinese] PHP Warning: Recursion detected in RequestContext::getLanguage MW v1.31.0-wmf.6 - https://phabricator.wikimedia.org/T180050 [20:36:55] anomie, MaxSem: I'm gonna go ahead and remove it. Is there anywhere else where I would need to set the cookie other than EditPage->edit() and SpecialCreateAccount->checkPermissions() ? [20:48:02] * MaxSem scratches head [21:13:58] dmaza: honestly, I'm not sure myself: ideally, we would want this on every blocked check - however, lookig at the code, adding something like that e.g. to Title::checkUserBlock() would be too messy due to a [21:14:03] mix of concerns [21:19:07] MaxSem: and even then Title::checkUserBlock() is probably not called when creating an account [21:19:15] ¯\_(ツ)_/¯ [21:19:31] what is called there, then? [21:19:45] it should be checking blocks there… [21:19:51] where? [21:20:15] when (attempting to) create an account [21:21:26] AuthManager->checkAccountCreatePermissions() [21:21:34] among other things [21:23:02] ideally, something like this that sets a cookie should be in a middlewhere before the response is delivered. I guess that MW that would mean on a hook somewhere right before rendering the page