Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Backend timeout looks like a request timeout

See original GitHub issue

The timeout defined in the backend section seems to be a timeout for the entire request. If I configure it lower than the time required to get the full response, but fast enough to get the template from the backend I get errors like:

Timeout exceeded, failed to respond in 100ms. Failed Fragment: http://XXX/account/

The fragment timeout however is set much higher in the template:

<div cx-url="{{server:status}}/account/" cx-timeout="4s">
</div>

Issue Analytics

State:
Created 7 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

cliftonccommented, Jun 20, 2016

Thanks, merged and published today.

1reaction

cliftonccommented, Jun 14, 2016

From memory it was a safety net, a way to ensure it never got stuck or took too long (which under load would stack requests up and take the whole thing down).

It may be better to have the backend timeout be for the request to the backend, and perhaps add an optional parserTimeout that could be added if you wanted the larger timeout to be enabled?