Using the okx futures simulation retest, call the interface to return ERR_INVALID_POSITION, please is this a bug?
Author: stargazer, Created: 2018-03-28 16:30:23, Updated:
The image above is the code and log and retrieve configuration parameters
- New Deribit futures exchange support and use cases
- System error: The GetMinStock function has failed
- BitMex Exchange.IO is not authorized
- Please provide the official interface of liqui and bibox exchanges
- Problems with setting parameters for SAR indicators
- How does the platform protect the security of policies written by individual developers?
- Uncaught RangeError: Array buffer allocation failed
- Why not offer USDT as a base currency for retesting transactions?
- The indicator in the feedback chart is automatically detecting a malfunction, please tell me what is going on.
- Why is there an error in the order and no error code?
- Please retest the error log box2018-03-27 19:59:50 Bitfinex error ERR_INSUFFICIENT_ASSET What does it mean and how to fix it
- OKEX cannot connect
- Data problems with retesting
- The inventors quantified the two days of performance decline?
- Timestamp seems to have been tampered with after the proxy was hung.
- What is the code if it's a coin transaction?
- Requests for synthesis Inventor quantification Code; have an idea
- How is it that Bitmex's entire stock is switched to individual stock through the API?
- Okcoin's international cyclic settings and the cyclic settings in the code are inconsistent based on what?
- I would like to know how to optimize the latency of the exchange.
stargazerI'm still having trouble with the simulation test, but the list that was hanging out couldn't be completed, is there a solution?
stargazerI'm still having trouble with the simulation test, but the list that was hanging out couldn't be completed, is there a solution?
stargazerOkay, I see, thank you, how long is it usually possible to do a transaction when the simulation is retrieved, and also ask for the return status, the type of the returned digit corresponds to what state, and it's different from the one in the API documentation.
Inventors quantify - small dreamsThe order is pending and not transacted, holding for [], i.e. no holding, and then going to the position, resulting in error: ERR_INVALID_POSITION i.e.: no holding, resulting in the position error.
stargazerThis is a list of all the different ways Dn-filebox.qbox.me/6c88fd7113224078ff40953c144a53cb18d9ca3c.jpg is credited in the database. I'm trying to get the botvs to return the order, but it's not working on OKEX.
stargazerThe futures I use for OKEX, they're based on the number of coins, not the number of contracts, how do you convert between that?
Inventors quantify - small dreamsOKEX Futures The following order quantities are all contracts, and are whole numbers.
stargazerThere is a problem again when I was hanging the list here https://dn-filebox.qbox.me/b1370f52e72b9133f45ef797cc185f6e40a5756a.png
stargazerOkay, I'll give it a shot.
Inventors quantify - small dreamsCancellation and renewal The price is unfavorable, and the transaction may be pending for a long time. At this time, you can only withdraw the order, re-pricing or wait.
stargazerI'm still having trouble with the simulation test, but the list that was hanging out couldn't be completed, is there a solution?
stargazerGood, thank you.
Inventors quantify - small dreamsThis is the location of the API documentation. This is a list of all the different ways Dn-filebox.qbox.me/666db1568c0aa524c2537b046cac597e45748793.png is credited in the database.
stargazerThis is a list of all the different ways Dn-filebox.qbox.me/7bb37ce50423b99ca7170e0753693a5deb21bc68.jpg is credited in the database. I'm also going to do an analogous retrieval, which is I'm going to hang a list, and I need a real user to eat the list, right?
Inventors quantify - small dreamsTo see where the market is headed, the status type of these has a constant value in the API documentation.
stargazerOkay, I see, thank you, how long is it usually possible to do a transaction when the simulation is retrieved, and also ask for the return status, the type of the returned digit corresponds to what state, and it's different from the one in the API documentation.