view release on metacpan or  search on metacpan

t/samples/rtcpan.rdf  view on Meta::CPAN

By the way, the last test in the attached test script fails because of
the bug I reported in https://rt.cpan.org/Ticket/Display.html?id=84312

</description>
<dc:creator>TOSHIOITO@cpan.org</dc:creator>
<dc:date>Sun, 31 Mar 2013 01:18:18 +0000</dc:date>
</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=85134">
<title>Return $self from -&#x3E;on_cancel?</title>
<link>https://rt.cpan.org/Ticket/Display.html?id=85134</link>
<description>It&#x27;d be useful for symmetry to have -&#x3E;on_cancel return $self, same as -&#x3E;on_done / -&#x3E;on_fail behaviour.

At the moment:

 my $f = Future-&#x3E;new
 -&#x3E;on_done(sub { ... })
 -&#x3E;on_fail(sub { ... });

works as expected, but:

 my $f = Future-&#x3E;new
 -&#x3E;on_done(sub { ... })
 -&#x3E;on_fail(sub { ... })
 -&#x3E;on_cancel(sub { ... });

doesn&#x27;t - $f ends up as either undef or 1 in the above example.

cheers,

Tom</description>
<dc:creator>TEAM@cpan.org</dc:creator>
<dc:date>Wed, 8 May 2013 10:32:27 +0000</dc:date>
</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=88967">
<title>Can&#x27;t call method &#x22;cancel&#x22; on unblessed reference ...</title>
<link>https://rt.cpan.org/Ticket/Display.html?id=88967</link>
<description>Unit tests and so on occasionally throw

  (in cleanup) Can&#x27;t call method &#x22;cancel&#x22; on unblessed reference at /usr/share/perl5/Future.pm line 992 during global destruction.

(in cleanup) suggests DESTROY, and the only DESTROY in IO::Async is this one, in Process.pm:

 518 sub DESTROY
 519 {
 520    my $self = shift;
 521    $self-&#x3E;{finish_future}-&#x3E;cancel if $self-&#x3E;{finish_future};
 522 }

Offhand I can&#x27;t quite recall if we need or want that in there. If so perhaps it just needs guarding by Devel::GlobalDestruction. May be best to delete it though if it&#x27;s not actually required.

-- 

Paul Evans</description>
<dc:creator>leonerd-cpan@leonerd.org.uk</dc:creator>
<dc:date>Wed, 25 Sep 2013 16:33:36 +0000</dc:date>
</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=89185">
<title>typo fixes</title>
<link>https://rt.cpan.org/Ticket/Display.html?id=89185</link>
<description>Future.pm
53: asynchonous -&#x3E; asynchronous
455: argmuents -&#x3E; arguments</description>
<dc:creator>dsteinbrunner@pobox.com</dc:creator>
<dc:date>Wed, 2 Oct 2013 00:55:04 +0000</dc:date>
</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=91147">
<title>Attempting to mark as -&#x3E;done when cancelling repeat { }</title>
<link>https://rt.cpan.org/Ticket/Display.html?id=91147</link>
<description>Seems that calling -&#x3E;cancel on a repeat {} block can cause things to be marked as done. Does the attached test case look valid?

This is from a larger piece of code which uses timeouts to cancel various actions, the &#x27;already cancelled and cannot be -&#x3E;done&#x27; error seems to crop up every now and then and I *think* this is the cause.

 # Repeat cycle
 ok 1 - mark trial as done
 # Cancel repeat future
 # Repeat cycle
 ok 2 - can cancel repeat future
 # Repeat cycle
 Future=HASH(0xf1ae08) is already cancelled and cannot be -&#x3E;done at .../Future.pm line 565.
        Future::done(Future=HASH(0xf1ae08)) called at .../Future.pm line 837
        Future::on_done(Future=HASH(0xf2ecf8), Future=HASH(0xf1ae08)) called at .../Future/Utils.pm line 204
        Future::Utils::_repeat(CODE(0xa24770), Future=HASH(0xf1ae08), REF(0xc3b8f0), CODE(0xf1ab20), 0) called at .../Future/Utils.pm line 196
        Future::Utils::__ANON__(Future=HASH(0xf2ecf8)) called at .../Future.pm line 516
        Future::_mark_ready(Future=HASH(0xf2ecf8)) called at .../Future.pm line 568
        Future::done(Future=HASH(0xf2ecf8)) called at util-cancel.t line 14

cheers,

Tom
</description>
<dc:creator>TEAM@cpan.org</dc:creator>
<dc:date>Tue, 3 Dec 2013 12:43:27 +0000</dc:date>
</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=92525">
<title>-&#x3E;export_to_level in Future::Utils</title>
<link>https://rt.cpan.org/Ticket/Display.html?id=92525</link>
<description>Currently Future::Utils is just importing the &#x27;import&#x27; sub from Exporter - for some helper modules it&#x27;s useful to apply imports to the caller, particularly for tidying up the &#x27;use&#x27; list when similar patterns of m...

Something along the lines of:

 use Some::Helper::Module qw(:all);
 try { fmap_void { pairmap { } ... } } catch { ... };

Inheriting from Exporter is my usual approach for this, alternatively would it be possible to add export_to_level to the import list?

With the inheritance approach, there seems to be a bug with base.pm (https://github.com/doy/try-tiny/pull/11) which parent.pm doesn&#x27;t have (https://github.com/doy/try-tiny/issues/14).

cheers,

Tom
</description>
<dc:creator>TEAM@cpan.org</dc:creator>
<dc:date>Tue, 28 Jan 2014 03:02:32 +0000</dc:date>
</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=93164">
<title>then doesn&#x27;t seem to check it&#x27;s input</title>
<link>https://rt.cpan.org/Ticket/Display.html?id=93164</link>
<description>In this simple example the non-sub passed to then gets silently ignored:

use warnings;