-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Custom Resources from using ray start
in CLI do not work as intended
#36374
Comments
I will try to find a Windows environment and use PowerShell to reproduce the issue you encountered. |
Merged
8 tasks
@lavkeshg Today i reproduce the issue in windows env, you should use follow case:
|
That worked for me! Thank you so much |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running into an issue where the examples for custom resources do not work in Powershell as intended.
ray start --head --num-cpus=3 --num-gpus=4 --resources='{"special_hardware": 1, "custom_label": 1}'
Should be straightforward enough, however it yields the following response,
--resources
is not a valid JSON string.Valid values look like this:
--resources='{"CustomResource3": 1, "CustomResource2": 2}}'
I have also tried the example for "valid" values suggested in the error response,
ray start --head --resources='{"CustomResource3": 1, "CustomResource2": 2}}'
This yields the exact same error as well.
I have also tried wrapping the whole text further within quotes looking at some other issues, like so,
ray start --head --num-cpus=3 --num-gpus=4 --resources="'{ \"special_hardware\": 1, \"custom_label\": 1 }'"
this didn't help either
I have attached the
environment.yml
used here.environment.yml
name: ray_unpack channels: default dependencies: python=3.8 pip pip: - -r requirements.txt
requirements.txt
joblib==1.2.0 numpy==1.24.0 pandas==1.5.2 psycopg2==2.9.5 PyYAML==6.0 ray==2.5.0 SQLAlchemy==1.4.45
I am running this on PSVersion: 5.1.17763.3770
Thank you!
The text was updated successfully, but these errors were encountered: