Bug Reporting

All posts which do not fit into any other sections of the forum.

Moderator: admin

Re: Bug Reporting

Postby Apprentice » Sat Dec 24, 2016 5:58 am

Can you provide a screenshot.
User avatar
Apprentice
FXCodeBase: Confirmed User
 
Posts: 36341
Joined: Thu Dec 31, 2009 11:59 am
Location: Zagreb, Croatia

Re: Bug Reporting

Postby chinabuaawd » Mon Mar 06, 2017 10:43 am

We are running 20 strategies on the same time in TS2.
And we meet problem on closing the positions on CFD products like: XAUUSD, US30, BUND,etc.
It always report error while closing a CFD position in TS2.

“Open order failedThe Quantity must be a positive integer number.”
with no message from the server, it seems that the TS2 reads a false position information locally on CFD products.

While it has no problem for several years with strategies less than 19 or 18 running in the same time.
The other cause of the problem could be the position with BUND which is an new strategy that added to the potfolio makes the TS confused.

While every strategy runs alone are working quite fine.

Does anybody has any idea about this issue?
chinabuaawd
 
Posts: 20
Joined: Wed May 07, 2014 10:32 am

Re: Bug Reporting

Postby Apprentice » Sat Mar 25, 2017 8:37 am

Can you provide strategy web references
it is quite possible, strategys have bugs.
User avatar
Apprentice
FXCodeBase: Confirmed User
 
Posts: 36341
Joined: Thu Dec 31, 2009 11:59 am
Location: Zagreb, Croatia

Re: Bug Reporting

Postby robocod » Fri Apr 07, 2017 7:06 am

I have a custom strategy, which in some scenarios can close an existing trade and open in the reverse direction. For example, close an existing long and open a short.

The close is using market close using "netting" order (i.e. NetQtyFlag="Y"). It is for a FIFO account.

In some case, the new trade (i.e. the one after the close) fails to open. I get the following error:

"The account is locked. Trading is not available."

I have no idea what causes this. The strategy seems to recover from this, and later trades work again.

The strategy works ok on back-tester. Could the use of netting order to close all positions somehow prevent the new open order for working?

PS: Searching around, I also found this error reported with a couple of other strategies (here and here). Seems to always be an issue when closing using "netting" order, and immediately entering new trade.
User avatar
robocod
FXCodeBase: Graduate
 
Posts: 298
Joined: Thu May 10, 2012 4:25 pm

Re: Bug Reporting

Postby ainelle » Mon Apr 10, 2017 1:51 pm

Hi,

It seems there is a timing synchronization problem between history and live candles.
I explain :
If I ask for the date of the last closed daily candle, the answer is : yesterday at 23h (I live in France) and this is normal.
But If I keep asking the same question during the day, the answer will be updated at 17h00 instead of 23h00.

The same problem happen with the timing of H8 candles which is 23h00/7h00/15h00 in the history, but 1h00/9h00/17h00 in live

The same problem happen with the timing of H4 candles which is 23h00/3h00/7h00/11h00/15h00/19h00 in history, but 1h00/5h00/9h00/13h00/17h00/21h00.

Regards,
Ainelle
ainelle
 
Posts: 24
Joined: Wed Feb 05, 2014 1:59 pm

Re: Bug Reporting

Postby Marcello » Tue Apr 11, 2017 12:07 pm

Please check how math.floor gives two different results for the same value when passed as a constant and when is passed as an expression ( see attached image)
Attachments
floor.PNG
Marcello
 
Posts: 20
Joined: Mon Jul 25, 2016 4:09 pm

Re: Bug Reporting

Postby Marcello » Tue Apr 11, 2017 6:47 pm

And more ...

Marcello wrote:Please check how math.floor gives two different results for the same value when passed as a constant and when is passed as an expression ( see attached image)
Attachments
remain operator.PNG
Marcello
 
Posts: 20
Joined: Mon Jul 25, 2016 4:09 pm

Re: Bug Reporting

Postby ainelle » Wed Aug 16, 2017 5:03 am

Is there anyone reading this topic anymore ?
ainelle
 
Posts: 24
Joined: Wed Feb 05, 2014 1:59 pm

Re: Bug Reporting

Postby Konstantin.Toporov » Wed Aug 16, 2017 1:07 pm

I was unable to reproduce these errors.
Which version of Indicore SDK are you using?
Were any specific setting applied?
Konstantin.Toporov
FXCodeBase: Initiate
 
Posts: 113
Joined: Mon Aug 31, 2015 10:16 am

Re: Bug Reporting

Postby ainelle » Wed Aug 16, 2017 1:55 pm

Konstantin.Toporov wrote:I was unable to reproduce these errors.
Which version of Indicore SDK are you using?
Were any specific setting applied?

who are you talking to ?
ainelle
 
Posts: 24
Joined: Wed Feb 05, 2014 1:59 pm

PreviousNext

Return to General Discussions

Who is online

Users browsing this forum: No registered users and 5 guests