=== mattuk1972_ is now known as mattuk1972 [12:03] good morning frankban and teknico [12:03] hi bac [12:03] bac, good morning [12:04] no mayan sightings in italy i presume === mattuk1972_ is now known as mattuk1972 [12:13] bac, none that I know of [12:30] bac, trunk and uistage are both broken right now, gary_poster's branch in review fixes them [12:32] * bac looks [12:32] just a fyi [12:33] teknico: ok, i'll review it now [12:34] frankban: are you working on gary's card or just reviewing it? (your face is on it) [12:35] teknico: how is staging broken? is there anything heroic i can do to get it up in the short term? [12:35] i can try to figure it out but wondered if you had thoughts [12:41] bac, frankban and I already reviewed that branch, we're only waiting for gary_poster to land it [12:42] bac, since trunk is broken, I assume staging also is as a consequence [12:42] teknico: i don't see your review here: https://codereview.appspot.com/7005044 [12:42] also neither of you added tags to the kanban card [12:42] so i didn't think it was fully reviewed [12:42] tsk, tsk [12:43] bac, right, sorry, the tags [12:43] bac, I'll add them now, it was a pair review, as apparent from the review text [12:44] oh, you added frankban's tag already, ok [12:44] I'm having lunch now [12:48] * gary_poster is about to land, teknico and bac [12:48] gary_poster: cool [12:51] gary_poster: i'm logged into uistaging so let me know when it lands and i'll kick it in the shins [12:51] thanks bac. double checking then will let it fly [12:56] bac, done. note that the "build" directory will need to be manually removed--it is now called "build-shared." thanks again. [12:57] gary_poster: i'll just let the cron job do it's thing at :00 [12:57] ok bac, but you may need to manually remove build still. Maybe after :00 though, yeah [12:58] gary_poster: the cron job may blow everything away. let's wait and see [12:58] ooh the excitement [12:58] ok [12:58] :-) [12:58] T-75! [12:59] the tooth I had a root canal on officially cracked all the way through yesterday :-/ Gonna try to find someone who can pull it for me today so I don't have to worry about all during break [12:59] ooh, yuck [12:59] yeah :-/ [12:59] there is nothing left to put a crown on? [12:59] no, just two halves [13:00] ugh. that's gross. i'm very squeamish about teeth issues [13:00] :-) sorry [13:01] dunno what uistage looked like before but seems to be happy now [13:07] ooh, gary_poster; sorry to hear that [13:09] thanks :-/ [13:09] gary_poster: so the update worked with no intervention [13:10] bac, awesome. I didn't know it blew things away [13:10] that kapil is smrt [13:10] I mean, I expected it to work, I just didn't expect it to clear out the old build dir [13:10] :-) [13:51] any preference on commercial cert vendors? godaddy, namecheap, thawte? [13:52] thawte! [13:52] nah [13:52] not godaddy [13:52] I have a bad taste in my mouth from godaddy for various reasons, but that probably shouldn't influence you [13:53] i like gandi.net for domain registration. they probably do certs. [13:53] namecheap is like 10/usd yr.. comodo cert based [13:53] * hazmat checks gandi [13:53] i have a weird testing issue i haven't seen before. my 'before' gets called if i run the whole suite, but if i run just the one group of tests it does not. [13:53] it jumps right into beforeEach [13:54] bac, benji has been having slightly related issues. his solution *might* affect your problem [13:54] gary_poster: it seems to have happened after i merged your latest commit. :( [13:54] (if he doesn't jump in to describe it I remember what he told me :-) ) [13:54] huh [13:54] not sure what I would have done to influence that [13:55] gary_poster: but i may have merged other versions of trunk earlier. can't recall the ordering. [13:55] bac, if you push your branch I can try to help [13:55] bac: which is defined first, the before or beforeEach? [13:55] before [13:55] actually, that shouldn't matter because the tests (I assume) are defined after both [13:56] before, beforeEach, afterEach, it, it [13:58] hazmat, I use gandi too, certificates included [13:58] hazmat, startcom is nice too: https://en.wikipedia.org/wiki/Comparison_of_SSL_certificates_for_web_servers [13:58] teknico, thanks [14:02] benji, gary_poster: more oddness. the problem only occurs with test-debug but not test-prod [14:03] that is odd [14:03] bac, dunno. :-/ like I said, happy to dig in if you think it would help [14:03] maybe the minifier is doing bad things to... something [14:03] he said prod was good, debug was bad [14:04] the minifier is automatically fixing our problems! [14:04] who knew that skynet started with a js minifier? [14:04] gary_poster: you wanna pair or just grab the branch? [14:05] bac, your branch you choose. can do both [14:05] let's go to g+:\\juju-ui [14:05] k [14:08] heh [14:16] gary_poster: maybe we could consider byg 1086822 fixed? [14:16] bug 1086822 [14:16] <_mup_> Bug #1086822: charm is very slow to start < https://launchpad.net/bugs/1086822 > [14:16] frankban, yes! thank you [14:16] mark as fixed by frankban :-) [14:17] Cool, :-) first bug fixed between the coffee and the cigarette [14:23] benji: fixed it. added 'done' to before() and it works. verified another test that didn't use 'done' was broken too and adding it was the cure. [14:23] benji: add that to your test hygiene stuff you're presenting [14:24] bac: interesting; was the before() doing anything asynchronous? Well, I guess it was. Rephrased: do you know what it was doing asynchronously? [14:24] * benji wonders when he started doing a presentation. [14:24] no [14:25] benji: gary said you had a list of things to clean up tests. perhaps i misinterpreted [14:25] benji: the before just grabbed namespace references [14:26] juju = Y.namespace('juju'), etc [14:27] bac: hmm, I wonder if the done() call is adding just enough delay that the YUI modules get loaded. If you are interested in experimenting, remove the done() and put in a busy wait that counts to 100000 or so before the namespace grabbing. I bet it will work just as well. [14:28] benji: any theories on why it only occurs when running a test in isolation? [14:29] my hypothesis is that when run with other tests the modules have already loaded before the test is even started, so there is no race; when run in isolation there is a race between the (asynchronous) test runner and the (asynchonous) YUI module loader [14:32] benji: i removed the done and added this: [14:32] while (!Y.Lang.isValue(models)) { [14:32] models = Y.namespace('juju.models'); [14:32] } [14:32] and it works [14:32] much more elegant than a busy wait [14:32] benji: but i put the trap around the getting of juju which happens before, and models was still undefined [14:33] i thought they might all come available about the same time, but no [14:33] nope... ASYNCHRONOUS! [14:34] in 1000 years "asynchonous" may be a swear word [14:34] ... still be a swear word === bcsaller1 is now known as bcsaller [14:35] benji: i read your previous comment as "ASYNCHRONOUS, BABY!" in the voice of dick vitale, fwiw [14:35] heh [14:37] so, in summary, the use of 'done' is an unrelated hack that just happens to work and muddies the water? [14:37] that is my strong hunch [14:42] ugh [14:42] benji, bac does it matter if we pass async: false to the loader [14:43] hazmat: that helps some (and that is what my branch does; which I hope to land today) [14:43] I believe there is still a race even with that. And I haven't been able to figure out how to remove it. [14:44] benji: with your branch try running 'juju application notification' in isolation [14:44] k [14:45] bac: 10 runs, all passed [14:45] good. in the name of science, try on trunk? [14:46] sure [14:46] bac: does test-prod or test-debug matter? [14:47] yes. i only see it fail on test-debug [14:47] k, that is what I used for running the test on my branch [14:48] three good runs and then "Uncaught TypeError: Cannot read property 'Database' of undefined" [14:48] 10 runs, 1 with that error [14:48] not a statistically significant difference between the two tests [14:55] that is the error i see [14:55] but i get it all of the time [14:56] bac: one thing to remember is that I have a slow computer, so the races seem to affect me less [14:56] argh have to setup email on jujucharms.com to finish the cert setup [14:57] benji: well i'm on a fast, new, shiny computer but running in a vm [14:57] bac.. mac? [14:57] just curious [14:58] hazmat: yeah, i looked around, considered the sputnik but couldn't live with the lower res and smallish display [15:11] * hazmat tries to remember how to setup a mail server [15:11] ah.. google you've made it so easy to forget so much [15:12] hazmat: step one, get a google apps account :) [15:12] heh [15:12] benji, i would have except now they want folks to pay for it. [15:12] * hazmat bails out to postfix [15:12] yeah, I had been meaning to set up my kids' email for a while and now I had to pay for it :( [15:13] but I've been using apps for free for about five years, so I don't feel to bad about it [15:28] bac bcsaller benji frankban hazmat Makyo teknico_ call in 2 [15:28] ah.. email used to be so much simpler.. i think i need domain keys setup === mattuk1972_ is now known as mattuk1972 [16:27] see ya juju team -all the best for 2013 - its been a pleasure [16:29] mattuk1972 have a good one [16:29] mattuk1972, its been fun, good luck on the future [16:32] bac, testing out notification tests in isolation [16:33] I think everybody was on depressants for that call :-P [16:33] hazmat: yes, that test fails in isolation as written [16:34] hazmat: is that what you are asking? [16:34] bac, yes [16:34] hazmat: and for that particular test, adding 'done' to 'before' makes it work [16:35] it looks to be related to what benji described with YUI and mocha async interactions. that test has before using the YUI.use() style setup [16:35] hazmat: unrelated, you assigned a card to francis, which is probably not what you intended. [16:35] doh [16:36] :-) [16:36] assigned a card to posterity, today's his last [16:37] bac, which card? === teknico_ is now known as teknico [16:40] bac, there's also some interaction with the browser cache trying to make these tests work, i either get a blank page, js error loading utils.js (registerHandler for handlebars), the database undefined error, or working tests. [16:40] er blank page with the util.js error [16:41] yep, I think the behavior around caching is part of the (or "a") race; loading the resources changes the timeings a bit [16:43] isolating just the notifiy tests in index.html makes things a little bit more sane [16:43] [16:43] oh benji, I thought we had a card to discuss your test pattern :-/ [16:43] leads to a new non failure, failure mode.. where the test runner finds no tests, and no console errors. [16:44] I forgoy yp ask you to talk about it explicitly [16:44] but also run sometimes [16:44] s/yp/to/ [16:45] hazmat: that failure mode is the one I was getting in my branch [16:46] benji, why are there two different styles here? [16:46] describe wrapper vs yui wrappre? [16:46] the describe wrappers seem to be better behaved with the async: false [16:47] I don't know for sure, I suspect people just tried different things at different times. [16:49] benji, ic... from history you added it to the test_notifications.js ... i'm going to remove that .. that's the issue with the non failure / failure [16:50] hazmat, anyone else, does it make sense to try to connect to rapi via wss (encrypted) if the gui browser access is not happening via https? [16:51] teknico, no [16:51] teknico, commonly the cert for the wss is not valid without user ack [16:51] so the wss won't load/connect [16:51] oh right, was forgetting about that [16:52] * hazmat grabs some coffee bbiam [17:02] benji, confirmed that was the issue [17:03] test notifications running reliably now.. [17:04] hmm.. no reviews on that commit? [17:04] https://codereview.appspot.com/6845084 [17:06] that turns the actual fix into a one liner.. [17:11] hmm.. firefox doesn't like extra param to the replace [17:11] hazmat the yui wrapper was the solution thiago had advocated, that we tried for a while and then agreed relatively recently to discard. So basically reverting https://codereview.appspot.com/6845084/diff/2002/test/test_notifications.js is the fix you have found? (I have been unable to dupe some people's errors, btw, so just because it works on one machine unfortunately does not guarantee it is a solution for others [17:11] , IME on this stuff) [17:12] gary_poster, in conjunction with async: false.. i'm still playing with it.. trying to make tests run in firefox [17:12] cool [17:12] teknico, frankban did you guys have success with the gallery / loader issue? [17:13] hazmat, gary_poster did :-) [17:13] cool [17:13] gary_poster, what was the solution? [17:13] hazmat, change the base and explicitly host the gallery files ourselves [17:14] cool [17:15] lunch and car to shop. biab [17:26] working in firefox reliably as well. needs a tweak to mocha timeout [17:27] still some odd interactions between suits [17:28] ugh.. ordering issues [17:28] running application_notifications tests before notification tests fails, but works fine in reverse [17:28] apologies, i'm in blather mode [17:29] hazmat, when I run "juju deploy local:precise/juju-gui" and I have changes in the local copy [17:29] hazmat, what's deployed, the modified local copy, or the latest committed revision? [17:29] teknico, if its already been deployed in the env.. it will use the cache copy [17:30] hazmat, I run "juju destroy _environment" every time [17:30] teknico, so two axis.. one is namespace.. cs: vs local: [17:30] teknico, those are separate charms to juju so it will always deploy what you tell it [17:31] teknico, second axis.. juju caches charms in the environment.. so if you update a charm locally and try to deploy again without incrementing the revision, it will deploy the older version [17:31] teknico, there's a -u/--upgrade flag on deploy [17:32] teknico, that will automatically increment the revision [17:32] hazmat, oh, right, the revision [17:32] teknico, i suggest always using deploy -u local:precise/juju-gui [17:32] hazmat, and running destroy_environment does not change anything, right? [17:32] teknico, it doesn't.. its stored in the control bucket which survives the env [17:33] hazmat, great, thanks for the -u tip [17:33] i heard some rumor that juju-core may end up storing/deploying all the charms via git [17:33] i presume to address this issue [17:34] of easy mutability [17:34] hazmat, via git? ;-o [17:36] while working with juju, gnome-keyring-daemon blowing up and forcing me to enter gazillion passphrases is not exactly helping... [17:36] teknico, bad session? [17:37] hazmat, it's been happening right after login for a few days now [17:37] hazmat, how do I clean up the session? [17:37] teknico, i'd retry logout/login [17:38] or reboot if that fails [17:38] teknico, alternatively use a passwordless ssh key [17:38] hazmat, it's happened on login right after boot for a few mornings now [17:38] for the env [17:38] er.. juju [17:38] hazmat, uhm, yeah, where's it configured? [17:39] teknico, https://juju.ubuntu.com/docs/provider-configuration-ec2.html see authorized-keys-path [17:39] or alternatively authorized-keys [17:41] ok [17:51] hum... I am seeing "error: old chunk mismatch" in all files in my MP (at least in the side by side view)... [17:52] frankban, we saw that a few days ago in another mp. i would suggest trying to propose again [17:53] not sure what triggers that [17:53] hazmat: trying... [17:54] hazmat: patch set #2 works, thanks [17:59] uhm, I'm getting: "Uncaught INVALID_STATE_ERR : Pausing to reconnect websocket" [18:00] I think I need a way to locally test encrypted connections to rapi first [18:02] has anyone seen this error when trying to send data down the websocket? "INVALID_STATE_ERR: DOM Exception 11" [18:03] the Internet says that it is because the ws isn't ready, but I am gating the call on env.get('connected') which is set from the we.on_open handler, so it should really be ready. [18:03] benji, which browser / version? [18:04] hazmat: Chromium. [18:04] version = whatever is current in 12.10 [18:06] 22 then.. offhand not sure, i'd check the logs from the improv/websocket side just as a sanity check.. or from the browser net panel [18:06] https://github.com/mbostock/d3/wiki/3.0 [18:07] bcsaller, benefits? [18:08] hazmat: not clear yet how much it impacts us, but the delta to support it looks small so its worth tracking the upgrade [18:09] the smooth zooming plugin made it in tough, we might want to use that [18:09] bcsaller, yeah.. the upgrade notes dont look like they'll hit us that bad [18:09] https://github.com/mbostock/d3/wiki/Upgrading-to-3.0 [18:09] not sure though.. haven't looked at the env code in a while [18:12] hazmat: ooh, it is something about the ws not being ready even though env.get('connected') is true: instead of calling the login RPC right away, I put it in a setTimeout for one second later and the call worked [18:13] benji, we've got a transparently reconnecting websocket.. as well.. so reconnects could be happening.. connected should work unless there's a reconnect happening [18:14] benji, does it fail reliably? [18:14] without the timeout [18:14] from the improve.py log it doesn't look there are any reconnects happening [18:14] yep, very reliably [18:14] i wonder if we're firing connected to early then [18:15] benji, login should happen after the server greeting [18:16] hazmat: hmm, that may be it, env.get('connected') means the WS is connected, not that the server is ready [18:16] I can change around my event sending so it will happen after the greeting [18:16] another question, does the server conform to this: http://paste.ubuntu.com/1397723/ [18:16] hmm.. not quite.. the error suggests something more fundamental.. the message would still go down the wire to the server [18:17] ah, indeed [18:17] but in the interests of being well behaved, we shouldn't login till we get a helo from the server [18:17] well, if I wait until after the welcome message it will work either way [18:17] that's fairly classic for network old-school net protocols (pop, imap, etc) [18:17] re. conforming interface: it doesn't look like it [18:17] yep [18:19] making good progress on the testing front fwiw [18:19] * hazmat grabs some food [18:19] hazmat: does the login process work like this: http://paste.ubuntu.com/1397723/ [18:19] or I should say, it doesn't look like it works like that [18:20] benji, right.. login isn't required atm, till we have the ability to login.. else everything would break. [18:20] benji, but the login flow should be the same [18:20] hazmat: in particular I am not getting and {'op': 'login', 'result': 'success', ...} messages [18:20] s/and/any/ [18:21] benji, that's a bug/broken then in rapi [18:21] benji, what do you get on the wire in response to send_rpc login? [18:21] hazmat: I get a {"log": [["info", "Login success"]], "request_id": 2, "user": "admin", "op": "login", "password": "admin", "result": true} back [18:22] I could use that to know if the login was successfull or not, but "log" messages sound like something that could be turned off. [18:23] hi bcsaller, i have questions about the zoomHandler and rescale [18:24] benji, yeah.. the current structure on the log messages isnt optional.. it was to help the wrapping on cli stuff for feedback, i could disable the message for the login method, but its still going to come back with an emty log array [18:24] so that looks correct just w/ a delta to the initial proposal [18:25] bcsaller: nm [18:25] so I should be using the log message to know whether or not the login was successful, right? [18:25] benji, result: true [18:25] cool, thanks [18:26] benji, if it fails .. there will be an err: true instead per the pastebin [18:26] k [18:26] gary_poster, I proposed my branch, but maybe shouldn't have, I added some disclaimers to not land without further testing [18:27] gary_poster, it's also going to conflict with frankban's branch, that I also reviewed [18:29] since it's EOY now, I thought I'd better put it out there so that it can be completed [18:30] thanks teknico [18:30] If I have time I might try to resolve for the heck of it [18:30] it would be cool to have this stuff really done :-) [18:30] and for the heck of the objectives, yeah :-) [18:31] teknico, you say "Also, this is not yet working while deploying manually, and needs [18:31] further testing. Do not land without checking first." [18:31] so, my crazy story would be this: [18:32] - get frankban's branch. [18:32] - turn https back on [18:32] (hacking branch) [18:32] try it out [18:32] - merge your branch [18:32] -resolve whatever needs to be resolved [18:32] - try it out [18:32] - (you say it won't work without some tweaks) [18:33] (so fix tweaks) [18:33] - profit! [18:33] which might mean trying to land the combined branches [18:33] yeah? [18:33] gary_poster, that sounds like an eminently reasonable plan :-) [18:33] heh ok :-) [18:33] thanks teknico [18:33] teknico, frankban have a great holiday break! [18:33] see you in 2013 [18:34] well, frankban's branch will likely be landable without problems [18:34] but that's details :-) [18:34] so, happy holidays everyone, and see you in the new year! [18:44] bye teknico. have a nice break [18:47] bye all, and happy holidays [18:49] frankban, teknico happy holidays [18:50] * hazmat tries to deciper.. TypeError: Cannot read property 'charm-search-result' of undefined [18:51] template is not compiled/included? [18:53] that assumption that Templates is on juju-views module might simply be fragile [18:54] looks reasonable on the face of ith though [18:59] Things work, tests pass, yuidoc explodes. Ah well. [19:00] Makyo, you know we have the helper command to make that disappear, right? [19:01] yuidoc-lint complaints, I mean--I assum that's what you are talking about [19:02] gary_poster, bad dependencies it looks like [19:03] gary_poster, charm-panel.js didn't declare its use of juju-templates [19:06] gary_poster, What was the command again? I can get the ones that are just improperly formatted, at least. [19:07] hazmat, looks like I have to restart. Makyo lemme see if I can find it before I do [19:07] ack [19:07] Makyo, ``make undocumented`` === gary_poster is now known as gary_poster|away [19:08] Thanks === gary_poster|away is now known as gary_poster [19:21] hazmat: that error is one I have seen too; it happens when the Templates data structure has not been define yet [19:22] benji, yeah.. it looks like charm-panel wasnt including the dep, i included and got to a diff errr [19:22] gary_poster, Should I propose and work on docs in the meanwhile? [19:23] gary_poster, instead of rebooting again, let's table to next year ? [19:23] hazmat bah [19:23] ok :-) [19:23] have a nice holiday [19:23] I never could figure out how the templates got loaded. I'm glad you fixed it. [19:24] Makyo, you mean while you are waiting on reviews? docs would be good, or maybe bac or bcsaller could use a pair? [19:25] i'm good. just slogging through tests. [19:25] gary_poster, Yeah, that's what I was thinking. On lunch now, but can do whatever's best after. [19:25] Makyo, cool. frankban and teknico have charm branches that need reviews. If your branch is up for review I'll also try to get to it ASAP [19:25] talk to you after lunch [19:26] * gary_poster restarts :-/ (G+ hangouts normally are not quite this flaky for me!) === gary_poster is now known as gary_poster|away === gary_poster|away is now known as gary_poster [19:42] aha.. forgot to poke a hole in the security group for inbound mail [19:59] aha. working email [20:07] hazmat, is this complaint from rapi? does it indicate anything to you? http://pastebin.ubuntu.com/1455528/ [20:08] that is from a test run [20:11] Makyo, "with undocumented methods and custom events, may get larger yet": undocumented methods were pre-existing though, yeah? [20:18] gary_poster, Yes, they just moved to different files, so the undocuented file didn't list them. [20:19] Makyo, then don't worry about it for this round :-) [20:19] gary_poster, Alright. May still need to document events fired, as was done with panzoom, but something for later. [20:21] hi bcsaller [20:21] gary_poster, its indicating the ws client is not valid [20:21] bac: one sec, on a call with gary [20:21] ok [20:21] gary_poster, and then terminating the connection [20:21] and yes its from rapi [20:22] hazmat, oh, right. that may be ok then. tests are failing for me [20:22] i assume this is from a wget to the endpoint in a unit test [20:22] bac: whats up? [20:23] bcsaller: in panzoom/rescale fcn at the end it fires a 'rescaled' event. is anyone using that right now? [20:23] hazmat, yeah. charm tests use a simple http check to see if the ws is there, and expect an error. That's a red herring for whatever the problem is. thank you [20:24] bac: not as of that branch, but the viewport code and some of the menu repositioning code in service will [20:25] bcsaller: can we do a quick chat? [20:25] yeah, I'll see if normal g+ is open [20:25] bac: it is [20:29] bac, bcsaller relations uses it. [20:30] bac: froze there [20:33] gary_poster, ready when you are for call. [20:40] Makyo: when you're done with the call give me a ping please [20:40] bcsaller, Free now. [20:40] Makyo: getting on g+ [20:54] allrighty, the login branch is available for review at https://codereview.appspot.com/7007047 [20:54] after I take a short break I will see if anyone else needs reviews [21:00] hazmat: i just got golang 1.0.2 and rebuilt lbox using it. i still see the same problem authenticating. [21:00] argh [21:00] bac, clean build, sure about the executable ? [21:01] its possible they've slipped for multiple releases but that's sad [21:02] hazmat: oh, wait it is an old executable [21:16] gary_poster, cert should be in place by eod, just configuring nginx [21:16] going to run an errand, bbiab [21:17] thanks hazmat [21:17] * gary_poster has to go back to car shop [21:21] Makyo: could you review my panzoom test branch? [21:21] bac, in a bit [21:21] thanks [21:21] maybe it'll be on rietveld by then [21:35] yow, after merging in the trunk I get massive test failures [21:36] "Uncaught TypeError: Cannot read property 'notifier' of undefined" [21:38] * Makyo dogwalkinates. [21:52] benji, any resolution on that? [21:54] gary_poster: nope; I am pretty sure it is another initialization race, but I haven't figured it out yet. [21:54] ok benji. I think hazmat may have a fix-all-the-tests branch coming up [21:54] hmm, that is interesting: GET /juju-ui/templates.js 404 1ms - 54 [21:54] but I know that's not very satisfactory [21:55] gary_poster, incidentally your consistency in testing may be the result of browser cache [21:57] hazmat, maybe so [21:57] though I do clear it out for various reasons [21:58] ahh, a "make clean" and "make build" cleared up the tempate.js 404; it must have moved [21:58] most of the tests pass on my branch now [22:07] um. I think d3 just changed all their file names in their npm package. [22:08] ah. [22:08] we are getting 3.0.0 [22:12] i'm going to call it a day. i'll check back later and land my branch if it gets favorable reviews. [22:13] well, I guess I have a race to fix in the new year; see you guys then [22:13] sounds good bac. I want to go take a break too. Have a great holiday. I'll shoot you a review in a bit if noone else has [22:13] hope everyone has a good break. [22:13] benji have a great break [22:13] gary_poster: thanks, you too! [22:13] * bac o/ [22:14] hazmat, bcsaller, Makyo, have a great holiday, & see you in 2013! [22:14] See ya :) [22:14] :) [22:14] gary_poster, happy holidays === gary_poster is now known as gary_poster|away [23:31] still a work in progress.. but its up.. https://jujucharms.com/