Wednesday, 2015-10-07

*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant00:59
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 264 seconds)03:15
*** xcv <xcv!~xcv@37.120.122.31> has joined #immutant03:35
*** xcv <xcv!~xcv@37.120.122.31> has quit IRC (Ping timeout: 250 seconds)03:40
*** jcrossle_ is now known as jcrossley3-away04:44
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant05:49
*** deadghost <deadghost!~deadghost@122.166.89.46> has joined #immutant06:06
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Remote host closed the connection)06:07
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant06:11
*** mgoldmann|away is now known as mgoldmann06:14
*** xcv <xcv!~xcv@2a02:2450:102b:5b:50b9:45ae:8899:68ad> has joined #immutant06:36
*** xcv <xcv!~xcv@2a02:2450:102b:5b:50b9:45ae:8899:68ad> has quit IRC (Ping timeout: 256 seconds)06:41
*** deadghost <deadghost!~deadghost@122.166.89.46> has quit IRC (Ping timeout: 264 seconds)06:52
*** je <je!~je@mail.natur-energi.dk> has joined #immutant07:03
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Remote host closed the connection)07:06
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant07:07
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant07:21
*** xcv <xcv!~xcv@2a02:2450:102b:5b:50b9:45ae:8899:68ad> has joined #immutant07:45
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Remote host closed the connection)08:29
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant08:30
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Ping timeout: 272 seconds)08:35
*** msw_ <msw_!c25fc538@gateway/web/freenode/ip.194.95.197.56> has joined #immutant08:40
msw_Imagine you have an immutant application structured using ssierra's components. Your -main starts the system when it's getting deployed on wildfly. Now ... I'd like to stop the system when it's getting undeployed. (Where) can I register a callback in the runtime so the container will call me before it undeploys me?08:42
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant08:43
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant08:58
*** xcv <xcv!~xcv@2a02:2450:102b:5b:50b9:45ae:8899:68ad> has quit IRC (Ping timeout: 256 seconds)09:02
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Remote host closed the connection)09:03
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant09:03
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Ping timeout: 250 seconds)09:08
*** anthracite <anthracite!~anthracit@pdpc/supporter/active/anthracite> has joined #immutant10:12
*** qwerty_nor <qwerty_nor!~Thunderbi@37.229.49.175> has joined #immutant10:20
*** anthracite <anthracite!~anthracit@pdpc/supporter/active/anthracite> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)11:02
*** anthracite <anthracite!~anthracit@pdpc/supporter/active/anthracite> has joined #immutant12:02
*** lance|afk is now known as lanceball12:14
*** bbrowning_away is now known as bbrowning12:18
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant12:20
*** msw_ <msw_!c25fc538@gateway/web/freenode/ip.194.95.197.56> has quit IRC (Quit: Page closed)12:22
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 250 seconds)12:28
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant12:32
*** xcv <xcv!~xcv@37.120.122.31> has joined #immutant12:33
*** deadghost <deadghost!~deadghost@122.178.235.102> has joined #immutant12:34
*** tcrawley-away is now known as tcrawley12:47
*** jcrossley3-away is now known as jcrossley312:49
tcrawleymsw_: in case you read the log: http://immutant.org/documentation/current/apidoc/immutant.util.html#var-at-exit12:51
jbossbotTitle: immutant.util documentation12:51
jcrossley3i think he does12:53
jcrossley3or did12:53
tcrawleyyeah12:53
jcrossley3you'd think someone who read the logs might read the docs, too ;)12:53
jcrossley3sorry, msw_! :)12:53
jcrossley3now we'll find out for sure if he reads the logs12:54
tcrawleywell, it's one fn buried in a ns with a bunch of unrelated fn's12:54
tcrawleyheh12:54
jcrossley3pb12:54
jcrossley3tcrawley: a lot of those fn's in 'util' might be more easily found in a ns called 'runtime' maybe.12:58
tcrawleyor immutant.runtime-util. or immutant.util.runtime, or immutant.util.runtime-util12:58
tcrawley:)12:58
jcrossley3util is almost always a garbage dump12:59
jcrossley3if we introduce a new ns, i'd like it to be top-level12:59
jcrossley3lifecycle?12:59
jcrossley3admin?12:59
jcrossley3although, if i'm looking down that left side of ns's for something that might contain an undeploy hook, util is the only viable candidate to me13:00
tcrawleyof your suggestions, I like runtime the best13:00
tcrawleyI say we leave it for now13:01
jcrossley3kk!13:01
*** bobmcw <bobmcw!~bobmcw@va-67-233-84-133.dhcp.embarqhsd.net> has joined #immutant13:20
*** bobmcw <bobmcw!~bobmcw@va-67-233-84-133.dhcp.embarqhsd.net> has quit IRC (Changing host)13:20
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has joined #immutant13:20
*** xcv <xcv!~xcv@37.120.122.31> has quit IRC (Remote host closed the connection)13:22
*** xcv <xcv!~xcv@2a02:2450:102b:5b:1c48:df6e:6796:da2e> has joined #immutant13:56
*** deadghost <deadghost!~deadghost@122.178.235.102> has quit IRC (Ping timeout: 268 seconds)14:32
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has joined #immutant14:41
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 252 seconds)14:42
*** anthraci_ <anthraci_!~anthracit@pdpc/supporter/active/anthracite> has joined #immutant14:47
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant14:48
*** anthracite <anthracite!~anthracit@pdpc/supporter/active/anthracite> has quit IRC (Read error: Connection reset by peer)14:49
*** je <je!~je@mail.natur-energi.dk> has quit IRC (Ping timeout: 268 seconds)14:55
*** msw_ <msw_!5d87c5c0@gateway/web/freenode/ip.93.135.197.192> has joined #immutant14:56
msw_Thanks! .. and to satisfy the curiosity: I do read both - logs and docs. I was looking in the wrong spot though.14:57
jcrossley3msw_: :)14:57
jcrossley3msw_: we can't come up with a better ns to put that thing in, but we're open to suggestions14:58
tcrawleymsw_: howdy!14:58
msw_heyho.. Nah it's all good. Frankly, I stared at too many windows containing docco that I just failed to look at the first place, immutant's API doc14:58
msw_I was rummaging through jboss notes and looking through the management interface values and .. got lost. I thought you guys surely know about it if it exists.. and actually you put it where I'd expect it, namespace wise.14:59
jcrossley3coolio15:00
msw_I've only ever deployed naked and on wildfly... is the "ee" field stable enough so I could potentially deploy to apache's EE container as well?15:02
msw_(IANAJEE - I am not a Java/EE Engineer!)15:02
tcrawleymsw_: we don't currently support to deploying to other EE containers, namely because we tie in to wildfly-specific bits to get handles on the messaging/caching/etc systems that are there15:05
tcrawleywe've discussed supporting other containers, but haven't figured out what that would take15:05
tcrawleyour web support is container-agnostic, so would work in any servlet container, but the all the other init bits assume we are in WildFly15:06
tcrawleyand will get partially loaded even if you are only using web, so will barf if you deploy to !wildfly15:06
msw_yeah I noticed that part (loading deps even when only using web) even already with using the full immutant package (not the modules) and running on a non- standalone-full container...15:11
msw_Ok, good to know15:11
msw_(... but you explicitly documented the requirement for -full in that case, so you're golden there)15:13
jcrossley3msw_: where are you located?15:14
msw_central EU, why?15:14
jcrossley3we're in US southeast, so not around when you ask question. we try to be responsive though, so if you have a twitter handle or some such, we can reply rather than you having to look at logs, but whatever works15:17
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Remote host closed the connection)15:17
msw_yeah you bastards you are neighboring my old home state (VA), aren't you (*shakes fist at US immigration*) -- but seriously, I'm fine with asynchronous replies, and having them in here has the benefit of rolling indexed documentation of sorts15:19
*** anthraci_ <anthraci_!~anthracit@pdpc/supporter/active/anthracite> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)15:20
jcrossley3msw_: i'm near atlanta and tcrawley is near asheville, but our fearless leader, bobmcw, is in your shitty home state ;)15:21
msw_oi! appalachia FTW!15:22
*** mgoldmann is now known as mgoldmann|away15:23
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant15:23
bobmcwmsw_: wytheville, south of blacksburg15:30
msw_sigh.. I miss Floyd15:32
msw_btw, we still expect wildfly to run out of permgen space upon continuously deploying?15:35
msw_or only when there's uncaught top-level exceptions bubbling out?15:37
msw_in other words, do you expect to be able to run a wildfly (standalone) container without restarting the container, in production, while deploying a couple dozen times to it?15:39
msw_(because, I don't)15:39
*** deadghost <deadghost!~deadghost@122.167.82.86> has joined #immutant15:52
tcrawleymsw_: you don't expect to be able to? or you don't restart?15:52
tcrawleyI don't expect you to run out of permgen unless you are spawning threads/threadpools that you don't shut down15:53
*** bbrowning is now known as bbrowning_away15:53
tcrawleywe do shut down clojure's agent pool on undeploy (via clojure.core/shutdown-agents)15:53
tcrawleybut you may have other things that do start threads (core.async, for example)15:54
tcrawleyeven though Immutant 2 doesn't use ShimDandy, these same caveats apply: https://github.com/projectodd/shimdandy#preventing-memory-leaks15:55
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Remote host closed the connection)15:55
msw_ok, trying to reproduce the problems and see if I did it via core.async or something else15:56
tcrawleythe easiest step is to look at the threads in visualvm, and see if they are increasing as you redeploy15:57
tcrawleythen look at the thread names to see if you see duplicates15:57
jcrossley3i concur with tcrawley wrt immutant libraries and permgen, but any library you depend on may contribute to permgen leaks when run on a java app server. i think most production admins kill their server as a part of the process of redeploying their apps.15:57
tcrawleyif that doesn't give a clue, you probably have to take a memory dump and use a memory analyzer (like Eclipse MAT) to see what is holding references15:58
tcrawleythat's not much fun, but sure is a learning experience :)15:58
msw_good to know, jcrossley3.15:58
msw_I used jmx + top threads to identify problems in wildfly before (that I caused, naturally) -- pity I didn't note _how_ I made these problems appear15:59
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has quit IRC ()16:01
msw_er .. now I tried deploying a dev war onto my widlfly with a vanilla ... and now it isn't finding immutant/web/as.clj?16:02
msw_wtf, lein-immutant 2.0.1 just fixed a very similar bug16:03
*** bobmcw <bobmcw!~bobmcw@va-67-233-84-133.dhcp.embarqhsd.net> has joined #immutant16:04
*** bobmcw <bobmcw!~bobmcw@va-67-233-84-133.dhcp.embarqhsd.net> has quit IRC (Changing host)16:04
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has joined #immutant16:04
msw_hah! PEBKAC. *phew*16:05
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Ping timeout: 255 seconds)16:08
*** xcv_ <xcv_!~xcv@vpn-18-101-24-183.mit.edu> has joined #immutant16:17
*** xcv <xcv!~xcv@2a02:2450:102b:5b:1c48:df6e:6796:da2e> has quit IRC (Read error: No route to host)16:19
*** xcv <xcv!~xcv@2a02:2450:102b:5b:1c48:df6e:6796:da2e> has joined #immutant16:20
*** xcv_ <xcv_!~xcv@vpn-18-101-24-183.mit.edu> has quit IRC (Read error: Connection reset by peer)16:20
*** bobmcw <bobmcw!~bobmcw@va-67-233-84-133.dhcp.embarqhsd.net> has joined #immutant16:45
*** bobmcw <bobmcw!~bobmcw@va-67-233-84-133.dhcp.embarqhsd.net> has quit IRC (Changing host)16:45
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has joined #immutant16:45
*** deadghost <deadghost!~deadghost@122.167.82.86> has quit IRC (Ping timeout: 246 seconds)16:57
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has joined #immutant17:01
*** GitHub188 <GitHub188!~GitHub188@192.30.252.42> has joined #immutant17:10
GitHub188[wunderboss] tobias pushed 2 new commits to master: http://git.io/vcj7l17:10
GitHub188wunderboss/master c7d5650 Toby Crawley: Only call stop callback if daemon actually started.17:10
GitHub188wunderboss/master 6dbd527 Toby Crawley: Actually close registered resources when stopping a destination [#14]17:10
*** GitHub188 <GitHub188!~GitHub188@192.30.252.42> has left #immutant17:10
jbossbotTitle: Comparing 3208e8c458a5...6dbd5271b087 · projectodd/wunderboss · GitHub17:10
projectodd-ciProject wunderboss-incremental build #291: SUCCESS in 4 min 19 sec: https://projectodd.ci.cloudbees.com/job/wunderboss-incremental/291/17:14
projectodd-ci* Toby Crawley: Only call stop callback if daemon actually started.17:15
projectodd-ci* Toby Crawley: Actually close registered resources when stopping a destination [#14]17:15
jbossbotgit [immutant] push master 125183d.. Toby Crawley Wboss build and test to fix failure to close destination closeables on stop [IMMUTANT-583]17:22
jbossbotgit [immutant] push master URL: http://github.com/immutant/immutant/commit/125183d7117:22
jbossbotjira [IMMUTANT-583] Registered closeables aren't closed when a destination is stopped (regression from 2.0.0) [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-58317:22
projectodd-ciProject immutant2-incremental build #653: SUCCESS in 3 min 49 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/653/17:26
projectodd-ciProject immutant2-incremental-integs build #159: STILL FAILING in 4 min 0 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/159/17:31
projectodd-ciToby Crawley: Wboss build and test to fix failure to close destination closeables on stop [IMMUTANT-583]17:31
jbossbotjira [IMMUTANT-583] Registered closeables aren't closed when a destination is stopped (regression from 2.0.0) [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-58317:31
msw_I've just had a 20 min 10 second deploy loop running (touch bla.dodeploy for a dev war for a pretty much vanilla project). The project does nothing but calling web/run (actually not even that because it has an intentional missing close-paren).17:37
msw_This: http://uharc.net/~phaeton/wildfly-immutant-deployspam.png makes me think it won't do well with bigger projects :) [wf 9.0.1 F, imm 2.1.0, l-i 2.0.1, clj 1.7, openjdk8]17:37
*** bbrowning_away is now known as bbrowning17:38
msw_nor does this http://uharc.net/~phaeton/wildfly-immutant-deployspam-mem.png . For a vanilla project, I definitly expected a constant memory usage after tcrawley's statements above17:40
tcrawleymsw_: hmm. is the time scale at the bottom of those graphs minutes:seconds? if so, that looks like multiple deploys/second, not every 10 seconds17:40
tcrawleyah, that's hour:minute, just in your TZ :)17:41
projectodd-ciProject immutant2-incremental-integs-eap build #203: STILL FAILING in 12 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs-eap/203/17:41
projectodd-ciToby Crawley: Wboss build and test to fix failure to close destination closeables on stop [IMMUTANT-583]17:41
jbossbotjira [IMMUTANT-583] Registered closeables aren't closed when a destination is stopped (regression from 2.0.0) [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-58317:41
tcrawleymsw_: I assume that missing paren causes the deploy to fail? if so, it's possible that WildFly doesn't properly free a classloader in that case?17:43
tcrawleywould you mind running the same test with non-broken code?17:43
msw_I'll repeat with a correct application. deployment fails, as expected.17:45
tcrawleyjcrossley3: does `cd integration-tests && lein with-profile +cluster all` work for you with HEAD?17:48
tcrawleyjcrossley3: nevermind. it looks like it's an issue with the newer deploy-tools brought in by lein-immutant 2.0.1, which was in my ~/.lein/profiles.clj17:52
msw_tcrawley: Your assumption seems correct. This one cleans up behind itself (more) : http://uharc.net/~phaeton/w-i-ds2.png17:53
msw_difference to previous graph is just added the missing close paren (and thus having no errors during the deploy)17:53
tcrawleyinteresting. did you notice if the number of threads remained ~constant in failed deploy case?17:54
*** lanceball is now known as lance|afk18:16
*** jcrossley3 is now known as jcrossley3-away18:17
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has quit IRC (Remote host closed the connection)18:32
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has joined #immutant18:34
msw_yeah they did, tcrawley18:36
*** xcv <xcv!~xcv@2a02:2450:102b:5b:1c48:df6e:6796:da2e> has quit IRC (Ping timeout: 256 seconds)18:37
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has quit IRC (Ping timeout: 264 seconds)18:38
tcrawleymsw_: hmm, then it's likely a classloader isn't getting released. I don't see the failing-deploy case as a big deal though, because if you have that many failing deploys, you're doing something wrong :)18:40
tcrawleyare you satisfied in the !failure case?18:40
msw_tcrawley: I was imitating development deployments. I agree this must not happen in a production setting. I'm satisfied with the !failure case (for now; I'll try find another leak lateron if I remember enough of the specifics). I was doing this more to make you aware of it, so you could evaluate the case yourself.18:42
*** lance|afk is now known as lanceball18:43
tcrawleygotcha. I think for the development case, I think it's fine to have to restart the container. but if you feel otherwise, I'm going to ask you to open an @issue :)18:43
proddbotWe'd be happy as a turtle dove, my friend, if you would file an issue at https://issues.jboss.org/browse/IMMUTANT18:43
tcrawleyand if you can figure out the other case, I'm happy to take a look at that as well18:44
msw_oh proddbot, remember I'm the aggressive helpful guy :P Thanks tcrawley, I'll come back to you on that if I can reproduce an errant case.18:46
tcrawleyproddbot remembers all18:46
msw_NOW you tell me18:47
*** msw_ <msw_!5d87c5c0@gateway/web/freenode/ip.93.135.197.192> has left #immutant18:48
*** je <je!~je@x1-6-c0-3f-0e-f8-01-dc.cpe.webspeed.dk> has joined #immutant18:50
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant18:52
*** qwerty_nor <qwerty_nor!~Thunderbi@37.229.49.175> has quit IRC (Ping timeout: 256 seconds)19:04
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Remote host closed the connection)19:06
*** dm3 <dm3!~dm3@78.60.230.119> has joined #immutant19:06
*** dm3 <dm3!~dm3@78.60.230.119> has quit IRC (Ping timeout: 244 seconds)19:10
*** jcrossley3-away <jcrossley3-away!~user@71-90-202-1.dhcp.stls.mo.charter.com> has quit IRC (Quit: ERC Version 5.3 (IRC client for Emacs))19:16
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d13b:f3e4:9ac4:7258> has joined #immutant19:18
*** jcrossley3 <jcrossley3!~user@redhat/jboss/jc3> has joined #immutant19:19
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has joined #immutant19:34
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has quit IRC (Ping timeout: 240 seconds)19:39
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d13b:f3e4:9ac4:7258> has quit IRC (Remote host closed the connection)19:41
*** dustinm- <dustinm-!~dustinm@105.ip-167-114-152.net> has quit IRC (Ping timeout: 240 seconds)19:47
*** dustinm <dustinm!~dustinm@105.ip-167-114-152.net> has joined #immutant19:49
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has joined #immutant19:52
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 272 seconds)20:06
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Quit: Leaving)20:07
*** je <je!~je@x1-6-c0-3f-0e-f8-01-dc.cpe.webspeed.dk> has quit IRC (Ping timeout: 272 seconds)20:32
*** xcv <xcv!~xcv@cable-86-56-57-202.cust.telecolumbus.net> has joined #immutant20:42
*** xcv <xcv!~xcv@cable-86-56-57-202.cust.telecolumbus.net> has quit IRC (Ping timeout: 264 seconds)20:47
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Remote host closed the connection)20:53
*** tcrawley is now known as tcrawley-away20:59
*** deadghost <deadghost!~deadghost@122.167.240.85> has joined #immutant21:07
*** bbrowning is now known as bbrowning_away21:26
*** lanceball is now known as lance|afk21:29
*** xcv <xcv!~xcv@37.120.104.228> has joined #immutant21:46
*** pandeiro <pandeiro!~user@189.33.244.242> has joined #immutant21:49
*** xcv <xcv!~xcv@37.120.104.228> has quit IRC (Ping timeout: 268 seconds)21:50
*** danielglauser <danielglauser!~danielgla@75-148-43-81-Colorado.hfc.comcastbusiness.net> has quit IRC (Remote host closed the connection)21:52
*** xcv <xcv!~xcv@37.120.104.228> has joined #immutant22:20
*** danielglauser <danielglauser!~danielgla@2601:282:800:27f2:791f:646e:36c1:c63> has joined #immutant22:36
*** xcv <xcv!~xcv@37.120.104.228> has quit IRC (Remote host closed the connection)23:11
*** deadghost <deadghost!~deadghost@122.167.240.85> has quit IRC (Ping timeout: 240 seconds)23:18

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