-
Notifications
You must be signed in to change notification settings - Fork 123
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
Problem(s) with multiple imports #59
Comments
…orts as a workaround for an issue described in capnproto/pycapnp#59 Fixes numenta#1991
Hmm, I'm having a lot of trouble reproducing (specifically I'm getting a |
Will do. Thanks! I tried to craft a simpler scenario, but wasn't able to reproduce. FWIW, if you look at the history of numenta/nupic-legacy#2007, the failing Travis builds were related to the same failure (the python interpreter crashed). The crashes stopped and it all started working when I switched to relative imports. Thanks for trying it out! |
Upgrading to 0.5.4 did the trick. Thanks! |
…orts as a workaround for an issue described in capnproto/pycapnp#59 Fixes numenta#1991
Firstly, I'm on a mac.
I have two schemas. One imports and uses the other. When I import both schemas in Python, I get an error related to "Duplicate IDs", and in some cases, it crashes the python interpreter.
Importing individually is fine:
Importing them together raises a
KjException
related to duplicate IDs:Then, if I change the import in
delta.capnp
to be relative, I get a segfault:For good measure, just to verify that I didn’t duplicate the ID:
It’s as if there’s a problem importing
AdaptiveScalarEncoderProto
a second time. Once implicitly in thedelta.capnp
schema and again explicitly in python.I ran into a problem because a test I'm working on that imports both schemas was crashing my Python interpreter. For example, when I run numenta/nupic-legacy@e8ca7b5:
With the crash reporter generating this message:
The text was updated successfully, but these errors were encountered: