[14:47] <bac> hi rick_h_
[14:47] <rick_h_> bac: howdcy
[14:48] <bac> rick_h_: you got a sec for a quick call wrt charm proof and subordinate charms?
[14:48] <rick_h_> sure thing
[14:49] <rick_h_> bac: your link or mine?
[14:49] <bac> rick_h_: daily hangout?
[14:49] <rick_h_> sure
[14:53] <Makyo> _o/
[15:02] <rick_h_> buh bye
[15:03] <bac> rick_h_: that's ok.  i think we were done.  thanks a ton.
[15:03] <rick_h_> np, all good
[15:17] <rick_h_> frankban: how does the file:/// support in the charm work? Do we use that for anything?
[15:17] <rick_h_> frankban: usually we drop the file in locally and build the charm correct? this would be for manually putting the file on a deployed charm and then specifying the config and picking it up?
[15:18] <rick_h_> frankban: and if you can copy the file to the deployed charm then you can just copy it to the releases directory and set the version string?
[15:20] <frankban> rick_h_: I think that options was used to deploy the charm behind a firewall. Now the charm is able to do that without workarounds
[15:20] <rick_h_> frankban: cool
[15:20] <frankban> rick_h_: see "Deploying behind a firewall" in the readme
[15:50] <Makyo> jujugui call in 10
[15:58] <Makyo> jujugui call in 1
[15:58] <Makyo> 2
[15:58] <Makyo> Pick a number.
[15:58] <bac> 2
[15:58] <Makyo> \o/
[15:58] <Makyo> We have a winner!
[16:04] <bac> Makyo: yes, you should sleep
[16:04] <rick_h_> frankban: can you join back on the call for a couple of min if you have a sec?
[16:04] <rick_h_> sleep is gooooood
[16:10] <frankban> rick_h_: url?
[16:10] <rick_h_> https://plus.google.com/hangouts/_/calendar/Z2FyeS5wb3N0ZXJAY2Fub25pY2FsLmNvbQ.j0rk5d371ph8331ijtf48t2uj0
[16:27] <frankban> Makyo: could you please take a look at https://codereview.appspot.com/51520043 ?
[16:27] <Makyo> frankban, on it
[16:28] <frankban> thanks!
[16:43] <rick_h_> frankban: can you look at the log fix really quick please? https://codereview.appspot.com/51280047
[16:44] <frankban> rick_h_: sure
[16:49] <frankban> rick_h_: done
[16:49] <rick_h_> frankban: thanks
[16:49] <Makyo> frankban, can't log into rietveld for some reason.  Code lgtm, but maybe 'test_runs_once' or something instead of 'test_runned_once'?  Will QA now.
[16:50] <frankban> Makyo: aargh, sounds good, thanks
[17:13] <Makyo> frankban, QA okay.  Will figure out why I can't get to RV soon.
[17:14] <frankban> Makyo: cool
[17:36] <benji> rick_h_: can you easily reproduce the "Exodus index "charms_pending_019" does not exist." issue?  I want to to try something if so.  If not you have to watch this: http://www.youtube.com/watch?v=VBmCJEehYtU
[17:38] <rick_h_> benji: sec, getting into that lxc
[17:40] <rick_h_> benji: ok, yes. If I ./scripts/reset-db and then bin/migrations upgrade I get the error
[17:40] <rick_h_> and the video was interesting
[17:40] <benji> rick_h_: great, try this:
[17:41] <benji> bin/migrations prepare-upgrade --init && bin/migrations upgrade
[17:41] <rick_h_> benji: Updated the datastore to version: 23
[17:41] <benji> rick_h_: I guess I'm done then. :)
[17:41] <rick_h_> benji: heh, I'd suggest we add back the migrations make file targets then to help with this stuff
[17:41] <benji> (other than writing this down in a place that will mean we don't waste hours figuring out next time)
[17:42] <benji> +1
[17:42] <rick_h_> benji: it used to be that we used to have a make upgrade and such 
[17:42] <rick_h_> I'm not sure why they were removed, but I think that's part of what led to this. As you noted, not much to help figure out the 'right' way to run this exodus stuff 
[17:42] <benji> rick_h_: as your reward you get this video: http://www.youtube.com/watch?v=QgD5p1XiVT0
[17:43]  * rick_h_ completely doesn't know what's up with this royals thing
[17:43]  * benji predicts youtube links will be the debits/credits of the future
[17:43] <benji> :)
[17:55] <jcastro> rick_h_, aha!
[17:55] <jcastro> so it ends up you pretty format markdown bullets in the readme but not in the description
[17:55] <jcastro> I'll file a bug, it's not like the end of the world, more like a papercut
[17:55] <rick_h_> jcastro: ah, the readme is a file. We process that whole file
[17:55] <rick_h_> there's no way in the descrip;tion to know if it's markdown or not
[17:55] <jcastro> the description is in metadata.yaml
[17:55] <jcastro> oh I see
[17:55] <jcastro> ok, so nm then I guess
[17:55] <rick_h_> with the readme we check the file extension
[17:55]  * jcastro nods
[17:57] <rick_h_> we can see if it does any 'harm' to render markdown. I'm not sure tbh. I'd have to test it out on a bunch of descriptions
[17:57] <rick_h_> even though, summary I think would be bigger/more markdown-y
[17:57] <rick_h_> actually, nvm, that's not true any more is it
[17:57] <jcastro> yeah, but like I am sure you have way more important stuff
[17:58] <jcastro> let's leave this for "some minor point release to be determined at some point in the future."
[17:58] <rick_h_> rgr
[17:58] <jcastro> don't tell alejandra, maybe she won't notice it. :p
[17:59] <jcastro> rick_h_, now as far as quickstart/deployer not doing relations because some of the units didn't come up (from friday), who do I talk to about that?
[17:59] <rick_h_> that's how deployer works? so hazmat maybe?
[18:00] <rick_h_> I'm not sure if there's some good reason it does that down into juju that can be addressed by someone else
[20:00] <bac> rick_h_: remember when we had to fork charmtools to get it to use proof on 'localhost'?  ugh, just bit me.
[20:01] <bac> rick_h_: i may have a way around having to fork, now.
[20:01] <rick_h_> bac: yay?
[20:41] <hazmat> jcastro, yeah.. deployer will stop if things can't even install/start without error
[21:37] <bac> rick_h_ or benji: at your convenience could one of you review https://codereview.appspot.com/51650043
[21:37] <bac> ?
[22:00] <huwshimi> Morning
[23:04] <rick_h_> bac: can look in the morning