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

[Bug] ImportError: Not all Ray Dashboard dependencies were found. #19956

Closed
1 of 2 tasks
alvin-yang68 opened this issue Nov 1, 2021 · 7 comments
Closed
1 of 2 tasks
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@alvin-yang68
Copy link

Search before asking

  • I searched the issues and found no similar issues.

Ray Component

Dashboard

What happened + What you expected to happen

ray.init(include_dashboard=True) throws ImportError: Not all Ray Dashboard dependencies were found. To use the dashboard please install Ray using pip install ray[default].

This issue was encountered on both Windows 10 and Ubuntu 20.04. Running pip install ray[default] did not fix the issue.

Versions / Dependencies

Ray 1.7.0
Python 3.8.10
Windows 10

Reproduction script

import ray
ray.init(include_dashboard=True)

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@alvin-yang68 alvin-yang68 added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Nov 1, 2021
@nocluebutalotofit
Copy link

Same problem with
Ray 1.7.0
aiohttp 3.8.0
Python 3.9.5
macOS Big Sur

import aiohttp.signals
from aiohttp.frozenlist import FrozenList  # noqa: F401

fail with aiohttp 3.8.0 which is permitted by ray/python/requirements.txt which says aiohttp>=3.7

nocluebutalotofit added a commit to nocluebutalotofit/lppls that referenced this issue Nov 2, 2021
@ralbertazzi
Copy link

Getting the same problem due to aiohttp 3.8.0 that released breaking changes :(

@nocluebutalotofit
Copy link

Getting the same problem due to aiohttp 3.8.0 that released breaking changes :(

Yes, that is why simple downgrading ray does not help.

@dennymarcels
Copy link

dennymarcels commented Nov 3, 2021

Same.
Ray 1.8 and 1.7
Python 3.9
Debian 11

I confirm that downgrading aiohttp to 3.7 solves it temporarily.

@nocluebutalotofit
Copy link

nocluebutalotofit commented Nov 4, 2021

Same. Ray 1.8 and 1.7 Python 3.9 Debian 11

I confirm that downgrading aiohttp to 3.7 solves it temporarily.

This should be reflected in ray/python/requirements.txt:
Instead of "aiohttp>=3.7" something like "aiohttp==3.7".

@KananVyas
Copy link

Same. Ray 1.8 and 1.7 Python 3.9 Debian 11
I confirm that downgrading aiohttp to 3.7 solves it temporarily.

This should be reflected in ray/python/requirements.txt: Instead of "aiohttp>=3.7" something like "aiohttp==3.7".

This works! Even inside docker as well

@jamesmishra
Copy link
Contributor

I think this issue was fixed when PR #20261 landed on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

6 participants