gehtsoft / forex-connect Goto Github PK

I am experience an issue with using two (or more) Python scripts connecting to the same trading account. This is not happening for practice accounts. The api fails when I launch a second script as soon as I connect to fxconnect using the same account (run fxcm.login(...)).

My Python version is 3.6.8, I'm on Ubuntu 18.04.2 LTS. I have tried different releases of forecxonnect (1.6.3 and 1.6.0).

On 1.6.3 and 1.6.2:
When I run one script connected to fxcm and launch a second one, the first one fails with the error 'terminate called without an active exception'.
On 1.6.0:
When I run one script connected to fxcm and launch a second one, the second one works and the first one just hangs without any error messages. If I try to cancel it by pressing Ctrl+C, nothing happens. If I launch the first one again in new terminal, it works (but this is still a problem because I need the first one running). So, evey time I launch a new script, the running one fails.

Hi,
I think the TableListener C code has a timestamp bug, because the timestamp for each update is not set to milliseconds, only showing the seconds.

For example I currently get the following timestamps.
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43
2019-06-24 19:13:43

Should be something like this.
2019-06-24 19:13:43.022
2019-06-24 19:13:43.053
2019-06-24 19:13:43.068
2019-06-24 19:13:43.070

This is a fairly critical bug because there is no way to eliminate 'out of order' ticks/updates, would appreciate if someone could look into it ASAP.

Cheers

James

Android samples present in this repo are outdated.

The last version available seems to be here : http://www.fxcodebase.com/wiki/index.php/Download in the 1.6 file : ForexConnectAPI-1.6-Android.tar.gz

Also, regarding these samples in ForexConnectAPI-1.6-Android.tar.gz :

• The FXTSMobile sample crash on wrong password input

• The GetReport sample don't

Can you please explain what cause the crash ? I can't find a way to correct it in FXTSMobile sample

Thanks !

I get this error when trying to install:
ERROR: Could not find a version that satisfies the requirement forexconnect
ERROR: No matching distribution found for forexconnect

Win10
Python 3.9.12
pip 23.3.1

Hi,

I am using forexconnect in python to do trading with a demo account. I am able to trade on tradingview but not with the api. An example was at 08:44gmt (on thursday) where I was able to open a position on trading view on CORNF but not with python. I was able to do that on a previous demo account (2 weeks ago) but not on the new one I am working with.

Do you have any idea why?

Many thanks

Hi everyone,

Is there a way to know the opening and the closing time of an instrument with forex-connect?

Many thanks

pip install forexconnect
ERROR: Could not find a version that satisfies the requirement forexconnect (from versions: none)
ERROR: No matching distribution found for forexconnect

I was reading your sample code for your build live history and was wondering how do you build it for different time frames? Like if I wanted it for 4 hours. and as well, how do you add the live history to a dataframe?

SessionStatusListener.py, ResponseListener.py and TableManagerListener.py all have a hard-coded wait(30) in them. Under various circumstances, that wait can be exceeded. In such a case, the system can segfault and core-dump.

There are a number of issues here:

• The end user is not given the option to set their own timeout for this value. This should be a parameter exposed in the constructor or other area that allows the user to set the value.
• The segfault is not handled by the code in question.
• Ideally, the error would be captured and sent back to the end user as an actionable message.

What should happen is:
Timeout -> 'Tablemanager timeout awaiting [possibly 5he callstack]. Waited ** seconds without response'
Now the client should be able to take that information and, increase the allowed timeout via the configurable value, re-evaluate the code their using to see if there is an issue, or reach out to FXCM to investigate issues with slow processing (in the case of things like orders).