Skip to content
This repository has been archived by the owner on Nov 26, 2022. It is now read-only.

WARNING: CCXT: unable to create order poloniex / STEEM/ETH: poloniex POST https://poloniex.com/tradingApi HTTPSConnectionPool(host='poloniex.com', port=443): Read timed out. (read timeout=10) #315

Closed
trungtv opened this issue Apr 27, 2018 · 3 comments

Comments

@trungtv
Copy link

trungtv commented Apr 27, 2018

Dear Catalyst Maintainers,

Before I tell you about my issue, let me describe my environment:

Environment

  • Operating System: (Windows Version or $ uname --all)
    Darwin -Pro.local 17.5.0 Darwin Kernel Version 17.5.0: Mon Mar 5 22:24:32 PST 2018; root:xnu-4570.51.1~1/RELEASE_X86_64 x86_64

  • Python Version: $ python --version
    Python 3.6.3 :: Anaconda custom (64-bit)

  • Python Bitness: $ python -c 'import math, sys;print(int(math.log(sys.maxsize + 1, 2) + 1))'
    64

  • How did you install Catalyst: (pip, conda, or other (please explain))
    pip

  • Python packages: $ pip freeze or $ conda list

Now that you know a little about me, let me tell you about the issue I am
having:

Description of Issue

My algo created an order to sell some on poloniex. Due to read timeout, the order get to be executed twice. Which is the best way to configure ccxt timeout in Catalyst?

WARNING: CCXT: unable to create order poloniex / STEEM/ETH: poloniex POST https://poloniex.com/tradingApi HTTPSConnectionPool(host='poloniex.com', port=443): Read timed out. (read timeout=10)
[2018-04-27 02:54:38.126355] WARNING: exchange_blotter: Ordering again.

Sincerely,
$ whoami

@lenak25
Copy link
Contributor

lenak25 commented Apr 29, 2018

Hi @trungtv ,

Thanks for catching this, there isn't a simple way to set the timeout, we are working to solve this by handling the timeout exception properly.

Lena

@AvishaiW
Copy link
Contributor

AvishaiW commented May 1, 2018

Hi, I added a code that is suppose to fix such exceptions and which should avoid duplicate orders to the develop branch. tests are still needed in order to make sure it works properly, once they are done, we will release this.

@lenak25
Copy link
Contributor

lenak25 commented May 9, 2018

Fixed at release 0.5.10.

@lenak25 lenak25 closed this as completed May 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants