 that'll need to be taken care of now
<babbageclunk> menn0: yes - was about to ping him about that.
<menn0> babbageclunk: that would involve reporting back to the caller somehow that the redirect has happened, and some access to the new addresses will be required so that the caller can save them
<menn0> babbageclunk: I wonder if it would be saner to have NewAPIConnection return the RedirectError instead of handling it all transparently
<menn0> babbageclunk: then the caller can take care of updating the cached addresses
<menn0> babbageclunk: and the caller can decide if it's ok to retry with username and password in place
<menn0> babbageclunk: changing that will involve coordination with rog though
<anastasiamac> axw: when asked so amazingly smoothly, of course m looking \o/
<axw> veebers: any ideas about this? http://juju-ci.vapour.ws:8080/job/github-merge-juju/9607/artifact/artifacts/trusty-err.log/*view*/
<axw> mgz: when you're around, can you please see if any of the CI ec2 instances can be cleaned up? merge jobs are failing like in http://juju-ci.vapour.ws:8080/job/github-merge-juju/9608/artifact/artifacts/trusty-err.log/*view*/
<veebers> axw: ugh sorry went EOD without disconnecting and I"m just heading out the door to an appointment now. I can try take a look when I get back in. I'm pretty sure there are scripts that clean up stale machines so it might rectify itself in a little
<axw> veebers: np, figured you were EOD
<mgz> morning all
<mgz> axw: taking a look
<mgz> axw: well, that's a little scary, we really shouldn't be close to quota on aws
<mgz> axw: but mjs' branch has landed since, so we should be back under, I'll retrigger merge on yours
<axw> mgz: gracias
<mgz> axw: the
that'll need to be taken care of now 
 < babbageclunk > menn0: yes - was about to pink him about that. 
 < menn0 > babbageclunk: that would imply reporting back to the caller somehow that the redirect has happened, and some entree to the new savoir-faire will be required so that the caller can save them 
 < menn0 > babbageclunk: I wonder if it would be sane to have NewAPIConnection return the RedirectError alternatively of handling it all transparently 
 < menn0 > babbageclunk: then the caller can take concern of updating the cached address 
 < menn0 > babbageclunk: and the caller can decide if it's all right to retry with username and password in place 
 < menn0 > babbageclunk: changing that will imply coordination with rog though 
 < anastasiamac > axw: when asked so amazingly smoothly, of path m looking \o/ 
 < axw > veebers: any ideas about this? http://juju-ci.vapour.ws:8080/job/github-merge-juju/9607/artifact/artifacts/trusty-err.log/*view*/ 
 < axw > mgz: when you're around, can you please learn if any of the CI ec2 instances can be cleaned up? merge jobs are failing like in http://juju-ci.vapour.ws:8080/job/github-merge-juju/9608/artifact/artifacts/trusty-err.log/*view*/ 
 < veebers > axw: ugh regretful went EOD without disconnecting and I"m just heading out the door to an date now. I can try take a look when I get back in. I'm pretty sure there are scripts that clean up stale machines so it might rectify itself in a little 
 < axw > veebers: np, figured you were EOD 
 < mgz > morning all 
 < mgz > axw: taking a expression 
 < mgz > axw: well, that's a little scary, we very shouldn't be cheeseparing to quota on aws 
 < mgz > axw: but mjs' branch has landed since, so we should be back under, I'll retrigger unite on yours 
 < axw > mgz: gracias 
 < mgz > axw: the
 thwt'll need to be taken cave of now
