Hi 1nickt,

To get the default behavior, one can specify the on_post_exit option. The status code for __DIE__ is 255 typically.

MCE::Loop->init(
    max_workers => 2, chunk_size => 1, user_begin => sub {
        $SIG{'INT'} = sub {
            my $signal = shift;
            say "Hello from $signal: $$";
            MCE->exit(0);
        };
    },
    on_post_exit => sub {
        my ($mce, $e) = @_;
        if ($e->{status} == 255) {
            MCE::Signal::stop_and_exit('__DIE__');
        }
    }
);

[download]

More info on on_post_exit is found here. The die handler for MCE workers is found inside MCE::Core::Worker ( ~ line 649 ). I cannot change the MCE->exit(...) line to MCE::Signal::stop_and_exit('__DIE__'). That will break scripts where MCE is called from inside an eval block.

local $SIG{__DIE__} = sub {

   ...

   local $SIG{__DIE__}; local $\ = undef;
   my $_die_msg = (defined $_[0]) ? $_[0] : '';
   print {*STDERR} $_die_msg;

   $self->exit(255, $_die_msg, $self->{_chunk_id});
};

[download]

TODO: When on_post_exit is not specified, have MCE workers abort input due to uncaught exception. Revisit eval. I was unable to get $@ to stick at the manager level. To make this work, I need to call die with the error obtained from the worker at the manager level.

eval { mce_loop { ... } @input };

# TODO: Today, $@ is not set at the manager level.
# Thus, the eval block succeeds. Will fix this.

if ( $@ ) {
    ...
}

[download]

Fortunately, one has control with the on_post_exit handler on what to do: e.g. restart_worker, stop_and_exit.

In reply to Re^7: Interrupt multi-process program while using MCE::Shared hash: END block code does not (all) run by marioroy
in thread Interrupt multi-process program while using MCE::Shared hash: END block code does not (all) run by 1nickt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.