"Segmentation fault (core dumped)" after installing the required sparse library in a Qiskit env (conda virtual env)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 668
- Forks
- 141
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 4
Description
Hi,
We encountered a serious issue when running jupyter notebook code with the support of sparse library.
Can someone help?
Thanks!
Describe the bug
In a Qiskit 0.30 conda virtual env, after installing the required sparse library using pip, the ipython run will error out with
"Segmentation fault (core dumped)" message.
issue_with_sparse.log
To Reproduce
- Activate conda virtual env and run the "01_neural_networks.ipynb" sample code with below commands:
conda activate qiskit0.30_test
ipython -c "%run 01_neural_networks.ipynb"
This will prompt you to install the sparse library.
- Install sparse library by executing "pip install 'qiskit-machine-learning[sparse]'" inside the conda virtual env
- Rerun the "01_neural_networks.ipynb" sample code will produce the "Segmenttation fault" error.
Expected behavior
expect no prompt for install sparse library and no errors popped up for the ipython run
System
- OS and version: RHEL 8.4 (s390x)
- Conda: 4.10.1
- Sparse: version: 0.13.0
- NumPy version: 1.20.3
- Numba version: 0.54.1
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue_with_sparse.log and reproduce the failure using 01_neural_networks.ipynb and the listed ipython command in the qiskit0.30_test environment. Compare the RHEL 8.4 s390x versions of Sparse, NumPy, and Numba, and document a confirmed cause or compatibility fix when the notebook runs without prompting or segfaulting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, numpy, python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100