You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Opening ticket for tracking:
When running a test for a couple of days or even less, there are scenarios that the CSV file is suddenly split into multiple files which sometimes causes an issue displaying the history performance when run in verbose mode. So far I've seen this occur on Binance, and Gate_io
Steps To Reproduce
Here are the steps to reproduce the issue (see attachments in the section below):
Create any market making strategy using Binance or Gate_io connector
Start the strategy and leave it running for a long duration
Regularly check your test bot by running history --verbose
Check the data file folder if an error occurs when the history --verbose command is run.
Note: replicating the behavior is difficult to do so, I tried several steps such as:
Interrupt the bot after a fill event, was able to create another CSV file but happened once only and unable to do it again even if I repeat the same method.
Interrupting the network when a filled event happen
Change configuration such as changing the markets after getting a fill
I will update add more details if in case I get to capture the issue again. Screenshots
Release version
0.46.0
Attachments
WARNING: Do NOT publish any exchange API keys or your wallet's private key. Whoever has access to them may steal your assets!
Optional: your discord username:
The text was updated successfully, but these errors were encountered:
Describe the bug
Opening ticket for tracking:
When running a test for a couple of days or even less, there are scenarios that the CSV file is suddenly split into multiple files which sometimes causes an issue displaying the history performance when run in verbose mode. So far I've seen this occur on Binance, and Gate_io
Steps To Reproduce
Here are the steps to reproduce the issue (see attachments in the section below):
Note: replicating the behavior is difficult to do so, I tried several steps such as:
I will update add more details if in case I get to capture the issue again.
Screenshots
Release version
0.46.0
Attachments
WARNING: Do NOT publish any exchange API keys or your wallet's private key. Whoever has access to them may steal your assets!
Optional: your discord username:
The text was updated successfully, but these errors were encountered: