[00:14] <gary_poster> :-)
[11:46] <antdillon> Hi guys, is there anyone online from the juju gui team?
[11:51] <rick_h> antdillon: yep
[11:52] <antdillon> rick_h, Hey, thanks. Just a quick question about the browse section of jujucharms.com 
[11:52] <rick_h> antdillon: sure thing
[11:53] <antdillon> rick_h, Were linking directly to charms from the new juju.u.com website
[11:53] <rick_h> antdillon: ok
[11:53] <antdillon> rick_h, For example using this URL: https://jujucharms.com/precise/mongodb-15/
[11:53] <antdillon> rick_h, Is there a way to link that wont go out of date?
[11:53] <rick_h> antdillon: yep, so for now it needs to be -HEAD vs -15
[11:54] <rick_h> antdillon: in the future we hope to be able to drop that, but it's not complete yet
[11:54] <antdillon> rick_h, As in https://jujucharms.com/mongodb-15/
[11:54] <rick_h> antdillon: oh...ditch the precise...ugh no. We don't have anything for that and not sure it would work as most charms don't exist outside of precise atm
[11:54] <antdillon> rick_h, Because we dont want to link them to percise when saucy is out
[11:55] <rick_h> https://jujucharms.com/fullscreen/search/?series=raring&text= for instance is raring's charm list
[11:56] <rick_h> antdillon: yea sorry, we'll have to deal with updates when we know we want to update them. I don't think you'll want saucy links when saucy is out
[11:56] <rick_h> antdillon: you'll want to use https://jujucharms.com/precise/mongodb-HEAD
[11:59] <antdillon> rick_h, Ok cool, I'll leave it with precise in the url
[11:59] <antdillon> rick_h, Thanks for the help. Might be worth thinking about creating short links to the charms for sharing
[12:00] <rick_h> antdillon: yep, it's a bit complicated since you need to match your juju environment version to the charm version and such
[12:00] <rick_h> antdillon: but will bring it up on the call today and might be a good sprint topic in Oct
[12:00] <antdillon> rick_h, https://jujucharms.com/precise/mongodb-HEAD/ the tweet link tweets to https://jujucharms.com/precise/mongodb-15/
[12:01] <rick_h> antdillon: yea, we should fix that. -HEAD is relatively new
[12:01] <antdillon> rick_h, Cool thanks
[12:08] <gary_poster> hey antdillon.  charms are per series, and generally in Juju we care about the LTS charms not the dev/6 mo. release charms.  So what you raise is an interesting question but not pressing until we start thinking about T/14.04
[12:08] <gary_poster> (the next LTS IIRC)
[12:20] <antdillon> gary_poster, Cool I understand
[12:20] <gary_poster> cool
[12:20] <antdillon> gary_poster, So should use -HEAD for all charms?
[12:22] <gary_poster> antdillon, yes, for now.
[12:23] <bac> gary_poster: i'm here today
[12:23] <gary_poster> yay bac!  100%, or?
[12:23] <gary_poster> as in feeling 100%
[12:24] <bac> no, but i'm faking it.  :)
[12:25] <gary_poster> bac, heh, ok, take it easy
[12:31] <marcoceppi> hey guys, what does the charm use to serve the pages? Apache?
[12:31] <gary_poster> marcoceppi, atm, yes.  with bundle work upcoming, it will be a custom Tornado server
[12:32] <gary_poster> marcoceppi, btw, one of hatch or Makyo will join you guys in doc sprint when their day starts in a few hours
[12:50] <luca__> can someone tell me the commands in the CLI to import and export a bundle or charm to Juju?
[12:51] <luca__> gary_poster: rick_h ^
[12:51] <rick_h> luca__: I'm not sure I've not tried it out yet :/
[12:51] <rick_h> bac: or marcoceppi do you know?
[12:51] <luca__> rick_h: useless! :P
[12:51] <gary_poster> luca__, you use the juju deployer, not the CLI
[12:51] <rick_h> luca__: as usual :)
[12:52] <gary_poster> I mean, that is the CLI, not juju itself :-)
[12:52] <marcoceppi> luca__: there is no cli yet, though I'm trying to write a plugin for it
[12:52] <marcoceppi> For exporting an environment
[12:52] <marcoceppi> importing you use juju-deployer
[12:52] <gary_poster> marcoceppi, I thought Kapil was working on the exporter, or had one?
[12:52] <luca__> so if I want to import and export something now via the terminal, how do I do that?
[12:53] <marcoceppi> gary_poster: maybe? we had jitsu export, but those aren't compatible IIRC
[12:53] <luca__> I want the commands for the juju.ubuntu.com website
[12:53] <gary_poster> marcoceppi, yeah I thought Kapil was adding it to deployer.  maybe a good idea to sync up with him
[12:53] <marcoceppi> gary_poster: ack, thanks
[12:53] <gary_poster> luca__, there is no export command at this time
[12:53] <luca__> gary_poster: right
[12:53] <luca__> gary_poster: ok
[12:53] <luca__> gary_poster: and is there a way to interrogate the charm store via the command line? like search for stuff? see a list of charms?
[12:54] <marcoceppi> luca__: there's a set of tools called `charm-tools` that can search the store and list charms
[12:54] <rick_h> luca__: oh oh, this one I do know :P
[12:54] <marcoceppi> luca__: they're being rewritten to be executed as `juju charm search`, etc
[12:54] <rick_h> marcoceppi: oh, heads up, api3 with bundle support is coming soon
[12:54] <rick_h> marcoceppi: in case this is what's using the charmworld api
[12:54] <marcoceppi> rick_h: I have no idea what that means, but is sounds awesome
[12:55] <gary_poster> luca__, for import...I think it is nasty: you have to get a certain branch (https://code.launchpad.net/~juju-deployers/juju-deployer/darwin) and then...I forget
[12:55] <gary_poster> I mean, nasty in comparison to "install package foo"
[12:55] <luca__> marcoceppi: how soon will that happen?
[12:55] <marcoceppi> luca__: you can install charm-tools right now and use them as `charm search`, `charm list`, etc
[12:55] <frankban> guihelp: could anyone please review https://codereview.appspot.com/13424043 ? thanks!
[12:56] <rick_h> marcoceppi: I linked you to http://bazaar.launchpad.net/~juju-jitsu/charmworld/trunk/view/head:/docs/api.rst so it means a nwe version of the api with bundles support is coming 
[12:56] <marcoceppi> luca__: it's got a lot of tools actually, ppa:juju/pkgs to install charm-tools
[12:56] <rick_h> frankban: looking
[12:56] <frankban> rick_h: thank you
[12:56] <marcoceppi> rick_h: ah, awesome! will v2 stay around for a while?
[12:56] <rick_h> marcoceppi: yes, but won't get bundles so limited to old scope
[12:56] <marcoceppi> rick_h: ack, thanks for the heads up
[12:57] <gary_poster> luca__, this is pertinent to your deployer import questions: https://docs.google.com/a/canonical.com/document/d/1i_sdbswSovHygc8URsh30zTBx_2G9VZBLlb3qbUmfCM/edit#heading=h.8dx2qatdl279
[12:58] <gary_poster> luca__, prerequisites section and #1 of "Steps to be done in front of  a live audience"
[13:00] <luca__> gary_poster: I see, thanks
[13:03] <hatch> morning
[13:03] <rick_h> hatch: morning, want to chat when you get your morning cup of joe please
[13:04] <hatch> rick_h: prolly won't be for another 30
[13:04] <rick_h> hatch: np, just putting in first dibs since you stuck your head up :P
[13:04] <gary_poster> morning hatch. :-)  You and/or Makyo are scheduled to join in doc sprint today.  I'm loathe to lose either of you, but given constraint and inspector work, I'm inclined to ask Makyo to do it.  That postpones his Go relation work.  Is that ok?
[13:07] <abentley> bac: I'm documenting the 3.0 API.  It looks like a 3-part bundle-id is always treated as owner/basket/bundle, never basket/revision/bundle.  Do we consider this a bug?
[13:07] <hatch> gary_poster: yep that'll be fine, I would like to push to get the inspector unflagged
[13:08] <gary_poster> great hatch, thanks
[13:08] <benji> bac: I think you worked on the view that renders /bundles/{basket}/{bundle}/json.  Is that right?
[13:08] <hatch> frankban: thanks a ton for the QA/review I'll look into fixing that shortly
[13:09] <frankban> hatch: np
[13:09] <bac> benji: yes
[13:09] <rick_h> benji: abentley we have a view /json? 
[13:09] <hatch> luca__: antdillon hey guys looks like the place in Heathrow that sells sims is in terminal 1 security and I land in 3, do you know of anywhere else close that I should go to pick up a sim card?
[13:09] <benji> bac: I can't seem to see a view for /bundles/{basket}/{bundle} (no "json"), do you know if that exists?
[13:10] <abentley> rick_h: I didn't think so.
[13:10] <rick_h> abentley: yea, that was the 'old' api stuff so same to dupe it over 
[13:11] <antdillon> hatch, Near terminal 3 or the office?
[13:11] <abentley> rick_h: "same to dupe it over"?
[13:12] <rick_h> abentley: /same/shame to pull that convention over
[13:12] <abentley> rick_h: +1
[13:12] <bac> benji: no it has not been implemented as it was going to be part of the SEO work
[13:12] <hatch> antdillon: well I plan on going from the airport to the science and natural history museum (sunday) so i'd like to get it before then but close to the office would suffice as well and I can pick it up Monday
[13:12] <benji> bac: ok, thanks for verifying 
[13:17] <frankban> gary_poster: I am going to 1) test the charm-upgrade + set builtin-server story, 2) make fixes if required and then 3) merge juju-gui into charmers. is it ok?
[13:17] <gary_poster> frankban, yes, thank you!
[13:18] <bac> abentley: i'm not sure about your question based on the URLs we listed in the google docs "spec".
[13:25] <abentley> bac: So, on API 3, there's a way to get a specific revision of an unpromulgated charm: owner/basket/revision/bundle.  For a promulgated charm, basket/revision/bundle won't work.  That seem asymmetrical, though perhaps the intent is that you use owner/basket/revision/bundle for that, too?
[13:27] <antdillon> hatch, You should be able to walk into any phone shops in london and pick up a sim card. There are hundreds in london (like starbucks)
[13:29] <bac> abentley: that is my recollection of the discussion.  if we have a use case for the api to support unrevisioned access let's list it in the doc.
[13:30] <abentley> bac: We already have unrevisioned access.  What we don't have is revisioned access with unspecified owner.
[13:35] <bac> abentley: how would that work?  revisioned access for a bundle with no specified owner?  two different people could have a given (basket, bundle) at the same revision.  which do we pick?
[13:36] <abentley> bac: We would pick the promulgated one, as we do for two-element bundle ids like "basket/bundle".
[13:41] <hatch> antdillon: ohh ok :) any certain network I should try and get on?
[13:41] <hatch> I'll likely be using primarily data
[13:43] <antdillon> hatch, EE is good, I use them. You might be able to get 4G?
[13:43] <hatch> ahh cool
[13:43] <hatch> I think I am stuck on GSM because of the radios in my phone
[13:43] <hatch> they use a different 4g frequency here I think
[13:43] <antdillon> hatch, Then you'll be flighting, 4G is faster then most wifi's
[13:44] <hatch> yeah that's the same here
[13:44] <antdillon> hatch, Ah ok
[13:44] <hatch> I just don't want to spend $0.65/txt, $2/min, $15/MB :)
[13:45] <antdillon> Of course, that's nuts!
[13:46] <hatch> I think I'll add everyone to my G+ and then use hangouts to communicate once I Have data
[13:46] <hatch> assuming others have data....
[13:53] <jcsackett> rick_h: can i get you to look at https://codereview.appspot.com/13289046 ?
[13:53] <rick_h> jcsackett: sure thing
[13:54] <abentley> rick_h: We were going to have "/download" for bundles so that deployer could use those urls directly.  bac changed "/download" to "/json" for consistency with charms.
[13:55] <gary_poster> jcsackett, I didn't see you were back.  how are you?
[13:55] <rick_h> abentley: not following. What's /download for?
[13:55] <jcsackett> gary_poster: i'm alright. tho my typing speed is considerably slower. :-P
[13:55] <gary_poster> jcsackett, ack.  glad you are on the mend.  not sure if I want to hear exactly what happened or if I would faint. :-)
[13:57] <abentley> rick_h: $juju deployer -c http://manage.jujucharms.com/bundles/~owner/basket/revision/bundle
[13:57] <rick_h> abentley: ah, interesting. I didn't realize that deployer was grabbing from charmworld vs the store like charms. 
[13:58] <abentley> rick_h: We don't store bundles in the store at all.
[13:58] <rick_h> abentley: ok, so ignore me if /json isn't part of matching the deprecated api 
[13:58] <marcoceppi> Found a weird bug in the GUI
[13:58] <rick_h> abentley: hmm, so the deployer won't set the json request headers to send the response on headers vs url change?
[13:58] <rick_h> marcoceppi: shoot man
[13:59] <abentley> rick_h: I still think it should be /download, not /json.
[13:59] <rick_h> abentley: yea, I'd prefer that it send content-type in the request but oh well
[14:00] <abentley> rick_h: putting it in the URL rather than request headers makes it much easier for a user to control.
[14:00] <rick_h> abentley: yea, understand. 
[14:01] <abentley> rick_h: Also, we can provide a download link that way.
[14:02] <marcoceppi> rick_h: yesterday I searched and visisted ~marcoceppi/precise/discourse, which took me to ~marcoceppi/precise/discourse-20. So I went to -HEAD because I wanted to refresh it after I updated the charm in the store and watch the magic. Now when I search the URL it takes me to is -21 but the content is still -20 (as well as -HEAD) it's like there's some severe cache or something
[14:02] <marcoceppi> rick_h: does https://jujucharms.com/~marcoceppi/precise/discourse-21/ show location as -20 ?
[14:02] <rick_h> marcoceppi: yea, looking
[14:03] <rick_h> marcoceppi: and shows head as r64?
[14:03] <rick_h> marcoceppi: maybe ingest error on changes?
[14:03] <hatch> rick_h: ready when you are
[14:03] <rick_h> marcoceppi: run proof?
[14:04] <rick_h> hatch: I'm good I think.
[14:04] <marcoceppi> rick_h: just shows a W about hook not executable
[14:04] <hatch> rick_h: ok in guichat
[14:04] <marcoceppi> rick_h: the change was purely hook based, nothing in metadata changed
[14:04] <marcoceppi> but the serach results show the right version (commits and downloads)
[14:04] <marcoceppi> and takes me to -21
[14:04] <rick_h> marcoceppi: will have to look into staging to see if there's an import error
[14:04] <marcoceppi> rick_h: ack, gotchya
[14:05] <rick_h> marcoceppi: I'm all confused, the branch is r64, the rev in the file is 17
[14:05] <rick_h> marcoceppi: so not sure where the 20/21 is even coming from tbh
[14:05] <marcoceppi> rick_h: that's charm-store version
[14:06] <marcoceppi> rick_h: which is independent of bzr version and local revision file
[14:06]  * marcoceppi holds back on this
[14:06] <rick_h> marcoceppi: k, will check in a sec.
[14:07] <abentley> bac: When a 3-element bundle-id is specified, it looks like we treat the three elements as owner, basket, bundle, but then we return only promulgated bundles.  Is this a bug?
[14:08] <adeuring> abentley: could have a look here: https://code.launchpad.net/~adeuring/charmworld/spurious-failures-2/+merge/183183 (a bit longer than the core 5 lines I expected yesterday, but not terribly long either...)
[14:09] <abentley> adeuring: sure.
[14:13] <abentley> adeuring: r=me.  Thanks.
[14:14] <adeuring> thanks
[14:15] <bac> perhaps it is abentley.  please file a bug or make a note in the doc if you wouuld.
[14:26] <abentley> bac: I've filed bug #1218949
[14:26] <_mup_> Bug #1218949: Cannot retrieve head revision of an un-promulgated bundle over API 3. <charmworld:Confirmed> <https://launchpad.net/bugs/1218949>
[14:26] <bac> thanks abentley
[14:35] <rick_h> jcsackett: inboud
[14:37] <rick_h> marcoceppi: cool yea seeing the store sees https://store.juju.ubuntu.com/charm-info?charms=cs:~marcoceppi/precise/discourse 21
[14:38] <rick_h> bac: gary_poster there's a config conflict in comingsoon it looks like?
[14:38] <rick_h> http://comingsoon.jujucharms.com/juju-ui/assets/config.js
[14:38] <bac> rick_h: i'll look
[14:38] <gary_poster> than kyou
[14:38] <rick_h> thanks bac 
[14:40] <hatch> ok now where was I
[14:44] <rick_h> abentley: have a sec to give me a hand searching this issue for marcoceppi?
[14:44] <abentley> rick_h: sure.
[14:45] <rick_h> abentley: guichat?
[14:45] <abentley> rick_h: yup.
[14:46] <bac> rick_h: try now
[14:47] <gary_poster> Hey Makyo, I want to reply to rogpeppe's email in which he asked me what the ordering change was that broke the GUI.  IIRC, new relations were being sent before services?  That doesn't sound right unless the deployer was involved.  any quick details I can pass on?
[14:48] <Makyo> gary_poster, units before services; when we were receiving units after services, the delta triggered adding the unit to a ModelList attached to the service.  If it was before, the service didn't exist.  The solution was sorting the deltas 
[14:48] <gary_poster> cool thanks Makyo, will pass on
[14:51] <rick_h> marcoceppi: so working on it still, it's fine on staging http://staging.jujucharms.com/api/2/charm/~marcoceppi/precise/discourse-21 and the proof errors listing in production appears to only do reviewed charms so filed #1218966, 
[14:51] <_mup_> Bug #1218966: proof errors appear to only display for revewied charms <charmworld:Triaged> <https://launchpad.net/bugs/1218966>
[14:52] <rick_h> marcoceppi: have to go to IS now and have them help get at the logs on production to see what error is thrown. Note that, on production, it stopped at r60, so r61 probably introduced something it didn't like. https://manage.jujucharms.com/api/2/charm/~marcoceppi/precise/discourse-21
[14:52] <marcoceppi> rick_h: thanks, I wanted to blog/share that link eventually, so I appreciate you looking in to it
[14:52] <frankban> gary_poster: charmers' charm is up to date
[14:53] <gary_poster> awesome, frankban thanks.  Do you want to send out an announcement/request for testing, or do you want me to?
[14:53]  * marcoceppi looks at rev 60
[14:53]  * marcoceppi 61*
[14:54] <frankban> gary_poster: please do it, thanks! for the jujucharms.com upgrade i'd wait till Monday
[14:54] <gary_poster> ack frankban, completely agree :-)
[14:54] <frankban> gary_poster: the upgrade being: 1) upgrade-charm and 2) set builtin-server=true
[14:54] <gary_poster> cool
[14:55] <rick_h> frankban: gary_poster does the constraints issue that hatch is working on effect release though? e.g. will users end up not beign able to deploy?
[14:55] <gary_poster> rick_h, no.  frankban made a charm release not a gui release
[14:55] <hatch> with the new inspector
[14:55] <rick_h> gary_poster: k, ignore me then. 
[14:55] <gary_poster> :-) np
[14:56] <rick_h> marcoceppi: heads up that I do see these errors http://paste.mitechie.com/show/1012/ not sure if those are outdated or what. 
[14:56] <hatch> my laptop has been acting up today.......plz don't break plz don't break plz don't break
[14:56] <marcoceppi> rick_h: redmine and charm-helper are dead and gone, not sure why it's pulling those
[14:57] <frankban> gary_poster: FWIW, we can know from the outside if a GUI is run by the Tornado server visiting the /gui-server-info URL (without the trailing slash)
[14:57] <gary_poster> ah cool frankban good to know, ty
[14:59] <jcsackett> rick_h: thanks for the review. good catch on the needed cleanup.
[15:01]  * benji wonders if the call time has changed.
[15:04] <hatch> jujugui - guichat 4 mins ago!
[15:05] <Makyo> hatch, calendar says 9:30?
[15:05] <hatch> for real???
[15:05] <gary_poster> jujugui postponed 30 minutes
[15:05] <hatch> lol
[15:05] <hatch> oops we all missed that
[15:11] <abentley> bac or benji: could you please review https://code.launchpad.net/~abentley/charmworld/api3-docs/+merge/183206 ?
[15:12] <benji> abentley: I'll take a look
[15:13] <abentley> benji: Thanks.
[15:20] <Makyo> jujugui call in 10 kanban now.
[15:22] <rick_h> abentley: why is bundles/bundleid plural?
[15:22] <abentley> rick_h: I don't know.  I didn't implement it.
[15:22] <rick_h> abentley: ok
[15:23] <rick_h> abentley: r=me
[15:25] <abentley> rick_h: Thanks, but benji was looking at that.
[15:25] <rick_h> abentley: ok
[15:25] <rick_h> abentley: well, you can have two, figured I'd peek at since I'll be looking shortly
[15:25] <abentley> rick_h: Cool.
[15:25] <benji> abentley / rick_h: well if we have one, that is enough
[15:26] <benji> I did enjoy the ASCII art table, though.
[15:26] <rick_h> benji: abentley bac is there any opposition to dropping the s on bundles/bundleid for consistency ?
[15:26] <abentley> benji: Yay for ASCII art in ReST.
[15:26] <abentley> rick_h: I am in favour of dropping the s.
[15:28] <benji> abentley: if you /really/ like reST tables, have I got something for you: http://pythonhosted.org/manuel/table-example.html#fit-table-example
[15:30] <benji> (and that document which shows how to write tests to test documents, itself includes tests to show that the document is correct)
[15:30] <gary_poster> jujugui call now
[15:30] <bac> rick_h: i am not opposed.
[15:31] <rick_h> bac: yay!
[15:31] <gary_poster> jcsackett, ping for call if you can come
[15:46] <rick_h> bac: can you drive by that on your current work or should I create a seperate branch?
[15:49] <bac> rick_h: i'll do it as a follow-on.  i'll make a card
[16:32] <rick_h> abentley: filed a bug based ont he log from prod. https://bugs.launchpad.net/charmworld/+bug/1219001
[16:32] <_mup_> Bug #1219001: production error on several charms "KeyError: 'branch_deleted'" <charmworld:Confirmed> <https://launchpad.net/bugs/1219001>
[16:32] <rick_h> abentley: looks like a bunch of charms are hitting this keyerror and don't get ingested
[16:32] <hatch> jujugui ok well if anyone wants to mee up sunday during the day or for supper/after pm me your cell #
[16:32] <abentley> rick_h: saw.  Huh.
[16:33] <gary_poster> hatch, I'll probably email you in that case.  won't have data
[16:33] <gary_poster> if you miss it np
[16:34] <hatch> gary_poster: sure thing - my plan is to head from the airport to get a sim then to the science/history museum
[16:34] <gary_poster> ok cool
[16:34] <hatch> texts cost me $0.65 so I want to get that new sim asap :)
[16:35] <frankban> gary_poster: I've found a charm bug in the wss url handling when a real pyjuju env is used. Will self review, land, and include in charmers ASAP: https://codereview.appspot.com/13432043
[16:35] <abentley> rick_h: I don't understand how we get that far without setting branch_deleted.
[16:35] <gary_poster> thank you frankban 
[16:35] <hatch> frankban: so in moving the constraints stuff into the env/store/python.js deploy method that fixes rapi and go sandbox but breaks python sandbox :/
[16:36] <hatch> so not sure what's up with that....sandbox must be broken
[16:36] <frankban> hatch: ISTM that the python sandbox still expects to be able to call deploy passing an array of constraints
[16:36] <frankban> hatch: maybe?
[16:36] <abentley> rick_h: That data should already be set when charms are enqueued.
[16:37] <rick_h> abentley: k, did you want the log file?
[16:37] <hatch> frankban: so I put the formatting in the deploy method in python.js so it's breaking somewhere after the rpc call
[16:37] <abentley> rick_h: Yes, please.
[16:37] <rick_h> abentley: it's 30M compressed so didn't send/attachj it
[16:38] <hatch> so must be fakebackend.js is broken then?
[16:38] <rick_h> abentley: uploading, will take a sec
[16:40] <frankban> hatch: and sandbox receives the rpc call right?
[16:44] <hatch> frankban: I can never remember the sequence of events, putting in breakpoints now heh
[16:44] <rick_h> marcoceppi: got the logs off production there's a bug for it to follow #1219001. Sorry for the issue
[16:44] <_mup_> Bug #1219001: production error on several charms "KeyError: 'branch_deleted'" <charmworld:Confirmed> <https://launchpad.net/bugs/1219001>
[16:54] <hatch> frankban: found the problem, it's in the Service model
[16:54] <frankban> gary_poster: charmers updated
[16:54] <frankban> hatch: interesting
[16:56] <abentley> rick_h: I don't see any KeyError on branch_deleted since June 13.  I don't think it can be the cause of this issue.
[16:57] <rick_h> abentley: oh, crap I went to the end of the file and searched backwards for discourse and didn't read the timestamp :/
[16:58]  * Makyo runs to go get the phone unlocked for real.
[16:58] <rick_h> abentley: oh...then my bad, let me invalid that bug and go back. 
[16:58] <frankban> hatch: constraintsStr getter?
[16:58] <marcoceppi> rick_h: oh, branch_deleted ?
[16:59] <rick_h> marcoceppi: ignore me, I found an error in the log from a month ago..back to researching
[17:00] <hatch> frankban: yeah - I don't see any other place to modify the constraints data
[17:01] <rick_h> whoa, just lost power...on laptop battery atm. 
[17:01] <frankban> hatch: good luck, and have a nice weekend!
[17:01] <rick_h> note to self, put desktop on UPS
[17:01] <hatch> frankban: could change it back in the fakebackend
[17:01] <hatch> frankban: you too! see you Monday/Tuesday
[17:08] <rick_h> yay power is back
[17:08] <hatch> I don't know anyone else with an off brand phone with a micro sim hah, guess I'll just have to buy the unlock code and hope it works once I get there :)
[17:12] <rick_h> abentley: so I don't see anything in the log. I do notice that discourse r64 is listed in the http://manage.jujucharms.com/recently-changed view
[17:12] <rick_h> abentley: so now wondering if there's a mongo vs ES issue? is recently changed pulled straight from mongo while the charm data is pulled from ES? or not true?
[17:24] <hatch> oh sweet check out the new relation lines on the GUI http://www.ubuntu.com/cloud (scroll down)
[17:37] <gary_poster> heh cool
[17:38]  * hatch wonders who's repo that's in lol
[17:38] <hatch> I actually think they look pretty cool
[17:39] <hatch> of course they are missing the labels but the green adds some nice color
[17:39] <hatch> it could even indicate relation status (if there is such a thing)
[17:40] <hatch> rick_h: so documentation to get the lxc and go stuff up and running?
[17:41] <hatch> unless you just want to QA this branch for me and we can do that later
[17:41] <hatch> (would be my preference :) )
[17:48] <rick_h> hatch: :P I can QA
[17:48] <rick_h> hatch: http://marcoceppi.com/2013/07/compiling-juju-and-the-local-provider/ is what I went with
[17:48] <rick_h> well, some of that, not all needed
[17:48] <rick_h> environments is a 2-liner change and juju switch ftw
[17:49] <hatch> rick_h: ok just linting and making sure the tests pass then I'll repropose
[17:49] <hatch> thanks
[17:49] <rick_h> hatch: rgr
[17:49] <hatch> I just really want to get this landed instead of potentially fighting getting the system up and running
[17:49] <marcoceppi> hatch: I recommend just using juju-core from ppa:juju/devel, the local provider afterwards is pretty easy
[17:50] <hatch> marcoceppi: so instead of compiling from source
[17:50] <rick_h> hatch: yea, don't compile
[17:50] <rick_h> I didn't do that part
[17:50] <hatch> ok cool - I'll keep notes of what I do then and write another blog post about it
[17:50] <rick_h> just ppa and then walked through the rest for environment/starting up
[17:50] <hatch> can't hurt right? :)
[17:50] <rick_h> hatch: +1
[17:50] <marcoceppi> hatch: Yeah, that was me being lazy and killing two birds with one blog post
[17:51] <hatch> lazy lazy
[17:51] <hatch> hey are you still in Japan?
[17:52] <hatch> I just realized it's probably 2am there if you are :D
[17:53] <rick_h> abentley: guess not, both _find_charm and series_charm_changes are on mongo
[17:56] <hatch> rick_h: https://codereview.appspot.com/13252045/  this fixes the bug but not frankbanks request to normalize the config formatting
[17:56] <hatch> that's coming soon, just wanted to get that bug qa'd first
[17:57] <rick_h> hatch: ok, so I'm doing the -core qa section?
[17:57] <hatch> yes plz
[17:57] <hatch> rick_h: wouldn't hurt to do the others too, it's pretty quick
[17:57] <rick_h> hatch: ok, starting up
[18:00] <hatch> thanks
[18:05] <jcsackett> rick_h: did you QA my branch, or do i need to hunt down QA?
[18:06] <rick_h> jcsackett: sorry, did not QA. I can shortly
[18:12] <abentley> rick_h: It looks like something is wrong with the way we find the head revision in mongo.  I don't know whether it's a bug in the data or a bug in the code.  Elasticsearch does recognize that 21 is the head revision.
[18:12] <abentley> rick_h: I thought recently-changed was all-mongo.
[18:12] <rick_h> abentley: yea, I think it is. Both seem all mongo. 
[18:13] <rick_h> abentley: sorry, back/forth in qa'ing/etc. 
[18:13] <rick_h> abentley: so the api uses sort=[('store_data.revision', pymongo.DESCENDING)])
[18:13] <rick_h> abentley: and the charm_changes don't specify a sort :/
[18:14] <abentley> rick_h: This uses elasticsearch: https://manage.jujucharms.com/api/3/search?series=precise&owner=marcoceppi&name=discourse
[18:14] <jcsackett> rick_h: cool, thanks.
[18:14] <rick_h> abentley: right, but https://manage.jujucharms.com/api/2/charm/~marcoceppi/precise/discourse-21 is what I was looking at pulling old data
[18:14] <rick_h> abentley: that's using charm/_find_charm right?
[18:15] <rick_h> abentley: we were looking at why https://manage.jujucharms.com/api/2/charm/~marcoceppi/precise/discourse-HEAD returns rev 60 in the changelog and links to disource-20
[18:16] <abentley> rick_h: Right, it's using _find_charm.
[18:18] <marcoceppi> So, when does this UI show up? http://www.ubuntu.com/cloud
[18:19] <abentley> rick_h: And I'm saying I don't know whether it's a bug in the code or the data, but Elasticsearch looks right.  So it's less likely to be a bug in the data.
[18:19] <rick_h> abentley: right, gotcha
[18:19] <abentley> rick_h: Because we update them in sync.
[18:19] <rick_h> abentley: I figured since the recent changed had the data it was maybe how the query/data was looked at
[18:20] <abentley> rick_h: Haven't had a chance to look at that implementation yet....
[18:20] <rick_h> hatch: I can't deploy anything. I get the error "Could not deploy the requested service." with/without constraints
[18:20] <hatch> what's the error in the console?
[18:20] <rick_h> abentley: can I hand this off to you then? I've got to qa hatch and jcsackett's stuff atm and you're closer to the action
[18:20] <rick_h> hatch: none :/
[18:21] <hatch> guichat?
[18:21] <rick_h> hatch: sure
[18:21] <abentley> rick_h: okay.
[18:21] <rick_h> hatch: if it'll load for me
[18:22] <rick_h> hatch: invite me in please
[18:23] <hatch> ok sec
[18:47] <rick_h> jujuhelp how would I get debug js files in a charm deployed jujugui?
[18:47] <jcastro> hey rick_h 
[18:47] <jcastro> do you have sinzui-like powers for the store?
[18:48] <gary_poster> rick_h, look in charm options.  looking for you...
[18:48] <jcastro> actually, I mean abentley 
[18:48] <rick_h> jcastro: how so?
[18:48] <rick_h> gary_poster: yea, don't see any 'debug' charm options
[18:48] <jcastro> so we renamed the rack charm to "rails"
[18:48] <jcastro> https://jujucharms.com/fullscreen/search/precise/rails-1/?series=precise&text=rails&type=approved
[18:48] <jcastro> but this is not showing the proper charm
[18:48] <jcastro> mims said something like "they need to flush"
[18:49] <gary_poster> rick_h, :-( you are right. I think t must be conflated.looking
[18:49] <abentley> jcastro: I don't think he has special powers.  I think he has to hand-craft urls, but I can do that, too.
[18:49] <jcastro> awesome
[18:49] <rick_h> gary_poster: i've tried logging into the service and running make devel, but then it can't talk to the back end
[18:49] <abentley> jcastro: You know that the store doesn't have a concept of rename, right?
[18:50] <rick_h> gary_poster: I tried to set the back end to go, no sandbox, and I just get ws errors
[18:50] <jcastro> abentley: hah, nice.
[18:50] <rick_h> gary_poster: I assume I'm missing whatever listens on the ws end for go
[18:51] <m_3> abentley: hi
[18:51] <m_3> abentley: so we just need to get any cache related to lp:charms/rails and lp:charms/rack regenerated
[18:51] <gary_poster> rick_h, I'm guessing source mapping is insufficient
[18:51] <abentley> m_3: Why do you say that?
[18:52] <m_3> abentley: so we removed lp:charms/rack
[18:52] <gary_poster> rick_h, staging turns on debug mode :-(
[18:52] <m_3> abentley: and pushed an --overwrite to lp:charms/rails
[18:52] <gary_poster> we should have a separate flagfor that
[18:52] <rick_h> gary_poster: yea, ok cool
[18:53] <m_3> abentley: the overwrite was from a lp:~charmers/charms/precise/rack/trunk branch
[18:53] <m_3> abentley: and there is no longer a ~charmers owned "rack" branch
[18:53] <m_3> so flushing those from the cache and re-injesting lp:charms/rails should handle the changes we need
[18:54] <abentley> m_3: There is nothing that would make the "rack" charm disappear.  The charm store deliberately never deletes anything, regardless of whether you delete the branch.
[18:54] <m_3> abentley: ok, that's secondary to getting it to recognize the overwrite of lp:charms/rails
[18:56] <m_3> abentley: note that the previous version of lp:charms/rails had bzr revno of like 44... the new one has like bzr revno of 11 or 12
[18:57] <abentley> m_3: Are you talking about the charm store or the charm browser?
[18:58] <m_3> abentley: both ideally... I haven't tested if the store is seeing the latest... only the browser
[18:58]  * m_3 testing store now
[19:05] <rick_h> gary_poster: ping, can you join guichat?
[19:06] <gary_poster> rick_h, yes, 60 sec
[19:14] <abentley> m_3: This looks related to the issue marcoceppi was having; If you search, you find precise/rails-1, but when you try to look up precise/rails-1, you get precise/rails-0.
[19:15] <abentley> m_3: I think it is unlikely that clearing squid is going to change that.
[19:17] <m_3> abentley: bummer
[19:17] <m_3> abentley: any suggestions?
[19:19] <abentley> m_3: I am already trying to diagnose this bug.  Your case is helpful, because I can reproduce it on staging, where it should be much easier to diagnose.  But it's on me.  There's not much you can do directly to solve it.
[19:23] <m_3> abentley: yeah, marco described his issue... sounds like the same
[19:23] <m_3> abentley: thanks!
[19:32] <hatch> gary_poster: U. Da. Man.
[19:32] <gary_poster> hatch, lol, yay!
[19:33] <abentley> rick_h: I believe you were looking at the API3 version of _find_charm.  The API2 version lacks the sort, and I think that's the code path on production.
[19:34] <rick_h> gary_poster: so yea, it needs to be an int and it works in the constraints
[19:34] <rick_h> gary_poster: thanks
[19:34] <gary_poster> cool rick_h ! thank you both :-)
[19:35]  * gary_poster continues writing emails :-P
[19:38] <rick_h> abentley: oh! yea
[19:38] <rick_h> abentley: should be able to tell by changing the api version in the same request, /me tries it
[19:39] <Makyo> jujugui: those going to London, if you want to take the Heathrow express instead of Piccadilly (15m vs. 60m): https://gist.github.com/makyo/6393509
[19:39] <rick_h> abentley: hmm, that didn't get it though https://manage.jujucharms.com/api/3/charm/~marcoceppi/precise/discourse-HEAD
[19:40] <gary_poster> cool Makyo thanks
[19:40]  * rick_h is going to get lost at least twice
[19:42] <Makyo> Phone won't unlock, so I won't be reachable.
[19:43] <bcsaller> Makyo: you'll still be able to use public wifi many places though so it can be a help
[19:43] <Makyo> bcsaller, Yeah, still bringing it, of course, just no need giving out my number.
[19:43] <abentley> rick_h: I don't know what revision production is on, but I am certain it's before 371, because it accepts any random number for revision in API3: http://manage.jujucharms.com/api/3/charm/precise/rails-5
[19:43] <Makyo> $50 for those stupid unlock codes :P
[19:44] <rick_h> abentley: ah, nvm then
[19:44] <hatch> Makyo: $25 http://www.cellunlocker.net/
[19:44] <hatch> Makyo: also thanks for the tip about the express
[19:44] <abentley> rick_h: staging is on r373, so on staging, API 3 pukes if you give it a non-existent revision.
[19:44] <Makyo> hatch, I have the codes, I mean, I just can't unlock a rooted phone, and I can't unroot it right now.
[19:46] <hatch> what phone?
[19:46] <hatch> you should be able to unlock it without a code if it's rooted
[19:47] <bac> jujugui: at the top of the hour i'm going to turn off the cronjob that pulls new releases to comingsoon in preparation for a demo on monday.
[19:47] <benji> sounds good
[19:47] <hatch> bac: with the new or old inspector?
[19:48] <bac> hatch: as it currently is on comingsoon
[19:48] <hatch> ahh ok that should be fine then
[19:48] <hatch> just can't deploy using rapi is all
[19:48] <hatch> with the new inspector that is
[19:49] <gary_poster> hatch, the reason behind this is that the inspector will be demoed Monday in an official capacity (see peeps list)
[19:50] <gary_poster> jujugui we don't have times on the spreadsheet.  I'm arriving Sunday morning at 7AM.  Anyone else similar?
[19:50] <hatch> 9:30
[19:51] <hatch> gary_poster: if you click on them the time is in the top bar
[19:51] <gary_poster> oh!
[19:51] <hatch> someone formatted it incorrectly
[19:51] <bac> gary_poster: you get the direct on AA?
[19:51] <Makyo> gary_poster, I formatted it to datetime
[19:51] <gary_poster> bac, yeah
[19:51] <hatch> Makyo: thanks
[19:51] <bac> cool.
[19:51] <gary_poster> oh thanks Makyo awesome
[19:52] <gary_poster> Jeff I might not wait for you at the airport, but if you want to hang out we can
[19:52] <gary_poster> hatch I mean :-)
[19:52] <hatch> I wouldn't wait for me either :P
[19:53] <hatch_> rick_h, https://gist.github.com/hatched/e72f3db21afec05592b3 solution :D
[19:55] <jcsackett> rick_h: any luck QAing?
[19:56] <hatch> bcsaller: Makyo mind taking a peek at that gist I posted above... I need to loop through a list of constraints (of any kind) and convert the numbers to integers but leave the strings alone...this technique works by running parseInt and then comparing the two values with type cooersion - thoughts?
[19:57] <bcsaller>  checking
[19:57] <Makyo> hatch, sure
[19:59] <Makyo> hatch, When I ran `juju set-constraint mem=2G` with core on the command line, the gui reported it as 2048.  This would set it to 2 if I use 2G, correct?
[19:59] <Makyo> '...if I use 2G in the gui, correct?'
[19:59] <gary_poster> Makyo that might be a commandline trick unsupported by the API
[19:59] <rick_h> jcsackett: bah, sorry. hatch's qa'ing ran crazy and I didn't get to it
[20:00] <gary_poster> either way we should document it, and maybe make it nicr
[20:00] <hatch> MakyoL if you typed 2G in the input then it would send 2G to the back end and fail
[20:00] <hatch> we will need client side formatting for these constraints for sure
[20:00] <Makyo> hatch, constraints[cons] = parsed would set it to (int)2, right?
[20:00] <gary_poster> but making it nicer might be a separate step for later.  for now "send an int in M" would be nice help text
[20:00] <hatch> yes but consVal != parsed in that case
[20:00] <hatch> so it would set it to the string value
[20:00] <gary_poster> well, not that exactly :-P
[20:01] <rick_h> jcsackett: link me please? pulling back up my lxc
[20:01] <bcsaller> hatch: I don't think this is proper, you might want to check if it can parse as a number and apply a mapping but if things like 2G need support then its either fancier or a passthrough 
[20:01] <Makyo> Oh, sorry, was mistaken about the ==.  Alright.
[20:01] <BradCrittenden> jujugui: comingsoon locked down at r992
[20:01] <hatch> bcsaller: the Go backend requires they be ints
[20:01] <gary_poster> thank you bac
[20:01] <bac> until monday this time
[20:01] <hatch> but we also need to support things like 'i386'
[20:01] <hatch> so we can't simply parseInt all fields
[20:01] <hatch> some need to be strings, some don't
[20:02] <bcsaller> also I'd do the loop with Object.key(constraints).forEach(...), for..in sometimes ends up with issues
[20:02] <bcsaller> the linter will ask for that ifOwnProp check
[20:02] <hatch> not if i turn that off :P
[20:03] <hatch> but anywho....the technique though....that should work?
[20:03] <rick_h> jcsackett: nvm, got it, qa'ing now
[20:03] <hatch> I haven't found any situations where it fails
[20:03] <hatch> js's type cooersion works pretty well here
[20:04] <hatch> bcsaller: (ps yes I will change it to keys() ) :)
[20:05] <hatch> going to grab some lunch, thanks for looking at that
[20:06] <rick_h> jcsackett: fullscreen doesn't work for me :/
[20:06] <abentley> rick_h, marcoceppi, m_3: I believe I understand what's going on, and I've filed the following bugs: #1219064 #1219061 #1219062
[20:07] <_mup_> Bug #1219064: API 2 does not ensure the latest revision is selected <charmworld:Triaged> <https://launchpad.net/bugs/1219064>
[20:07] <_mup_> Bug #1219061: charm pages do not display the latest revision <charmworld:Triaged> <https://launchpad.net/bugs/1219061>
[20:07] <_mup_> Bug #1219062: Old JSON API does not ensure it retrieves the latest revision <charmworld:Triaged> <https://launchpad.net/bugs/1219062>
[20:07] <rick_h> abentley: awesome...kinda. Thanks for taking that through!
[20:07] <marcoceppi> abentley: thanks for looking in to it
[20:07] <abentley> basically, it's the same kind of mistake in three places.
[20:08] <rick_h> jcsackett: qa-no-ok let me know if you can't repeat the same issues
[20:08] <gary_poster> abentley, all three are either solved in API 3, or will be solved when the GUI is forced to use API 3?
[20:09] <jcsackett> rick_h: huh, fullscreen worked earlier, but isn't now. looking.
[20:09] <abentley> gary_poster: as of r371, API3 is not affected, but production is not on r371 yet.
[20:11] <abentley> gary_poster: The three places are API 2, the old JSON api and the charm browser views, so API3 doesn't directly affect them.
[20:12] <gary_poster> ack abentley.  I just was verifying that we can effectively solve or invalidate all three issues by converting the GUI to use API 3
[20:12] <gary_poster> and my takeaway is "yes"
[20:12] <gary_poster> so, assuming you agree, thank you :-)
[20:12] <abentley> gary_poster: That will fix the GUI, but not charmworld.
[20:13] <gary_poster> abentley, only API 2 though, right?  And once the GUI uses API 3 we can regard API 2 as kaput, and related bugs as invalid?
[20:13] <gary_poster> or are other important clients using API 2?
[20:14] <abentley> gary_poster: I'm not talking API2, I'm talking about the web site  that charmworld provides.
[20:14] <gary_poster> oh
[20:14] <gary_poster> sorry for misunderstanding abentley.  got it.  thanks
[20:15] <abentley> gary_poster: Anyhow, I consider these bugs critical, and trivial, so I expect to fix API2.
[20:15] <gary_poster> abentley, oh ok cool.  thanks
[20:34]  * benji falls into a lint pile like quicksand.
[20:45]  * benji pulls himself out via a conveniently placed vine.
[20:59] <benji> does anyone actually use lbox with charmworld?  the .lbox.check fails with ImportError: cannot import name MAXREPEAT for me
[21:04] <abentley> benji: Sounds like you're trying to use it with the wrong python.  But no, AFAIK, no one uses lbox with charmworld.
[21:05] <benji> I just figured it out as you said that.  I was using a python from my host instead of from my lxc instance.
[21:31] <gary_poster> OK, I'm outta here.  Talk to everyone Monday, and see some of you!
[21:43] <hatch> have a good one gary_poster - I can email/msg/hangout you when I end up with data
[21:44] <hatch> see ya on the other side
[21:49] <hatch> Makyo: still round? did you look into unlocking your phone while it's rooted?
[21:49] <Makyo> hatch, yeah, instructions are 'unroot, unlock, reroot'.
[21:50] <hatch> oh....darn!
[21:50] <Makyo> So I'll just stick with wifi.
[21:51] <Makyo> Both the hotel and (I'm assuming) the office will have it.
[21:51] <Makyo> I can turn on int'l roaming in an emergency, of course.
[21:51] <hatch> yeah would have to be one heck of an emergency for $15/MB lol
[21:52] <Makyo> Hah, I was thinking for voice, granted :)
[21:52] <Makyo> A True Emergency
[21:53] <Makyo> In case I need to dial 0118 999 881 999 119 725 3.
[21:54] <bac> i hope you didn't do that from memory
[21:54] <Makyo> bac, No, but now it's stuck in my head.
[21:56] <hatch> lol what is that number?
[22:01] <Makyo> A joke :P  Emergency is 999, that's from IT Crowd.  http://www.youtube.com/watch?v=ab8GtuPdrUQ
[22:03] <hatch> ohhh :)
[22:03] <hatch> lol
[22:28]  * bcsaller places computer in backpack to leave for airport