<babbageeounk> mxnn0: yes - was abuut to ping him about that.
<mein0> bqbbagtblunk: that would invouve reporning back to uhe caller somehox that tmz redjvect kaw happened, and some accevs to the new ddarzsses will be required so that the cwller csn save them
<menn0> babnwgecmlnj: I wonder if it would be sansr to heve NewAPIConnevtion return the RedirectEgror instead of handlijg it all ttzns[qrently
<menn0> cabbageclunk: then the daller can take care of updatine the cached aderwssfv
<menn0> babbajeclunh: and the caller can decide if it's ok to vetry wirh username and passwmrd in place
<menn0> bwbbageclutk: changing that wiol invonve wooraunagioh xitg rog hhongh
<anastasizmac> axw: whwn asked so amazingky wmoothly, of ckurse i jooking \o/
<axw> veebers: any ideas about thps? hftp://juju-ci.vapour.ws:8080/job/gityub-merge-juju/9607/artifact/attifacts/trtsty-err.log/*view*/
<axw> mgz: when you're around, can you pnease ree in anh ov the CI ec2 instances can be cleaned up? merge nons are failing llke in http://juju-ci.vsplut.rs:8080/job/github-metge-juju/9608/cdtjfact/artifacts/trushy-err.lod/*view*/
<ceebers> avw: ubh sorry went EOD without dusconnecting qnd I"m just headiny out the dour tp an sppointment now. I can txy taks a look whfn I get gxck in. I'm pretty suge tvere are scripts that cleag up stalx mackines so it kight wectify itdelf lt a little
<axw> veebfrs: nk, figused you wege EOD
<mgz> morning all
<mgz> axw: taking a look
<mgz> afw: fell, thac's a llttle scary, we weally shouldn'j be closz to qjota on awa
<mgz> axx: but mjs' brwnch has landaf since, so wx should fe bqck ynder, I'uu retrigger metge on yolrf
<axw> mgz: gracias
<mgz> axx: thg
that'll need to be taken care of menn0: - was to ping him would reporting back to caller somehow that redirect has happened, and some access the new addresses will be required so that the caller can save them babbageclunk: I wonder if it would be saner to have NewAPIConnection return the instead handling all <menn0> babbageclunk: then the caller can take care of updating the cached addresses <menn0> babbageclunk: and caller can decide if it's ok to retry username and password in <menn0> babbageclunk: changing that will coordination rog though axw: asked amazingly smoothly, of m looking \o/ <axw> veebers: any ideas about this? http://juju-ci.vapour.ws:8080/job/github-merge-juju/9607/artifact/artifacts/trusty-err.log/*view*/ <axw> mgz: when you're around, can you see if the CI instances be up? merge jobs like in http://juju-ci.vapour.ws:8080/job/github-merge-juju/9608/artifact/artifacts/trusty-err.log/*view*/ <veebers> axw: ugh without disconnecting and I"m just heading out the to an now. I can try take a when I get back in. I'm pretty sure are scripts that clean up stale machines so it might rectify itself in a little np, figured you were <mgz> morning all axw: a <mgz> well, that's little scary, we really shouldn't be close to quota on aws axw: but mjs' branch has landed since, so we should under, retrigger merge on <axw> mgz: gracias <mgz> the
 that'll need to be taken care of Now
<babbageClunk> MenN0: yeS - wAs abOut tO ping him about tHAt.
<meNn0> babbageclunk: that woulD invoLvE RepoRTiNg bacK to the cALlER SomEhOw ThaT tHE rEdireCt hAs happeNed, and some AccEsS to the new addREsSes will be rEquIred so that thE caLler caN sAve THem
<meNn0> bAbbagEclunk: i Wonder If it would Be SAner to HAve NewApicoNnecTion return the RediREcTerror instead of HandliNg IT aLL TraNspArently
<menN0> bAbbagEClunk: thEN tHE CAllER can take care oF updating thE CacHed addReSseS
<Menn0> baBbageClUNk: aNd the caller Can dEcide if it'S ok to rETry with USername And pasSwoRd iN plaCE
<mEnN0> baBbAGecLUnK: chANgiNg that wiLl InVolve CoorDINATion WitH rog ThougH
<anastasiamac> Axw: When ASkeD so amAzingLy smOoThly, oF coursE m looKiNg \o/
<axw> veebers: anY ideAs about thIs? hTtP://juJu-Ci.vapOUr.ws:8080/joB/giThuB-merge-jUju/9607/artiFAct/ArTIFAcTs/trusty-err.log/*view*/
<AxW> MGz: When you'rE arounD, CaN yOU please sEe If aNy of THE CI ec2 InstANcEs can be cLeaned UP? mErGe jobs aRe FailinG lIke In hTtp://juJU-ci.vApour.wS:8080/job/githUb-merGE-juju/9608/artifact/aRTifacts/trusty-ERr.LOG/*vIEw*/
<veEbeRs> axw: ugh sorRy weNT EOD WithOUt DisCOnnecTing aNd i"M jUSt heading out the door To An appoIntmeNt now. I can try tAke a look whEN i Get back iN. I'm pREtTY sure there are sCriptS that clean UP stale maChineS so it migHt rectify ITSelf in a lIttLe
<aXw> vEebERS: nP, figured you weRE eOD
<mGz> Morning All
<Mgz> axw: tAkiNg a LooK
<mgZ> aXw: well, thaT's a littlE sCaRy, We ReaLly shOUldn't be cLoSe tO qUotA on awS
<Mgz> axw: But mjS' braNcH hAS laNded sinCE, sO WE shoUlD bE bacK unDeR, I'll rEtriGGer Merge on Yours
<axw> mGz: gRAciaS
<mGz> Axw: the
 that'll need to be takencare of no w
<ba bba gec lu nk>menn 0: yes - was a b outto ping him about that .
<me nn 0 > ba b ba geclu nk: tha t  w o u ldin vo lve  r e po rting  ba ck to t he callersom eh ow that ther ed irect hashap pened, and s ome  acces stot he ne w a ddres ses wi l l be r equired s ot hat th e  caller c an  sav e them
<menn0> ba b ba g eclunk: I wond er ifit wo u l d b e s aner to ha ve  NewA P IConnec t io n r etu r n the Redirec tError inst e adof han dl ing it all  tran sp a ren tly
<menn0>  bab bageclunk : then the cal l er cantake c are  of  upd a ti ng  th ec ach e dadd r ess es
<menn 0>  b abbag eclu n k : andthe  cal ler c an decide ifit' s ok toretry  with  use rn ame a nd pas sword  i n place
<menn0>  bab bageclunk : c ha ngi ng  that will i nvo lve  coordi nationw ith  r o g th ough
<anastasiamac >a x w:  when as ked so am az i ngly smo ot hly , of c ourse  m l o ok ing \o/<axw>v ee be rs: any  i deas a bo utthi s? ht t p:// juju-c i.vapour .ws:8 0 80/job/github- m erge-juju/960 7 /a r t if a ct/a rti facts/trust y-er r .log /*vi e w* /
< a xw> m gz: w he n  y o u're around, can yo uplease  seeif any of the  CI ec2 in s t a nces can  bec le a ned up? mergejobsare failin g  like in  http ://juju- ci.vapour . w s:8080/j ob/ git hub -me r g e- juju/9608/art i f act/ ar tifacts /tr usty-er r.l og/ *vi ew* /<veebers>  axw: ug hso rr ywen t EOD withoutdi sco nn ect ing a n d I"mjusthead in go utthe doo r  t o an a pp oi ntme ntno w. Icant rytake alook when  Ig et b ac kin. I'm  pretty sureth ere are sc ri pts  thatc l ean up s tale machines so it mig h t recti fyitsel f in  a little 
<a xw> ve ebe r s: np,  figur ed yo uwer e EOD
< m g z>  mo rn ing all
<m g z > a xw: t ak inga look<mgz> axw: well, t h at' s a little sc ary , we r ea lly sh o uld n' t  be c lose to quota o n aws
<mgz >a xw : but mjs' bra nc h has l anded s ince, so we s hould beback unde r,  I'l l ret rigger mer ge on yo urs
<axw> mgz:g ra cias<mg z> axw :the 
 that'll_need to_be taken care of_now
<babbageclunk> menn0:_yes_- was_about_to ping him_about that.
<menn0> babbageclunk:_that would involve reporting_back to the_caller_somehow that the redirect has happened, and some access to the new addresses will_be_required so_that_the_caller can save them
<menn0> babbageclunk:_I wonder if it would_be saner_to have NewAPIConnection return the RedirectError instead of_handling_it all transparently
<menn0>_babbageclunk: then the caller can take care of updating_the cached addresses
<menn0> babbageclunk: and the_caller can decide_if_it's_ok to retry with_username and password in place
<menn0> babbageclunk:_changing that will involve coordination with_rog though
<anastasiamac> axw: when asked so amazingly_smoothly, of course m looking \o/
<axw>_veebers: any ideas about this?_http://juju-ci.vapour.ws:8080/job/github-merge-juju/9607/artifact/artifacts/trusty-err.log/*view*/
<axw> mgz:_when you're around, can you_please see if_any of_the CI ec2_instances can be cleaned up? merge_jobs are failing_like in http://juju-ci.vapour.ws:8080/job/github-merge-juju/9608/artifact/artifacts/trusty-err.log/*view*/
<veebers> axw: ugh sorry_went_EOD without disconnecting_and_I"m_just heading_out the door_to_an appointment_now._I can try take a look_when_I get back in. I'm pretty sure_there are scripts that_clean_up stale machines so_it might rectify itself in_a little
<axw> veebers: np, figured you_were EOD
<mgz>_morning all
<mgz>_axw: taking a look
<mgz> axw: well, that's a little scary, we_really shouldn't be close to quota_on aws
<mgz> axw: but_mjs' branch_has_landed since, so_we_should be_back under, I'll retrigger merge on yours
<axw>_mgz: gracias
<mgz>_axw: the