MagicStack / MagicStack/vmbench
Could not start server
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 189
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
[19:12:45 fxsatlin01 vmbench] (master)$ ./run_benchmarks --benchmarks tcpecho-uvloop-protocol,tcpecho-uvloop-sockets
TCP echo server (uvloop)
========================
Starting server...
docker run --rm -t -p 25000:25000 -e UID=10710547 -e GID=22002 -v /localdisk/work/amalakho/vmbench/.cache:/var/lib/cache -v /localdisk/work/amalakho/vmbench/sockets:/tmp/sockets --name magicbench magic/benchmark vex bench python /usr/src/servers/asyncioecho.py --addr=0.0.0.0:25000 --proto --uvloop
Trying to connect to server at address 127.0.0.1:25000
Could not start server
----------------------
Traceback (most recent call last):
File "/usr/src/servers/asyncioecho.py", line 4, in <module>
import uvloop
File "/usr/local/python-venvs/bench/lib/python3.5/site-packages/uvloop/__init__.py", line 7, in <module>
from .loop import Loop as __BaseLoop, Future
File "uvloop/includes/stdlib.pxi", line 31, in init uvloop.loop (uvloop/loop.c:108082)
AttributeError: module 'asyncio.base_events' has no attribute '_check_resolved_address'
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the failing ./run_benchmarks command for the tcpecho-uvloop benchmarks and start with /usr/src/servers/asyncioecho.py, where the traceback occurs while importing uvloop. Compare the installed uvloop and Python asyncio versions around _check_resolved_address; done means the server starts and the benchmarks can connect successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100