Skip to content
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

Open
TheBorgy opened this issue Jan 3, 2023 · 9 comments

Comments

@TheBorgy
Copy link

TheBorgy commented Jan 3, 2023

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

@giovanniquinones
Copy link
Contributor

Please update your numpy version.
If the error persists, please provide the full command and bam file you are using to reproduce the error.

@alaminzju
Copy link

After updating numpy version, I got another error "ImportError: cannot import name 'Reader' from 'parser'". This problem was solved by running conda install --channel "conda-forge" pyvcf.

@giovanniquinones
Copy link
Contributor

Thank you for sharing.
I realize it will help to share a docker/singularity image given the many dependencies-related issues.
Will work on that and share it soon enough.

@giovanniquinones
Copy link
Contributor

singularity container uploaded

@JiangyanYu
Copy link

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)

@giovanniquinones
Copy link
Contributor

Thanks for bringing this to my attention.
Please refer to this link: sylabs/singularity#515
It seems you need to login first before trying to pull the image.
Please let me know if that works for you.

@JiangyanYu
Copy link

JiangyanYu commented Apr 13, 2023

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
Generate an access token at https://cloud.sylabs.io/auth/tokens, and paste it here.
Token entered will be hidden for security.
Access Token:
INFO: Access Token Verified!

$ singularity remote list
Cloud Services Endpoints
NAME URI ACTIVE GLOBAL EXCLUSIVE INSECURE
SylabsCloud cloud.sylabs.io YES YES NO NO
Keyservers
URI GLOBAL INSECURE ORDER
https://keys.sylabs.io YES NO 1*
Active cloud services keyserver

$ singularity pull library://giovas/collection/s5
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)

@giovanniquinones
Copy link
Contributor

The repository was private. I apologize for the inconvenience. I made it public now.

@JiangyanYu
Copy link

Thanks! Now I am able to pull the image without remote login.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants