![]() 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. (/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. I'm mostly testing locally (because of well-known accessibility issues with some exchanges). 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). Further details about this change are shown on the timeline below: At 0 00:00 AM (UTC), Binance will suspend XZC staking purchases. Displays quick information about the current price of Binance Coin in your browsers toolbar. Please let me know if I'm missing anything. Following the announcement from the Firo team, Binance will update the ticker of XZC to FIRO. Binance has updated the /api/v3/exchangeInfo endpoint recently to take a list of symbols in this format 'DOGEUSDT','ETHBTC', so maybe they will add that to other endpoints. The run-tests suite is mostly for running many of them in multiple languages in parallel. usr/local/bin/node js/test/test binance # js-only, doesn't create unnecessary load on your system ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |