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
IO::Socket::Async sometimes gives "bindexpayload needs a VMExceptio" #5790
Comments
From @zoffixznetI can only reproduce it on camelia and the issue happens when m: await On other boxes, the code either succeeds, gives "unable to resolve IRC conversation: https://irclog.perlgeek.de/perl6/2016-11-09#i_13539836 P.S: timotimo just pushed a commit to MoarVM to give extra debug info |
From @jnthnOn Wed, 09 Nov 2016 08:51:08 -0800, cpan@zoffix.com wrote:
Golfed it all the way down to: my $p = Promise.new; And fixed it, and added a test in S17-promise/basic.t. Seems it was a regression when I improved error reporting for Promises a while ago to present the backtraces of both the original error and the one where the result of the Promise was acquired. To do that I used rethrow, but that got upset and spewed an internal error (the one seen here) if given an exception that was never previously thrown. Now it just copes. /jnthn |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130064 (status was 'resolved')
Searchable as RT130064$
The text was updated successfully, but these errors were encountered: