IRC Logs for #circuits Monday, 2013-11-04

*** ConlifctX[LpTp] has joined #circuits06:56
ConlifctX[LpTp]good morning :)07:10
prologicafternoon :)07:13
ConlifctX[LpTp]ohh :)07:19
ConlifctX[LpTp]yes, good afteroon :)07:19
ConlifctX[LpTp]i have a new kid :) a girl and im super excited :) (and in shock ofc) :)07:20
ConlifctX[LpTp]that is so strange :)07:20
*** ConlifctX[LpTp] has quit IRC08:31
*** ConlifctX[LpTp] has joined #circuits08:38
*** ConlifctX[LpTp] has quit IRC08:41
*** koobs has quit IRC08:42
*** koobs has joined #circuits08:42
*** Conlifct_ has joined #circuits08:44
*** koobs has quit IRC08:49
*** koobs has joined #circuits08:49
*** koobs has quit IRC08:50
*** koobs has joined #circuits08:50
*** koobs has quit IRC08:50
*** koobs has joined #circuits08:50
*** Conlifct_ has quit IRC09:07
*** ConlifctX[LpTp] has joined #circuits09:19
prologicConlifctX[LpTp], congrats09:25
prologicreally!09:25
prologicI was the same - still am :)09:25
ConlifctX[LpTp]thank you :))))09:25
*** ConlifctX[LpTp] has quit IRC09:30
*** ConlifctX[LpTp] has joined #circuits09:52
*** ConlifctX[LpTp] has quit IRC09:59
*** ConlifctX[LpTp] has joined #circuits10:06
*** ConlifctX[LpTp] has quit IRC12:47
*** ConlifctX[LpTp] has joined #circuits12:48
*** ConlifctX[LpTp] has quit IRC12:52
*** ConlifctX[LpTp] has joined #circuits13:29
*** ConlifctX[LpTp] has quit IRC13:33
*** ConlifctX[LpTp] has joined #circuits13:41
*** ConlifctX[LpTp] has quit IRC13:53
*** ConlifctX[LpTp] has joined #circuits13:54
*** ConlifctX[LpTp] has quit IRC13:58
spaceoneprologic: important question:15:06
spaceoneif i have 2 handlers for a event and the first handler fails will the second handler be called?15:07
spaceoneit would be nice if Debugger prints out every called handler15:10
spaceoneit seems that 1. handler(1) 2. handler_failure 3. handler(2).. so i could stop event handling in the failure handler, right?15:17
spaceonehow to do this? event.stop() is new in circuits-dev, right?15:18
spaceonehmm, i would have expected the other handlers not to be executed before the failure handler was called.15:46
spaceoneanother thing:15:49
spaceonefire(write(sock))15:49
spaceonefire(close(sock))15:49
spaceonefire(write(sock))15:49
spaceoneprologic: can i at least use the success event for this?16:01
spaceoneso if all handlers completed successfully that the success handler will be called16:02
spaceoneprologic: would the success handler be called if no handler for the origin event exists?16:03
*** ConlifctX[LpTp] has joined #circuits16:14
*** ConlifctX[LpTp] has quit IRC16:16
*** ConlifctX[LpTp] has joined #circuits16:43
*** ConlifctX[LpTp] has quit IRC17:25
*** ConlifctX[LpTp] has joined #circuits17:26
*** Conlifct_ has joined #circuits17:27
*** ConlifctX[LpTp] has quit IRC17:27
*** Conlifct_ has quit IRC17:47
*** Conlifct_ has joined #circuits17:55
*** Conlifct_ has quit IRC18:01
*** ConlifctX[LpTp] has joined #circuits18:02
*** ConlifctX[LpTp] has quit IRC18:06
spaceoneprologic: also: can i see if a event was handled? (or if no handler is registered for it)18:30
*** ConlifctX[LpTp] has joined #circuits18:45
*** ConlifctX[LpTp] has quit IRC19:00
prologicspaceone, yes the 2nd handler will run regardless of failed handlers before21:08
prologicspaceone, The Debugger does display the actual handler usually in the form of Class.handler_function_name21:08
prologicspaceone, yes, event.stop() to filter/stop the event propagation21:09
prologicspaceone, little bit hard to execute the next handler only after the failure event of the previous handler21:09
prologicspaceone, would require quite comple synchronoization which would cost in terms of performance21:10
prologicspaceone, yes I believe you can use the success feedback channel, it should only be fired iif all handlers succeeded21:11
prologicspaceone, yes. event.handler is set to the last handler that handled that event21:11
prologicit will be None if no handler handled it21:12
spaceoneprologic: thanks21:25
spaceonei think the correct way of doing this is to use the success event21:26
spaceoneprologic: will there be a foo_failure_success event?21:26
prologicOnly if you set Success.failure = True21:28
spaceoneprologic: for me Debugger prints only the event but not the handler_function_name (? or am i blind), at least i see only one handler not two for a event21:29
spaceoneit would be usefull to see also the class name of the handler21:29
prologicdo you want yo see this for every event. or only errors.21:30
prologicbecause it should for errors21:30
spaceonehmm, when i say Debugger(verbose=True) i want to see every detail21:30
spaceoneits often not easy to understand the debugger output because it logs unneccessary parameters which <repr>s prints out to much information21:31
prologicok,21:31
prologicsend me a pull request with this21:32
prologicits not haed to add21:32
spaceoneyes21:32
spaceoneah, if i implement this i will only give you a diff,,, i hate bittbucket21:33
prologicok thats fine too21:33
prologicir tou could try our github mirrirs21:33
prologicgive me a chance to make that work21:33
prologic:)21:34
spaceoneyes, it is not urgently21:35
prologicok21:35
prologicdiff is fine21:35

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