-
Notifications
You must be signed in to change notification settings - Fork 738
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development installation: Requirements? #512
Comments
Hi @DerWeh -- Thanks for letting us know about this. I'll add the information to install npm in the documentation once we resolve the rest of the issues you're observing. node v8.10.0 and npm v3.5.2 are pretty old (2018/2015). Can you try updating them with: sudo apt update |
Indeed, the Ubuntu on my machine is quite old (and I have some constrains not allowing me to upgrade). Tried it on a different machine with a newer Ubuntu. $ nodejs --version
v12.22.9
$ npm --version
8.5.1 With the newer version, the command runs with the following output: $ make install
cd /home/wehandre/workspace/code/interpret/shared/vis && npm install
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Redundant dependency in your project.
npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
added 1127 packages, and audited 1128 packages in 2m
150 packages are looking for funding
run `npm fund` for details
4 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
cd /home/wehandre/workspace/code/interpret/shared/vis && npm run build-prod
> @interpretml/[email protected] build-prod
> webpack --mode production
events.js:291
throw er; // Unhandled 'error' event
^
Error [ERR_WORKER_OUT_OF_MEMORY]: Worker terminated due to reaching memory limit: JS heap out of memory
at Worker.[kOnExit] (internal/worker.js:238:26)
at Worker.<computed>.onexit (internal/worker.js:168:20)
Emitted 'error' event on Worker instance at:
at Worker.[kOnExit] (internal/worker.js:238:12)
at Worker.<computed>.onexit (internal/worker.js:168:20) {
code: 'ERR_WORKER_OUT_OF_MEMORY'
}
make: *** [Makefile:86: build-javascript] Error 1 I'm not really interested in developing dashboards and visualizations, so it seems it's fine to just use $ chmod u+x build.sh
$ ./build.sh followed by installing the Python module. The relevant test are passing, so this is good enough for me (but it might be useful to document it for other developers). |
I tried to install
interpret
as I want to contribute. However, following the instructions in https://interpret.ml/docs/installation-guide.html causes errors. It's probably some fault from my side, as I have no knowledge of JavaScript.Executing the documented steps yields the error:
So I installed
npm
Now I get the following error:
Am I doing something wrong, or do I need additional dependencies? In general, it would be good to list the minimal requirements necessary to build
interpret
(orinterpret-core
).Another question would be concerning the Python version. The REAMDE suggests that Python 3.7 is still supported, the setup.py suggests that Python 3.8 is required, and the docs recommend Python 3.10.
I think it is most appropriate to use the oldest supported Python version for development to make sure all used features are available; but to me, it is not clear which is the minimum version required. I couldn't find any hard constrain, only documentation.
The text was updated successfully, but these errors were encountered: