FWIW, I think it was 1ee27e660a8dce3ae
> On 06 May 2016, at 11:55, Lloyd Fournier wrote:
>
> It works now!
>
> whoever fixed it++. Close this! (and #125758).
>
> On Mon, May 2, 2016 at 11:34 PM Will Coleda via RT
> wrote:
> On Wed Apr 27 03:02:14 2016, lloyd.fo...@gmail.com wrote:
> > Now I'
It works now!
whoever fixed it++. Close this! (and #125758).
On Mon, May 2, 2016 at 11:34 PM Will Coleda via RT <
perl6-bugs-follo...@perl.org> wrote:
> On Wed Apr 27 03:02:14 2016, lloyd.fo...@gmail.com wrote:
> > Now I'm at home I tried it on my Mac, I can confirm that:
> >
> > perl6 -e 'my $
On Wed Apr 27 03:02:14 2016, lloyd.fo...@gmail.com wrote:
> Now I'm at home I tried it on my Mac, I can confirm that:
>
> perl6 -e 'my $waiter = Proc::Async.new(:path, :args World>).start; await start { await $waiter }'
>
> prints Hello World and then hangs forever.
>
> On Wed, Apr 27, 2016 at
Now I'm at home I tried it on my Mac, I can confirm that:
perl6 -e 'my $waiter = Proc::Async.new(:path, :args).start; await start { await $waiter }'
prints Hello World and then hangs forever.
On Wed, Apr 27, 2016 at 2:58 PM Lloyd Fournier
wrote:
> Not sure if it's relevant here but last time
Not sure if it's relevant here but last time I checked there is an issues
with await and Proc::Async on Mac.
RT #125758 for example which looks similar to this.
On Wed, 27 Apr 2016 at 7:08 AM, Will Coleda via RT <
perl6-bugs-follo...@perl.org> wrote:
> On Fri Sep 05 14:44:06 2014, elizabeth wrote
On Fri Sep 05 14:44:06 2014, elizabeth wrote:
> (since leont has been so busy with other stuff, I thought to report
> the problem he found)
>
> 12:11 * leont suspects he's observing Promise.allof spinlocking or
> some such. 100% CPU usage, but no input is coming in :-/
> 12:19 lizmat leont: c
