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
require inside thread segfault hang #4737
Comments
From @LLFournTwo async + require bugs. Replace LWP::Simple with whatever you like 1. segfault Thread.start({ say "entering"; require LWP::Simple; say "leaving" }) 2. HTTP::Server::Tiny hangs use HTTP::Server::Tiny; HTTP::Server::Tiny.new(port => 8080).run: sub ($env) { # then curl localhost:8080, you'll only get "requiring!". This is perl6 version 2015.10-220-g4988c70 built on MoarVM version Mac OSX |
From @jonathanstoweThis may be related to the https://rt-archive.perl.org/perl6/Ticket/Display.html?id=126390 On Sun Nov 08 01:11:45 2015, lloyd.fourn@gmail.com wrote:
|
From @LLFourn#1 require inside thread now gives: perl6 -e 'Thread.start({ say "entering"; require Linenoise; say "leaving" On Sun, Nov 8, 2015 at 8:11 PM perl6 via RT <perl6-bugs-followup@perl.org>
|
From @AlexDanieldogbert++ noticed me that this issue is resolved (according to the provided snippets). It is indeed so. Second snippet may need this change: -return 200, ['Content-Type' => 'text/plain'], 'we win'; I can confirm that both issues are not reproducible using recent-ish rakudo, but I can't tell when these problems were fixed. The first problem is not really reproducible on any rakudo, even the one mentioned in the OP (huh??). Also, there's some problem using HTTP::Server::Tiny on pre 2015.12 rakudos (“Supplier” did not exist back then?). Anyway, marking as 「testneeded」. If anybody wants to find what commit affected these snippets, I'm pretty sure you'll have to bisect it manually without a bot. On 2015-11-08 01:11:45, lloyd.fourn@gmail.com wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielWell, bisectable just told me that maybe I should mention at least one of the suspected commits. (2016-05-12) rakudo/rakudo@2511398 Output before and after that commit: https://gist.github.com/8e47787d7d7c7e6cf1ee7161740a999d Basically, the behavior changed more than once and it's just a pain to decipher what happened. On 2018-03-09 09:12:32, alex.jakimenko@gmail.com wrote:
|
Migrated from rt.perl.org#126587 (status was 'open')
Searchable as RT126587$
The text was updated successfully, but these errors were encountered: