Thursday, 2015-04-16

*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant01:23
*** tcrawley-away is now known as tcrawley01:24
*** tcrawley is now known as tcrawley-away01:25
*** Guest18134 <Guest18134!~willy@2620:10d:c082:1054:bae8:56ff:fe2b:432c> has joined #immutant01:34
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 264 seconds)01:34
Guest18134hey guys, is it possible to set the http status code when using immutant.web.async/as-channel?01:35
*** Guest18134 <Guest18134!~willy@2620:10d:c082:1054:bae8:56ff:fe2b:432c> has quit IRC (Remote host closed the connection)01:53
*** deadghost <deadghost!~deadghost@49.230.72.114> has quit IRC (Ping timeout: 264 seconds)03:38
*** deadghost <deadghost!~deadghost@49.230.72.114> has joined #immutant04:21
*** jcrossle_ <jcrossle_!~user@71-90-202-246.dhcp.stls.mo.charter.com> has joined #immutant05:18
*** jcrossley3-away <jcrossley3-away!~user@redhat/jboss/jc3> has quit IRC (Remote host closed the connection)05:18
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant05:48
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)06:21
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant06:22
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 256 seconds)06:26
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant06:34
*** je <je!~je@mail.natur-energi.dk> has joined #immutant07:02
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant07:11
*** jcrossle_ is now known as jcrossley3-away07:18
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)07:37
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant07:37
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has joined #immutant07:38
*** egli <egli!~user@alouette.sbs.ch> has joined #immutant07:39
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 264 seconds)07:42
*** dm3 <dm3!~dm3@pub158181119172.dh-hfc.datazug.ch> has joined #immutant07:54
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)08:07
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant08:10
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Remote host closed the connection)08:11
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant08:14
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)08:28
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant09:39
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant10:27
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: Leaving)10:51
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant11:09
*** bbrowning_away is now known as bbrowning11:53
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)12:03
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant12:09
*** tcrawley-away is now known as tcrawley12:12
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)12:28
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant12:30
*** jcrossley3-away is now known as jcrossley312:45
*** egli <egli!~user@alouette.sbs.ch> has quit IRC (Remote host closed the connection)12:53
*** lance|afk is now known as lanceball12:55
*** je <je!~je@mail.natur-energi.dk> has quit IRC (Ping timeout: 264 seconds)12:56
*** tcrawley is now known as tcrawley-away13:04
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 264 seconds)13:16
*** _kardan <_kardan!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has joined #immutant13:39
*** egli <egli!~user@alouette.sbs.ch> has joined #immutant13:45
bbrowningjcrossley3: so https://github.com/projectodd/wunderboss/blob/af973d97185875f9fe663907080225749c5eb649/modules/scheduling/src/main/java/org/projectodd/wunderboss/scheduling/QuartzScheduling.java#L236 is the offending line14:08
bbrowninghttps://github.com/projectodd/wunderboss/blob/af973d97185875f9fe663907080225749c5eb649/modules/scheduling/src/main/java/org/projectodd/wunderboss/scheduling/QuartzScheduling.java#L23614:08
bbrowning(was that previous paste bolded text for anyone else?)14:08
bbrowning"String name = this.keys.remove(key);" - name is sometimes getting set to null there14:08
bbrowningso either that JobKey didn't exist in the map or for some reason it had a null value14:09
jcrossley3hmm14:09
jcrossley3bbrowning: that makes me want to blame quartz14:11
bbrowningquartz is calling the trigger listeners in the right order14:11
jcrossley3since its trigger is the only thing removing by JobKey14:11
bbrowningI'm adding some println debugging now14:11
bbrowningI see that we're not calling currentJobs.put until after the trigger listeners have fired, which is odd14:12
jcrossley3uh, yeah, that would be wrong14:12
bbrowninghttps://github.com/projectodd/wunderboss/blob/af973d97185875f9fe663907080225749c5eb649/modules/scheduling/src/main/java/org/projectodd/wunderboss/scheduling/QuartzScheduling.java#L123 is the problem14:13
bbrowningthat and line 12514:13
bbrowningwe schedule the job then call currentJobs.put14:13
bbrowningand the job fires between those two calls14:13
jcrossley3ah!14:13
jcrossley3good catch!14:13
jcrossley3you want to fix, or shall i?14:14
bbrowningI'll fix since I can reproduce14:14
jcrossley3kk! thanks!14:14
bbrowningsuggestions on a fix? swap the order of the two calls, or add more synchronization somewhere?14:14
jcrossley3i think put before schedule should do it?14:14
jcrossley3though that may cause other weirdness, come to think of it14:15
bbrowningyeah - I didn't know if it was after for a reason, like if scheduleJob throws14:15
jcrossley3actually, it would be better for both the service and the jobs to synchronize on the same thing14:17
jcrossley3that should solve it regardless of order of 123/12514:17
bbrowningyeah14:18
jcrossley3i think remove all the synchronized keywords from the static class14:18
jcrossley3and have remove(JobKey) synchronize on the service14:19
jcrossley3which means Jobs can't be static14:19
jcrossley3it needs a reference to the service instance14:20
bbrowningaye14:21
bbrowningit can either be static and pass in the service on construction or not be static14:21
bbrowningmight as well not be static since it's only used from the service14:21
jcrossley3or leave it static, and just have the trigger sycnhronize on QuartzScheduling.this before it removes?14:22
bbrowningyeah that might be the simplest thing14:22
jcrossley3that's the only place it's accessed unsynchronized14:22
jcrossley3on QuartzScheduling.this, i should say14:23
jcrossley3concurrency is hard14:23
bbrowningwe should totally rewrite this in node14:24
bbrowning1 thread!14:24
jcrossley3haha14:24
jcrossley3actually, since subscribe is sync'd, it's probably fine to just switch the order of those calls, but you'd need to handle the possible exception and remove it14:27
jcrossley3the sync in the trigger is prolly simpler14:28
bbrowningit is :)14:28
*** GitHub111 <GitHub111!~GitHub111@192.30.252.42> has joined #immutant14:28
GitHub111[wunderboss] bbrowning pushed 1 new commit to master: http://git.io/vv6gW14:28
GitHub111wunderboss/master 3e507cf Ben Browning: Fix a race condition when unscheduling jobs that trigger immediately...14:28
*** GitHub111 <GitHub111!~GitHub111@192.30.252.42> has left #immutant14:28
jbossbotTitle: Fix a race condition when unscheduling jobs that trigger immediately · projectodd/wunderboss@3e507cf · GitHub14:28
jcrossley3bbrowning: thanks for figuring that out!14:29
bbrowningwelcome! it's weird that sometimes a virtual machine seems to be the only way to reproduce racism like this14:29
jcrossley3i'm gonna create a jira for it, just so it's noted in our next release.14:30
bbrowningok14:30
projectodd-ciProject wunderboss-incremental build #234: SUCCESS in 2 min 22 sec: https://projectodd.ci.cloudbees.com/job/wunderboss-incremental/234/14:31
projectodd-ciBen Browning: Fix a race condition when unscheduling jobs that trigger immediately14:31
*** deadghost <deadghost!~deadghost@49.230.72.114> has quit IRC (Ping timeout: 255 seconds)14:43
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant14:47
*** deadghost <deadghost!~deadghost@49.230.72.114> has joined #immutant14:56
*** tcrawley-away is now known as tcrawley14:57
*** deadghost <deadghost!~deadghost@49.230.72.114> has quit IRC (Ping timeout: 264 seconds)15:06
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)15:09
*** deadghost <deadghost!~deadghost@49.230.72.114> has joined #immutant15:18
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant15:25
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)15:30
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant15:33
*** jcrossle_ <jcrossle_!~user@71-90-202-246.dhcp.stls.mo.charter.com> has joined #immutant15:33
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Client Quit)15:34
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant15:35
*** jcrossley3 <jcrossley3!~user@71-90-202-246.dhcp.stls.mo.charter.com> has quit IRC (Ping timeout: 245 seconds)15:35
*** jcrossle_ is now known as jcrossley315:38
*** lanceball is now known as lance|afk15:41
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant15:46
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 240 seconds)16:03
*** cap10morgan <cap10morgan!~cap10morg@75-148-43-81-Colorado.hfc.comcastbusiness.net> has joined #immutant16:07
cap10morganIs there a way to configure an Immutant app you're deploying to wildfly w/ env vars? preferably at deployment time.16:07
jcrossley3cap10morgan: do you use the environ lib?16:10
cap10morganI don't think so, no. But I can if it would help here. :)16:10
jcrossley3check it out, yeah16:11
cap10morganMy problem isn't getting env vars into my clojure app, it's getting them over to wildfly when I deploy the .war to it.16:11
jcrossley3ah, wildfly16:11
tcrawleyyou would have to restart wildfly with those vars set for the .war to pick them up16:12
cap10morganOK, well, is there some other way to inject configuration into a deployed app at deployment time?16:12
cap10morganI realize this is now just a wildfly question. :)16:12
jcrossley3cap10morgan: does deployment involve creating the war?16:14
cap10morganjcrossley3: up until it hasn't; we've doing that in the docker build step.16:14
cap10morgan*up until now16:14
jcrossley3so you're creating docker images?16:15
jcrossley3wouldn't they include wildfly, too?16:15
cap10morganyes, w/ .war files in them. if they see a linked wildfly container at runtime, they deploy the .war to that container.16:15
cap10morganso no, they don't include wildfly16:15
jcrossley3cap10morgan: so this may not help you, but when you refer to both "docker" and "wildfly", i think this: https://medium.com/@jstrachan/the-decline-of-java-application-servers-when-using-docker-containers-edbe032e1f3016:17
jbossbotTitle: the decline of Java application servers when using docker containers — Medium16:17
cap10morganyeah, we've played around w/ all these approaches. the problem w/ the big monolithic "all services + application server" image is that it's very opaque. what versions of what services are running in that thing? and that you have to re-deploy a big giant blob of everything for even the tiniest change (I sure it hope it doesn't crash!).16:20
cap10morganso we've moved more towards app containers that know how to deploy themselves to linked wildfly containers and undeploy themselves on exit so they can still manage their app's lifecycle using normal docker tooling but also share JVMs16:21
cap10morganwhich is mostly important for us w/ Datomic licenses (which are unfortunately structured per JVM, but we're not going to change that overnight)16:22
cap10morganI'm going to try an approach where we build the .war at deploy time and render the env vars into a config file that goes into the war.16:29
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)16:31
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant16:32
*** mgoldmann is now known as mgoldmann|away16:37
*** bbrowning is now known as bbrowning_away16:37
jcrossley3cap10morgan: i think that's a sensible approach16:39
*** dm3 <dm3!~dm3@pub158181119172.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 245 seconds)17:00
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)17:00
*** bbrowning_away is now known as bbrowning17:01
*** _kardan_ <_kardan_!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has joined #immutant17:04
*** _kardan <_kardan!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has quit IRC (Ping timeout: 265 seconds)17:06
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)17:20
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant17:23
*** lance|afk is now known as lanceball17:27
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Read error: Connection reset by peer)17:34
*** bobmcw <bobmcw!~bobmcw@va-184-0-214-62.dhcp.embarqhsd.net> has joined #immutant17:34
*** bobmcw <bobmcw!~bobmcw@va-184-0-214-62.dhcp.embarqhsd.net> has quit IRC (Changing host)17:34
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has joined #immutant17:34
*** hiredman_ is now known as hiredman17:40
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant17:53
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant17:55
bbrowningjcrossley3: cap10morgan: TorqueBox users will have a similar problem in TorqueBox 4 that I don't know how to solve yet18:01
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)18:04
bbrowningI was wondering if we should support putting a .properties or similar file next to the .war on disk to override things18:05
bbrowningbut haven't really thought that out thoroughly18:05
*** _kardan_ <_kardan_!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has quit IRC (Read error: Connection reset by peer)18:07
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has quit IRC (Ping timeout: 244 seconds)18:07
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)18:19
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant18:24
tcrawleybbrowning: I looked in to that, but couldn't figure out how to reliably find the deployments/ dir, or what to do if the .war was deployed via the management api18:30
bbrowningtcrawley: iirc we already reliably find the deployments/ dir18:30
*** _kardan <_kardan!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has joined #immutant18:30
bbrowningas far as the management api, perhaps we just wouldn't support it in that case18:31
bbrowningTB4 has to know that to be able to extract the jar inside the .war, I think18:33
bbrowningor perhaps we only reliably know the .jar location but not the deployments/ dir18:33
tcrawleyI recall trying it, and ApplicationRunner#jarURL was giving me the path to the tmp dir where WF explodes the war, but I could be remembering it incorrectly18:33
bbrowningyeah I actually feel like I had to just hardcode some $jbossfoobar/deployments at one point in the past18:33
bbrowningin an old version of WildFlyService.java - https://github.com/projectodd/wunderboss/blob/81e832103a2800731eaec3a2b405812efb899bc8/modules/wildfly/src/main/java/org/projectodd/wunderboss/wildfly/WildFlyService.java#L6018:35
bbrowningwe looked for a foo.properties inside deployments/ next to foo.jar18:35
tcrawleyah18:36
tcrawleywe could certainly do that again I suppose18:36
tcrawleyit would be handy18:36
bbrowninglooks like it still looks for external .properties files for .jars - https://github.com/projectodd/wunderboss/blob/master/modules/core/src/main/java/org/projectodd/wunderboss/ApplicationRunner.java#L7418:38
bbrowningso uberjar but not inside wildfly lets you add a foo.properties to override some things18:38
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)18:38
tcrawleyright18:38
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant18:47
*** jcrossle_ <jcrossle_!~user@71-90-202-246.dhcp.stls.mo.charter.com> has joined #immutant18:53
*** jcrossley3 <jcrossley3!~user@71-90-202-246.dhcp.stls.mo.charter.com> has quit IRC (Ping timeout: 264 seconds)18:58
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Read error: Connection reset by peer)19:13
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant19:13
*** jcrossle_ is now known as jcrossley319:18
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)19:36
*** GitHub60 <GitHub60!~GitHub60@192.30.252.46> has joined #immutant19:51
GitHub60[wunderboss] tobias tagged 0.6.1 at f5bf7e3: http://git.io/vvXlB19:51
*** GitHub60 <GitHub60!~GitHub60@192.30.252.46> has left #immutant19:51
jbossbotTitle: Commits · projectodd/wunderboss · GitHub19:51
*** GitHub139 <GitHub139!~GitHub139@192.30.252.42> has joined #immutant19:51
GitHub139[wunderboss] tobias pushed 2 new commits to master: http://git.io/vvXl819:51
GitHub139wunderboss/master e05cbf6 Toby Crawley: [maven-release-plugin] prepare release 0.6.119:51
GitHub139wunderboss/master e24017e Toby Crawley: [maven-release-plugin] prepare for next development iteration19:51
*** GitHub139 <GitHub139!~GitHub139@192.30.252.42> has left #immutant19:51
jbossbotTitle: Comparing 3e507cfcccdf...e24017e4db79 · projectodd/wunderboss · GitHub19:51
projectodd-ciProject wunderboss-incremental build #235: SUCCESS in 2 min 25 sec: https://projectodd.ci.cloudbees.com/job/wunderboss-incremental/235/19:54
projectodd-ci* Toby Crawley: [maven-release-plugin] prepare release 0.6.119:54
projectodd-ci* Toby Crawley: [maven-release-plugin] prepare for next development iteration19:54
*** jcrossle_ <jcrossle_!~user@71-90-202-246.dhcp.stls.mo.charter.com> has joined #immutant20:01
*** jcrossley3 <jcrossley3!~user@71-90-202-246.dhcp.stls.mo.charter.com> has quit IRC (Ping timeout: 264 seconds)20:04
*** _kardan <_kardan!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has quit IRC (Quit: Computer has gone to sleep.)20:07
*** jcrossle_ is now known as jcrossley320:16
jbossbotgit [immutant] push thedeuce d42cab6.. Toby Crawley Make this test more robust....20:17
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/commit/d42cab65d20:17
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has joined #immutant20:17
projectodd-ciProject immutant2-incremental build #564: SUCCESS in 4 min 46 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/564/20:22
projectodd-ciToby Crawley: Make this test more robust.20:22
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)20:30
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant20:30
projectodd-ciProject immutant2-incremental-integs build #51: FAILURE in 9 min 2 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/51/20:31
projectodd-ciToby Crawley: Make this test more robust.20:31
tcrawleydingdang20:32
jbossbotgit [immutant] push thedeuce d5c6e2c.. Toby Crawley Give CI more time.20:33
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/commit/d5c6e2c5520:33
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 256 seconds)20:35
*** bbrowning is now known as bbrowning_away20:35
projectodd-ciProject immutant2-incremental build #565: SUCCESS in 6 min 28 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/565/20:40
projectodd-ciToby Crawley: Give CI more time.20:40
jcrossley3tcrawley: we're just going to call final 2.0.0, right?20:55
jcrossley3not 2.0.0-Final20:55
*** je <je!~je@x1-6-c0-3f-0e-f8-01-dc.cpe.webspeed.dk> has joined #immutant20:56
projectodd-ciYippie, build fixed!21:00
projectodd-ciProject immutant2-incremental-integs build #52: FIXED in 19 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/52/21:00
projectodd-ciToby Crawley: Give CI more time.21:00
tcrawleyjcrossley3: 2.0.0-Final-FINALLY21:12
tcrawleyyeah, 2.0.021:12
jcrossley3kk!21:12
*** tcrawley is now known as tcrawley-away21:14
*** bbrowning_away is now known as bbrowning21:17
*** lanceball is now known as lance|afk21:38
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant21:44
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 248 seconds)21:52
*** bbrowning is now known as bbrowning_away21:54
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has quit IRC (Quit: bobby_)22:24
*** je <je!~je@x1-6-c0-3f-0e-f8-01-dc.cpe.webspeed.dk> has quit IRC (Ping timeout: 272 seconds)22:28
*** cap10morgan <cap10morgan!~cap10morg@75-148-43-81-Colorado.hfc.comcastbusiness.net> has quit IRC (Ping timeout: 265 seconds)22:28
*** bobmcw_ <bobmcw_!~bobmcw@va-184-0-214-62.dhcp.embarqhsd.net> has joined #immutant23:58
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Ping timeout: 245 seconds)23:59

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!