Invalid JSON Structure in bots/data/account_state_history.json (e.g "End of file expected.json")

[sultanmyrza]

Describe the bug

Description

The account_state_history.json file generated in the bots/data directory lacks a parent key to wrap the data, resulting in an invalid JSON structure. This issue might prevent seamless parsing and usage of the file in downstream processes that expect valid JSON formatting.

While this issue doesn't affect core functionality, fixing it might improve the file's compatibility with other tools and future integrations.

Below is an example of the current output:

{"timestamp": "2024-12-28T07:01:24.573523", "state": {"master_account": {"binance": [...omitted for brevity...]}}}
{"timestamp": "2024-12-28T07:01:24.574862", "state": {"master_account": {"binance": [...omitted for brevity...]}}}
{"timestamp": "2024-12-28T07:01:24.575405", "state": {"master_account": {"binance": [...omitted for brevity...]}}}

Expected Behavior

The JSON file could follow standard formatting by wrapping the data in a parent key (e.g., account_history, snapshots, or data):

{
  "account_history": [
    {"timestamp": "2024-12-28T07:01:24.573523", "state": {"master_account": {"binance": [...omitted for brevity...]}}},
    {"timestamp": "2024-12-28T07:01:24.574862", "state": {"master_account": {"binance": [...omitted for brevity...]}}},
    {"timestamp": "2024-12-28T07:01:24.575405", "state": {"master_account": {"binance": [...omitted for brevity...]}}},
  ]
}

Environment

• Hummingbot Dashboard Version: [v2.1.0]
• Operating System: [macOS 15.1]

Additional Notes

While the data content in account_state_history.json is correct, the JSON structure itself is not valid JSON. This issue could be addressed to ensure better interoperability with other tools and systems that expect standard JSON formatting. This is not a critical bug and does not impact core functionality.

Steps to reproduce bug

Steps to Reproduce

1. Configure Binance credentials by entering API key and secret at http://localhost:8501/Credentials
2. Wait for the system to generate the account_state_history.json file in the bots/data directory
3. Open the generated file
4. Notice that each JSON object is written as a separate line without a parent key or array structure, resulting in invalid JSON formatting