Bug feedback
Author: ethands, Created: 2018-07-08 13:36:54, Updated: 2018-07-08 17:37:50The bot can't stop after the host goes offline, indicating that the node specified by this bot has gone offline. If you need to restart, please re-specify and update the parameters You can't update the parameters at this time, prompt Failed to update parameters, please confirm the bot is in standby mode! It's impossible to delete the bot while the billing and script are still running and can't be stopped.
This happens after the public server is not available.
- Small white questions in the python version of the live digital currency trading library
- GetTicker: 400: {"code": 2, "data": {}, "message": "invalid params"}
- After the configuration is complete, the Control Center - > Robot - > Debugging Tool, after running, the alarm as follows, please ask how to solve.
- Can we divide the quantity of transactions in the coin circle into the following 9 types?
- The first test bot, using the default code, only had a getaccount function that told me not to log in.
- Inventors Quantify (FMZ.COM) Compatibility update for the new signing mechanism for the Bitcoin API interface
- ZBG is also starting to mine.
- Recheck can output logs, but the hard disk has no log output, see the following error, what could be the reason?
- Getaqccount function in fcoin reported an error
- Bigone's API is there a problem, why hasn't it been working, online etc!!!!!
- Exchange CoinBig General Protocol Supported by plugins
- You can solve the logging problem in time.
- Problems with customized multi-user quantified platforms
- Top-One General Protocol Python version two
- Fcoin market price trading is problematic
- Kneeling down to a drawing-line template for drawing multiple page breaks
- Getticker function error in coinex
- Allcoin General Protocol Plugin to start mining on July 6th
- What is the role of setting exchange.SetTimeout ((3000) at the beginning of the policy?
- Can you access CoinEX's API, why am I showing errors?
ZeroStop trying again, and we'll follow up on Monday.
The Little DreamThe bot should have been deployed on the public server, then the public server may have restarted or stopped, causing the problem. Thanks for the suggestions and questions, we'll take care of it, if there are still problems, trouble contact the QQ group.
Lightning quantifiedOn top of that, I've also encountered this situation, deleting the host, which causes the bot to stop. Trying to find customer service. https://dn-filebox.qbox.me/5664563e13fd5c04a60bffb9ab0996a6e951bbd3.png
The Little DreamThe QQ group is full, for now, and you can telegram: https://t.me/fmzquant_cn
ethandsIt is now possible to stop it. Let it be temporary. Monday is said.
Lightning quantifiedYes, there is a bug in the process here, and when the host is removed, the associated bot should be stopped and removed.
Lightning quantifiedI am a bot that runs on a public server in the United States, using my own computer as a host. Later, I deployed my own server overseas and removed the host, while the bot that was originally associated with it could not be removed. How many QQ groups?
ethandsThere is also the friend below who is acting as if he is his own host. This is already a bug in the process, the host should regularly confirm the state of the robot when executing the script, the robot should be able to stop or delete it directly if the host is not available, and the host should stop executing the script if it detects that the robot has been stopped or deleted. Please restore the host first, I'll switch to my own host and then try to fix this problem. The costs and losses incurred in this regard should be considered to be compensated in an appropriate manner, at least in one way. The costs are not stopped during this period, and the unanticipated quantified results result from the inability to stop the strategy.