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

[Core] Fix bug to support S3 pre-signed url for .whl file #48560

Merged
merged 7 commits into from
Dec 16, 2024

Conversation

yantzu
Copy link
Contributor

@yantzu yantzu commented Nov 5, 2024

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

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: Jeffrey(Xilang) Yan <[email protected]>
@yantzu yantzu changed the title [Core] Support S3 pre-signed url for .whl file [Core] To support S3 pre-signed url for .whl file Nov 5, 2024
@yantzu yantzu changed the title [Core] To support S3 pre-signed url for .whl file [Core] Fix bug to support S3 pre-signed url for .whl file Nov 5, 2024
@jcotant1 jcotant1 added the core Issues that should be addressed in Ray Core label Nov 18, 2024
@yantzu
Copy link
Contributor Author

yantzu commented Dec 11, 2024

@rynewang @dentiny could you help to review this pr

Copy link
Contributor

@dentiny dentiny left a 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

@dentiny dentiny requested a review from jjyao December 12, 2024 11:41
@dentiny
Copy link
Contributor

dentiny commented Dec 12, 2024

@jjyao for approval and merge.

@jjyao jjyao added the go add ONLY when ready to merge, run all tests label Dec 12, 2024
@jjyao jjyao enabled auto-merge (squash) December 12, 2024 17:33
@github-actions github-actions bot disabled auto-merge December 13, 2024 02:13
@yantzu
Copy link
Contributor Author

yantzu commented Dec 13, 2024

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

@yantzu
Copy link
Contributor Author

yantzu commented Dec 16, 2024

@jjyao jjyao merged commit 6cbbf56 into ray-project:master Dec 16, 2024
4 of 5 checks passed
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Issues that should be addressed in Ray Core go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants