[13:02:33] (CR) QChris: Add scheduler mode to wikimetrics (7 comments) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/111623 (owner: Milimetric) [13:21:30] (CR) Nuria: Add scheduler mode to wikimetrics (1 comment) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/111623 (owner: Milimetric) [13:29:55] (CR) Nuria: [WIP] Run recurring reports using the scheduler (4 comments) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/112165 (owner: Milimetric) [14:00:38] average, csalvia: We're in the appear.in hangout for standup [14:30:18] csalvia: nuria: I froze on the hangout [14:30:25] sorry, but we can finish talking here quickly [14:30:37] so nuria, you were saying it's ok if I comment out the delete stuff? [14:30:37] ok, very well [14:30:57] sure, we can "move it" to a different changeset [14:31:06] so as to reduce scope of the change [14:31:21] ok, cool [14:31:56] so this change is supposed to make sure that the recurrent / public notions make sense together [14:32:03] I think that means we need to merge csalvia's change into it [14:32:04] yes [14:32:11] and that they rae tested [14:32:13] but besides that, I think we're done [14:32:16] oh right [14:32:20] and add a shitton of tests :) [14:32:25] csalvia did you tested your change in vagrant? [14:33:24] what about the other two changesets you have? [14:35:00] sorry milimetric, what about the other two (smaller) changes? [14:35:40] I think those are more or less fine. After qchris gets done reviewing them, we can just merge those [14:36:20] but i mean, i don't think they're missing anything fundamental, probably just need to be cleaned up [14:37:06] No need to wait for me. If someone else reviews stuff, it would make my life simpler. [14:37:23] So just review and merge! :-) [14:37:31] the only remaining thing on those (that I can see) [14:37:47] is that they are creating files on source [14:37:59] which will also not work in production [14:38:19] but I think qchris had another work item [14:38:30] oh, the scheduled_tasks file? [14:38:55] of making that very change work in vagrant/puppet setup [14:38:55] yeah, the path to that is configurable but we have to add the setting to the puppet config [14:38:55] yes [14:39:17] we basically just have to update the puppet template for the queue config to match the one in the Change [14:40:40] yes, that and create the directory where scheduling would go via puppet [14:41:02] then, are we doing that with your change or after? [14:41:47] well isn't it a separate change anyway nuria? I mean, it's a puppet change that can't be linked to this, right? [14:42:56] (PS31) Milimetric: [WIP] Run recurring reports using the scheduler [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/112165 [14:43:00] (CR) jenkins-bot: [V: -1] [WIP] Run recurring reports using the scheduler [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/112165 (owner: Milimetric) [14:43:35] weird, flake8 shows fine on my machine but jenkins -1ed me [14:44:22] well, nuria, I pushed my latest to that change, so feel free to clean up / hack at it, it's all yours until you're done for today [14:44:29] milimetric see this one: https://gerrit.wikimedia.org/r/#/c/111623/13/wikimetrics/configurables.py [14:44:51] but push what you have at the end and I'll try to finish it tonight like I promised :) [14:46:03] Will do. [14:46:49] As for teh other change you are right, rest of changes are on puppet minus the one mentioned by christian on configurables.py [14:46:53] hm, that's an interesting point, nuria you meant qchris's comment on that configurables? [14:47:03] right [14:47:21] so if we put that in config, it means we have to somehow put that big dictionary into yaml and read it out properly [14:47:23] does that work? [14:49:40] like, I mean we'd need this in yaml somehow: [14:49:41] CELERYBEAT_SCHEDULE = { 3 [14:49:41] # Executes every day at midnight 4 [14:49:41] 'update-daily-recurring-reports': { 5 [14:49:41] 'task': 'wikimetrics.schedules.daily.recurring_reports', 6 [14:49:42] 'schedule': crontab(minute=0, hour=0), 7 [14:49:44] }, 8 [14:49:46] } [14:50:15] mmm.. [14:51:06] ok, gotta get ready to walk to the office, but i'll leave irc on [14:51:18] thanks for the comments qchris, I'll try to address today [14:51:23] ok, let's tak later [14:51:38] milimetric: yw :-) [14:52:31] milimetric: about the yaml thing above. You mean my request about reordering so we can get rid of the coupling? [14:53:22] not reordering, you mentioned trying to put CELERYBEAT_SCHEDULE in the configuration so that it's loaded and we don't have to load it in code [14:54:01] I admit that would be better but I'm not sure how to technically do it [14:54:38] Technically, it could just be merging dictionaries. [14:54:56] First loading some (maybe hard-coded) defaults into the dict. [14:55:10] Then merging in user supplied key/values. [14:55:24] Then merging in overrides. [14:56:02] (Currently we have loading user supplied values. Then merging overrides. Then merging the schedule) [15:01:41] oh, ok, so we'd still have code interact with the CELERYBEAT_SCHEDULE setting, but in a generic way and not a specific way [15:01:45] cool, I like it, will make it so [15:02:02] the other part I wasn't sure I understood was the scheduled_tasks controversy :) [15:02:58] so, I'll fix the gitignore to only expect those files at the root of the repository, but why is that "poisoned"? wouldn't putting them somewhere else in the filesystem have to necessarily assume some file permissions we're not guaranteed to have? [15:10:58] milimetric: About scheduled_tasks. Yes, having those files in a well defined place would be great. [15:11:19] like, is ./scheduled_tasks ok? [15:11:22] I am not sure root would be the best place. Some projects have a special directory where generated files go to. [15:11:26] oh ok [15:11:28] i see [15:11:39] that's a good idea, let's make a generated folder [15:11:39] Then the main directory and the sources etc stay clean [15:11:52] i like it, we do that [15:12:09] So if some process dies horribly, you can just kill the generated directory, and you are back to normal. [15:12:12] Cool \o/ [15:12:15] Thanks. [15:12:31] yeah, in general if I'm doing something dumb like this you can feel free to suggest a solution [15:12:37] it's probably because I don't know any better :) [15:12:56] :-P [15:12:57] ok, gonna go grab breakfast and I'll be back online in an hour or so [15:13:02] do you guys need anything from me? [15:13:03] Meh. Both solutions work. [15:13:14] Enjoy your breakfast! [15:13:26] k :) [15:34:15] (PS1) Nuria: Adding coding guidelines to README [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120541 [15:34:19] (CR) jenkins-bot: [V: -1] Adding coding guidelines to README [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120541 (owner: Nuria) [15:34:42] opppps sorry [15:36:41] (Abandoned) Nuria: Adding coding guidelines to README [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120541 (owner: Nuria) [15:38:42] (PS1) Nuria: Adding coding guidelines to README.md file [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120542 [15:41:36] milimetric: a generated directory sounds good. Same aproach we are using with public reports [15:42:11] I agree with qchris, we should not be creating files on source [16:34:31] Hello. I was looking for some stats on a beta feature usage across all wikis(or as many as possible). Is there anything for that? [16:41:56] (CR) Nuria: [WIP] Run recurring reports using the scheduler (1 comment) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/112165 (owner: Milimetric) [16:42:39] hi nuria [16:42:41] we're in the office [16:43:41] ok, very well. I updated README , send CR to qchris and looked at your patch #31. from what i can see what is left to be done is writing tests [16:44:09] is there something else you had in mind? [16:46:15] nope, just checking if you want to hang out before you leave for the day [16:46:58] thanks for taking a look at #31, I'll write tests all day :) [17:34:32] hi, is anyone around that can help me with a sqlalchemy/database problem? [17:45:56] (PS2) Nuria: Adding coding guidelines to README.md file [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120542 [17:49:48] Hi, terrrydactyl with wikimetrics? [17:50:42] yeah. i'm getting some trouble with filtering through my tables [17:50:43] https://gerrit.wikimedia.org/r/#/c/119343/3/tests/test_controllers/test_cohorts.py [17:50:57] i get an ObjectDeletedError when i try to run my tests. [17:52:04] any ideas nuria? [17:54:07] milimetric: is all of limn and wikimetrics now fully migrated to eqiad labs? [17:54:43] terrrydactyl [17:55:02] you have a missmatch between the data you shold in your orm until you commit your session [17:55:10] and what is on the db [17:55:28] I think it will help to separate the code a little bit and test in smaller units [17:55:49] like separate controller logic from storage logic and test those separately 1st [17:56:32] yes ottomata, all migrated [17:57:09] nuria: do you mean deleting each element in a separate function and testing that? [17:57:49] terrrydactyl actually separating your testing logic in smaller units [17:58:03] but not on separate functions [17:59:10] the current testing logic is to test if the cohort is deleted if there is an owner and no viewers, test if cohort i deleted if there is an owner and viewers, and test if cohort is deleted from a viewer's personal list. i'm not sure how you mean to separate it out more. [17:59:44] sorry, let me rexplain: so you are not testing the controllers and storage at the same time [18:00:18] just test storage operations on db separated from what is going on at the controller layer, amkes sense? [18:00:23] *makes sense? [18:01:54] yeah i think so [18:02:00] let me mull over it for a bit [18:03:33] i will be offline but dan is in SF , he can help you to separate logic a bit which will uncover where is the error coming from [18:07:12] okay, thanks nuria [18:17:38] milimetric: just to be double sure, it is ok to delete the pmtpa instances, right? [18:56:19] anyone remember the URL to the page explaining the sampled requestlogs format? [18:57:30] milimetric, around? [18:57:35] the analysts/researchers are grabbing lunch [18:58:15] hey Ironholds [18:58:20] yes, we're just wrapping up a meeting [18:58:25] let's all do lunch [18:58:39] ottomata: sorry, in meeting but yes, safe to delete all instances, I care not about any of them [18:58:51] *all pmtpa instances :) [19:01:31] Ironholds: found it [19:01:31] https://www.mediawiki.org/wiki/Analytics/Kraken/Data_Formats#Web_Request_Format [19:02:59] ottomata, ta! [19:03:01] milimetric, cool! [19:19:01] DarTar: any news : https://rt.wikimedia.org/Ticket/Display.html?id=6845 ? [20:10:37] matanya: no, I applied for a 1-week extension :p [20:10:51] but I’ll send out a reminder [20:10:55] haven't it passed? :) [20:11:00] hmm I don’t think so [20:11:43] was due to march 13 +7 days = 20 [20:11:50] it is 24 now :P [20:12:42] shite, ok I thought I had it for Wed/Thurs this week [20:14:01] matanya: I’ll send out a reminder in a moment, I am sorry about the delay [20:14:33] no worries, just a friendly reminder [20:17:46] milimetric: can I delete hadoop-test1 and 2, and hypercube? [20:17:52] yes [20:17:57] anyone know anything about foundry or smartdoc instances? [20:18:28] those are the only two instances we have left in pmtpa! [20:20:25] tetragenic! [20:20:46] mutagens cause active genetic damage, tetragens damage an embroyo directly without altering the genetic code [20:20:49] (sorry; debate at lunch) [21:09:38] ottomata: nobody spoke up about foundry or smartdoc, so let's AXE them :) [21:09:55] k i mean, where did they come from? [21:09:56] what are they? [21:09:59] those are ones I didn't know anything bout [21:16:18] Ironholds: I updated the page you got referred to with the maintained version of the webrequest log format: [21:16:19] https://wikitech.wikimedia.org/wiki/Cache_log_format [21:22:11] qchris, thanks! [21:27:09] ottomata: i know nothing about those instances, I looked and couldn't figure out what they were for [21:27:22] k i'll wait and ask in standup tomorrow just in case [21:27:22] I'm certain that if neither you or me care/know about them, we're safe [21:27:27] ok [21:27:29] no reason not to [21:39:29] how's appear.in ? is it stable ? can you guys use it ? [21:39:40] I might jump in too tommorow [21:46:02] matanya: reminders sent, I have one account confirmed for removal, I hope to hear about the remaining ones withint 24-48 hrs [21:54:55] average: Yes, It has been working fine so far (at least for me) [21:55:18] We had the last couple of standup using appear.in, and worked well. [21:55:33] And you can do without Google plugins :-) [21:56:19] very nice :) [21:59:10] thanks DarTar please update that account and i'll preper a patch for it [22:02:23] *the ticket [22:05:51] hey, that'd be awesome average :) [22:06:16] and yeah, so you know the batcave address right? appear.in/wmf-analytics-batcave [22:41:11] halfak: hey there, got a moment? [23:13:06] sumanah, sorry to miss you. What's up? [23:14:03] oh halfak in #wikimedia-research I asked: I could swear that, back in 2011 or 2012, I saw our research about how new people hit Edit, see wikitext, and bounce off. [23:14:23] halfak: And I'm giving a speech tomorrow and I thought I'd mention the bounce rate but I can't find it! [23:14:44] Hmm... Nothing I'm aware of. There could have been user studies that were done before I came on. [23:14:50] Sorry to not be able to help more. [23:15:01] Did you ask DarTar? [23:15:50] hey sumanah [23:15:54] Hi DarTar! [23:16:03] halfak: thanks for the thought! [23:16:10] was that the Trevor experiment? [23:16:33] Could have been [23:17:21] Maybe I've been searching on the wrong keywords, because I do not think I've found it, DarTar, and would welcome any pointers [23:17:50] that was about making the edit icon larger [23:18:17] oh, moving the edit icon to the left -- well, that might help illustrate my point too [23:18:19] but as a result produced some data about the click-through and completion rate [23:18:56] I can try and dig it up, I don’t think it;s on Meta [23:21:04] https://meta.wikimedia.org/wiki/Change_to_section_edit_links [23:21:15] "In 2009, the Wikipedia Usability Initiative proposed an approach where section edit links would be "moved next to the title" and icon would be added. Years later this was tested on a subset of all anonymous or registered editors to English Wikipedia, with promising results: the number of clicks on section edit links increased by 116%!" [23:25:16] https://meta.wikimedia.org/wiki/Research:Section_edit_modification [23:25:22] thanks DarTar, I think I can use this [23:27:58] sumanah: yes, keep in mind that was never run again as a controlled test in Growth/E3, it’s something I feel we should try to do at some point [23:28:49] and assuming Growth (or VE or whoever wants to test any modification of the UI) has bandwidth [23:29:15] Right, got it [23:33:39] (CR) QChris: [C: -1] Adding coding guidelines to README.md file (15 comments) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/120542 (owner: Nuria) [23:34:38] qchris: go to sleep! :) [23:34:43] man, you work way too hard [23:34:58] Argh ... it's late. You're right. [23:35:03] :-) [23:35:09] Ok. You convinced me. [23:35:13] Good night. [23:35:45] (PS14) Milimetric: Add scheduler mode to wikimetrics [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/111623 [23:35:47] (CR) jenkins-bot: [V: -1] Add scheduler mode to wikimetrics [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/111623 (owner: Milimetric) [23:36:32] (CR) Milimetric: "patchset 14 addresses the things I claim to address in these comments." (9 comments) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/111623 (owner: Milimetric)