rick_h_ | hatch: or maybe not, damn I'm beat. Going to call it good for now and catch back up in the morning | 00:18 |
---|---|---|
bac | rick_h_: i've been mojo-ing using ec2 as the host (not target) and i'm getting the same juju-deploy failures i see everywhere | 00:29 |
bac | i forgot to capture the output, so i'm running again to get it for analysis tomorrow | 00:29 |
=== kadams54 is now known as kadams54-away | ||
=== kadams54-away is now known as kadams54 | ||
rick_h_ | bac: rgr ok thanks for the heads up | 01:33 |
=== kadams54 is now known as kadams54-away | ||
bodie_ | #jujuskunkworks | 03:41 |
bodie_ | grh | 03:41 |
bodie_ | fat-fingered the /join somehow | 03:41 |
=== kadams54 is now known as kadams54-away | ||
kadams54 | hatch: How're things looking with the services view? | 14:39 |
hatch | hey aren't you supposed to be gone? :) | 14:40 |
kadams54 | hatch: Yeah, we have parent-teachers conferences today and I'm waiting for the next to begin. | 14:40 |
hatch | ahhh - yeah it's going | 14:41 |
hatch | just working on moving of that mvvisibility method | 14:41 |
kadams54 | Up to the DB? | 14:41 |
hatch | down to the DB | 14:43 |
hatch | :P | 14:43 |
lazyPower | hatch: http://paste.ubuntu.com/8761147/ - is this expected behavior? take a look at the postgres defaults.. this is an export from jujucharms.com | 14:45 |
lazyPower | it predisposed them with "nulls" and .nan | 14:45 |
hatch | loooking | 14:47 |
rick_h_ | lazyPower: no, I thought this was fixed. This is latest revision of GUI? | 14:47 |
hatch | no that's definitly not correct | 14:47 |
lazyPower | rick_h_: its whatever is deployed to jujucharms.com | 14:47 |
hatch | :/ | 14:47 |
rick_h_ | lazyPower: oh well then heh | 14:47 |
lazyPower | i did the drag/drop thing, relate, and export for a user in #juju | 14:47 |
rick_h_ | lazyPower: drag/drop your bundle or one in the gui? | 14:48 |
rick_h_ | e.g. 'drag/drop thing' ? | 14:48 |
rick_h_ | oh you grabbed the services | 14:48 |
rick_h_ | not a bundle, ok | 14:48 |
lazyPower | rick_h_: no i built it on jujucharms.com and exported it | 14:49 |
lazyPower | sorry, i should have been more specific in how i phrased that | 14:49 |
rick_h_ | lazyPower: anyway, no. I thought we didn't include the config items that weren't the default and looks like we're failing to diff null vs default | 14:49 |
rick_h_ | hatch: ^ make sense? | 14:49 |
hatch | yeah this is all broken - can someone try comingsoon to see if it exhibits the same issue? | 14:51 |
hatch | ok finished what I was doing | 14:52 |
hatch | now I can test it | 14:52 |
rick_h_ | hatch: yea, does it on comingsoon as well | 14:53 |
lazyPower | glad we caught it internally | 14:53 |
lazyPower | rick_h_: want a bug for follow up on this? | 14:54 |
rick_h_ | lazyPower: got a card on the board for it and we'll look into it thanks | 14:54 |
lazyPower | rick_h_: ack. Thanks for taking a look. | 14:55 |
rick_h_ | jujugui call in 6 kanban please | 14:55 |
hatch | rick_h_: bug I found while testing that https://bugs.launchpad.net/juju-gui/+bug/1388119 | 14:55 |
mup | Bug #1388119: Relation selector shows ghost model id instead of display name <juju-gui:New> <https://launchpad.net/bugs/1388119> | 14:55 |
rick_h_ | ugh | 14:56 |
hatch | and yes I was able to reproduce that issue | 14:56 |
hatch | there are some postgres config values which are "null" there might be an inforrect conditional in there | 14:57 |
hatch | incorrect even | 14:57 |
hatch | lazyPower: I'm starting on that bug fix now - was there a bug created on LP? | 15:24 |
lazyPower | hatch: negative | 15:24 |
hatch | ok np | 15:24 |
hatch | lazyPower: rick_h_ I have found the issue with the export - it's actually on deploying the charm just fyi | 15:38 |
* hatch stepping out to grab a coffee | 15:38 | |
hatch | ugh haloween is the worst | 16:04 |
hatch | glad noone on my block has decorations for it this year | 16:04 |
hatch | bahaha https://twitter.com/rob_pike/status/525533749677932545 | 17:04 |
hatch | ahh today is just one of THOSE days | 17:15 |
hatch | rick_h_: lazyPower so postgres actually defines fields as null | 17:19 |
hatch | aws_access_key_id: | 17:20 |
hatch | type: string | 17:20 |
hatch | default: null | 17:20 |
hatch | description: EXPERIMENTAL. Amazon AWS access key id. | 17:20 |
hatch | which acts all sorts of stupid in js | 17:20 |
lazyPower | hatch: which charm rev is that? | 17:20 |
hatch | is this valid juju? | 17:20 |
hatch | umm | 17:20 |
hatch | http://bazaar.launchpad.net/~charmers/charms/precise/postgresql/trunk/view/head:/config.yaml | 17:20 |
lazyPower | it should be either default:, default: "", or default: "null" depending on how its being checked in the code | 17:20 |
hatch | ok so should this be supported in the GUI or should proof have failed? | 17:21 |
hatch | dealing with types across 3 languages is....intersting :) | 17:22 |
hatch | 4 languages I guess | 17:22 |
hatch | YAML > Python (proof) > Go > JS | 17:22 |
hatch | lol | 17:22 |
hatch | rick_h_: lazyPower I'm going to bench this one and move onto the other critical bug until we have an answer on where the problem actually si | 17:24 |
lazyPower | hatch: good question | 17:25 |
lazyPower | default: null is valid | 17:25 |
lazyPower | it just depends on how the charm is readng the vaules | 17:25 |
lazyPower | *values | 17:25 |
hatch | ok so does null === "null" ? | 17:26 |
hatch | or is null truley the null value | 17:26 |
hatch | if it is "null" then it's working properly | 17:26 |
hatch | well - at least properly enough :) | 17:27 |
lazyPower | it will evaluate to string | 17:27 |
hatch | ok so it's current functionality is acceptable then? | 17:28 |
hatch | ahh there is an issue then - because we should show 'null' in the pre-deployment inspector | 17:29 |
hatch | lazyPower: so `null` should be treated as "null" ? because in JS/JSON null is special | 17:30 |
lazyPower | hatch: field type is string | 17:30 |
lazyPower | thats why ti would be "null" | 17:30 |
hatch | can it be anything else? | 17:30 |
lazyPower | if you want the null character, you omit a value | 17:30 |
lazyPower | thats the *only* way to get a null character to return from a yaml field of type string. | 17:30 |
hatch | ahh | 17:30 |
hatch | ok there is a bug here then - but aiui it shouldn't break | 17:31 |
hatch | your bundle export should still be valid | 17:31 |
hatch | no? | 17:31 |
lazyPower | hatch: i suppose, i'm going to flying jumpkick a bug against postgres for follow up | 17:32 |
hatch | lol | 17:32 |
hatch | ok I'll bench this one then for now - put it in tracking until we can confirm | 17:32 |
lazyPower | sounds good hatch - if its not a bug in gui sorry for the run around. | 17:34 |
hatch | lazyPower: well no there is a bug - we don't show the null value in the pre-deployment inspector - and then we send "null" strings thinking that it had been changed | 17:35 |
hatch | BUT | 17:35 |
lazyPower | ah combination of wonky behavior | 17:35 |
hatch | yeah | 17:35 |
hatch | so yes the export is 'broken' but I don't think it's critical :) | 17:35 |
hatch | I'd like to get a little more input on the real desired outcome before implementing a fix | 17:36 |
hatch | lazyPower: rick_h_ I updated the card in tracking on the kanban so we can discuss | 17:41 |
hatch | Makyo: didn't you have some drupal sites? http://www.eweek.com/security/drupal-users-had-seven-hours-to-patch-or-be-hacked.html | 17:42 |
Makyo | hatch, wordpress. Both are awful, each in its own way. | 17:43 |
hatch | oh haha ok :) | 17:43 |
hatch | I can honestly say I've never worked with either | 17:43 |
hatch | well I think I deployed a wordpress site once to play with it | 17:43 |
rick_h_ | hatch: ok, thanks for that | 17:45 |
rick_h_ | hatch: are you going to look at the relation card then? | 17:45 |
hatch | already started, yup | 17:45 |
hatch | going to grab lunch soon though | 17:45 |
hatch | rofl nodejs was forked | 17:47 |
hatch | could there be any more drama in the js world | 17:47 |
Makyo | Oh man, another spaceflight accident :/ http://www.breakingnews.com/topic/virgin-galactic-spaceship-incident-oct-31-2014/ | 18:41 |
rick_h_ | :/ | 18:45 |
hatch | :( | 18:59 |
=== alexpilotti_ is now known as alexpilotti | ||
hatch | so there is a competition for Ubuntu scopes...hmmmm | 19:21 |
=== kadams54 is now known as kadams54-away | ||
hatch | nice, bug fixed, time to write tests | 21:18 |
hatch | ahh all the old tests still pass - that means alls good right? ;) | 21:20 |
rick_h_ | :P | 21:25 |
hatch | well I suppose it would if this was ever tested :/ | 21:25 |
hatch | writing these tests are going to take a while | 21:45 |
hatch | there are 0 tests for the addambiguousrelation method | 21:46 |
rick_h_ | fertile ground :) | 21:46 |
hatch | lol yeah this code has only been in here for....2 years? | 21:46 |
hatch | lol | 21:46 |
hatch | we got a roomba yesterday | 21:50 |
hatch | it's cleaning algorithm seams very inefficient | 21:50 |
rick_h_ | heh | 21:50 |
rick_h_ | yea, everyone thinks that the first time they see one in action | 21:51 |
hatch | but after it's done the carpet is remarkably clean | 21:51 |
hatch | it has also never gone back to its base station | 21:51 |
rick_h_ | lol | 21:51 |
hatch | I don't know if it learns or not | 21:52 |
hatch | I don't think so because it runs into the same thing multiple times | 21:52 |
rick_h_ | no, I don't thihnk it does. It can't tell that you're running it in the same spot vs a new room/etc | 21:52 |
hatch | there is a sticker on it which says that they encourage people to reprogram it :) | 21:53 |
hatch | maybe I can develop a smarter algo :P | 21:53 |
hatch | what do you mean? I we have the dock in one spot and it just goes all over the house | 21:53 |
hatch | so it should be able to build a map | 21:53 |
* rick_h_ goes to get ready for trick-or-treating | 21:57 | |
hatch | enjoy | 22:01 |
=== lazyPower is now known as lazyWeekend | ||
=== kadams54 is now known as kadams54-away | ||
=== kadams54-away is now known as kadams54 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!