Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

if (!match) throw new Error('invalid bucket size spec: ' + spec); #2737

Open
leopardcoder opened this issue Jul 9, 2021 · 1 comment
Open
Labels

Comments

@leopardcoder
Copy link

leopardcoder commented Jul 9, 2021

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04
  • Zenbot version (commit ref, or version): 4.1.0
  • Zenbot branch: Installed zenbot maybe 3 months ago.
  • NodeJS version: v10.19.0
  • Python version (when using a python script): Python 3.8.10 (i use python just to generate sim commands and run them as subprocess in a script)
  • Did I make any changes to conf-sample.js?: no.

I write a commmand in linux. I get this error quite often:
./zenbot.sh sim binance.ANKR-BNB --strategy ti_hma --filename /home/linas/zenbot/simulations/ANKR-BNB/ti_hma_binance_ANKR-BNB_20210501_20200531.html --start 20210501 --end 20210530 --buy_pct 1 --sell_pct 1 --
silent

I get this error:
/home/linas/zenbot/node_modules/timebucket/lib/bucket-size.js:15
if (!match) throw new Error('invalid bucket size spec: ' + spec);
^
Error: invalid bucket size spec: undefined
at BucketSize.parse (/home/linas/zenbot/node_modules/timebucket/lib/bucket-size.js:15:21)
at new BucketSize (/home/linas/zenbot/node_modules/timebucket/lib/bucket-size.js:5:21)
at Bucket.resize (/home/linas/zenbot/node_modules/timebucket/lib/bucket.js:30:14)
at Command. (/home/linas/zenbot/commands/sim.js:106:49)
at Command.listener [as _actionHandler] (/home/linas/zenbot/node_modules/commander/index.js:413:31)
at Command._parseCommand (/home/linas/zenbot/node_modules/commander/index.js:914:14)
at Command._dispatchSubcommand (/home/linas/zenbot/node_modules/commander/index.js:865:18)
at Command._parseCommand (/home/linas/zenbot/node_modules/commander/index.js:882:12)
at Command.parse (/home/linas/zenbot/node_modules/commander/index.js:717:10)
at /home/linas/zenbot/zenbot.js:46:13

@stale
Copy link

stale bot commented Jan 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant