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

Minio + Ray Integrations #967

Merged
merged 34 commits into from
May 30, 2024
Merged

Minio + Ray Integrations #967

merged 34 commits into from
May 30, 2024

Conversation

acashmoney
Copy link
Contributor

@acashmoney acashmoney commented May 7, 2024

What type of PR is this?

Remove the categories that do not apply

  • 🎮 Feature

Description

Partial step towards full Ray migration

Copy link

vercel bot commented May 7, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
docs ⬜️ Ignored (Inspect) Visit Preview May 23, 2024 9:42am

@acashmoney acashmoney changed the title [DO NOT MERGE] WIP: Minio + Ray Integrations Minio + Ray Integrations May 30, 2024
@acashmoney acashmoney marked this pull request as ready for review May 30, 2024 05:48
Copy link
Collaborator

@supraja-968 supraja-968 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was able to test the end to end flow of this PR, before we moved to the unified docker compose. Approving this as the initial changes for the upcoming PR #970 that will be a continuation of the ray features implemented here

@acashmoney acashmoney merged commit 2957551 into main May 30, 2024
13 of 15 checks passed
@acashmoney acashmoney deleted the minio-integration branch May 30, 2024 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants