-
Notifications
You must be signed in to change notification settings - Fork 1
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
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObjec #8
Comments
Please update your numpy version. |
After updating numpy version, I got another error "ImportError: cannot import name 'Reader' from 'parser'". This problem was solved by running |
Thank you for sharing. |
singularity container uploaded |
Thanks for sharing the singularity image. Unfortunately when I pull the image, I received the 401 unauthorized error. Details of the errors are below: FATAL: While pulling library image: error fetching image: request did not succeed: UNAUTHORIZED: unauthorized to access repository: giovas/collection/s5, action: pull: unauthorized to access repository: giovas/collection/s5, action: pull (401 Unauthorized) |
Thanks for bringing this to my attention. |
Thanks for the quick response! I have tried remote login with token generated from cloud.sylabs.io, unfortunately the error persists (see below). By the way I looked for the image in cloud.sylabs.io libraries but could not find any items. Is it not pushed or is it private? Thanks! $ singularity remote login --username jiangyanyu $ singularity remote list $ singularity pull library://giovas/collection/s5 |
The repository was private. I apologize for the inconvenience. I made it public now. |
Thanks! Now I am able to pull the image without remote login. |
I pip installed the program as suggested. Attempting to run test data in this repository generated the following error
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObjec
The text was updated successfully, but these errors were encountered: