IndexError('index 0 is out of bounds for axis 0 with size 0') #793

leohrs · 2023-04-20T20:38:51Z

Trying to run in SHIBBRL market on binance, but I keep getting
"IndexError('index 0 is out of bounds for axis 0 with size 0')" when the bot starts.
happens both on Docker Desktop windows or directly on prompt. Version 8.0.5.
Only tried binance so far.
Also, I only get this message if running on an existing market in which I have sufficient funds and in live mode, meaning:
• if I run in test mode it works.
• If i choose another quote_currency, it'll prompt that I have insufficient funds.
• If i try a non-existing market, it'll give me "non-existing market" message.

my config file:

"binance": {
"api_url": "https://api.binance.com",
"config": {
"autorestart": 1,
"base_currency": "SHIB",
"disablebuynearhigh": 1,
"enableinsufficientfundslogging": 1,
"enabletelegrambotcontrol": 1,
"granularity": "15m",
"live": 1,
"nobuynearhighpcnt": 1,
"nosellmaxpcnt": 3,
"nosellminpcnt": -13,
"quote_currency": "BRL",
"selllowerpcnt": -21,
"telegram": 1,
"trailingbuypcnt": 1,
"trailingstoploss": -1,
"trailingstoplosstrigger": 3,
"disablelog": 0,
"use_sell_fee": 1,
"buypercent": 99,
"termwidth": 180,
"termcolor": 1,
"verbose": 0,
"log": 1,
"debug": 1
},
"api_key_file": "binance.key"
},
"telegram": {
"token": "REMOVED",
"user_id": "REMOVED",
"client_id": "REMOVED",
"datafolder": "",
"logger_level": "DEBUG"
},
"scanner" : {
"atr72_pcnt" : 1.0,
"exitaftersell" : 1,
"enableleverage" : 0,
"use_default_scanner" : 1,
"maxbotcount" : 6,
"exchange_bot_count": 3,
"autoscandelay" : 0,
"enable_buy_next": 1,
"autostart": 0,
"terminal_start_process": ""
}
}

thiazzz · 2023-04-21T12:33:05Z

I have the same. Did you already find a solution?

MirekF · 2023-04-21T12:49:49Z

Hi,same problem with BTC/BUSD Binance21. 4. 2023 v 14:33, thiazzz ***@***.***>: I have the same. Did you already find a solution? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

leohrs · 2023-04-21T13:45:09Z

So far no solution, at least here. It seems that all config is fine, might be something with binance API handling maybe?

leohrs · 2023-04-21T18:13:36Z

update: same config works fine in kucoin

whittlem · 2023-04-21T21:26:26Z

I need to go through verification with Binance again. I stopped using Binance after it said I need to go through verification again. I need to sort this out to be able to troubleshoot this.

FenarkSEC · 2023-04-22T09:00:47Z

I am having the same issue as well, using the Helm chart on a Kubernetes cluster.

thiazzz · 2023-04-22T11:07:38Z

I could provide a temporary API key from a subaccount in Binance for testing? Would that make it easier to investigate and solve?

achillebnt · 2023-04-22T12:24:13Z

Maybe i found the problem: doing some debug i see in line 191 it try to set variable quote_min by index name MIN_NOTIONAL but dataframe doesn't have that index, instead it return this:

0 PRICE_FILTER
1 LOT_SIZE
2 ICEBERG_PARTS
3 MARKET_LOT_SIZE
4 TRAILING_DELTA
5 PERCENT_PRICE_BY_SIDE
6 NOTIONAL
7 MAX_NUM_ORDERS
8 MAX_NUM_ALGO_ORDERS

pycryptobot/models/AppState.py

Line 191 in bff0c33

df[df["filterType"] == "MIN_NOTIONAL"][["minNotional"]].values[0][0]

afgvdp · 2023-04-24T07:35:05Z

Same problem here. If it helps, the "opentrades" bot runs normally, but I am not able to start a bot manually or trough telegram.

I'll share the JSON from the "opentrades" bots, and the "scanner" bots.

This one WORKS:

{
"botcontrol": {
"status": "active",
"manualsell": false,
"manualbuy": false,
"started": "2023-04-23T16:36:32.134203",
"startmethod": "telegram",
"watchdog_ping": "2023-04-24T07:34:01.420447"
},
"preventlosstriggered": false,
"exchange": "binance",
"margin": "-11.2487%",
"delta": "-45.57",
"price": 2.948,
"df_high": " ",
"from_df_high": " ",
"trailingstoplosstriggered": false,
"change_pcnt_high": 0.0,
"indicators": {
"EMA": true,
"BULL": false,
"MACD": true
},
"signal": "WAIT"
}

This one, DOESN'T work:

{
"botcontrol": {
"status": "active",
"manualsell": false,
"manualbuy": false,
"started": "2023-04-23T23:23:48.310596",
"startmethod": "telegram"
},
"preventlosstriggered": false,
"exchange": "binance",
"margin": "",
"delta": "",
"price": 0.0,
"df_high": " ",
"from_df_high": " ",
"trailingstoplosstriggered": false,
"change_pcnt_high": 0.0
}

whittlem · 2023-04-24T18:28:54Z

Maybe i found the problem: doing some debug i see in line 191 it try to set variable quote_min by index name MIN_NOTIONAL but dataframe doesn't have that index, instead it return this:

0 PRICE_FILTER 1 LOT_SIZE 2 ICEBERG_PARTS 3 MARKET_LOT_SIZE 4 TRAILING_DELTA 5 PERCENT_PRICE_BY_SIDE 6 NOTIONAL 7 MAX_NUM_ORDERS 8 MAX_NUM_ALGO_ORDERS

pycryptobot/models/AppState.py

Line 191 in bff0c33

df[df["filterType"] == "MIN_NOTIONAL"][["minNotional"]].values[0][0]

Thanks, I will take a look.

whittlem · 2023-04-24T18:31:06Z

Guys, can you confirm if this is a Telegram issue or a general issue? I used the config at the top and I don't get an error message when I run the bot on that market for live or test modes. If the issue happens just as the bot starts, I don't get it.

Config:

{
  "binance": {
    "api_url": "https://api.binance.com",
    "config": {
      "autorestart": 1,
      "base_currency": "SHIB",
      "disablebuynearhigh": 1,
      "enableinsufficientfundslogging": 1,
      "enabletelegrambotcontrol": 1,
      "granularity": "15m",
      "live": 0,
      "nobuynearhighpcnt": 1,
      "nosellmaxpcnt": 3,
      "nosellminpcnt": -13,
      "quote_currency": "BRL",
      "selllowerpcnt": -21,
      "telegram": 1,
      "trailingbuypcnt": 1,
      "trailingstoploss": -1,
      "trailingstoplosstrigger": 3,
      "disablelog": 0,
      "use_sell_fee": 1,
      "buypercent": 99,
      "termwidth": 180,
      "termcolor": 1,
      "verbose": 0,
      "log": 1,
      "debug": 0
    },
    "api_key_file": "binance.key"
  },
  "telegram": {
    "token": "<removed>",
    "client_id": "<removed>"
  }
}

Running bot like this:
% python3 pycryptobot.py

whittlem · 2023-04-24T18:35:37Z

Maybe i found the problem: doing some debug i see in line 191 it try to set variable quote_min by index name MIN_NOTIONAL but dataframe doesn't have that index, instead it return this:

0 PRICE_FILTER 1 LOT_SIZE 2 ICEBERG_PARTS 3 MARKET_LOT_SIZE 4 TRAILING_DELTA 5 PERCENT_PRICE_BY_SIDE 6 NOTIONAL 7 MAX_NUM_ORDERS 8 MAX_NUM_ALGO_ORDERS

pycryptobot/models/AppState.py

Line 191 in bff0c33

df[df["filterType"] == "MIN_NOTIONAL"][["minNotional"]].values[0][0]

You are right about this... I was able to re-create this with a script.

import sys

sys.path.insert(0, ".")

from controllers.PyCryptoBot import PyCryptoBot  # noqa: E402
from models.TradingAccount import TradingAccount  # noqa: E402
from models.AppState import AppState  # noqa: E402
from models.exchange.binance import AuthAPI as BAuthAPI, PublicAPI as BPublicAPI  # noqa: E402

app = PyCryptoBot(exchange="binance")
account = TradingAccount(app)
state = AppState(app, account)
state.minimum_order_quote()

And returns this:

Traceback (most recent call last):
  File "<removed>/pycryptobot/examples/script-binance_v2.py", line 13, in <module>
    state.minimum_order_quote()
  File "<removed>/pycryptobot/./models/AppState.py", line 191, in minimum_order_quote
    df[df["filterType"] == "MIN_NOTIONAL"][["minNotional"]].values[0][0]
IndexError: index 0 is out of bounds for axis 0 with size 0

