Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ModuleNotFoundError: No module named 'numpy'

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
numpy, python
Domain
performance

Research direction

Start by running ./run_benchmarks and inspect the import and dependency setup used by ./echo_client, which fails while importing numpy. Check how this repository documents or installs Python dependencies, then verify that the benchmark command runs past the warmup without ModuleNotFoundError.

Written by the indexing model from the issue text.

Description

./run_benchmarks leads to -


Warming up server...
./echo_client --output-format=json --addr=127.0.0.1:25000 --msize=1024 --duration=10 --concurrency=10
Traceback (most recent call last):
  File "./echo_client", line 14, in <module>
    import numpy as np
ModuleNotFoundError: No module named 'numpy'
Traceback (most recent call last):
  File "./run_benchmarks", line 587, in <module>
    main()
  File "./run_benchmarks", line 517, in main
    subprocess.check_output(warmup_cmd)
  File "/usr/lib/python3.8/subprocess.py", line 415, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['./echo_client', '--output-format=json', '--addr=127.0.0.1:25000', '--msize=1024', '--duration=10', '--concurrency=10']' returned non-zero exit status 1.```

Note - The installation progressed without any issues.
Dominant language
Python
Stars
189
Forks
48
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MagicStack/vmbench

All issues in MagicStack/vmbench

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.