14:28:47 <karsten> #startmeeting metrics team 14:28:47 <MeetBot> Meeting started Mon Aug 27 14:28:47 2018 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:28:47 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:28:52 <karsten> irl: around? 14:28:58 <irl> yes 14:29:10 <karsten> cool! let me put some topics on the pad.. 14:30:49 <karsten> do you have anything else? 14:31:02 <irl> ok, i do not have any topics to add unless you wanted to talk about anything in the big review 14:31:43 <karsten> no need to talk more about the big review, unless there's more that needs discussion. 14:31:52 <karsten> great that you did the review this fast! 14:32:04 <irl> it was just the </p> thing but it's not a blocker 14:32:11 <karsten> other than that, I think that we'll have to do some serious testing when putting out the next releases. 14:32:47 <karsten> all in all I think the code is in better shape now. 14:32:50 <irl> yep 14:33:14 <karsten> alright, then let's go through my topics. 14:33:26 <karsten> * metrics-team post with bug report (karsten) 14:33:33 <karsten> there was a bug report on the list. 14:33:39 <irl> about searching for host names? 14:33:46 <karsten> yes. 14:33:51 <irl> it's the same issue as #27187 14:33:52 <karsten> I only looked briefly. it looked real. 14:33:56 <irl> it is real 14:33:57 <karsten> ah! 14:34:07 <karsten> okay, I did not make that connection. 14:34:18 <irl> the details documents are all correct now and have all the details, the summary document is not updated and so the indexer is not updated 14:34:33 <karsten> okay. do you mind replying on the list, pointing to the ticket? 14:34:47 <irl> ok, i will do that once i've added the info to the ticket also 14:34:54 <karsten> perfect! 14:35:07 <karsten> * instant vs localdatetime vs zoneddatetime (karsten) 14:35:16 <karsten> so, last week I briefly looked into java 8 changes. 14:35:26 <karsten> one thing I did not touch is related to dates/times. 14:35:44 <karsten> the blocker was that I wasn't sure whether zoneddatetime is even the right type. 14:35:55 <karsten> previously, iwakeh suggested localdatetime. 14:36:07 <karsten> but I'm also not sure whether we'd be better off using instant. heh. 14:36:18 <irl> localdatetime is definitely wrong because it's ambiguous 14:37:01 <irl> i guess there are hard questions we need to answer 14:37:03 <karsten> yes, that sounds plausible. though I briefly thought about documenting that we're always using UTC as timezone. 14:37:08 <irl> does tor believe in leap seconds? 14:37:33 <karsten> I don't know. 14:38:00 <irl> instant seems to use the "java time" which is defined differently to UTC 14:38:11 <karsten> oh? 14:38:27 <karsten> I thought it just uses UTC and nothing else. 14:38:35 <karsten> but, I could be wrong. 14:38:41 <irl> in UTC there are days with leap seconds where actually seconds are shorter in time than other days 14:39:06 <irl> ntp will do this for you but some people prefer to just have clocks jump a second instead 14:39:29 <karsten> okay, I was thinking about how to approach this. 14:39:37 <karsten> (I did not intend to resolve this today.) 14:39:58 <karsten> would it help to go through the codebases and find all different ways how we're using date/time data? 14:40:08 <irl> i think a tor-spec laywer needs to see what tor believes and does not believe about time 14:40:52 <karsten> so, okay, assuming we do that, 14:40:56 <irl> but yes, a list of how we currently use time is helpful too 14:41:07 <karsten> we'll still have to decide what to do with descriptors/data that don't come from tor. 14:41:21 <karsten> we could argue that those follow tor, though. 14:41:47 <karsten> so, how about I make such a list, and then we discuss next time whether/how we want to involve network team folks? 14:42:11 <irl> there should be mappings from one time into another, but ideally we would convert to one canonical time once it enters tor metrics 14:42:24 <irl> that sounds like a good plan 14:42:33 <karsten> okay. 14:43:35 <karsten> alright, 14:43:37 <karsten> * exonerator release with #27266 (karsten) 14:43:57 <karsten> once this ticket is reviewed (no big rush), we'll have to put out a release. 14:44:12 <karsten> this will also be the first release to ship with all those little code changes. 14:44:21 <karsten> when is a good time to make this release? 14:44:59 <irl> tomorrow is probably the only full day i have this week, wednesday will be rushed and then thursday i'm on the train to emfcamp 14:45:11 <irl> i can review the change this afternoon and we can release tomorrow? 14:45:18 <karsten> sure, if that works for you, great! 14:45:21 <irl> cool 14:45:49 <karsten> * planned exonerator database change (karsten) 14:45:54 <karsten> this is mostly a heads-up for now. 14:46:05 <karsten> I'm still working on the big exonerator database schema update. 14:46:14 <irl> for performance? 14:46:24 <karsten> smaller database and performance, yes. 14:46:31 <irl> right ok 14:46:44 <karsten> the migration script still contains a bug that I just found. 14:47:06 <karsten> I also sent a list of questions to Sebastian who wrote most of the original changes. 14:47:30 <karsten> after that I'll do another test run here, which can easily take days. 14:47:56 <karsten> one question is: would you want to do a review while the test is running or afterwards? 14:48:06 <karsten> it's not a tiny change. 14:48:33 <karsten> or would you prefer Sebastian to do the review, assuming that he has time to do it? 14:48:46 <irl> i guess as soon as it's something that can be reviewed you can set it to needs_review and then i can pick it up 14:49:01 <karsten> sounds good to me. 14:49:07 <irl> i'm not familiar at all with exonerator's codebase or schema so it would be good if Sebastian can take at least a quick look 14:49:16 <karsten> okay. 14:50:23 <karsten> * planned onionoo 7.0 release next week (karsten) 14:50:36 <karsten> we said after Sep 3. 14:50:46 <karsten> which can easily be a few days later. 14:50:54 <karsten> in any case, that's probably next week. 14:51:25 <irl> i will still be in a field on sep 3 14:51:43 <karsten> no worries. is the second half of next week better? 14:51:55 <irl> sep 7 would be my first full day back but i may be catching up still if anything urgent has come up 14:52:10 <karsten> okay, then let's maybe aim for the week after. 14:52:12 <karsten> no rush here. 14:52:48 <irl> we could do monday 10th sep 14:53:05 <karsten> okay. 14:53:19 <karsten> are we going to have a team meeting next thursday, by the way? 14:53:25 <karsten> or should we move that? 14:53:56 <irl> i think i will be on the train back 14:54:03 <irl> so probably we should move it 14:54:18 <karsten> by one day to friday? 14:54:26 <irl> sounds good 14:54:40 <karsten> same time? 14:54:43 <irl> yep 14:54:50 <karsten> great! 14:54:57 <karsten> last topic: any volunteers around? 14:55:15 <karsten> and by that I mean: any volunteers who mentioned on a mailing list that they'd like to volunteer? 14:55:40 <karsten> if not, that's fine. it was very short notice. 14:55:55 <irl> regarding python 14:56:02 <karsten> yep? 14:56:08 <irl> there is a ticket about adding support for collector's index.json to stem 14:56:23 <irl> if someone wants to do metrics and really wants to also do it in python, that would be a good ticket to take on 14:56:32 <irl> i can see it being useful to researchers 14:56:40 <karsten> good idea. 14:56:49 <karsten> do you have the number? 14:57:16 <irl> #17979 14:57:49 <irl> atagar even considers the lack of this module a defect, which is nice (: 14:58:03 <karsten> heh. 14:58:14 <karsten> alright. I don't have anything else. 14:58:35 <karsten> what about you? 14:58:57 <irl> nothing more from me 14:59:14 <karsten> alright! 14:59:38 <karsten> then let's talk more next week. (and do the release tomorrow, asynchronously.) 14:59:47 <karsten> thanks, and bye! 14:59:51 <irl> bye! 14:59:52 <karsten> #endmeeting