Although I'm not getting an error running the bot I can see the error above. I'll fix this and hopefully it fixed it for all of you. Thanks, this helped a lot.

MirekF · 2023-04-24T18:46:49Z

My configuration: (with live:0 it’s OK) { "binance": { "api_url": "https://api.binance.com", "api_key_file": "binance.key", "config" : { "base_currency" : "BTC", "quote_currency" : "BUSD", "live" : 1, "sellatloss" : 0, "sellatresistance" : 0, "trailingstoploss" : -1.5, "trailingstoplosstrigger" : 5, "nosellmaxpcnt" : 3, "nosellminpcnt" : -3, "disablebullonly" : 0, "disablebuynearhigh" : 1, "disablebuymacd" : 0, "disablebuyobv" : 1, "disablebuyelderray" : 0, "disablefailsafefibonaccilow" : 1, "disableprofitbankreversal" : 0, "disabletracker" : 1, "disabletelegram" : 1, "autorestart" : 1, "graphs" : 0, "stats" : 0, "enableinsufficientfundslogging": 1, "telegrambotcontrol": 0, "websocket": 0, "disablelog": 0, "buymaxsize": 0, "buyminsize": 0, "sellsmartswitch": 0, "trailingbuypcnt": 0.5, "telegramtradesonly": 0, "granularity": "1hour", "enableml": 0, "use_sell_fee": 1 } }, "telegram": { "token": "", "user_id": "0000000000", "client_id": "", "datafolder": "", "logger_level": "DEBUG" }, "scanner" : { "atr72_pcnt" : 1.0, "exitaftersell" : 1, "enableleverage" : 0, "use_default_scanner" : 1, "maxbotcount" : 6, "exchange_bot_count": 3, "autoscandelay" : 0, "enable_buy_next": 1, "autostart": 0, "terminal_start_process": "" } }

…

On 24. 4. 2023, at 20:31, Michael Whittle ***@***.***> wrote: Guys, can you confirm if this is a Telegram issue or a general issue? I used the config at the top and I don't get an error message when I run the bot on that market for live or test modes. If the issue happens just as the bot starts, I don't get it. Config: { "binance": { "api_url": "https://api.binance.com", "config": { "autorestart": 1, "base_currency": "SHIB", "disablebuynearhigh": 1, "enableinsufficientfundslogging": 1, "enabletelegrambotcontrol": 1, "granularity": "15m", "live": 0, "nobuynearhighpcnt": 1, "nosellmaxpcnt": 3, "nosellminpcnt": -13, "quote_currency": "BRL", "selllowerpcnt": -21, "telegram": 1, "trailingbuypcnt": 1, "trailingstoploss": -1, "trailingstoplosstrigger": 3, "disablelog": 0, "use_sell_fee": 1, "buypercent": 99, "termwidth": 180, "termcolor": 1, "verbose": 0, "log": 1, "debug": 0 }, "api_key_file": "binance.key" }, "telegram": { "token": "<removed>", "client_id": "<removed>" } } Running bot like this: % python3 pycryptobot.py — Reply to this email directly, view it on GitHub <#793 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA66ISATSFDWZWRWDDYVWLDXC3BHLANCNFSM6AAAAAAXGAHDEY>. You are receiving this because you commented.

whittlem · 2023-04-24T18:47:09Z

I believe it's fixed. Doing a release now.

leohrs · 2023-04-24T18:48:01Z

With live 0 or open orders It Will run… Le lun. 24 avr. 2023 à 15:47, MirekF ***@***.***> a écrit :

My configuration: (with live:0 it’s OK) { "binance": { "api_url": "https://api.binance.com", "api_key_file": "binance.key", "config" : { "base_currency" : "BTC", "quote_currency" : "BUSD", "live" : 1, "sellatloss" : 0, "sellatresistance" : 0, "trailingstoploss" : -1.5, "trailingstoplosstrigger" : 5, "nosellmaxpcnt" : 3, "nosellminpcnt" : -3, "disablebullonly" : 0, "disablebuynearhigh" : 1, "disablebuymacd" : 0, "disablebuyobv" : 1, "disablebuyelderray" : 0, "disablefailsafefibonaccilow" : 1, "disableprofitbankreversal" : 0, "disabletracker" : 1, "disabletelegram" : 1, "autorestart" : 1, "graphs" : 0, "stats" : 0, "enableinsufficientfundslogging": 1, "telegrambotcontrol": 0, "websocket": 0, "disablelog": 0, "buymaxsize": 0, "buyminsize": 0, "sellsmartswitch": 0, "trailingbuypcnt": 0.5, "telegramtradesonly": 0, "granularity": "1hour", "enableml": 0, "use_sell_fee": 1 } }, "telegram": { "token": "", "user_id": "0000000000", "client_id": "", "datafolder": "", "logger_level": "DEBUG" }, "scanner" : { "atr72_pcnt" : 1.0, "exitaftersell" : 1, "enableleverage" : 0, "use_default_scanner" : 1, "maxbotcount" : 6, "exchange_bot_count": 3, "autoscandelay" : 0, "enable_buy_next": 1, "autostart": 0, "terminal_start_process": "" } } > On 24. 4. 2023, at 20:31, Michael Whittle ***@***.***> wrote: > > > Guys, can you confirm if this is a Telegram issue or a general issue? I used the config at the top and I don't get an error message when I run the bot on that market for live or test modes. If the issue happens just as the bot starts, I don't get it. > > Config: > > { > "binance": { > "api_url": "https://api.binance.com", > "config": { > "autorestart": 1, > "base_currency": "SHIB", > "disablebuynearhigh": 1, > "enableinsufficientfundslogging": 1, > "enabletelegrambotcontrol": 1, > "granularity": "15m", > "live": 0, > "nobuynearhighpcnt": 1, > "nosellmaxpcnt": 3, > "nosellminpcnt": -13, > "quote_currency": "BRL", > "selllowerpcnt": -21, > "telegram": 1, > "trailingbuypcnt": 1, > "trailingstoploss": -1, > "trailingstoplosstrigger": 3, > "disablelog": 0, > "use_sell_fee": 1, > "buypercent": 99, > "termwidth": 180, > "termcolor": 1, > "verbose": 0, > "log": 1, > "debug": 0 > }, > "api_key_file": "binance.key" > }, > "telegram": { > "token": "<removed>", > "client_id": "<removed>" > } > } > Running bot like this: > % python3 pycryptobot.py > > — > Reply to this email directly, view it on GitHub < #793 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA66ISATSFDWZWRWDDYVWLDXC3BHLANCNFSM6AAAAAAXGAHDEY >. > You are receiving this because you commented. > — Reply to this email directly, view it on GitHub <#793 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFUR2JN6NDML372QCI7BRTDXC3DCJANCNFSM6AAAAAAXGAHDEY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Leo Henry

whittlem · 2023-04-24T18:53:08Z

8.0.7 is available now. Docker image is building now. The issue should be fixed.

afgvdp · 2023-04-24T19:14:45Z

/addnew from telegram - WORKS
/scanner and open bot - WORKS

Thank you!

afgvdp · 2023-04-24T21:51:27Z

Found a issue with the new release 8.0.7

The Index 0 is fixed, but now the Telegram Bot don't recognize the active bots. I think that maybe could be the same problem as this one:

#727 (comment)

afgvdp · 2023-04-25T06:17:54Z

In 8.0.7 BOTs are not buying due to "Insufficient Funds":

Bot1 2023-04-25 02:15:00 POLYXUSDT 15m *** Skipping LIVE Buy Order -- Insufficient Funds ***

Manual Buy doesn't work either.

demkoma20 · 2023-04-26T16:28:10Z

I am still getting indexError when I stopped previous session and set LIMIT sell order.
On lower price levels I tried to start but got IndexError. When I unlock funds from LIMIT order bot works but start where ends. And that's what I don't want.

whittlem · 2023-04-26T20:06:07Z

In 8.0.7 BOTs are not buying due to "Insufficient Funds":

Bot1 2023-04-25 02:15:00 POLYXUSDT 15m *** Skipping LIVE Buy Order -- Insufficient Funds ***

Manual Buy doesn't work either.

This may sound like a thick question, but I have to ask. You definitely have sufficient funds? E.g., at least 10 of the quote currently (as a guide)

whittlem · 2023-04-26T20:08:51Z

This week is super busy for me but I'll take a look next week. If anyone can help narrow down the problem, that would help. For example, is it Binance only? Is it Docker or CLI or both? Is it happening with the Telegram bot only or both?, If you can provide more info to help me recreate what you are seeing that would help. If you can provide your config.json and the way you are running your bots that would help as well.

afgvdp · 2023-04-27T09:21:31Z

