08:00:06 #startmeeting horizon 08:00:07 Meeting started Wed Apr 20 08:00:06 2016 UTC and is due to finish in 60 minutes. The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:08 derp 08:00:11 The meeting name has been set to 'horizon' 08:00:32 o/ derp 08:01:22 o/ 08:01:54 Quiet meeting :) 08:02:11 so, who's excited about next week? :-) 08:02:38 The summit schedule link is in the Horizon room topic; if you haven't seen it yet then https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Horizon%3A 08:02:41 not me :/ 08:02:50 ah, no :-( 08:02:52 r1chardj0n3s: Least tactful question ever 08:02:54 haha 08:02:59 I am the worst 08:03:29 so, I have a patch up to integrate upper-constraints into our tox env 08:03:47 which isn't merged, but would have saved us from novaclient shenanigans 08:03:47 I saw that. Its failing tests right now iirc 08:03:59 anyways, I�m going to use the next week to do some good things in Horizon 08:04:18 and ironically it's failing now because david's novaclient compat patch landed, and we're not compatible with the old, upper-constraints pinned version of novaclient any longer :-) 08:04:29 for example, we almost made integration tests work for Angular content 08:04:37 more specifically, LI wizard 08:04:38 (I'm pretty sure that's why it's failing) 08:04:56 r1chardj0n3s: So, we need to pin our tests to a version of novaclient? 08:04:58 tsufiev: an integration test for Swift UI would be awesome, since people just broke it grrrrrr 08:05:08 r1chardj0n3s, ack 08:05:16 r1chardj0n3s: Yup. The bug report for that swift issue has the guilty patch I believe 08:05:18 robcresswell: actually, it might be that my patch needs to include a reversion of david's patch :/ 08:05:25 or something compatibility work anyway 08:05:43 robcresswell: I've already put up a patch to fix the swift ui broeken 08:05:55 https://bugs.launchpad.net/horizon/+bug/1567830 08:05:56 Launchpad bug 1567830 in OpenStack Dashboard (Horizon) "“10 $digest() iterations reached” Error occur in ng-swift" [High,Confirmed] 08:06:09 https://review.openstack.org/#/c/308129/ 08:06:23 hey, where's *my* autobot link?! 08:06:25 grr 08:06:30 o/ 08:06:35 no link for r1chardj0n3s 08:06:37 bugs get bots, not patches 08:06:38 :P 08:06:45 anyhoo, the match that caused that bug wasn't compatible with the new "link" type in action-list 08:06:58 it was only being used in swift ui so I put up a patch that removes it 08:07:09 Nice 08:07:19 Could you tag that bug in it too, if it fixes it? 08:07:21 I like it less, but it works 08:07:25 I did 08:07:44 oh 08:07:50 no, I tagged a separate bug 08:07:51 https://bugs.launchpad.net/horizon/+bug/1572386 08:07:53 Launchpad bug 1572386 in OpenStack Dashboard (Horizon) "Action list "link" actions broken after patch #295605" [Undecided,In progress] - Assigned to Richard Jones (r1chardj0n3s) 08:08:05 I didn't realise there was an existing bug (I did search, honest) 08:08:25 I'm just going to point out that its one of three bugs tagged "swift" 08:08:32 >.< 08:08:40 see previous "I am the worst" :-) 08:08:44 haha 08:09:26 Anyway, if you could tag the other bug too (which would rerun tests anyway) that would be helpful 08:09:37 yup 08:09:43 Thanks r1chardj0n3s 08:10:16 tsufiev: So we nearly have angular integration tests? 08:10:37 robcresswell, nearly - yes, I like the word :) 08:10:43 :-) 08:10:56 Great news 08:11:04 I have a few folks who are chipping in on the integration test side of things, so I might encourage them in that direction... 08:11:32 I guess, we may have a working test for NG LI by the start of the summit 08:12:00 Oh, one thing I should mention; given the number of people leaving Horizon, our stable-maint team is extremely light right now. If you have any interest in backporting, please help review or propose patches 08:12:02 hopefully, doug-fish will stop looking then towards JS based integration tests :) 08:13:49 :) 08:14:48 We have an open agenda, so if there are any topics to be discussed feel free 08:14:54 otherwise we can just end early 08:15:55 I would keep reminding about AVAILABLE_REGIONS renaming, but I guess that the target audience is in another TZ 08:16:39 Yeah I think you'll get more attention in the later meeting if you're around 08:16:44 otherwise I can bring it up 08:17:03 robcresswell, I�m going to attend another meeting as well 08:17:18 ah, another thing 08:17:58 in the patch https://review.openstack.org/#/c/279573/ a point was raised that we need unit-tests which pass both for py2 and py3 08:18:35 which doesn�t seem entirely reasonable to me, because there is no way to run Horizon with py3 08:18:38 or there is? 08:19:13 r1chardj0n3s, it�s about unicode and py3, in case you�re interested 08:19:27 ah, ok 08:19:29 So there's an openstack-wide effort to support py3. Given the scale of the work, its unfair for projects to suddenly regress on py3 support. 08:19:44 So I don't believe it is an unfair expectation, personally 08:19:48 which is actually hilarious because I'm getting poorly-encoded characters in IRC from you at the moment tsufiev ;-) 08:19:56 "itŽs" 08:20:14 lol 08:20:27 Huh. The only weird chars I saw was from pkarikh doing copy paste, irssi was going nuts. 08:20:27 I'll have a look at that patch tomorrow, if that's OK? 08:20:42 r1chardj0n3s, sure 08:21:13 Its a pain to work around, but we should maintain the py3 UT support so that the python 3 guys can move forward :) 08:21:14 did not know that the special backtick my keyboard generates is in unicode :O 08:21:45 robcresswell, what if I skipped these tests explicitly if py3 env was detected :)? 08:22:16 If py3: pass 08:22:27 _ = string.upper 08:22:36 volkswagen lib for py3 ;) 08:23:00 ha! 08:23:07 I forgot about that 08:23:51 tsufiev: I believe the general advice from r1chardj0n3s re: unicode is to aritrarily throw in encode and decode statements until it works. 08:24:07 even better if you use the oslo safe_* functions 08:24:28 robcresswell: you know we're going to be in the same physical space next week, right? and someone recently encouraged me to work on my right hook... 08:24:43 haha 08:24:56 robcresswell, that is almost what I did... but let us wait until r1chardj0n3s says his expert ju 08:25:06 *makes his expert judgement on that patch 08:25:35 did you see how many people agreed with my proposal to remove safe_encode and safe_decode ... on twitter? 08:25:40 totes makes it a solid proposal 08:26:23 * tsufiev does not follow twitter much 08:26:46 Who'd have thought the best way forward for discussion is to limit everyone to 3 lines at a time. 08:27:08 "best" hmmm ;-) 08:27:18 becase that leaves no space for objections :) 08:27:39 Idk, people are very good at objecting to things on twitter 08:28:18 It would be good to deprecate it though 08:28:56 indeed 08:29:28 Right, anything else? 08:29:40 Remember there will be no meetings next Wednesday due to Summit. 08:30:52 Thanks all 08:30:55 #endmeeting