![]() There is likely additional logging output above. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)ġ3 verbose stack at ChildProcess.emit (events.js:159:13)ġ3 verbose stack at maybeClose (internal/child_process.js:943:16)ġ3 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)ġ4 verbose pkgid verbose cwd /Users/fredfortier/Code/enigma/ccxtġ7 verbose argv "/usr/local/Cellar/node/9.2.1/bin/node" "/usr/local/bin/npm" "run" "build"Ģ2 error build: `npm run export-exchanges & npm run vss & npm run pandoc-python-readme & npm run pandoc-doc-readme & npm run pandoc-doc-manual & npm run pandoc-doc-install & npm run pandoc-doc-exchanges & npm run pandoc-doc-exchanges-by-country & npm run transpile & npm run update-badges & npm run browserify`Ģ3 error This is probably not a problem with npm. Displays quick information about the current price of Binance Coin in your browsers toolbar. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)ġ3 verbose stack at EventEmitter.emit (events.js:159:13)ġ3 verbose stack at ChildProcess. Note that most of those testing keys there are outdated/expired/deleted, because someone screws my nonce numbers all the time ) This is why I keep a secret local list of other keys for private testing.ġ verbose cli ġ1 silly lifecycle Returned: code: 1 signal: nullġ2 info lifecycle Failed to exec build scriptġ3 verbose stack Error: build: `npm run export-exchanges & npm run vss & npm run pandoc-python-readme & npm run pandoc-doc-readme & npm run pandoc-doc-manual & npm run pandoc-doc-install & npm run pandoc-doc-exchanges & npm run pandoc-doc-exchanges-by-country & npm run transpile & npm run update-badges & npm run browserify`ġ3 verbose stack at EventEmitter. Let me know if I can help with anything else. Yes, Travis also runs tests for us, but some exchanges were intentionally switched off there. We use Travis to verify the syntax and check for transpilation results/errors. The HMAC SHA256 signature is a keyed HMAC SHA256 operation. SIGNED endpoints require an additional parameter, signature, to be sent in the query string or request body. SIGNED (TRADE and USERDATA) Endpoint Security. I'm mostly testing locally (because of well-known accessibility issues with some exchanges). TRADE and USERDATA endpoints are SIGNED endpoints. You can copy keys.json to, and edit the local file to override the keys and settings for local testing. We had to add "skip": true to keys.json for Binance, to avoid testing it on Travis. The test.js loads config settings from or keys.json (the one it finds first, in that order). Please let me know if I'm missing anything. ![]() ![]() The run-tests suite is mostly for running many of them in multiple languages in parallel. Youll need to use the WSS API, receive message for each trade real-time and aggregate them by each second. usr/local/bin/node js/test/test binance # js-only, doesn't create unnecessary load on your system The lowest granularity that Binance REST API supports (for kline history) is 1 minute candles. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |