New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
await start {} hangs when using HTTP::UserAgent #4659
Comments
From @OvidI was trying to write up a new concurrency examples for a talk when I encountered this: real 0m12.382s real 0m13.869s # hangs forever unless we do a FIRST $ua.get outside of start {} |
From ovid@cpan.orgI forgot to mention this is on OS X Yosemite (10.10.5). This is perl6 version 2015.09-412-g32d7b08 built on MoarVM version 2015.09-79-gee9fc2b Cheers, |
The RT System itself - Status changed from 'new' to 'open' |
From @jonathanstoweI can confirm this happens on other platforms than OS X. It is not isolated to HTTP::UserAgent and happens with LWP::Simple too. In both cases according to strace it gets hung up in a futex(). I'm struggling to replicate with bare IO::Socket::INET code though. |
From @jonathanstoweAnd the reason that it couldn't be replicated in IO::Socket::INET code is that it isn't the socket apparently: <ollej> I'm having an issue when using the URI module inside a Promise. Unless I've used the URI module before awaiting the result, the program never finishes. Using rakudo 2015.09. Which can be reduced to: use URI; await start { say URI.new("http://localhost") }; So IO::Socket::INET is off the hook. On Mon Oct 19 14:41:59 2015, jns+bc@gellyfish.co.uk wrote:
|
From @jonathanstoweInfact: <llfourn> perl6 -MIETF::RFC_Grammar::URI -e "await Promise.in(1).then({ require IETF::RFC_Grammar::URI });" will hang On Wed Oct 21 03:33:33 2015, jns+bc@gellyfish.co.uk wrote:
|
From @zoffixznetTo give an update on this. With Rakudo built on Dec 30, 2015, I no longer get any hangs with neither nor perl6 -MIETF::RFC_Grammar::URI -e "await Promise.in(1).then({ require IETF::RFC_Grammar::URI });" This is on Debian Wheezy. I tried both on 32bit 2-core and 64bit 1-core boxes. |
From @dogbert17On Wed, 30 Dec 2015 09:12:25 -0800, cpan@zoffix.com wrote:
This problem has been fixed. Part of the problem seems to have been the |
@dogbert17 - Status changed from 'open' to 'resolved' |
From @AlexDanielFWIW it's not possible to reproduce the issue on older rakudos because it was sweeped under the rug in the URI module itself: raku-community-modules/URI#21 So yes, #126587 is a “testneeded” ticket for the underlying issue. On 2018-03-09 12:58:27, jan-olof.hendig@bredband.net wrote:
|
Migrated from rt.perl.org#126390 (status was 'resolved')
Searchable as RT126390$
The text was updated successfully, but these errors were encountered: