question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Node.js: Not all sent parameters were read; read '11' parameter(s) but was sent '13'

See original GitHub issue

Hi, Thanks for this amazing lib!

I got this error and don’t know what to do, is there something obvious that I missed? Thank you in advance!

Kind Regards

  • OS: Windows 10
  • Programming Language version: Node.js v14.15.3
  • CCXT version: 1.56.29
await this.client.createOrder('BTCUSDT', 'limit', 'buy', amount, limit, { 'stop': 'loss', 'stop_price': stop })
BadRequest: binance {"code":-1104,"msg":"Not all sent parameters were read; read '11' parameter(s) but was sent '13'."}
    at binance.throwExactlyMatchedException ( location... \node_modules\ccxt\js\base\Exchange.js:595:19)
    at binance.handleErrors ( location... \node_modules\ccxt\js\binance.js:4384:18)
    at  location... \node_modules\ccxt\js\base\Exchange.js:657:18
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async timeout ( location... \node_modules\ccxt\js\base\functions\time.js:195:24)
    at async binance.request ( location... \node_modules\ccxt\js\binance.js:4411:26)
    at async binance.createOrder ( location... \node_modules\ccxt\js\binance.js:2310:26)
    at async binanceClient.buyTrade ( location...\lib\binanceClient.js:284:13) {
  constructor: [class BadRequest extends ExchangeError]
}

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:12 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
kroitorcommented, Sep 14, 2021

@GianniKoch the “Stop price would trigger immediately” error is covered here:

In short, it means that your order side / price / stop price arguments would cause this stop-loss order to be triggered immediately upon placing it, therefore it does not make much sense to place such a stop limit order in the first place. That error is reported to you by the exchange API directly in reply to your specific request. You should be able to see which exact params are being generated and sent and what exactly is wrong in verbose mode.

1reaction
GianniKochcommented, Sep 13, 2021

Oh, my bad, I see it now. Well if it works now, thanks for your time and effort! I appreciate it ❤️

Read more comments on GitHub >

github_iconTop Results From Across the Web

Errors | Node.js v19.3.0 Documentation
AssertionError s are a special class of error that can be triggered when Node.js detects an exceptional logic violation that should never occur....
Read more >
Not all sent parameters were read; read '2' parameter(s) but ...
The reason is client sending parameters that's not required/permitted. e.g. curl -H "Context-Type: application/json" ...
Read more >
Sending command line arguments to npm script - Stack Overflow
However, I would like to be able to run something like npm start 8080 and have the argument(s) passed to script.js (e.g. npm...
Read more >
Rest parameters - JavaScript - MDN Web Docs
The rest parameter syntax allows a function to accept an indefinite number of arguments as an array, providing a way to represent variadic ......
Read more >
Configure Node.js apps - Azure App Service - Microsoft Learn
Configure a Node.js app for Azure App Service. Article; 10/18/2022; 11 minutes to read; 13 contributors. Feedback. Choose a hosting platform.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found