Must provide nupic core release directory. --nupic-core-dir #619
Comments
@oxtopus @scottpurdy Here is an updated bug report of the problem I mentioned in standup this morning. I think this is a P1 bug because I have multiple reports of this problem halting OS X binary installations. |
nupic now depends on a more recent version of nupic.bindings (0.2.1 from https://github.com/numenta/nupic/blob/master/external/common/requirements.txt#L22). We'll need to validate that this is still a problem in recent nupic and nupic.core (I suspect not). |
@oxtopus Releasing 0.3.3 now... |
@oxtopus That leads me to believe that 0.3.3 will not fix this issue 😭 I'll try it anyway. |
Probably not. |
@oxtopus @scottpurdy @subutai @jcasner I think we need to make this issue our top priority. I've confirmed that Linux binary installations are not working, and I have strong reason to believe that OS X has the same problem. |
👍 though, installing nupic.bindings separately should fix the problem. |
Yes it will, but I want a friction-less binary installation. |
Meanwhile, |
I think we should update the README to state that Linux users can A) use easy_install, B) manually install nupic.bindings from S3 Linux wheel, or C) install nupic.bindings from source/repo. I think it will be better to work towards a source build than bring back all of the logic for downloading and including the binary linux egg for nupic.bindings in the setup.py of nupic. @rhyolight and @oxtopus - thoughts? |
👍 for install-from-source. Let's commit to moving away from setup.py hackery. |
This is what the README says to do now, and it is broken. |
Just a note... I have an Ubuntu laptop I've been running NuPIC on, but I haven't updated it in a few months. This morning I pulled in all the latest nupic changes and ran:
And it worked fine. However, yesterday when I started from scratch on Ubuntu 12, I ran directly into the exact reported issue. I don't know what would be different between a fresh Ubuntu and an older one. |
The same results with Matt in my Ubuntu 14.04 VM [1], and a Debian 8.2 VM [2], (default build-essential installs 4.9 with worked!). Tried Debian to see if it recreated Ryan's problem, but this morning 0.2.1 and nupic installed fine (after making sure known pip packages are installed first, such as upgrading default numpy, being super user for numpy install, etc.). uname -a |
So I just ran though the exact same installation procedure as yesterday on Ubuntu again (fresh VM), and I did NOT run into this problem this time. I guess our release of 0.3.3 yesterday actually fixed this problem?! |
Something happened in one of these change sets that fixed the problem for me: |
I think I know what happened here. Yesterday, after the 0.3.3 release, I noticed that the README instructions pointed to |
But I can't install it...the same error with nupic.bindings persists. |
@felippemr Are you getting the error you originally reported in numenta/nupic-legacy#2570?
Or are you getting the error reported above in this issue?
Either way, the console output from the latest 0.3.3 release would be helpful. Can you run the following commands (again, I know!) and give us the console output you get on OS X?
If I can see the output of |
@felippemr Also, what version of pip are you using? ( And thank you for persisting with us on this issue. I really want to make sure that there are no current installation problems. I'll be getting a new OS X machine today so I can make an installation video. I'll run into the same problems you are running into (hopefully, if the issue persists). |
I am getting this error:
When I do this
The output to
And finally my pip version is:
|
@felippemr Before a reply from Matt, could you also run |
Reopened as a P2, because I don't think this affects all users. This may be a pip issue. I will own this and work with @felippemr to get it resolved ASAP. @felippemr are you comfortable upgrading pip? A newer version might solve this problem. Try: |
|
I was able to install nupic.bindings but received a diffenrent error when trying to install nupic....but I think that the problem with nupic.bindings was my pip version.... Thank you guys! |
Ok Great! The error you are getting is because you probably need to install XCode command line tools, which will give you a C compiler that is necessary for Capnproto installation. Then try starting from scratch again:
How does that work? |
|
Thank you guys! |
😌 whew |
Hi Matt, I've just seen that you closed this ticket but I am having the same problems as explained here. (OSX 10.10.5). I had the same problem: So this is the output if it is of help...
and
Any idea on what to test next? Maybe it can be some incompatibiliy with the anaconda environment? |
Wow, it never ends!! 😝 I'm reopening and starting from scratch on OS X now to try to replicate this. |
@garikoitz This is probably because you are running Anaconda python. There are many opportunities to confuse OS X when you have multiple versions of python installed on the system. I just ran through a complete install of NuPIC on a new OS X Yosemite with the system version of Python with no problems. However, I did notice this in your logs:
Did you try that? |
Thanks Matt!
Should I create another independent Python environment for nupic to work in? I am relying in anaconda por work related projects so I cannot remove it. |
@garikoitz If I'll be creating more tutorial videos over the next couple of days to show people how to build and install from scratch on OS X and Ubuntu. |
@garikoitz I notice a ' ' (space character) in the whl install (between |
Hi Matt, I cloned the code and compiled it, and this is the end of the output:
Is it possible to install nupic.bindings in some other way? |
@rcrowder I think it was a formatting problem I had when I sent the code. In any case I did it again right now and this is the result:
thanks for your help! |
@garikoitz Saw that space first in an email update, and thought it might have been something like that. Cheers. |
@rhyolight sorry, didn't read the whole thread. Just an update: I didn't reproduce the |
Hi again, I've tried everything but nupic.bindings installation is not working for me. |
The instructions in the nupic.core README are current. I'm working on a document for developer setup at https://github.com/numenta/nupic/wiki/Numenta-Developer-Setup. It's specific to Numenta employees, and makes assumptions about your environment that may not be true, but it may be helpful. You should also be able to use the example in https://github.com/oxtopus/nupic-build-matrix/blob/master/ubuntu/14.04/clang/Dockerfile#L38-L58 |
I think that numenta/nupic-legacy#2603 captures this issue better, so I am closing this. |
@garikoitz This video might help you install from source code: https://www.youtube.com/watch?v=sxb_Zrls7Zs |
Thanks! gari@GariMBP* nupic $* ./scripts/run_nupic_tests -u ============================================================================= platform darwin -- Python 2.7.10 -- py-1.4.30 -- pytest-2.7.2 -- rootdir: /Users/gari/soft/nupic, inifile: plugins: cov, xdist collecting 6 items__gari@GariMBP* nupic $* gari@GariMBP* nupic $* gari@GariMBP* nupic $* gari@GariMBP* nupic $* gari@GariMBP* nupic $* pip install pytest Requirement already satisfied (use --upgrade to upgrade): pytest in Requirement already satisfied (use --upgrade to upgrade): py>=1.4.29 in gari@GariMBP* nupic $* pip install --upgrade pytest Collecting pytest Using cached pytest-2.8.0-py2.py3-none-any.whl Requirement already up-to-date: py>=1.4.29 in Installing collected packages: pytest Found existing installation: pytest 2.7.2
Successfully installed pytest-2.8.0 gari@GariMBP* nupic $* ./scripts/run_nupic_tests -u INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File INTERNALERROR> config._do_configure() INTERNALERROR> File INTERNALERROR> INTERNALERROR> File INTERNALERROR> self._hookexec(self, self._nonwrappers + self._wrappers, INTERNALERROR> File INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) INTERNALERROR> File INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute() INTERNALERROR> File INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> File INTERNALERROR> multicall.execute() INTERNALERROR> File INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> File INTERNALERROR> config.pluginmanager.register(reporter, INTERNALERROR> File INTERNALERROR> ret = super(PytestPluginManager, self).register(plugin, INTERNALERROR> File INTERNALERROR> hook._maybe_apply_history(hookimpl) INTERNALERROR> File INTERNALERROR> res = self._hookexec(self, [method], kwargs) INTERNALERROR> File INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) INTERNALERROR> File INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute() INTERNALERROR> File INTERNALERROR> args = [all_kwargs[argname] for argname in INTERNALERROR> KeyError: 'nodeid' gari@GariMBP* nupic $* *I've tried with two different versions of pytest, but I got two different pytest-dev/pytest#1034 2.- But then, if the problem was only the testing, I would expect hotgym gari@GariMBP* simple $* ./hotgym.py Fatal Python error: PyThreadState_Get: no current thread Abort trap: 6 What do you recommend? I am thinking in creating a separate python thanks! *Gari * On Thu, Sep 24, 2015 at 2:13 PM Matthew Taylor notifications@github.com
|
@garikoitz I had problems with |
thanks! I didn't know that, will test it and let you know. On Fri, Sep 25, 2015 at 8:32 AM Matthew Taylor notifications@github.com
|
Originally reported as numenta/nupic-legacy#2570 and numenta/nupic-legacy#2543 but now failing with a different error that seems to be internal to
nupic.core
.Just to clarify, the command
pip install https://s3-us-west-2.amazonaws.com/artifacts.numenta.org/numenta/nupic.core/releases/nupic.bindings/nupic.bindings-0.2-cp27-none-linux_x86_64.whl
seems to work fine, but the subsequentpip install nupic
then throws the following error.CC @breznak @felippemr
The text was updated successfully, but these errors were encountered: