[02:02:36] <wikibugs>	 10Africa-Wikimedia-Developers, 10MediaWiki-Special-pages, 10Easy, 10Patch-For-Review: Special:Version produces warning when there's an open_basedir restriction, when checking for $wgGitBin - https://phabricator.wikimedia.org/T74445#4021536 (10RazeSoldier) I push a patch. https://gerrit.wikimedia.org/r/#/c/...
[11:29:16] <wikibugs>	 10Africa-Wikimedia-Developers, 10Developer-Relations: Africa Wikimedia Developers Leaderboard Monthly Statistics for the year 2018 - https://phabricator.wikimedia.org/T184192#4021969 (10rosalieper)
[12:57:45] <wikibugs>	 10Africa-Wikimedia-Developers, 10Developer-Relations: Africa Wikimedia Developers IRC general meeting #4 - https://phabricator.wikimedia.org/T185803#4022033 (10D3r1ck01)
[20:29:29] <d3r1ck>	 africanhope: Welcome :)
[20:29:47] <d3r1ck>	 Zppix: Hey! :)
[20:29:54] <africanhope>	 d3r1ck: Welcome man
[20:30:34] <africanhope>	 lol I meant Hello man*
[20:30:41] <d3r1ck>	 Yup!
[20:30:47] <d3r1ck>	 Got a patch to review :)
[20:30:56] <africanhope>	 on Github right?
[20:31:00] <d3r1ck>	 yes! :D
[20:31:26] <africanhope>	 I am it right now, we should speed things up and get the repo moved onto gerrit :)
[20:32:28] <africanhope>	 by the way thanks for the unit test you added
[20:33:42] <d3r1ck>	 africanhope: Yup!
[20:33:57] <d3r1ck>	 I'm still adding unit test, we should have 100% coverage :D
[20:35:05] <africanhope>	 d3r1ck: You moved several steps ahead, I was about to ask you about test coverage for methods others than routes handlers
[20:35:33] <africanhope>	 I Just refreshed the PR and saw your latest commit
[20:36:06] <d3r1ck>	 Yeah, I'm adding tests for UD methods now
[20:38:35] <africanhope>	 What do you mean by UD?
[20:38:56] <africanhope>	 Should I review and merge it or wait for additional commits?
[20:43:01] <d3r1ck>	 User Defined :)
[20:43:11] <d3r1ck>	 Just wait for 1 more commit for now :D
[20:43:24] <d3r1ck>	 If the PR is not good, you can request for improvement or decline it :D
[20:47:23] <africanhope>	 Duh! already merged
[20:49:51] <d3r1ck>	 Another up and running, just 1 commit actually africanhope 
[20:49:53] <d3r1ck>	 :D
[20:50:00] <africanhope>	 d3r1ck: Seen one more PR, are you done?
[20:50:05] <d3r1ck>	 Ops, I've already merged it :D
[20:50:13] <africanhope>	 lol, np
[20:50:15] <d3r1ck>	 It's okay, sorry to bother you :)
[20:50:28] <d3r1ck>	 So did you manage to run the unit tests?
[20:50:39] <d3r1ck>	 I'm using "nosetests"
[20:50:45] <d3r1ck>	 africanhope: ^
[20:51:57] <africanhope>	 not yet, still looking at the Issues created
[20:52:04] <d3r1ck>	 Ohh okay! :)
[20:52:28] <d3r1ck>	 africanhope: But do you think the UnitTests is a good idea?
[20:52:52] <africanhope>	 You mean python3-nose dependency or the Unit test concept?
[20:53:27] <africanhope>	 as for the concept it's more than important but a matter of good practice, and I am more than happy to see that implemented in this project
[20:54:35] <d3r1ck>	 :)
[20:54:43] <d3r1ck>	 So I was talking about the application having some unit tests
[20:55:08] <d3r1ck>	 That will save us some time in the future when adding more features and you know, testing the application in case of any issues that arise :)
[20:55:43] <africanhope>	 Yes having that is a great idea, it should even serve as a common practice for future projects
[20:58:53] <d3r1ck>	 Okay, thanks for endorsing :)
[21:02:24] <africanhope>	 you've done great on the issues
[21:02:40] <africanhope>	 I'll take time tomorrow to add few that I have in my mind
[21:05:45] <d3r1ck>	 Okay! Feel free to add as more issues as you want
[21:05:59] <d3r1ck>	 So about the Gerrit repo, when do you think we should do it?
[21:06:03] <d3r1ck>	 Later?
[21:06:06] <d3r1ck>	 africanhope: ^
[21:15:30] <africanhope>	 d3r1ck: I think we'll fix the 6 existing issues and move the repo to Gerrit
[21:16:22] <africanhope>	 I won't add extra issues, or many only one or two
[21:17:23] <d3r1ck>	 Okay cool :)
[21:27:34] <d3r1ck>	 africanhope: Maybe you can update the app on Toolforge?
[21:34:40] <africanhope>	 yeah I'll do a pull
[21:36:42] <africanhope>	 pulled and restarted k8s
[21:37:01] <africanhope>	 by the way, is it necessary to restart k8s?
[21:50:00] <d3r1ck>	 I think no need for that
[21:50:19] <d3r1ck>	 paladox: Does one need to restart the k8s service when new files are added to a directory?
[21:50:24] <d3r1ck>	 Zppix: ^
[21:50:37] <paladox>	 d3r1ck hmm, maybe, though not sure.
[21:50:41] * paladox dosen't use k8s
[22:01:41] <d3r1ck>	 Okay! thanks paladox 
[22:04:21] <Zppix>	 Yes
[22:04:29] <Zppix>	 d3r1ck: 
[22:04:43] <d3r1ck>	 Thanks Zppix 
[22:14:46] <Zppix>	 np
[22:16:36] <d3r1ck>	 africanhope: Zppix answered your question :)
[22:16:54] <Zppix>	 africanhope:  a quick way to do it is kubectl delete pods --all
[22:17:30] <africanhope>	 Zppix: thank you
[22:18:13] <africanhope>	 the thing is last time I ran into a situation where jinja files (HTML) did not seem updated
[22:18:38] <africanhope>	 I had to restart k8s, but was not sure k8s was to blame