[14:29] <mbruzek> rick_h_ ping
[14:33] <rick_h_> mbruzek: pong
[14:34] <mbruzek> rick_h_: https://github.com/CanonicalLtd/jujucharms.com/issues/33  
[14:34] <mbruzek> I am having some problems with jujucharms.com and I created an issue.
[14:34] <rick_h_> mbruzek: yep, we're on it. We've got a request for logs into webops
[14:35] <mbruzek> This is related to a new charm that I just pushed so I was not sure if you have seen this problem before.
[14:35] <rick_h_> mbruzek: landscape folks brought it to our attention yesterday and we've been bug hunting but unable to dupe locally so chasing down prod
[14:35] <rick_h_> ty for the bug report
[14:35] <rick_h_> yes, basically ingestion isn't happening on prod atm
[14:35] <rick_h_> the logs say it is, but none of them are getting pulled in
[14:36] <mbruzek> Most welcome, if there is anything I can do to help, please let me know.
[15:43] <marcoceppi> rick_h_: is bundle inheritence still going to work in the new store/juju?
[15:45] <rick_h_> marcoceppi: /me is processing
[15:45] <rick_h_> so you cannot have more than one bundle per file, there was talking of inheritance via other means
[15:46] <rick_h_> rogpeppe2: might recall better what we ended up doing vs talked about, I'm looking for the doc atm
[15:47] <rogpeppe2> marcoceppi: the idea was that a single bundle means a single bundle, and that people could use tooling to resolve inheritance before publishing
[15:47] <rick_h_> marcoceppi: yep see https://docs.google.com/a/canonical.com/document/d/1SF8hTBi6oVbki8V__beNij6wnQU-5cm6PZsy5gf0j_Y/edit and go down to "changes from the original format"
[15:48] <rogpeppe2> marcoceppi: we already have code that can parse the old bundle format and produce the new format
[15:48] <rick_h_> marcoceppi: so basically 'no, not until we write something to help do that for us'
[15:48] <marcoceppi> rick_h_ rogpeppe ack, ta
[15:49] <rogpeppe> marcoceppi: in my view, the added functionality that inheritance provided wasn't worth the complexity that it added to the whole tool chain
[15:50] <marcoceppi> rogpeppe: I only ask because there's talk of some kind of bundle on bundle activity from server team and I wanted to amke sure they understood inheritence as it was today won't be there
[15:51] <rogpeppe> marcoceppi: i like the idea of bundle composition better than i do bundle inheritance
[15:51] <rogpeppe> marcoceppi: it would be nice to be able to put a bunch of bundles together into a larger one
[15:52] <rogpeppe> marcoceppi: but again, that's perhaps something that could be accomplished with appropriate tools
[15:52] <marcoceppi> sure, again just wanted to make sure those working on these concepts had a complete deck of cards
[15:52] <marcoceppi> no jokers floating around ;)
[15:52] <rogpeppe> marcoceppi: :)
[15:52] <rogpeppe> marcoceppi: good plan
[15:56] <rick_h_> uiteam call in 5 kanban please
[17:16] <rick_h_> mbruzek: can you push an update to your charm please?
[17:16] <rick_h_> mbruzek: a small something so we can watch the log as it goes by?
[17:16] <mbruzek> rick_h_: In standup now, but you want me to push something to mellanox?
[17:16] <rick_h_> yes, please, at your convienence
[17:17] <mbruzek> rick_h_: OK should be done in 15 minutes
[18:00] <mbruzek> hi rick_h_ just getting something to push 
[18:06] <mbruzek> hi rick_h_ ready to push when you are
[18:08]  * mbruzek is going to head to lunch
[18:37] <mbruzek> back
[18:54] <Makyo> uiteam Need reviews + QA for the two release blockers: https://github.com/juju/juju-gui/pull/688
[18:55] <kadams54> Makyo: Taking a look
[18:55] <mbruzek> rick_h_: ready when you are if you want me to push 
[19:46] <urulama> mbruzek: should there be new mellanox char BZR revision available? looks like bzr rev 7 is still last one
[19:46] <mbruzek> urulama: not yet I was waiting to push one
[19:46] <mbruzek> urulama: rick_h_ asked me to push so he could watch the logs
[19:47] <mbruzek> I can do that now if you like
[19:47] <mbruzek> I just didn't hear back from rick_h_
[19:49] <mbruzek> urulama: I *just* pushed now.
[19:49] <mbruzek> revision 8
[19:54] <urulama> mbruzek: thanks. much appreciated.
[20:13] <kadams54> Makyo: Trying to QA your issue but I've re-created my EC2 env twice. Both times server.go (juju API?) keeps reporting an "error writing response: EOF". Trying a third time…
[20:13] <kadams54> uiteam: any ideas why I'd be seeing this? ^^
[20:14] <Makyo> kadams54, I haven't seen that before.  Did all my testing in LXC, but will try EC2
[20:15] <kadams54> Makyo: I see it show up in debug-log. On the client, I get things like badly formed HTML or a broken charm icon.
[20:15] <kadams54> And the charmstore never replies.
[20:16] <Makyo> kadams54, oh, right.
[20:16] <Makyo> kadams54, that's because the charmstoreURL property isn't set.
[20:16] <urulama> kadams54: looks like it drops rpc connection somehow ... https://github.com/juju/juju/blob/master/rpc/server.go
[20:17] <kadams54> Makyo: I thought that had a default value?
[20:17] <Makyo> do `juju set juju-gui juju-gui-debug=true`, then juju ssh to that machine and edit /var/lib/juju-gui/release/.../build-debug/juju-ui/assets/config.js and add charmstoreURL: 'https://api.jujucharms.com/charmstore/v4/'
[20:18] <Makyo> kadams54, Not in the config.js in the older version of the charm.
[20:18] <Makyo> We haven't released the charm with that in there yet
[20:18] <Makyo> Sorry that's convoluted.  That work has been done in the charm, but not released yet
[20:19] <kadams54> Makyo: Hmm, is charmstoreURL the new version of charmworld-url?
[20:19] <Makyo> kadams54, yes
[20:43] <kadams54> Makyo: made the change, but still having problems… is this correct?
[20:43] <kadams54>   charm_store_url: 'https://api.jujucharms.com/charmstore/v4/',
[20:43] <kadams54> charmworldURL: "https://manage.jujucharms.com/",
[20:43] <kadams54> (In config.js)
[21:24] <urulama> mbruzek: https://jujucharms.com/mellanox/trusty/2
[21:25] <mbruzek> Thank you
[21:25] <mbruzek> What was the problem?
[21:25] <urulama> mbruzek: still problems with BZR revisions
[21:25] <urulama> mbruzek: bug not found yet :S
[21:25] <mbruzek> oh thank you
[21:25] <urulama> mbruzek: as you can see, it states that it is at bzr revision 7, although it should be at bzr revision 8
[21:26] <mbruzek> weird
[21:26] <mbruzek> I am just glad to have it on the website.
[21:27] <urulama> mbruzek: so, fyi, even though the charms look like they have old revisions, the actual code/archive is the latest ones. we have a bug in providing bzr info. 
[21:28] <mbruzek> urulama: Is there anything I can help with in the diagnosis?
[21:28] <urulama> mbruzek: getting closer thanks to your mellanox charm :)
[21:28] <urulama> mbruzek: not for now, thanks
[21:28] <mbruzek> urulama: happy to help if you need something.
[21:29] <urulama> mbruzek: btw, safari does not show the svg icon properly
[21:29] <urulama> (for mellanox)
[21:29] <urulama> it's completely white
[21:29] <mbruzek> weird.
[21:30] <mbruzek> It shows OK for me.
[21:30] <mbruzek> But Yeah the icon may not have been written correctly.
[21:32] <urulama> looks fine https://api.jujucharms.com/v4/trusty/mellanox-2/archive/icon.svg
[21:33] <urulama> anyway, thanks.