| Subject: | POE_ASSERT_DEFAULT cleanup |
Apparently we're not handling things quite right. Over in
irc.ist.unomaha.edu #poe last night:
21:16 <@dngor> POE_ASSERT_DEFAULT=1 ./any-mx-workers-program
So programs seem to run fine, but we are being a little sloppy under the
hood somewhere. Fix whatever the root cause is. Below, an example.
j
jhannah@klab:~/src/moosex-workers$ export POE_ASSERT_DEFAULT=1
jhannah@klab:~/src/moosex-workers$ perl -Ilib t/02.wheel.t
ok 1 - add command
ok 2 - STDOUT: HELLO
ok 3 - child closed.
20250: a 'got_child_closed' event was sent from
/usr/local/share/perl/5.8.8/POE/Resource/Signals.pm at 551 to session 2
(POE::Session=ARRAY(0x87bd0c8)) but session 2
(POE::Session=ARRAY(0x87bd0c8)) has neither a handler for it nor one for
_default
1..3