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

[Data] PythonObjectArray missing methods causing serialization failures + tests #49202

Merged
merged 2 commits into from
Dec 13, 2024

Conversation

xingyu-long
Copy link
Contributor

Why are these changes needed?

Discussed with @richardliaw and decide to open this PR based on #48737 with tests

Related issue number

N/A

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 :(

@jcotant1 jcotant1 added the data Ray Data-related issues label Dec 11, 2024
@alexeykudinkin alexeykudinkin added the go add ONLY when ready to merge, run all tests label Dec 13, 2024
@alexeykudinkin alexeykudinkin self-assigned this Dec 13, 2024
akavalar and others added 2 commits December 12, 2024 18:20
@xingyu-long
Copy link
Contributor Author

@alexeykudinkin thanks for approving it! could you also enable auto-merge? thanks a lot!

@richardliaw richardliaw enabled auto-merge (squash) December 13, 2024 02:42
@richardliaw richardliaw merged commit 3073fe7 into ray-project:master Dec 13, 2024
6 checks passed
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Dec 17, 2024
…es + tests (ray-project#49202)

## Why are these changes needed?

Discussed with @richardliaw and decide to open this PR based on
ray-project#48737 with tests

## Related issue number

N/A

## Checks

- [x] I've signed off every commit(by using the -s flag, i.e., `git
commit -s`) in this PR.
- [x] 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
   - [x] Unit tests
   - [ ] Release tests
   - [ ] This PR is not tested :(

---------

Signed-off-by: akavalar <[email protected]>
Signed-off-by: Xingyu Long <[email protected]>
Co-authored-by: akavalar <[email protected]>
Signed-off-by: ujjawal-khare <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Ray Data-related issues 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