-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[Core] Fix bug to support S3 pre-signed url for .whl file #48560
Conversation
Signed-off-by: Jeffrey(Xilang) Yan <[email protected]>
Signed-off-by: Jeffrey(Xilang) Yan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apology for the delay. Thanks for the fix! LGTM
@jjyao for approval and merge. |
Hi @jjyao ,the original build test failed, so I updated code to trigger another build, unluckily it still failed, but the failure should not related to this code changes, could you please take a look? orignal test link https://buildkite.com/ray-project/premerge/builds/31991 |
Hi, @jjyao the tests failed on different part each time,see |
…t#48560) Signed-off-by: Jeffrey(Xilang) Yan <[email protected]> Signed-off-by: ujjawal-khare <[email protected]>
Why are these changes needed?
We meet error if we use a pre-signed S3 .whl file url as runtime env py-modules.
It turns out that it is a bug of Ray, current Ray doesn't support any .whl file url that has params, query or fragment part. Because ray will change the file name to a non-standard one then pip install will fail.
This PR is to fix the issue.
Related issue number
None
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.