I ran a test and very many links have a timeout of 28.88858 defined, but it should default to 60s.

Comments

hass’s picture

Also found one options array with timeout (Float) -0.39116

hass’s picture

timeout (Float) 28.49453

hass’s picture

Are 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.

hass’s picture

Checking http://www.jugendarbeit.gmxhome.de gives me in WGET a Connection refused within 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!?

mikeytown2’s picture

Status: Active » Postponed (maintainer needs more info)

I 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

hass’s picture

Yeah, 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.

mikeytown2’s picture

I compute the time at the start of the loop. It is possible.

hass’s picture

I 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.

mikeytown2’s picture

See if you can repo this now that #1446662: stream_select timings has been committed.

mikeytown2’s picture

Any news on this, is this fixed?

hass’s picture

Sorry, no time. :-(

mikeytown2’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Going to close this. Can re-open if new info bubbles up.

mikeytown2’s picture

Issue summary: View changes

A