After updating to 2.0.0 (reinstall), I am getting error saying Error: ETIMEDOUT or ESOCKETTIMEDOUT #237
Comments
|
Something on your system or network is blocking. Can you post your full log please? |
|
maybe i have the same problem . 2016-12-22T19:09:20.023Z - warn: ExternalError: Probuilds failed to parse KDA for vladimir the programm arrive at 20 % and next stop |
|
|
@foodtooth @T9090 I have a theory. If you were to select one source at a time and import each individually, would they all import successfully? |
|
@dustinblackman Thanks for your reply, it works! I tried to select source one by one and check "Download ARAM item sets" to download two sources at a time and it works. (Only failed with the same error when I selected probuilds, but it worked when I tried again.) So I tried again with all of the sources without probuilds, but still failed with the same error. |
|
I have a feeling something on your systems is setting max connections per application. When using multiple sources, there's a large number of requests being made at the same time. I'll add queuing to limit the number of requests being made in hopes to solve this. @foodtooth @T9090 @Brelvor If willing, would you mind testing a build to see if it fixes your issue? |
|
@dustinblackman Sure, I would love to help. |
|
@dustinblackman just sent the build , i would gladly help. |
|
I got same error on app but I think it was different in log, probuilds failed to send data for garen so I had to remove probuilds for it to work |
|
@foodtooth @Brelvor @ninjay997 Sorry for the delay guys. Here's a test build that has Championify limited to making 10 requests at time. Try adding all the sources, and let me know if you end up with connection errors. If not, I'll add it to my next release. Thanks again for helping with testing. http://www62.zippyshare.com/v/XTo5dGky/file.html |
|
FWIW I'm seeing this error myself on my Mac running v2.0.1. But only if I include op.gg as a source. It doesn't matter how many/few other sources I have. It's worked in the past, but not today, and I am wondering if perhaps op.gg is down. Anyway it's a different issue than you're chasing with the 10 requests limit. My main feedback here is to make the error reporting a little better, like showing which source gave the error. The logfile is misleading; a naive user would look at this report below and blame champion.gg |
|
@NelsonMinar Fair point, that should have better error handling. I'll include it with the queue fix. Thanks. |
|
I am also now seeing this error, I played last night without any issue, something has changed, I am doing nothing different. |
|
I'm getting this error but I suspect it was due to op.gg stuck on Win 10 x64, v2.0.1 |
|
You sir are correct, removing that made it finish. Is there anyway to check them before trying to download each one, and skip if they fail the check? But continue with those that do not? |
|
Getting this now, too. Looks like bad error handling \ retry logic for when one of the pool's connections times out. |
|
I'm sorry that I had no chance to checkout github during Chinese New Year and failed to run the test build. Thanks for the new release! |
The error comes out when items are being downloaded, or even when I was in the main frame doing nothing.
Here is example of the error log while the downloading was in progress:
error: Error: ESOCKETTIMEDOUT at ClientRequest.<anonymous> (C:\Users\micha\AppData\Local\Championify\app-2.0.0\resources\app.asar\node_modules\request\request.js:779:19) at ClientRequest.g (events.js:286:16) at emitNone (events.js:86:13) at ClientRequest.emit (events.js:185:7) at Socket.emitTimeout (_http_client.js:614:10) at Socket.g (events.js:286:16) at emitNone (events.js:86:13) at Socket.emit (events.js:185:7) at Socket._onTimeout (net.js:334:8) at tryOnTimeout (timers.js:232:11) at Timer.listOnTimeout (timers.js:202:5)Anyone can help me?
The text was updated successfully, but these errors were encountered: