Closed YuriyTigiev closed 5 years ago
I just had your exact same problem. This is the issue
> talib@1.1.2 install /home/ytigiev/gekko/node_modules/talib
This version 1.1.2
does NOT build. Because package.json is set to ^ it means take the minor change, so even though it lists 1.0.2 it will take 1.x.x - this breaks the build.
Just do npm install --production redis@0.10.0 talib@1.0.2 tulind@0.8.7 pg
and this will work. This is the same script running in the docker build, so I don't know why the versions are different for local builds.
Once you do that, the final step is to fix the package.json versions so they are all static.
Notice how I removed all the ^
symbols in front of the version number. That is essential.
"dependencies": {
"async": "2.1.2",
"bitfinex-api-node": "1.2.1",
"chalk": "2.4.2",
"co-fs": "1.2.0",
"commander": "2.13.0",
"gekko": "0.0.9",
"humanize-duration": "3.10.0",
"koa": "1.2.0",
"koa-bodyparser": "2.2.0",
"koa-cors": "0.0.16",
"koa-logger": "1.3.0",
"koa-router": "5.4.0",
"koa-static": "2.0.0",
"lodash": "2.x",
"moment": "2.20.1",
"opn": "4.0.2",
"pg": "7.11.0",
"promisify-node": "0.5.0",
"prompt-lite": "0.1.1",
"redis": "0.10.0",
"relieve": "2.1.3",
"retry": "0.10.1",
"semver": "5.4.1",
"sqlite3": "4.0.4",
"stats-lite": "2.0.4",
"talib": "1.0.2",
"tiny-promisify": "0.1.1",
"toml": "2.3.0",
"tulind": "0.8.7",
"ws": "6.0.0"
},
Now you can wipe out node_modules, and run npm install --only=production
and let everything reinstall. This should work now.
I think it happened because I used a nodejs 12.0 with ubuntu 19.04
When Gekko and plugins will support the latest versions of modules?
Use nodejs v8.16.0 - it works stable and well. What do you need node v12 for?
I prefer to use the latest stable version of any software. Because they have fixed more bags.
OK good luck then . Since you are not willing to try a solution given to you, you'll have to solve the problem yourself.
FYI the newest version of node usually is incompatible with many software packages because they introduce breaking changes.
I never use latest nodejs and life as a developer is much easier because more things work with a slightly outdated version of node
I'm using a nodejs for a few months for developing a web site. I'm always using the latest version of nodejs and modules. I never had a problem with incompatible of modules, but maybe because my project is small.
Try NVM, node version manager. It allows you to quickly and easily switch versions of node and npm.
I have started to use dockers. This solution helps to fix a lot of problems. But when I build container I get a lot of warnings about modules versions. I'm not sure that application works properly in all cases
Get Outlook for Androidhttps://aka.ms/ghei36
From: IAMtheIAM Sent: Sunday, July 7, 23:06 Subject: Re: [askmike/gekko] Issues with install talib (#2802) To: askmike/gekko Cc: YuriyTigiev, Author
Try NVM, node version manager. It allows you to quickly and easily switch versions of node and npm. https://github.com/nvm-sh/nvmhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnvm-sh%2Fnvm&data=02%7C01%7C%7Cc0371271cc53450eb39108d7030e3420%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636981231841546018&sdata=742trCGDBoZpL1CUCXOcL45gXH1uI5sep%2B6pgX9Vlgg%3D&reserved=0 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faskmike%2Fgekko%2Fissues%2F2802%3Femail_source%3Dnotifications%26email_token%3DAFNSYQQBT35PS372OYD4ATLP6I5C5A5CNFSM4H2ZWK22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZLRHMY%23issuecomment-509023155&data=02%7C01%7C%7Cc0371271cc53450eb39108d7030e3420%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636981231841566029&sdata=ZX1Y8lzIeRPuDuWxBaBP5DUmIHVZ%2Bc91u2OmJ5Ttj8c%3D&reserved=0, or mute the threadhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFNSYQT4DEM46FILEHUXW4DP6I5C5ANCNFSM4H2ZWK2Q&data=02%7C01%7C%7Cc0371271cc53450eb39108d7030e3420%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636981231841586051&sdata=xc9RkynYu5d4iLTwKtjFpgJ9zZljmfWthGGLmZ1NS5c%3D&reserved=0.
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. If you feel this is very a important issue please reach out the maintainer of this project directly via e-mail: gekko at mvr dot me.
Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a ... [x] bug report [ ] question about the decisions made in the repository
Action taken (what you did) npm install talib --no-save
Expected result (what you hoped would happen) Install talib
Actual result (unexpected outcome)
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)