seat
seat copied to clipboard
How to increase the task timeout time?
When the data is large, always occurs ↓
GuzzleHttp\Exception\ConnectException: cURL error 28: Operation timed out after 30000 milliseconds with 282839 out of 452724 bytes received (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) in /var/www/seat/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:185
Operation timed out after 30000 milliseconds with 282839 out of 452724 bytes received
seems that 30 seconds is not enough to download the data.......
How to modify this 30 seconds?
Looking forward to your answer! o7
Plus: This happens a lot.
It's all because of 'timed out'.
Operation timed out after 30000 milliseconds with 466955 out of 541659 bytes received
Operation timed out after 30000 milliseconds with 282839 out of 542085 bytes received
Operation timed out after 30000 milliseconds with 460015 out of 541659 bytes received
......
Hi @KinomotoKi,
What's your bandwidth? Out of this, you can submit a pr to eseye repo, but 30sec to download 500ko is generally enough 😕
Hi @warlof ,
500Mbps downlink bandwidth. But in Asia, our connection to the UK seems to be slow.
Can I modify some settings on the local server to make it run time longer? I don't quite understand 'submit a pr to eseye repo'......
Do you mean to consult again on this page? → https://github.com/eveseat/eseye/issues
eseye is hardcoded to stop after 30 seconds. to change that you can make a config setting for it and make a pr to the repo
Hi @rohimma ,
Thank you for your reply, but I am not a professional........ So..... what 'make a pr to the repo' mean? and how to make a config setting for it?
Looking forward to your answer! o7
will see if i can make a pr for you this weekend, as a temp fix you could do this:
- go to the root folder where seat is installed
- go to the next file
vendor/eveseat/eseye/src/Fetchers/GuzzleFetcher.php
- change on line 279 the 30 to a bigger number
@rohimma , Thank you very much for your reply! I'll try it.~o7