[00:27] <phillw> balloons: ping
[01:16] <angelwarrior15> ;lotta people in here
[01:44] <akgraner> gema_, ping
[08:36] <gema_> akgraner: pong
[08:39] <gema_> akgraner: I will let you know as soon as we've settled with a name, we haven't had time to discuss it other than a line on g+
[09:13] <njin> hello, amd64+mac is the version for the macbook ?
[11:28] <jibel> njin, yes it is
[11:44] <akgraner> gema_, understood thanks!
[15:26] <jibel> stgraber, about ltsp, what happens if the server supports 3d but not the client and a user connects on both (connecting on the server first)?
[15:31] <BigWhale> Greetings.
[15:36] <stgraber> jibel: well, gnome-session should do the right thing and start in 3D on the server and 2D on the client
[15:36] <jibel> stgraber, even if .dmrc is shared and set to 'ubuntu'  ?
[15:37] <stgraber> jibel: yes
[15:38] <stgraber> jibel: "ubuntu" is supposed to first do the nux check and then start 3D if the machine is 3D capable, 2D otherwise
[15:38] <stgraber> jibel: "ubuntu-2d" always starts 2D even if the machine is 3D capable
[15:40] <jibel> stgraber, ok, and if the user logs in the server with 2d first then a client that supports 3d, it will starts a 2d session on the client ?
[15:41] <stgraber> as long as the user never explicitly chose "ubuntu-2d", it should start in either 3D or 2D mode depending on hardware
[15:41] <jibel> stgraber, ok, thanks
[15:41] <stgraber> if the user once specifically selects "ubuntu-2d", then any session from that point will be 2D only, whatever the hardware is
[15:41] <jibel> got it
[15:56] <davmor2> jibel: has anyone hit an issue on intel gfx hardware where by Ubiquity seems to stop on the last Who Are You?  page?  ie no slide show, and the progress bar is stuck where ever it was at the time you hit the continue button?
[15:58] <jibel> davmor2, none that I know. any crash or useful info in syslog ?
[15:58] <davmor2> jibel: there is a load of disc activity so it looks like it has continued as normal
[15:58] <davmor2> jibel: but the screen isn't advancing
[15:59] <davmor2> jibel: looks like the screen haslocked completely now actually,  I'll keep an eye on it as I go and see
[16:02] <SpamapS> has anyone else done the RAID1 tests this cycle?
[16:03] <SpamapS> I'm running into a situation where hot-re-adding the missing disks is failing.. have to zero the superblock and add them as a spare.
[16:06] <jibel> davmor2, can you switch to a console and see if there something useful in /var/log/syslog ? error message, segfault, X lockup ...
[16:07] <davmor2> jibel: Nope screen is completely locked up
[16:08] <jibel> davmor2, hm, CTRL+Fn does nothing ? and does the led changes when you press the CAPSLOCK key ?
[16:09] <davmor2> nope
[16:11] <davmor2> jibel: I'm gonna kill this do a fresh burn on a different dvd+r and see what happens then I think,  but this time round if it locks up on the continue button I'll drop to tty immediately
[16:11] <jibel> davmor2, ok. looks like a kernel bug
[16:29] <davmor2> jibel: right back to fresh, hit the continue button and I get the following from tail /var/log/syslog  feb 29 16:26:42 ubuntu kernel: [ 397.552209] [drm;drm_mode_getfb] *ERROR* invalid framebuffer id
[16:33] <davmor2> jibel: and now the system is completely locked up again :(
[16:33] <davmor2> not good
[16:34] <balloons> phillw, sorry missed your ping
[16:35] <balloons> cr3, another day.. still wondering how the apport issue is coming :-)
[16:35] <davmor2> jibel: I'm going to grab a alternate image instead I need a working system asap for work,  I'll have a play at the weekend and see what I dig up with the live cd
[16:43] <phillw> balloons: it's okay. I tagged them onto the agenda. only a couple of minor tweaks :)
[16:43] <balloons> cool cool
[16:43] <balloons> you want dj today? aka, would you like to host the meeting philw?
[16:44] <balloons> I already plan on talking alot about the checkbox tests.. probably don't need to see my name hosting the meeting too.. hehe
[16:44] <phillw> I can if you're busy. Hopefully Jason has got the hang of installing the IRC client onto the SII's server.
[16:45] <phillw> I have a gripe re: lubuntu, so I will also be entering some lines!
[16:47] <phillw> we found the cause of http://iso.qa.ubuntu.com/qatracker/reports/bugs/938472
[16:48] <phillw> which has caused major issue for a week :(
[16:49] <phillw> our graphics guy found it last night "it's a change on GTK3 3.2.1 syntax and theme standards (I'm angry because of so many changes, they won't make any standard if it goes that way) and Unico 1.0.1 (some textures changes, too)." He's working on a temp bug fix, then all the RC's need respinning :(
[16:52] <balloons> phillw, I'm not to busy to host/join.. Just thought I would offer it up.. share the love <3
[16:53] <phillw> he he, if you'd host. I'm still also on support in #lubuntu as well :)
[16:55] <PaoloRotolo> Hi all!
[16:55] <cr3> balloons: yeah, it's a subtle problem. I'll have another look today
[16:56] <balloons> kk phillw, will do
[17:54] <davmor2> OK that's annoying  if you add a wifi network for the alternate install to connect to you can't use wifi once the install is complete, but it always fails to find a wifi network if you don't
[17:57] <davmor2> also not so good that it stores the AP password in plain text
[18:00] <brendand> hey balloons
[18:00] <balloons> hey.. hopefully everyone makes it over hre
[18:00] <phillw> balloons: you have meetingology on here as well :)
[18:01] <balloons> can I/should I have 2 logs.
[18:01] <balloons> ?
[18:01] <brendand> davmor2, heh - that's a long story...
[18:01] <phillw> you can, yes
[18:01] <phillw> they will have unique names
[18:01] <balloons> #startmeeting ubuntu qa part II
[18:01] <meetingology> Meeting started Wed Feb 29 18:01:26 2012 UTC.  The chair is balloons. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[18:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:01] <balloons> hehe, it's better than not capturing it, even if there will be noise
[18:02] <balloons> alright, so yes short term, what do we do.. my thoughts on what to do with the checkbox tests after we had a test management tool was to migrate them at that point
[18:02] <balloons> and if we still had / used the wiki (or whatever, spreadsheet, whatever) they would also be migrated
[18:03] <balloons> our future delivery system should simply use the tests from the management system.. so they are maintained in one place
[18:03] <brendand> balloons, don't you think it would be better if you *just* ask people to add to the spreadsheet and then you and a few other people deal with updating checkbox?
[18:03] <balloons> and by having a nice test case management system everyone can see and update them easily
[18:03] <balloons> without having to be a dev, or use bzr
[18:04] <balloons> brendand, for anyone who can propose a merge, it makes it easier on me to accept the request.. if you can't I am pointing folks to adding the case to the wiki and I will manually import it
[18:05] <brendand> ok. let's make an action item to clarify that the wiki should not be used except by those who know they need to use it
[18:06] <balloons> for example, roignac has sent several merge requests that made it really nice on me for just accepting and not having to re-work his test cases
[18:06] <balloons> brendand, I'm also concerned about the spreadsheet
[18:06] <balloons> what does everyone think we should do in the short term for holding our test cases
[18:06] <balloons> put aside the issue of how to contribute for a moment
[18:08] <brendand> balloons, you're concerned as in you don't like it?
[18:08] <balloons> brendand, I think I like the spreadsheet even less than the wiki, simply because it's confusing for people
[18:08] <balloons> and everything in the spreadsheet is supposed to be/ should be in the wiki
[18:09] <brendand> it's something of a least worst option situation
[18:10] <balloons> for example, we could deprecate the wiki, and say checkbox branch has our testcases in it. if you want to contribute a new test and can't we could have an open spreadsheet to do so, we would manually import it, then remove the spreadsheet
[18:11] <balloons> my concerns with that would be making it hard to see all the testcases for everyone
[18:11] <balloons> and making it hard for the community to edit testcases
[18:11] <balloons> however it would be a short-term thing
[18:11] <brendand> right. i think a spreadsheet is better than a wiki for reviewing
[18:12] <balloons> does anyone have an alternative option to present?
[18:12] <brendand> i seem to recall that one of the reasons we moved away from the wiki was not because of it being a wiki but because many of the test cases themselves were actually useless
[18:13] <balloons> I'm not necessarily pushing the option above, just that it was an option
[18:13] <balloons> brendand, yes the wiki was in worse shape that I thought
[18:13] <balloons> anything not written recently was old and useless
[18:13] <balloons> in many cases it was blank
[18:14] <brendand> i think we need to head toward the optimum solution post-haste
[18:15] <brendand> make checkbox the definitive store until case-conductor is in place
[18:15] <brendand> for those who don't want to use bzr we have a 'new test cases' sheet as balloons suggested
[18:16] <brendand> this is reviewed every QA meeting and synced to checkbox, then wiped
[18:16] <balloons> if there's no other ideas put forward I'm ok with doing that
[18:17] <brendand> once case-conductor is in place AND we have a tool which syncs down test cases to checkbox, we can start putting test cases in there
[18:17] <balloons> sounds fine to me
[18:18] <balloons> do we feel a spreadsheet is necessary?
[18:18] <balloons> would the mailing list suffice? or is it ok to simply ask them to bzr branch and propose a merge?
[18:19] <brendand> balloons, it might limit the scope of contribution, but maybe for the short term
[18:19] <brendand> ML could work
[18:19] <brendand> i was just thinking to have an outlet for those with no bzr experience
[18:20] <brendand> balloons, and there's still the question of the testcases.qa wiki :)
[18:20] <balloons> yes I'm concerned about that
[18:20] <balloons> i don't want to limit
[18:20] <balloons> but perhaps just sending a mail would be best
[18:21]  * phillw has no bzr knowledge :/
[18:21] <balloons> awesome.. so phillw what makes sense for you
[18:22] <balloons> would you feel put off by having the tests in a bzr branch?
[18:22] <balloons> for instance, you can see all the tests right now by browsing them online
[18:22] <balloons> http://bazaar.launchpad.net/~nskaggs/checkbox/checkbox-app-testing/files/head:/jobs/
[18:22] <phillw> balloons: it is a case of learning and then teaching new testers. My concern is that if it is too complicated it will put them off.
[18:23] <balloons> phillw, what would you propose then?
[18:25] <phillw> balloons: the most difficult thing of all. A clear, easy to follow set of instructions for newcomers (And, if I can follow them, any one can.... trust me on that one when I made pcman write up how to set up debug in pcmanfm :P )
[18:25] <balloons> phillw, +1. we are working towards that
[18:26] <balloons> and this decision factors in.. we want this to get iteratively easier, not harder :-)
[18:26] <phillw> I was also the 'idiot' who idiot checked the GRUB 2 instructions way back when drs305 was writing them :)
[18:26] <balloons> but the biggest piece behind this checkbox thing was to get more testers out there
[18:26] <balloons> and I think / hope it will
[18:27] <balloons> this problem is sort of a side issue.. the main issue I was trying to solve was to get more testing, and better metrics on testing.. in addition, I wanted to increase the number of real tests
[18:27] <balloons> and get the tests we wrote used
[18:30] <phillw> I can only say from personal experience, that the likes of http://testcases.qa.ubuntu.com/Plans/LaptopTesting#System are followable?
[18:33] <brendand> balloons, i need to leave the conversation now. look forward to a few merges into your checkbox branch from me ;)
[18:35] <balloons> brendand, awesome thanks
[18:35] <balloons> phillw, are you trying to say you can or can't follow that wiki page?
[18:35]  * balloons is confused on sarcasm or not
[18:36] <phillw> balloons: I thought the wiki is due to go?
[18:36] <balloons> phillw, long term yes
[18:36] <balloons> but short term.. well we're deciding that now :-)
[18:37] <phillw> balloons: do you have the link to the wiki, please?
[18:37] <balloons> link to the wiki? this? http://testcases.qa.ubuntu.com/
[18:37] <phillw> I'm sufferring from tab overload
[18:37] <balloons> ahh
[18:38] <phillw> balloons: that looks familiar aka http://testcases.qa.ubuntu.com/Plans/LaptopTesting#System
[18:39] <phillw> it is simply 'what do you expect to happen" followed by - Does it?
[18:39] <balloons> so phillw.. here's a good example.. the nautilus tests are the same in the wiki and checkbox
[18:39] <balloons> http://testcases.qa.ubuntu.com/Applications/Nautilus
[18:39] <balloons> http://bazaar.launchpad.net/~nskaggs/checkbox/checkbox-app-testing/view/head:/jobs/nautilus.txt.in
[18:39] <balloons> phillw, yes the format of those tests are really iffy
[18:39] <balloons> they would need reworked to go into checkbox or case conductor, etc
[18:40] <phillw> ooh, pink! Yeah, they are in plain english as to what to expect etc.
[18:41] <phillw> Sorry, I've GTG - Dinner is served at 18:30 UTC on wednesdays here as I have the lubuntu meeting at 20:00 UTC.
[18:42] <balloons> gotcha
[18:42] <balloons> ok, well
[18:43] <balloons> I'll sumarize on the mailing list
[18:43] <balloons> thanks for the extended discussion
[18:43] <balloons> #endmeeting
[18:43] <meetingology> Meeting ended Wed Feb 29 18:43:18 2012 UTC.
[18:43] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-testing/2012/ubuntu-testing.2012-02-29-18.01.moin.txt
[18:43] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-testing/2012/ubuntu-testing.2012-02-29-18.01.html
[19:27] <phillw> is the qa email address ubuntu-qa-request@lists.ubuntu.com, or have I got the wrong one?
[19:36] <phillw> balloons: ping
[19:38] <botfather> phillw: you want to subscribe ?
[19:39] <botfather> i am going to try this https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
[19:39] <phillw> botfather: I'm already subscribed, I'm just having issues sending to it :(
[19:41] <botfather> ah you need the email without the -request i think
[19:42] <botfather> request is for membership requests if i recall correctly
[19:42] <botfather> mailman has been a veeery long time ago for me ;]
[19:43] <botfather> To post to this list, send your email to:
[19:43] <botfather> ubuntu-qa@lists.ubuntu.com
[19:51] <phillw> botfather: hmm, it said I'm already registered, but I'll remove -requests when I email. Thanks for your help :)
[20:12] <botfather> phillw: np ;]
[20:19] <balloons> phillw, pong
[20:19] <balloons> phillw, botfather is correct
[20:19] <balloons> is thats what you needed;-)
[20:21] <phillw> nope, doesn't like rafael can correct the issue with GTK / Unico
[20:21] <balloons> phillw, ohh.. meaning it's just broken?
[20:21] <phillw> balloons: can you join #ubuntu-meeting please
[21:17] <jibel> SpamapS, what's the status of raid1 testing ?
[21:31] <SpamapS> jibel: done on i386, 90% done on amd64
[21:31] <SpamapS> just waiting on my slow single disk to pretend to be two disks for kvm. ;)
[21:32] <jibel> SpamapS, :) great thanks
[21:33] <jibel> SpamapS, would you have a setup to test iscsi too ?
[21:34] <SpamapS> jibel: not in a realistic situation, but I could set it up via vms.
[21:34] <jibel> SpamapS, Vms are better than nothing
[21:35] <SpamapS> jibel: I will stir up some help on my team as well. The automated tests are ok, but they don't completely replace testing the actual user experience.
[21:35] <jibel> SpamapS, I agree
[22:16] <balloons> cr3, you around?
[22:28] <cr3> balloons: sorry, I'm there. got distracted with a security vulnerability this afternoon :)
[22:30] <balloons> no worries.. I'll bug you about something else :-0
[22:30] <balloons> all my submissions seem to be failing to upload for some reason
[22:30] <balloons> i get the little cannot submit, do it manually error :-(
[22:31] <balloons> so I went and took a look at your upstream bzr branch again
[22:31] <balloons> because perhaps everything "just works" there with apport and the submission stuff
[22:31] <balloons> I moved my jobs over, adjusted the setup.cfg file and ran checkbox-gtk
[22:32] <balloons> the log shows all the tests loading but then nothing to select to test :-(
[22:32] <balloons> so.. I open to trying to make upstream work (and potentially fix something), or fix my version. thoughts cr3?
[22:33] <balloons> my deadline for this is fast approaching ;-)
[22:35] <roadmr> balloons: did you look at the log file? any ERRORs?
[22:37] <balloons> hmm.. nothing popping out
[22:38] <balloons> it seems like everything worked when I specficied the results tracker in the ini file
[22:38] <balloons> i took it out and it seems broken again
[22:38] <balloons> not sure I remember how to do that..
[22:43] <balloons> found the old revision.. trying again with the results tracker url
[22:44] <balloons> no dice
[22:44] <balloons> arggh
[22:48] <cr3> balloons: so, you have a submission.xml file, right?
[22:49] <balloons> yep
[22:49] <cr3> balloons: ok, so try running this command:
[22:49] <cr3> xmllint --noout --nonet --relaxng ./report/hardware-1_0.rng submission.xml
[22:50] <balloons> mllint --noout --nonet --relaxng ./report/hardware-1_0.rng ~/.checkbox/submission.xml
[22:50] <balloons> warning: failed to load external entity "./report/hardware-1_0.rng"
[22:50] <balloons> Relax-NG parser error : xmlRelaxNGParse: could not load ./report/hardware-1_0.rng
[22:50] <balloons> Relax-NG schema ./report/hardware-1_0.rng failed to compile
[22:50] <cr3> balloons: note that "./report/hardware-1_0.rng" assumes you're in the root of the checkbox branch and you might need to provide a different path to your "submission.xml" file
[22:50] <balloons> ahh i see the report/hardware* file in the upstream branch
[22:50] <balloons> but not mine
[22:51] <balloons> /home/bugandboo/.checkbox/submission.xml validates
[22:51] <cr3> balloons: ok, so the submission.xml validates. what's the error that you get?
[22:51] <cr3> "Failed to contact server. Please try..."
[22:53] <balloons> yes
[22:53] <balloons> that's what I get
[22:53] <balloons> some lines
[22:53] <balloons> 2012-02-29 17:44:03,820 WARNING  Can't connect to https://staging.launchpad.net/+hwdb/+submit
[22:53] <balloons> 2012-02-29 17:44:03,820 DEBUG          Started firing exchange-error.
[22:53] <balloons> 2012-02-29 17:44:03,820 DEBUG          Calling /usr/share/checkbox/plugins/launchpad_prompt.py exchange_error(Failed to contact server. Please try
[22:53] <balloons> again or upload the following file name:
[22:54] <balloons> you can see i manually specificed staging in the ini file again
[22:54] <balloons> I can remove that altogether again.. but the error seems to persist. I had successfully gotten some tests up to lp in the past
[22:55] <cr3> balloons: did you ever successfully upload to staging.launchpad.net though?
[22:55] <balloons> i wanted to chat with you guys about that at one point.. it seemed to just upload to both places
[22:56] <balloons> fresh run without any ini override
[22:56] <cr3> balloons: hm, you mean to both places at the same time?
[22:56] <balloons> cr3, yes
[22:57] <balloons> i could link you to some of them
[22:57] <cr3> balloons: ok, that's weird
[22:57] <balloons> same error
[22:58] <balloons> 2012-02-29 17:56:44,945 WARNING  Can't connect to https://launchpad.net/+hwdb/+submit
[22:58] <balloons> i wonder if my launchpad_exchange plugin is too old
[22:58] <balloons> or new..
[22:58] <balloons> hehe
[22:58] <cr3> balloons: hm, let me see something in the exchnage code...
[23:01] <balloons> cr3, if you think adopting a released version of checkbox upstream would help, I would do it.. obviously what I have here is a fork of checkbox-unity
[23:01] <cr3> balloons: that should be fine, no worries
[23:01] <cr3> balloons: ok, so are you using the base checkbox from a branch or from the system?
[23:02] <balloons> hmm
[23:02] <cr3> balloons: most importantly, do you know where the checkbox.lib.transport module is imported from?
[23:02] <balloons> you know what i'm using the system checkbox
[23:03] <balloons> export CHECKBOX_SHARE=${CHECKBOX_SHARE:-/usr/share/checkbox}
[23:03] <cr3> balloons: and you're not specifying a PYTHONPATH pointing to the checkbox branch, right?
[23:03] <balloons> if [ "$CHECKBOX_SHARE" != "/usr/share/checkbox" ]; then
[23:03] <balloons>     export PYTHONPATH="$CHECKBOX_SHARE:$PYTHONPATH"
[23:03] <balloons> fi
[23:04] <cr3> balloons: ok, sudo gedit /usr/share/pyshared/checkbox/lib/transport.py
[23:04] <cr3> balloons: are you able to skip to a line number in gedit?
[23:05] <balloons> yea.. i just used geany
[23:06] <cr3> balloons: ok, jump to line 318 and change that line to look like this: https://pastebin.canonical.com/61301/
[23:06] <cr3> balloons: then, try submitting again and let me know if that fixes the problem
[23:07] <balloons> k trying
[23:08] <balloons> unknown URL type: /+hwdb/+submit
[23:08] <balloons> i'm sitting at the submit in checkbox, so we can play with this now
[23:10] <balloons> it's just submitting a post to that site
[23:10] <balloons> that's quite odd
[23:10] <balloons> should print the headers to see what the error is
[23:11] <balloons> hmm
[23:11] <balloons> lp error perhaps? that one seems to have magically gone thru
[23:11] <cr3> balloons: with the complete url or just the path?
[23:12] <balloons> i undid your change
[23:12] <balloons> complete url
[23:12] <cr3> balloons: bloody hell!
[23:12] <balloons> running again
[23:12] <balloons> sweet it failed again
[23:12] <balloons> ok, we should print some headers there
[23:12] <cr3> this is exciting!
[23:13] <balloons> ahh.. ok ;-)
[23:13] <balloons> i don't think my success was correct
[23:13] <balloons> once it errors once, it doesn't try again
[23:13] <balloons> so :-)
[23:13] <cr3> balloons: if you're getting "Can't connect", that's an IOError so you're not likely to get much out of it
[23:13] <balloons> whew.. sanity is returned
[23:13] <balloons> yea.. but I mean, literally it's not even sending a post?
[23:14] <balloons> err.. I mean getting a response
[23:14] <balloons> if it's a timeout thing..
[23:14] <balloons> i don't know.. it's weird
[23:14] <cr3> balloons: let's try changing the except to: IOError, error:
[23:14] <cr3> balloons: and the logging to: logging.warning("Can't connect to %s: %s", self.url, error)
[23:14] <cr3> balloons: ... if that makes sense
[23:15] <balloons> sure.. let's see what happens
[23:16] <balloons> ahh something more. a little anyway
[23:16] <balloons> Can't connect to https://launchpad.net/+hwdb/+submit: [Errno -2] Name or service not known
[23:19] <balloons> http://stackoverflow.com/questions/4673166/python-httplib-name-or-service-not-known
[23:19] <balloons> light reading...
[23:21] <balloons> VerifiedHTTPSConnection.. interesting, your doing cert verification
[23:22] <balloons> i'm going to mess with urlparse
[23:22] <balloons> i think you where close
[23:22] <cr3> balloons: yeah, slight limitation with httplib
[23:22] <cr3> balloons: it seems that the right host is being passed to VerifiedHTTPSConnection though, you might like to double check that though
[23:23] <balloons> it seems like you just wanted to kill the https in the connection call
[23:23] <balloons> i think that may work
[23:23] <balloons> but your code killed more than that i think
[23:24] <cr3> balloons: oh wait, what if unicode is the problem?
[23:25] <balloons> if so.. thoughts?
[23:25] <balloons> u could checkout and try and your box if you wish
[23:25] <balloons> oneiric seems to work better, if I remember
[23:26] <balloons> everything works for you on that box when you test my stuff :-)
[23:26] <cr3> balloons: can you try this real quick:
[23:26] <cr3> python
[23:26] <cr3> >>> from checkbox.lib.transport import HTTPTransport
[23:26] <cr3> >>> t = HTTPTransport(u"https://staging.launchpad.net/+hwdb/+submit")
[23:26] <cr3> >>> r = t.exchange("foo")
[23:26] <cr3> >>> print r.status
[23:27] <balloons> 200
[23:31] <balloons> trying with using netloc and path from urlparse
[23:34] <cr3> balloons: it might be worth checking exactly what's being passed to the HTTPTransport constructor, because the above command seems to work just fine
[23:35] <balloons> i started looking at that.. but you had the override in there, so I stopped :-)
[23:36] <cr3> balloons: I'd just worry about the url passed to the constructor of HTTPTransport, the rest should trickle down to VerifiedHTTPSConnection correctly considering the above worked
[23:39] <balloons> kk, checking
[23:39] <balloons> breaking things..
[23:39] <balloons> fun fun
[23:43] <balloons> weird
[23:47] <balloons> cr3, well I'm sure it's late for you also
[23:47] <balloons> this should work.. no reason really it's not
[23:47] <balloons> everything i'm seeing (when I'm not blowing things up) is working
[23:48] <balloons> I'm going to hang in the towel here in 5 mins.. one more try