/srv/irclogs.ubuntu.com/2014/01/02/#launchpad-dev.txt

stubAnother reason to dislike using HTTP as an RPC mechanism is $http_proxy.04:34
stubI need to unset the http_proxy environment variable in the Librarian process, so Swift requests don't go via Squid04:35
stub(which would be wasteful, and won't work anyway since the firewall rules won't let it happen)04:35
stubIs it OK to hack this in in lp.scripts.runlaunchpad.start_librarian ?04:36
wgrantstub: That's rather a reason to dislike mandatory egress HTTP proxies :)04:43
wgrantstub: But that might be the least bad solution.04:43
wgrantstub: Though, why is the librarian running with http_proxy at all?04:48
wgrantOnly certain scripts + the appservers should be04:48
wgrantAnd the latter only due to retarded firewall rules.04:48
lifelessstub: wgrant: just set no_proxy04:49
lifelessno need to unset http_proxy04:49
stubwgrant: It is in .bashrc, probably because we didn't think it would be harmful04:49
stublifeless: I don't know that one04:49
lifelessno_proxy=hostname04:49
lifeless-> requests to hostname won't go via the proxy.04:49
wgrantThat's an excellent recipe for totally breaking production.04:50
lifelesswgrant: howso ?04:50
wgrantlifeless: Nobody will think to check for that when changing the swift hostname.04:50
lifelesswgrant: you could set that in the librarian code itself.04:50
wgrantvom04:51
lifelesswgrant: that seems a little shallow a response04:51
stublifeless: I don't think I can set it in process. I will know the Keystone URL, but I don't know the Swift endpoint URLs.04:53
stubwgrant: it would work if we are consistently using internal DNS names now... All the keystone/swift stuff is new since we started doing that, so it should be reliable enough.04:57
wgrantstub: Heh, you overestimate the sanity of our firewall configs.04:58
stubwgrant: Although fixing it in .bashrc would just be a foot gun, so no real difference between unsetting http_proxy and setting no_proxy04:58
wgrantWe need to use http_proxy in order to connect to some internal hosts.04:58
stubwgrant: Yeah. I already checked if staging's upstream librarian is directly connectable ;)04:58
wgrantThe example that immediately comes to mind is blog.launchpad.net from the appservers, but that's probably not the only one.04:59
stubwgrant: productreleasefinder, bug-watcher... there are others.04:59
lifelessstub: don't you get the swift urls from keystone?05:00
stublifeless: I don't. The swift library I'm using does.05:00
lifelessstub: ah05:01
=== Ursinha_ is now known as Ursinha
replaceafillhello everybody, i've been trying to fix a couple of 'trivial' bugs and i have questions, can anyone help?16:04
cjwatsonreplaceafill: (I'm only here for about twenty seconds, but) it's usually best to ask questions straight out and then leave your client hanging around for a while - LP devs are on various timezones but should be able to reply eventually21:23
replaceafillcjwatson, ah ok understood, thanks!21:24
wgrantreplaceafill: Hi22:05
replaceafillhi wgrant22:07
wgrantreplaceafill: What questions did you have?22:09
replaceafillwgrant, i'm trying to fix this bug: https://bugs.launchpad.net/launchpad/+bug/26067722:09
_mup_Bug #260677: Include date with milestones on advanced search page <lp-bugs> <oem-services> <search> <trivial> <ui> <Launchpad itself:Triaged> <https://launchpad.net/bugs/260677>22:09
replaceafilllet me push my branch22:10
replaceafillwgrant, my push is taking way too long :(22:18
replaceafillhere's the diff though:22:18
replaceafillhttp://pastebin.ubuntu.com/6681167/22:18
wgrantreplaceafill: Where are you pushing to?22:19
replaceafillwgrant, i added a new vocabulary to be used in the "advanced" view22:19
replaceafillwgrant, launchpad22:19
replaceafillwgrant, my bandwitdh is very limited :(22:19
wgrantAh :(22:19
wgrantIt should only need to push a few hundred kilobytes.22:20
replaceafillit finished!22:20
replaceafillhttps://code.launchpad.net/~replaceafill/launchpad/bug-26067722:21
replaceafillnow lp is updating :)22:21
wgrantSo, what's not working?22:21
replaceafillbasically i'm not sure if my approach is correct22:21
replaceafilli followed Curtis Hovey's suggestion about creating a new vocabulary22:22
replaceafillthe name of the new vocabulary for example MilestoneWithExpectedDateVocabulary22:23
replaceafillseems "funny"22:23
wgrantIt's not too bad.22:25
replaceafillah, ok22:25
wgrantIt would be nice if Zope let us pass an argument into the vocab constructor, but it does not.22:25
replaceafillyou mean, so we could pass something to tell the vocabulary to insert the dates, right?22:26
replaceafill(in the titles)22:26
wgrantreplaceafill: Right, that would be nicer than having AWholeNewClassWithAVeryLongName22:32
wgrantBut it's sadly not possible.22:32
replaceafillright22:32
replaceafilldoes this look good enough to you?22:32
replaceafilli was also adding a unit test for the new vocabulary22:32
replaceafillbased on the tests of the existing one22:33
replaceafilllp/registry/tests/test_milestone_vocabularies.py22:33
wgrantRight, that would be a good idea.22:34
wgrantI'd just add two additional tests, I think.22:34
wgrantOne for a milestone with a date, and one without.22:35
replaceafillah, ok22:35
replaceafillin the unit test or the doctest?22:36
wgrantThe unit test. Doctests are deprecated.22:36
replaceafillah ok22:37
replaceafillgood to know :)22:37
replaceafillcan i set you as the reviewer of my branch after i'm done with the test?22:37
wgrantSure22:39
replaceafillok, i will22:40
replaceafillthank you wgrant22:40
wgrantnp, thanks for working on this22:40
replaceafilland expect some other nagging questions from me22:40
replaceafilli've been working on a couple more :)22:40
wgrantI look forward to it.22:41

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!