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
Some bug with a combination of $*KERNEL.hardware, slurp, run and Cro #1595
Comments
:( |
|
FWIW Please contact me if ssh access to the machine where this happens is needed. (I can reproduce on whateverable server and on my laptop, both using Cro 0.7.3 and HEAD-ish rakudo) |
|
What browser are you using? I can't repro under normal use on 2018.01—refreshing all I want and it works. However, if I load a page in Firefox and then try to load it in Chrome, it "hangs". Also hangs if I try to do it vice-versa (load in Chrome and then in FF). Also hangs on second connection if I telnet to it: Also hangs on second use with So sounds like Cro is not happy if it's not getting something it got during previous request. Here's a LiveHTTPHeaders capture of the request from Firefox from refreshing the page (where it works without hangs). If I replay this via telnet, I get no hang, so just need to golf this to figure out which piece makes it not hang: |
Well, one golf I got it simply the HTTP version; but do browsers even try HTTP/1.0 that it'd get a hang? Probably not the main reason. No hang with Hang: ( |
Nope, here's a WireShark dump of a packet that never gets a response to: |
|
Oh! I know what I'm doing differently! I'm hitting |
|
Curious that it requires the |
|
That said, that headers have an impact makes me wonder if it could somehow be a Cro thing, but then the |
|
This is still an issue, (still reproducible with the snippet in the OP) |
|
|
Both changes are a workaround for rakudo/rakudo#1595. This commit should be reverted later.
Both changes are a workaround for rakudo/rakudo#1595. This commit should be reverted later.
OK here's the golf:
Run it like this:
Now go to http://localhost:10001/, the page will open just fine. You'll see “Hello!” and in the terminal you'll see this:
Refresh the page (EDIT: press Ctrl+F5 instead of just F5), and you'll not get a response again (you'll be waiting until it times out). No output in the terminal, nothing.
The text was updated successfully, but these errors were encountered: