Closed (cannot reproduce)
Project:
HTTP Parallel Request & Threading Library
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Feb 2012 at 15:54 UTC
Updated:
3 Apr 2012 at 18:34 UTC
Comments
Comment #1
hass commentedAlso found one options array with
timeout (Float) -0.39116Comment #2
hass commentedtimeout (Float) 28.49453
Comment #3
hass commentedAre you using it to count down to 0? But it still starts at the defined values? So if the value is 28.49453, this means the request took 60s - 28.49453s = 31,50547s? Sounds very long. Running the request alone with wget takes less than 1 second.
Comment #4
hass commentedChecking
http://www.jugendarbeit.gmxhome.degives me in WGET aConnection refusedwithin a second. HTTPRL gives a timeout. hmmm... core is also inconsistent with wget. This suxxx. I'm loosing trust in PHP errors...It looks like HTTPL gives always a timeout if it does not understand the answer!?
Comment #5
mikeytown2 commentedI use the timeout as a count down to zero. Once it's below zero, I close that stream and set the timeout error.
http://drupalcode.org/project/httprl.git/blob/3fc823af93923ff4fa9a9938c4...
Let me know what you're expecting. Some of the inconsistencies where recently fixed in #1446662: stream_select timings
Comment #6
hass commentedYeah, I expected this, but If I shoot 8 requests and 6 of them have a value of 28.88858 than something in the logic must be wrong, isn't it?
It's unrealistic that different hosts and URLs have all the same time up to 5 digits after the comma.
Comment #7
mikeytown2 commentedI compute the time at the start of the loop. It is possible.
Comment #8
hass commentedI thought the async is a background job and you loop over it ever 25ms. In this case; if a request returns it get the current remaining timeout? It's not realistic in this case that no other request returned while looping for about 30s. Additionally the servers returned an error in less than a second. This meens the timeout value should be +/- 59s.
Comment #9
mikeytown2 commentedSee if you can repo this now that #1446662: stream_select timings has been committed.
Comment #10
mikeytown2 commentedAny news on this, is this fixed?
Comment #11
hass commentedSorry, no time. :-(
Comment #12
mikeytown2 commentedGoing to close this. Can re-open if new info bubbles up.
Comment #12.0
mikeytown2 commentedA