Fix request timeout handling #8
Comments
sounds correct. |
It is not really a timeout. Actually it works fine when it's a timeout (according to the rdflib code I see) See this issue I opened |
It's worth trying to patch that, and send the patch in with your bug report ( if you can ). Because there are not a lot of resources on that there. |
the rdflib code is a bit hard to correct. I've added a Q timeout to the promise. It works nicely but I don't know why it seems the React rendering of PersonContactOnProfileJumpWrapper does not trigger the underlying PersonContactOnProfile component (shouldComponentUpdate is not even called :s) |
Finally this seems more related to this issue: |
I see that these issues related to timeouts are still open. Am I right to assume that they are unresolved? I think I may have hit the problem - my application just hangs after attempting to fetch a URI that involves 303 redirection, via my own proxy (although I am manually changing the URI, rather than using the Fetcher's proxy handling capabilities). My proxy is almost certainly flakey (being very new), but having the application hang is a real problem. |
Hi, I have moved to work on the react based viewers written in ScalaJS. You may want to try that https://github.com/read-write-web/rww-scala-js . I am about to rewrite the server though, so it will be a bit of time before I get back to the client. |
When using a proxy, the proxy always respond within 10 sec, potentially with an error.
This is because there's a timeout set inside the proxy fetcher.
When not using a proxy, the jumping promise may stay unresolved. It there's no answer in 10 seconds I think the promise should be automatically rejected
The text was updated successfully, but these errors were encountered: