IRC Logs for #circuits Sunday, 2015-08-09

*** qwebirc22391 has joined #circuits00:14
*** qwebirc22391 has quit IRC00:15
*** nickpancakes has joined #circuits00:15
nickpancakeshey guys, I'm new to circuits, is there any way to find out what channel an handler is being fired from if it's set to handle on channel "*"?00:16
nickpancakesI legitimately have no clue how to get any information from a decorator like that.00:18
nickpancakesfigured out the channel that was firing by taking a closer look at my code, so scratch that entirely.00:28
*** nickpancakes has left #circuits ("WeeChat 1.1.1")00:28
*** ninkotech has quit IRC05:46
*** ninkotech has joined #circuits05:47
prologicmissed him :)10:26
prologicI've been helping my old man out with repairs around our home10:26
*** Osso has joined #circuits11:59
*** Coldblackice has quit IRC14:01
riotis there a tool to check code for exception handler coverage?14:38
rioti know this could easily be done by checking the AST, but i don't wanna go there.14:38
riotand apparently, i need a way to shoot components and restart them... also a lot of memory debugging :(14:39
rioti just made sure, my clientmanager component is completely "try: except Exception as e:" wrapped (too broad?! wth..)14:40
*** Osso has quit IRC17:02
*** Osso has joined #circuits17:11
prologicriot, circuits.core.utils.kill()20:55
riothmmm, that doesn't exist21:04
prologichang on :)23:06
prologicgot moved to circuits.tools23:07

Generated by 2.11.0 by Marius Gedminas - find it at!