In 8.0.7 BOTs are not buying due to "Insufficient Funds":
Bot1 2023-04-25 02:15:00 POLYXUSDT 15m *** Skipping LIVE Buy Order -- Insufficient Funds ***
Manual Buy doesn't work either.

This may sound like a thick question, but I have to ask. You definitely have sufficient funds? E.g., at least 10 of the quote currently (as a guide)

Hi Michael, it was solved in the Chat. Another guy told me to ser "buymaxsize". I did it and problem solved!

demkoma20 · 2023-04-28T06:18:27Z

This week is super busy for me but I'll take a look next week. If anyone can help narrow down the problem, that would help. For example, is it Binance only? Is it Docker or CLI or both? Is it happening with the Telegram bot only or both?, If you can provide more info to help me recreate what you are seeing that would help. If you can provide your config.json and the way you are running your bots that would help as well.

I tried only on Binance. Without Telegram or Docker/Kubernetes, running in shell through python3 ./pycryptobot.py --logfile cryptobot-BTCUSDT.log --market BTCUSDT --granularity 3600
Issue is occured when:

1st bot run - success
Stop bot
Previously bought funds by bot are locked in LIMIT order
2nd bot run - fail
Unlock funds
Bot run - success and started where ends

whittlem · 2023-05-01T20:14:43Z

I'm getting same "*** Skipping LIVE Buy Order -- Insufficient Funds ***" message. There is definitely a bug. I'm troubleshooting it and just waiting for the next buy signal to see what happens.

whittlem · 2023-05-03T18:44:56Z

Fixed for me in 8.0.9. Give it a try and let me know.

whittlem closed this as completed Jun 11, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

IndexError('index 0 is out of bounds for axis 0 with size 0') #793

IndexError('index 0 is out of bounds for axis 0 with size 0') #793

leohrs commented Apr 20, 2023 •

edited

Loading

thiazzz commented Apr 21, 2023

MirekF commented Apr 21, 2023 via email

leohrs commented Apr 21, 2023

leohrs commented Apr 21, 2023

whittlem commented Apr 21, 2023

FenarkSEC commented Apr 22, 2023

thiazzz commented Apr 22, 2023

achillebnt commented Apr 22, 2023

afgvdp commented Apr 24, 2023

whittlem commented Apr 24, 2023

whittlem commented Apr 24, 2023

whittlem commented Apr 24, 2023

MirekF commented Apr 24, 2023 via email

whittlem commented Apr 24, 2023

leohrs commented Apr 24, 2023 via email

whittlem commented Apr 24, 2023

afgvdp commented Apr 24, 2023

afgvdp commented Apr 24, 2023 •

edited

Loading

afgvdp commented Apr 25, 2023 •

edited

Loading

demkoma20 commented Apr 26, 2023

whittlem commented Apr 26, 2023

whittlem commented Apr 26, 2023

afgvdp commented Apr 27, 2023

demkoma20 commented Apr 28, 2023

whittlem commented May 1, 2023

whittlem commented May 3, 2023

IndexError('index 0 is out of bounds for axis 0 with size 0') #793

IndexError('index 0 is out of bounds for axis 0 with size 0') #793

Comments

leohrs commented Apr 20, 2023 • edited Loading

thiazzz commented Apr 21, 2023

MirekF commented Apr 21, 2023 via email

leohrs commented Apr 21, 2023

leohrs commented Apr 21, 2023

whittlem commented Apr 21, 2023

FenarkSEC commented Apr 22, 2023

thiazzz commented Apr 22, 2023

achillebnt commented Apr 22, 2023

afgvdp commented Apr 24, 2023

whittlem commented Apr 24, 2023

whittlem commented Apr 24, 2023

whittlem commented Apr 24, 2023

MirekF commented Apr 24, 2023 via email

whittlem commented Apr 24, 2023

leohrs commented Apr 24, 2023 via email

whittlem commented Apr 24, 2023

afgvdp commented Apr 24, 2023

afgvdp commented Apr 24, 2023 • edited Loading

afgvdp commented Apr 25, 2023 • edited Loading

demkoma20 commented Apr 26, 2023

whittlem commented Apr 26, 2023

whittlem commented Apr 26, 2023

afgvdp commented Apr 27, 2023

demkoma20 commented Apr 28, 2023

whittlem commented May 1, 2023

whittlem commented May 3, 2023

leohrs commented Apr 20, 2023 •

edited

Loading

afgvdp commented Apr 24, 2023 •

edited

Loading

afgvdp commented Apr 25, 2023 •

edited

Loading